An SMS switch receives SMS traffic from carriers, clients and applications and routes each message to the right destination. smsswit.ch is a hosted SMS switch that handles the whole path of a message: ingress, range lookup, screening, delivery and billing.
What the SMS switch does
- Ingress: accepts traffic on authenticated binds over SMPP 3.4, SMPP 5.0, HTTP, XML and REST.
- Range lookup: matches the destination to its hosted range or route plan in under a millisecond.
- Screening: checks velocity, source and content patterns, and holds suspect messages for review instead of dropping them.
- Delivery: sends the message to the client's bind or webhook and maps the delivery receipt back to the origin.
- Billing: writes buy rate, sell rate and payout to the CDR on submit.
Throughput and latency
Each node has capacity for 2,500 messages per second, and your plan sets your TPS: 20 TPS, 50 TPS, or CUSTOM with 200+ TPS. Median submit-to-response time is under 50 ms.
Compared with a typical legacy switch
- Capacity: 2,500 msg/s per node, against around 200 msg/s on one server.
- Billing: rated on submit with live margins, against batch CDR processing.
- Pricing: published monthly plans, against quote-only annual licences.
- Onboarding: live in 48 hours with migration support, against weeks of setup.
Where it fits
The switch connects to your carriers and vendors through carrier connectivity, applies your routing rules, and feeds billing and monitoring. New to the term?
Frequently asked questions
What is an SMS switch?
An SMS switch is the system that receives SMS traffic and routes it to vendors, clients or applications, while screening it, mapping delivery receipts and recording billing data for every message.
Which protocols does it support?
SMPP 3.4, SMPP 5.0, HTTP, XML, REST with webhooks, and SIP for voice.
How fast can I go live?
Ranges go live within 48 hours of a signed order. We can run both switches in parallel during cutover.
See it with your own ranges
We build a demo account around your range structure, with test ranges and a simulated carrier, so you can send traffic and check billing before you commit. Ask about SMPP connections, partnerships or migration in the same request.