Plans, approval & billing
Understand workspace approval, monthly allowances, and offline settlement.
Approval comes first
New workspaces begin pending. An administrator must approve both the workspace and requested plan. Payment alone does not grant approval. Pending or rejected workspaces cannot send or perform operational setup.
Monthly allowance
Channel allowances use UTC calendar months, including annual contracts. Email and WhatsApp have separate limits; WhatsApp plans also limit connected sending numbers. The Stored email contacts allowance counts email-profile contacts. WhatsApp consent records do not count toward this allowance. WhatsApp sends and connected numbers have separate limits. Accepted sends reserve capacity. Known-unsent cancellations and rejections release it once. Provider-accepted and unresolved sends retain their reservation. No automatic per-email overage charge is implemented.
Paid access and invoices
Paid plans require full settlement against an invoice or explicit, time-bounded administrator credit. Finance records bank transfer, UPI, cash, or cheque receipts offline. Invoice and payment records are immutable; corrections append reversals. The platform does not collect card payments.
Plan changes and retention
End-of-term cancellations and downgrades can be scheduled and cancelled before they take effect. Approved and settled target plans become eligible at the boundary. Message-content retention is a plan allowance; delivery metadata, consent history, and financial ledgers have separate retention requirements.
Public pricing versus your contract
The public pricing page and dashboard read the same active, versioned plan catalog for email, WhatsApp, and combined plans. Unpublished plan families show a contact option without invented rates. Your approved subscription snapshot determines access and charges. Existing subscription snapshots are not silently rewritten when catalog pricing changes.