Skip to content

Free planning tools

SMS planning calculators

Calculate the parts in an Arabic or English SMS and estimate campaign submission time from recipient count and your selected rate.

01
GSM-7

Typically 160 units in a single part.

02
Unicode

Typically 70 units in a single part.

03
Estimates only

Actual behavior depends on route and encoding.

How the estimate works

Parts matter more than visible characters

The estimate uses the GSM-7 basic and extension tables; characters such as braces and the euro sign cost two units. Arabic or a character outside these tables switches the estimate to Unicode, counted as UTF-16 units. Emoji may require multiple units as a visible sequence; actual support depends on connector and route.

For multipart text we assume 153 GSM-7 units or 67 Unicode units per part and avoid splitting an extension character or surrogate pair. Other headers or language tables can reduce capacity. These calculators do not establish ITBeep pricing or account limits.

Technical reference: length and encoding ↗

Understanding submission and delivery rates ↗

Planning only · no messages sent

Estimate your template and campaign

Use a non-sensitive sample. Results are estimates, not prices, delivery commitments or account limits.

Encoding: GSM-7 · Units: 47 · Estimated parts: 1

Estimated submission time: 100 seconds (about 1.7 minutes).

Excludes queueing, outages and handset delivery time. Parts per recipient is independent of the sample text above.

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. 01Enter a sample

    A non-sensitive template without real data.

  2. 02Review parts

    Compare Arabic and mixed text.

  3. 03Choose a rate

    Use your agreed limit when available.

  4. 04Validate on route

    Test before committing cost or schedule.

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.

  • 01Final template including links
  • 02Recipients and parts per recipient
  • 03Agreed submission rate
  • 04Allowance for errors and delays

Frequently asked questions

Straight answers about the service

Does the tool send my text to a server?+

No. The tool calculates results in your browser without sending or storing the text. Use a non-sensitive sample when trying your message.

Why is submission time not final delivery time?+

The estimate divides parts by submission rate. It excludes queue waiting, connection outages, network and handset delays and DLR arrival.

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.