Pay-as-you-go overages
What happens when you pass a plan allowance, and how to make sure it never happens by surprise.
Two ways a limit can behave
Which applies depends on your plan and whether pay-as-you-go is enabled on your account.
| Configuration | At the limit | Suits |
|---|---|---|
| PAYG enabled | Usage may continue and be billed as overage, subject to your account configuration | Businesses that must never stop taking calls |
| PAYG not enabled | The metered capability stops until the period resets or you upgrade | Businesses that want a hard ceiling on spend |
Neither is inherently better. Choose the one whose failure mode you can live with: an unexpected bill, or a stopped capability.
What can go into overage
See usage and limits for how each measure is counted.
- Call minutes
- AI usage
- Messages
- API requests
- Phone numbers are a fixed monthly cost per number rather than an overage
Keeping overage predictable
- Watch the usage panel before busy periods, not during them.
- Consider an add-on rather than sustained overage - it is usually the cheaper shape. See add-ons.
- Review after any change in call volume, a new number, or a new integration that drives API traffic.
Careful. An automated integration in a retry loop is the most common cause of unexpected API usage. Cap your retries - see rate limits.
How overage appears
Overage is billed through the same payment method as your subscription and appears on your invoices. See invoices and tax.