Text that knows which lane it's in.
One-time passwords and promotions have nothing in common operationally. Here they do not 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 does not compete for the throughput a login depends on, on the platform side. 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.
What to check for your markets.
SMS behaves differently in every market. These are the questions we answer during scoping, for your destinations.
- Markets and routes
- Delivery runs on eOcean's carrier and aggregator connections, strongest in Pakistan, the Middle East and South Asia, or on your own provider contracts mapped by traffic class and destination. Coverage and quality per destination are confirmed for your list, not assumed.
- Sender types
- Sender IDs and short codes are registered per market with the carrier or regulator, with their own lead times and content rules. Which types your destinations allow is confirmed during scoping.
- Inbound
- Replies are captured and can steer a journey where the route supports two-way messaging; not every sender type or market supports inbound.
- Encoding and segments
- A single-part SMS carries up to 160 GSM-7 units or 70 UCS-2 (Unicode) units. Longer messages are split and each part carries less, typically 153 or 67, because each part carries concatenation headers. Some characters count as two GSM-7 units, and one non-GSM character switches the whole message to UCS-2. Parts are billed individually, and the exact count depends on the encoded content and the route.
- Prerequisites
- Registered senders, templates where the market requires them, opt-in records per contact, and a routing order per traffic class.
An SMS gateway with one lane, one rate and a report that ends at "sent".