How to choose SMS switch software: a 12-point checklist

An SMS switch is the core system of a wholesale SMS or A2P business: it accepts messages from your customers, routes them to your suppliers, charges for them and returns delivery reports. Choosing the wrong one costs you margin, customers and a painful migration later. Use this checklist to compare SMS switch software before you buy.

What does an SMS switch do?

Your customers connect to the switch over SMPP or an HTTP API and submit messages. For each message the switch checks the account, screens the number and content, finds the price, picks a supplier, charges the customer and sends the message on. When the supplier returns a delivery report (DLR), the switch passes it back to the customer. Around that core you need rate plans, invoices, reports and a portal for customers.

The 12-point checklist

Protocols. SMPP 3.4 with transmitter, receiver and transceiver binds for customers and suppliers, SMPP over TLS, and an HTTP API with DLR webhooks.
Throughput. Ask for real messages-per-second figures on stated hardware, not just "unlimited". Check how many binds and suppliers it handles at once.
Routing strategies. Least-cost, failover, round robin, quality-based and static routing, by prefix and by MCC/MNC, with priorities and reroute on failure.
Route simulator. A way to see which supplier a number will use before you send real traffic.
Real-time billing. Every message charged as it is accepted, credit limits for prepaid and postpaid customers, per-segment billing for long messages and automatic refunds on failure.
Rates and margins. CSV import of buy and sell rate plans with a preview and rate history, multi-currency support and a margin view that flags routes selling below cost.
Invoicing. Customer invoices and vendor bills created from real traffic on each client's payment terms.
Number and content screening. Blocked numbers, opt-outs, duplicate detection, sender ID replacement, keyword filters and text rewrites.
Fraud protection. An IP firewall for repeated failed binds and SMS pumping (artificially inflated traffic) detection that can alert or block.
Encoding. GSM-7, UCS-2 (Unicode) and multipart messages handled and billed correctly.
Customer portal. Message history with export, balance, invoices, rate card, live bind status and self-service passwords.
Logs and visibility. For any message: which rate matched, which route was chosen, what it cost, supplier response time and when the DLR arrived. Plus user roles and an audit log.

Questions to ask in a demo

Can I get my own demo login with live message flow, not just slides?
What throughput did you measure, on which server, and how much CPU and memory did it use?
How long does installation take, and who owns the installation and the data?
Do portal changes (rates, routes, clients) apply without restarting the engine?
How are failed messages rerouted, refunded and reported to the customer?
Can I add WhatsApp or RCS with SMS fallback, and HLR/MNP lookups, later?

Self-hosted or cloud?

Self-hosted

Installed on your own server. Your message data, rates and customers stay with you, there is no per-message platform fee to the software vendor, and you control capacity.

Cloud / hosted

Run by the vendor. Faster to try and no servers to manage, but your traffic and data sit on their platform and you usually pay per message or per month on their terms.

How the LCR ONE SMS Switch measures up

The LCR ONE SMS Switch has a Go SMPP engine (SMPP 3.4 TX/RX/TRX, SMPP over TLS, HTTP API with DLR webhooks) that peaked at 1,380 messages per second on one server in our load test. It has five routing strategies by prefix and MCC/MNC with reroute and a route simulator, real-time billing with credit limits, multi-currency rates and margins, invoices and vendor bills, SMS pumping detection, an IP firewall, a customer portal and per-message logs. It is installed on your own server and can be live in about two days, with no lock-in.

See the SMS Switch → Book a free demo

FAQ

What is an SMS switch?

An SMS switch is software that accepts messages from customers over SMPP or HTTP, routes them to suppliers, charges for them and returns delivery reports. It is the core system of a wholesale SMS or A2P business.

What is the difference between an SMS switch and an SMS gateway?

An SMS gateway usually connects one business to the mobile network to send its own messages. An SMS switch connects many customers to many suppliers, with routing, rating and billing between them.

Which SMPP version should an SMS switch support?

SMPP 3.4 is the industry standard for A2P and wholesale SMS, with transmitter, receiver and transceiver binds. Support for SMPP over TLS is a plus for security.

How fast should an SMS switch be?

It depends on your volume, but ask for measured messages-per-second figures on real hardware. The LCR ONE SMS Switch peaked at 1,380 messages per second on one server in our load test.

Should I choose a self-hosted SMS switch?

If you want to own your data, avoid per-message platform fees and control capacity, a self-hosted switch is usually the better long-term choice.

Last updated: 26 October 2026 · LCR ONE