SMS termination

SMS termination, without the grey areas.

A2P and P2P termination over SMPP for aggregators, carriers and communication platforms. Route type, delivery-receipt handling and sender requirements are confirmed during interconnection.

Request SMS rates

Connection

Protocol: SMPP, parameters agreed
Throughput: Agreed per bind, in messages per second
Traffic: A2P · P2P
Receipts: Handling confirmed for the route
Sender IDs: Requirements checked before interconnection

Route types

Direct is direct. Grey is named grey.

Route classification matters. Confirm the downstream path, sender handling and delivery conditions for the destination before agreeing a service.

	Direct route	Grey route
Terminating operator	Paid for A2P as A2P	Bypassed
Sender ID	Subject to registration and network requirements	May be rewritten or stripped
Delivery over time	Subject to downstream network conditions	May be disrupted by filtering
Delivery receipts	Reflect the network's answer	Frequently unreliable
How we sell it	As direct	Only as grey, only where it is the sole path, only if you choose

Sender ID and local rules

Requirements depend on the market, message and route.

These examples describe specific regulatory requirements. Confirm how they apply to your traffic, who completes registration and what the terminating network accepts before traffic begins.

India

Bulk-message registration

TRAI's framework requires principal-entity, sender-header and content-template registration for bulk messaging. Check the applicable message category and consent requirements. TRAI guidance.

United Arab Emirates

Promotional-message rules

TDRA's promotional SMS rules cover prior consent, permitted sending times and a free opt-out. Confirm sender requirements with the terminating network. TDRA guidance.

Saudi Arabia

Bulk sender registration

CST's published guidance directs bulk SMS users to register sender names through their contracted service providers. Confirm the current registration process before activation. CST guidance.

Before activation

Confirm the route

Agree the sender format, message category, required registrations, consent responsibilities and test procedure for each destination and network.

What to agree for each route and destination

Delivery rate against submitted.
Submit-to-receipt latency — the delivery window required by your application.
Achieved throughput against the TPS agreed on the bind.
Error-code patterns — changes in reported failures can help identify a route issue.
Artificially inflated traffic — agree how suspicious volume changes are investigated and escalated.

What we do not sell

Numbers, short codes or long codes.
Two-way messaging services.
Campaign tooling. We terminate traffic; the platform is yours.
Grey routes presented as direct.

FAQ

SMS termination, in short.

Which traffic do you accept?+

Application-to-person traffic — one-time passwords, alerts, notifications, and marketing where the destination market allows it — and person-to-person traffic where an operator needs an outlet for it.

How are delivery receipts handled?+

Receipt availability, downstream status mapping and failure reporting are confirmed for each route during interconnection. A receipt is a network signal; it is not proof that a person has read a message.

What happens when a route degrades?+

Quality thresholds, escalation and any rerouting arrangements are agreed for the service before traffic begins.

How is throughput agreed?+

Per SMPP bind, in messages per second, and measured against what is actually achieved.

Next step

Tell us where your messages need to land.

Share destinations, traffic type and volumes. We come back with rates per destination, the route type for each, and what each market requires of your sender.

Request SMS rates