DraftThis page is a draft. Values set in grey monospace are placeholders and are not confirmed yet.
SMS Termination
A2P SMS termination for OTP, alerts, bulk and classic wholesale.
Direct, Premium and Standard routes for hubs, aggregators, carriers and CPaaS platforms sending at volume. Every rate-deck row carries a route class, a sender-ID rule and a date; TPS is committed per bind.
Terms at a glance
- Pricing
- Per message, by destination (MCC/MNC) and route class, in CURRENCIES
- Coverage
- Quoted per network (MCC/MNC) on your rate deck; full list on request CONFIRM_
BEFORE_ PUBLISH - Billing basis
- per submitted or per delivered message, agreed in your contract
- Rate deck
- Dated RATE_
DECK_ DATE, valid for RATE_ DECK_ VALIDITY; RATE_ NOTICE_ DAYS days’ written notice on every increase - Payment
- Prepaid start, no minimum commitment, month-to-month. Postpaid terms after POSTPAID_
AFTER_ CYCLES clean billing cycles and a credit review CONFIRM_ BEFORE_ PUBLISH - Throughput
- COMMITTED_
TPS_ PER_ BIND TPS committed per bind, up to MAX_ BINDS binds
Traffic
What each kind of traffic needs from a route.
| Traffic | What matters most | Usual route class |
|---|---|---|
| OTP and verification | Time to handset, sender ID and content intact, a receipt that matches the handset, and AIT monitoring on the account. A late code is a failed one. | Direct; Premium where a destination has no Direct route |
| Transactional and notifications | Steady delivery through unplanned peaks, the brand’s sender ID intact where it is registered, and receipts you can reconcile and pass on to your customer. | Premium or Direct, with failover rules agreed in advance |
| Bulk and marketing (opt-in) | Cost per delivered message, sustained TPS through the send, the segment count of long and Unicode messages, and local opt-out and quiet-hour rules. | Standard; Premium where the sender ID must arrive intact |
| Classic wholesale | Cost per delivered message, not just the deck price; a route stable enough to hold its LCR position; a clean SMPP bind; credit terms; notice before a rate rises. | All three, chosen per destination on the rate deck |
A guide, not a rule: the rate deck names the class of every destination, and you decide what to send on it. Marketing, sent in bulk or not, is a restricted category: opt-in only, listed in your traffic declaration before you send, and accepted where the destination’s rules and the route allow it. CONFIRM_
Routing
Three route classes, defined by sender ID and receipt source.
Class: Direct
- What it means
- Our own connection to the terminating operator. No intermediary.
- Sender ID
- Intact, subject to local registration rules
- Delivery receipt
- From the delivering network
- Typical use
- OTP and verification; critical transactional alerts
Class: Premium
- What it means
- One operator-grade intermediary, which can be the operator’s appointed A2P gateway where one exists.
- Sender ID
- Intact, subject to local registration rules
- Delivery receipt
- Passed through from the delivering network CONFIRM_
BEFORE_ PUBLISH - Typical use
- Transactional alerts and notifications; back-up to your primary route
Class: Standard
- What it means
- Cost-optimised; the path can vary with traffic conditions.
- Sender ID
- Stated per destination on the rate deck
- Delivery receipt
- Passed through from the delivering network CONFIRM_
BEFORE_ PUBLISH - Typical use
- Opt-in marketing and bulk campaigns; price-sensitive classic wholesale
We label every destination by its outcome (how the sender ID and the receipt arrive), not by what a contract chain says. Where an operator routes international A2P traffic through an appointed gateway, we label the destination Premium, never Direct. If a destination changes class, we tell you within ROUTE_
Classic wholesale
Termination to resell, quoted by destination.
For hubs, aggregators and carrier wholesale desks that buy termination and sell it on. Take the full A–Z or only your wanted list, in RATE_
Pin a destination to one class, or let it fail over under rules we agree with you. CDRs reach you as CDR_
Performance
Throughput per bind, latency to the handset, delivery from network receipts.
- Throughput
- COMMITTED_
TPS_ PER_ BIND TPS committed per bind, agreed per account, not a platform peak figure. - Peaks and scaling
- Bursts: BURST_
POLICY. Above your committed TPS: THROTTLE_ BEHAVIOUR. For more, add binds (up to MAX_ BINDS per account) or agree a higher commitment. CONFIRM_ BEFORE_ PUBLISH - Latency
- LATENCY_
P50 median and LATENCY_ P95 p95, submit to handset, measured on a TelQ-class tester over MEASUREMENT_ PERIOD. Per-destination figures in your monthly report. CONFIRM_ BEFORE_ PUBLISH - Delivery
- Delivery rate DLR_
RATE CONFIRM_ BEFORE_ PUBLISH: delivered DLRs from the network divided by messages submitted, over MEASUREMENT_ PERIOD. To check it, run your own TelQ test on our routes, or use any independent tester. - Resilience
- Multiple redundant route sources. If a route degrades, traffic fails over under rules we agree with you: FAILOVER_
POLICY. CONFIRM_ BEFORE_ PUBLISH
Delivery receipts
A receipt means the network said so.
Every delivery receipt (DLR) we return comes from the delivering network. Undeliverable, expired and rejected statuses are passed through as received. We never return or bill a ‘delivered’ we did not receive. CONFIRM_
Our DLR format, status list and error codes are in the onboarding spec.
Compliance
Sender IDs, handled per destination.
Alphanumeric, numeric and short-code sender IDs, as each destination allows. The rate deck states the sender-ID rule for every row. In registry countries, unregistered alphanumeric sender IDs are blocked or labelled whatever route they take: Spain has blocked them since 15 September 2026, Ireland labels them ‘Likely Scam’, and the UAE requires approval in advance. SENDER_
A summary of third-party regulation, not legal advice.
Connectivity
Connect over SMPP or HTTP.
- Protocols
- SMPP SMPP_
VERSIONS · HTTP API HTTP_ API - Security
- CONNECTIVITY_
OPTIONS and IP allow-listing on every bind CONFIRM_ BEFORE_ PUBLISH - Capacity
- up to MAX_
BINDS binds per account; window size WINDOW_ SIZE - Integration
- if your platform speaks standard SMPP, it binds without custom development. CONFIRM_
BEFORE_ PUBLISH
Acceptable use
What we don’t carry.
We don’t carry artificially inflated traffic (AIT) or SMS pumping, spam, phishing or smishing, unregistered or spoofed sender IDs, SIM-farm origination, or A2P traffic disguised as P2P. Full rules: Acceptable use policy.