Bulk and scheduled sends
Send to a list once, or at a future time, with per-batch pacing that protects your provider limits.
Read this article →Segments × destinations × sender type is the whole formula. Here is how to work it out before the invoice arrives.
You are not billed by characters but by segments, and a message that exceeds one segment is split — each part carries a small header, which reduces how much text fits in the parts after the first.
| Encoding | Single segment | Per segment when split |
|---|---|---|
| GSM-7 (Latin script, basic characters) | 160 characters | 153 characters |
| UCS-2 (Cyrillic, Arabic, CJK, emoji) | 70 characters | 67 characters |
Cost is per segment per destination, at the rate your own provider charges you. Nothing is repriced on the way through, so the rate that applies is the one on your contract — which is exactly why estimating cost is a matter of reading your provider’s price list with the segment count in hand.
Usage is derived from the same message log the console shows, so a filtered log and a usage figure cannot disagree. After a real send, filter the log to the window and count the rows — that is the number your provider will bill.
Send to a list once, or at a future time, with per-batch pacing that protects your provider limits.
Read this article →Keep the people you message in one place, import them in bulk, and group them without duplicating anyone.
Read this article →Connect a provider, issue a key, send your first message — and meet the two defaults that quietly cost money if you miss them.
Read this article →