Choose the billing model only after defining the outcome and allocating failure costs. The following compares possible contract structures; it does not claim that every named supplier offers each one.
| Billing model | Useful when | What to challenge | Contract question |
|---|---|---|---|
| Per minute | Call duration is measurable and configuration is stable | Silence, retries, transfer legs and longer conversations | Which events start and stop each meter? |
| Per call | You want a simpler volume-based allowance | Spam, short calls, repeat callers and calls that accomplish nothing | What is a billable call, and which calls receive credits? |
| Subscription with included usage | Demand is predictable enough to value committed capacity | Underused allowances, overages and peak restrictions | What happens in both a quiet month and a surge month? |
| Per booking or qualified lead | The commercial outcome can be unambiguously verified | Duplicates, ineligible jobs, cancellations and disputed attribution | Which system proves eligibility and completion? |
| Per resolution | Buyer and supplier agree on what a resolved task means | Premature closure and unresolved repeat contact | When is an outcome final, and when is a charge reversed? |
| Project plus managed-service retainer | You want explicit implementation and ongoing operating work | An attractive setup fee followed by undefined change charges | Which changes, tests and incidents are included each month? |
Our recommendation is to require a sample invoice for a deliberately awkward month: low utilisation, a seasonal peak, long calls, transfers, integration failures and repeat contact. A billing model that is easy to explain can still price the wrong result.