DEVELOPER DOCS

Billing and usage

Understand usage records, credits, limits, and the billing portal.

Published rates

Calls are billed to the second after the first minute. The configured Stripe prices and the values shown at checkout must match the pricing page.

Usage records

Verified end-of-call events provide call duration and outcomes. Messaging callbacks provide status information for SMS. The application associates usage with an organization and uses event identifiers to avoid repeating the same charge on webhook retries.

Credits

Credit records should be treated as a ledger, not a value the browser can edit. Operations reserve the relevant amount before dispatch and reconcile verified results afterward. Your plan and policy determine what happens when a balance is exhausted. Do not assume unlimited usage from the word “Phone.”

Stripe checkout

Use the dashboard Upgrade action or the Phone setup flow to create a checkout session. The server chooses from configured price identifiers rather than accepting an arbitrary amount supplied by the browser. Introductory pricing applies only under the approved customer and coupon rules.

Customer portal

The billing portal is the place to review supported card changes, invoices, subscriptions, and cancellation options. A portal link is generated for the authenticated organization's billing customer. It must not allow access to a customer chosen by a browser parameter.

Meters and taxes

Call-minute and SMS meters require the correct Stripe meter configuration. Stripe Tax behavior depends on the configured account, product tax settings, locations, and customer information. Review the commercial settings before accepting a live payment.

Questions

Review the pricing page, the Phone plan, and your applicable agreement. Contact the team if the usage record or a billing outcome does not look right.

Never miss a call again.

Put your calls, texts, and next steps in one workspace.