​
Prepaid model

The platform runs on prepaid balance. Before any message is sent, balance must be available. There is no credit or post-pay billing.
Your workspace balance has two components at all times:
StateMeaning
FreeImmediately spendable — used for new sends
ReservedHeld for in-flight work — released or charged when the message resolves
The balance check before every send runs against free only, not the total. Reserved balance is not available for new sends until the underlying reservation resolves.

​
The four billing units

Every send is classified into one of these units. Pricing and tiering differ by channel — see the per-channel billing pages for details.
UnitWhat it coversChannels
Basic MessageShort text with no rich content; all email; all SMS (coming soon)RCS, Email, SMS
Single MessageRich cards, carousels, media, long text, or any suggestion chipsRCS only
ConversationTraffic inside an active 24-hour RCS sessionRCS only
MAUMonthly active user — one flat charge per subscriber per agent per calendar month on the RCS newsletter channel. Covers all sends that month; no per-message charge.RCS newsletter only
Email is always Basic Message regardless of content length. SMS (coming soon) will also be Basic Message. The Basic/Single distinction exists only for RCS standard messaging. MAU is a subscriber charge, not a per-message charge. It is triggered on the first newsletter send of the month to a subscriber, and covers all subsequent sends to that subscriber for the rest of the month at no additional cost. Sends are still limited to one per day per subscriber.
The RCS newsletter channel has a send limit of one message per day per subscriber. A second send on the same calendar day is rejected.
RCS newsletter capability must be set at agent creation (newsletter_enabled: true) — it cannot be added later. See Newsletter enablement.

​
Per-channel tiers

Pricing is tiered by volume — but each channel has its own independent tier. Your RCS send volume, email send volume, and SMS send volume each count toward their respective channel tier separately. Reaching a higher tier on one channel does not affect pricing on another.
  • Volume is tracked per channel, not combined across channels.
  • Tier upgrades happen mid-month the moment a threshold is crossed. The lower price applies from the next message sent — not from month start. A single invoice may show two price bands for the same channel.
  • Tier downgrades apply only to volume-qualified upgrades. If you fall below your 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.
Current tier thresholds and prices for each channel are visible in the Billing section of your dashboard.

​
Next steps

Channel message types

Full mapping table across email, RCS, and SMS.

Billing API

Balance, usage, tier, invoices, and alerts.

Billing (RCS)

Basic/Single split, conversation sessions, and newsletter MAU.

Billing (Email)

Email tier structure and Basic Message unit.