Understand allowances, wallet and reservations
Convert checks billing availability before delivery. Depending on your plan and settings, messaging can consume included allowance, wallet funds, or approved overages. Use the prices and allowances shown in your workspace; example costs in documentation are not a pricing quote.
Estimates and actual charges
A campaign estimate helps you review cost for the selected audience and channel. Actual results can differ as eligibility, routing, message content, and delivery outcomes change. Inspect final campaign and recipient results alongside billing transactions.
A successful
test: true single-message request has zero cost. Automation simulation also does not spend funds. Dashboard test delivery and SMTP test submission can be real sends and should be treated accordingly.Reservations and settlement
Accepted queued work may reserve funds or allowance before the provider receives the message. Your available balance can therefore decrease while work is pending. Charges are captured and reservations released according to the existing delivery and settlement flow.
Batch acceptance is per recipient. Valid recipients can queue while later rows are rejected for insufficient funds. Read both accepted and rejected results; do not assume the whole input array was funded merely because HTTP 202 returned.
Paused journeys and pending work
Pause or archive can hold an automation's progress while preserving pending message reservations. These actions are not interchangeable with explicit cancellation. Review Stop all active executions when cancellation is intended.
Ambiguous provider acceptance needs reconciliation. Do not clear pending records or recreate sends simply to restore an available balance; the provider may have accepted the original message.
Resolve billing failures
insufficient_balance: review available wallet funds and pending reservations, then use the existing funding flow if appropriate.plan_limit_reached: inspect renewal/allowance and overage settings.frequency_limit_reached: wait or correct audience/purpose policy rather than changing keys or sender.
Inspect the existing transaction before retrying. Once the underlying capacity issue is resolved, a changed/new logical message needs a new idempotency key; an uncertain retry retains its original key and payload.
Campaign totals and wallet balance answer different questions. Check reservation/settlement status when a balance seems lower than completed sends alone explain.