Free tool · Messaging
SMS throughput and campaign planner
Enter a message volume and a sending window to see the throughput you need, or a throughput to see how long the campaign takes.
We list the rules we could verify. A topic with no verified rule is left out, not guessed. This is reference information, not legal advice; check the regulator link and the last-verified date.
Enter the number of messages to see the result.
- Segments to send
- Throughput needed
- Per hour
- Sending time
- Sending days in this window
Plan with headroom: retries, delivery reports, operator limits and sending-hour rules lower the real rate.
How this works and its limits
Runs in your browser: what you enter stays on your device and is never uploaded.
The planner divides the number of segments by the seconds in your sending window, or the reverse. Count segments, not messages: a long or Unicode message sends as several segments.
Real campaigns rarely run at a flat rate. Leave headroom for retries, delivery reports and peaks, and agree the throughput of each connection before launch.
Data sources and licences
Operator names, brands and codes shown here are public reference data compiled from national regulators and other public sources. Their appearance does not indicate any partnership, endorsement, agreement or connectivity between unicomam.com and the named operators. All trademarks belong to their owners. Data is provided “as is” with no warranty; verify against the official source before relying on it for routing, billing or compliance decisions.
Regulatory information is for reference only and is not legal advice; check the regulator link and the “last verified” date.
What SMS throughput means
Throughput is how many messages, strictly segments, a connection accepts per second, usually written as TPS. It decides how quickly a campaign or a burst of verification codes can go out: the volume you need to send, divided by the time you are allowed to send in, gives the throughput you need.
Count segments, not messages. A message longer than one segment, or one written in UCS-2, is sent as several segments, and each one uses throughput. A campaign of short Latin-script messages and the same campaign written in Chinese can need throughput that differs by a wide margin.
To work out the throughput you need, multiply the number of recipients by the segments per message and divide by the seconds in your sending window, across the days the campaign may run. To work out how long a campaign takes, divide the segments by the throughput you have, then fit the result into your daily window to see how many sending days it needs.
The sending window matters as much as the volume. Sending-hour rules for promotional traffic shorten the day, and a campaign that must reach every recipient before a deadline needs the throughput that fits its window, not an average over the whole day. Verification traffic behaves differently: a modest average with sharp peaks when many users sign up or log in at once, so plan for the peak.
Retries after temporary failures, delivery reports flowing back on the same connection, operator-side limits and maintenance pauses all lower the effective rate. Plan with headroom rather than the full throughput, and agree the throughput of each connection before launch: a connection that sends faster than agreed is throttled and has to retry, which slows everything down.
Throughput can also differ by destination, because some operators accept traffic more slowly than others, so a campaign across several countries may need a different rate per destination. Our A2P connections carry 200+ TPS per bind; tell us when your peaks need more, and we plan the connections with you.