Text that knows which lane it's in.
One-time passwords and promotions have nothing in common operationally. Here they never share a lane.
What it's for.
The message that reaches almost any phone: codes, alerts, reminders, statements, recovery, and the last rung of every fallback chain.
Separate lanes.
OTP, transactional, marketing and informational traffic each carry their own channel order, escalation and dispatch rate. Route codes through a premium local account and promotions through a cheaper one, on your own provider contracts, mapped by traffic class and by destination. A marketing burst cannot consume the throughput a login depends on. A dedicated secured route class exists for sensitive traffic.
Send what your systems already say.
If your core system emits finished text, point it at xNotify as it is. The platform recognises each message against your templates, categorises it for pricing and compliance, and groups similar messages so you can see how many of each kind went out. Nothing gets rewritten on your side.
Write within the limits.
Character and segment limits are enforced as you type, with a live preview and AI-assisted copy that is checked before it can send.
Replies that steer the journey.
Inbound SMS is captured and a journey can wait on it: YES, STOP, 1, each mapped to its own path with its own window, and a fallback for silence. A structured reply becomes named data the journey can act on.
What comes back.
Delivery status and inbound replies, as events. Every message keeps its route, each attempt and the carrier's final word.
An SMS gateway with one lane, one rate and a report that ends at "sent".