Operator tools / Messaging
SMS cost calculator
Check the cost of a reminder before it reaches 1,000 subscribers.
GSM-7 or UCS-2 · EN / FR examples · Runs in your browser
Paste the final text, with variables filled in. Examples use fictional values. Nothing is sent or saved. Limit: 10,000 UTF-16 units.
Use your provider’s rate per SMS segment, in your chosen currency. No default tariff.
Message estimate
- Encoding
- GSM-7
- Billable segments
- 0
- Septets
- 0
- Units per segment
- 160
- Cost per message
- Enter a rate
- Cost for 1,000 subscribers
- Enter a rate
One identical message per subscriber. Excludes taxes, fees, retries and provider changes to the text.
Encoding check
Enter a message to check its encoding.
Accents can change the bill
Keep the accents that fit: é è à ù. Check those that switch encoding: ê ç â î ô û. The rewrite is optional and never changes your original text until you choose “Use this rewrite”.
GSM-7 extension characters {}[]~\|^€ and form feed each take two septets. Emoji use Unicode; a single symbol can use multiple UTF-16 units. Combining accents are counted exactly as pasted, without automatic normalization.
For example, 160 basic GSM-7 characters fit in one segment. Replacing one with ê makes that 160-unit message three Unicode segments. See the SMS segment capacity reference for the standard limits and provider exceptions.
Questions operators ask
Why can one French accent increase SMS cost?
é, è, à and ù are in GSM-7. ê, ç, â, î, ô and û are not. One unsupported character changes the encoding of the entire message to UCS-2, which has a smaller segment capacity.
How are segments counted?
GSM-7 allows 160 septets for one segment, or 153 per segment for multipart text. UCS-2 allows 70 UTF-16 units, or 67 per multipart segment. GSM-7 extension characters cost two septets; emoji can take two UTF-16 units. Two-unit characters stay together at segment boundaries.
Is this a provider quote or a sending tool?
No. This offline calculator multiplies the segment count by the rate you enter. It does not send SMS or look up prices. Carrier headers, national language tables, provider rewriting, fees and retries can change the final charge.
Are the templates already enabled in ISPAgents?
These are example texts from the EN/FR pilot messaging pack, with fictional values. They do not establish installed triggers or delivery. ISPAgents notification workflows remain a guided pilot requiring onboarding and workflow verification.
Planning collections? Read about ISP payment automation in guided pilot and WhatsApp workflow roadmap.