• 228 destinations
  • No KYC, ever
  • Bitcoin, Monero, USDT and 4 more

Delivery and reporting

Throttling and pacing

Throttling (or pacing) is the deliberate limiting of a campaign's send rate, in messages per minute or spread over hours, so that replies, calls and clicks arrive at a pace the receiving side can absorb.

Sending as fast as possible is rarely the goal. A promotion with a hypothetical 2% reply rate, sent at 400 messages a minute, produces eight conversations a minute for whoever answers them; a link that sends a thousand people a second to one landing page tests the server more than the offer. Pacing spreads the send, either as a fixed rate per minute or as a total spread evenly over a number of hours, and combined with local delivery windows it keeps the send inside acceptable hours.

Pacing also protects routes. A sudden spike on a new destination looks like spam to operators, and filters react to volume as well as content. The word throttling is also used for limits imposed from outside: an API's rate limit, or a carrier slowing traffic that exceeds the rate agreed for a route. The first kind is a choice; the second is a ceiling to plan around.

Pace and window have to fit together. Take a hypothetical list of 30,000 numbers and a local window from 08:00 to 20:00, which is 720 minutes. At 50 per minute the send takes 600 minutes and ends at 18:00. At 40 per minute it would need 750 minutes, so 28,800 messages leave inside the window and the remaining 1,200 wait for the next day's.

Three mistakes are common:

  • Pacing so slowly that the tail of a campaign spills into the next day.
  • Applying a campaign's pace to codes and alerts, which should never wait behind marketing.
  • Treating a 429 response as a failure instead of slowing down and retrying after the delay the API asks for.

At SMSMeteor: a campaign can be paced per minute or spread over a number of hours, and paused and resumed; see scheduling. In the API, a batch takes pace.per_minute, the maximum messages per minute, or pace.over_hours, which spreads the batch evenly over that many hours. Pace combines with window, the local-time window per destination inside which quiet hours apply, and messages not sent by window.local_end wait for the next day's window.

Go further

See the term in practice.An email address opens the account, the rate card is public, payment is crypto, the test key is free.
Start sending