SMS operations, investigated end to end
SMS runs alongside voice as a first-class part of SWITCH/T, not a bolt-on. Every message is recorded, filterable, and reportable in the same place you manage numbers, customers, and billing.
This page covers the platform-level SMS operations available to every tenant. If you need SMPP binds, HTTP provider integration, or your own message-routing infrastructure, that is the job of the separate SMPP/HTTP Gateway product.
Transaction records
Every message, in either direction, is recorded and searchable. That includes messages that never reached anyone \u2014 unallocated inbound SMS, or outbound messages a routing rule restricted \u2014 so nothing simply disappears.
- SMS transaction records and history
- Date, tenant, destination, network, supplier, and client filtering
- Delivery receipt status
- Missed and restricted SMS visibility
- Unallocated SMS investigation
Routing and test traffic
Access and routing rules decide which messages reach which destination, and a pool of test numbers lets you validate inbound SMS behaviour before it goes live for real traffic.
- SMS access and routing rules
- Test-number management for inbound SMS testing
- SMPP connection-state visibility where configured
Supplier, client, and network reporting
- Supplier traffic reporting
- Client traffic reporting
- Network, DDI, and CLI statistics
- Application-level statistics
- Cost and billing context
- Record export and API access
Need SMPP or HTTP gateway infrastructure?
These platform-level SMS operations sit above message delivery. SMPP binds, HTTP provider integration, and DLR correlation infrastructure are handled by the dedicated gateway product.
View the SMPP/HTTP Gateway →