MESSAGE sends
| Send content | Billing unit |
|---|---|
| Text ≤ 160 UTF-8 chars, no suggestions, no rich body | Basic Message |
| Text > 160 chars | Single Message |
| Any suggestions (reply or action chips) | Single Message |
| Rich card, carousel, or media | Single Message |
CONVERSATION sends
Traffic inside an active 24-hour session bills as Conversation. A session opens when a user replies to an outbound message. Sends within the session window are billed at the Conversation rate; the initial outbound hold resolves at that price. See RCS conversation for the full session lifecycle. Conversation units count toward the RCS tier volume.NEWSLETTER sends (MAU)
The RCS newsletter channel bills as a single MAU (Monthly Active User) charge — there is no per-message charge on top.- MAU — charged once per subscribed user per agent per calendar month, triggered on the first send of that month to the subscriber
- Subsequent sends to the same subscriber in the same month: no charge (
hold_amount: 0)
429.
For tier volume, MAU counts as 1 per unique subscriber per month regardless of how many days you sent to them.
RCS tier
RCS has its own independent tier separate from email and SMS. Your RCS send volume (Basic + Single + Conversation + MAU) only affects your RCS pricing.Tier transitions
- Upgrade — triggered mid-month when your RCS volume crosses a threshold. Lower pricing applies from the next message sent.
- Downgrade — if you fall below a tier’s threshold for three consecutive calendar months, you downgrade at the start of the fourth month. One month back above the threshold resets the counter.
API entry points
RCS text
Basic vs Single from length and suggestions.
RCS conversation
Session lifecycle and Conversation billing.
RCS newsletter
MAU per subscriber per month — no per-message charge.
Billing units
Prepaid model, per-channel tiers, and transitions.