Skip to content

A guide to SMS performance

How to measure SMS performance

Learn how to measure SMS submission speed, delivery reporting and availability, and compare performance by destination, campaign size and peak periods.

01
Processing

Internal work before route submission.

02
Submission

Route acceptance rate over a defined interval.

03
Delivery

An outcome supported by available receipts.

Measurement definitions

Four ways to measure performance

Historical volume counts messages or parts over a documented period. Processing capacity describes infrastructure under a defined load. Submission rate measures what a route or operator actually accepts per second. Delivery performance depends on DLR availability and state definitions; these measures are not interchangeable.

Before comparing results, agree the unit: logical message, SMS part or API request. Record sample size, destination, encoding, sender, peak and observation window. Where data supports it, report median and p95 alongside missing receipts and exclusions.

Availability and operations

Repeatable testing and a defined service agreement

Platform availability measures whether you can access and use the service. Route availability measures whether messages can be submitted to the network. Handset status and coverage also affect delivery. When agreeing an SLA, define the measurement point, observation period and maintenance windows.

Retain pseudonymous references and consistent timestamps for request acceptance, submission and receipt. Compare normal load, peaks and recovery after an outage. Separate acceptance, rejection, expiry and unknown outcomes without exposing message secrets or customer numbers.

Planning observations for Jordan

How should you test SMS in Jordan?

Test one of your Arabic templates on the target networks. Check the sender ID, number of parts and delivery report, during both normal and peak periods. Long links and some symbols can increase parts and message cost.

Pricing and procurement guide ↗

Assessing the route ↗

Implementation steps

How we prepare and launch the service

We review the use case and requirements, then test the setup before production sending begins.

  1. 01Define

    Unit, destination, period and objective.

  2. 02Test

    Authorized sample and agreed load.

  3. 03Reconcile

    Events, receipts and unknown outcomes.

  4. 04Review

    Exceptions and evidence before publication.

Information we need

Share these details for an accurate proposal

These details help us confirm pricing, requirements, and the right operating model from the first conversation.

  • 01Measurement unit and success definition
  • 02Sample distribution and encoding
  • 03SLA scope and exclusions
  • 04Monitoring and review owner

Frequently asked questions

Straight answers about the service

Does TPS mean messages delivered per second?+

TPS means transactions per second. In SMS connectivity it commonly measures submission of messages or parts to a route. Handset delivery is a separate stage tracked through delivery reports.

Does the calculator guarantee a duration?+

No. It estimates submission of a specified number of parts at an assumed rate, excluding network and handset delays and outages.

Service inquiry

Download the SMS pricing guide

Share your details and expected sending volume to receive the pricing guide for your use case.

We use your details to follow up on this request.