Message parts and pricing
An SMS is sent and charged in parts. How many parts a message needs depends on its length and on which characters it uses.
GSM-7 and UCS-2
Every message is sent in one of two encodings. We choose it from your text; you do not set it. The response tells you which was used in encoding.
- GSM-7 covers plain English letters, digits and common punctuation. Messages use it unless they contain a character outside the GSM-7 alphabet.
- UCS-2 is used as soon as one character falls outside GSM-7: emoji, curly quotes, many accented letters, and Ghanaian letters such as
ɛandɔ. A single such character switches the whole message to UCS-2.
Part sizes
| Encoding | Fits in one part | Per part when split |
|---|---|---|
| GSM-7 | 160 characters | 153 characters |
| UCS-2 | 70 characters | 67 characters |
A split message carries a little extra data in each part so the phone can join them back together, which is why a part holds fewer characters once a message is split. For example, a 161 character GSM-7 message needs 2 parts.
In GSM-7, these characters count as two: ^ { } \ [ ~ ] | € and the form feed character.
The 255 part limit
A message can use at most 255 parts. Longer text is refused with 400 MESSAGE_TOO_LONG and nothing is sent or charged.
How cost is worked out
You pay per part, per recipient, at your account's SMS rate:
cost = parts x recipients sent x your rate per part
- Your rate is shown in the dashboard under Account > Billing.
partsin the response is per recipient. A 2 part message to 100 recipients is charged for 200 parts.- Only recipients that are sent count. Numbers on your Do-Not-Call list are skipped and not charged.
- For a message sent now, the full cost is taken from your balance up front, and
costin the response is exact. If your balance does not cover it, the request fails with 402INSUFFICIENT_BALANCEand nothing is sent. - For a scheduled message,
costis an estimate at today's rate andchargedis false. Nothing is charged until it is sent, and the balance is checked again then.
Refunds
Parts that the network reports as failed, rejected or expired are refunded to your balance automatically. Some outcomes are not refunded automatically:
| Recipient status | Refunded? |
|---|---|
delivered | No, it was delivered. |
failed | Yes, automatically. |
rejected | Yes, automatically. |
expired | Yes when the network reported it expired. No when it expired because no delivery receipt arrived within 48 hours, since a missing receipt does not prove the message was not delivered. |
unconfirmed | Not automatically. We could not confirm whether the network accepted it. It is not resent, and our support team reviews these. |
skipped | Never charged. |
If a whole message fails (for example a scheduled message that could not be sent when due), any charge is refunded. See delivery status and webhooks for every status.