Credit-based pricing

Credit-based pricing is a model in which a buyer prepays for a pool of credits, then draws it down as different actions consume different credit amounts. The credit acts as a conversion layer that abstracts away varied unit costs across features. Customers manage one balance instead of several metered line items. Contracts typically define expiry windows, whether unused credits roll over, and terms for topping up before the pool runs out. This differs from usage-based pricing, which bills for consumption after the fact rather than drawing down a prepaid balance. Example: a support team's credits may deplete at different rates across channels such as voice and chat, since each action, like a voice minute handled by an AI voice agent versus a chat reply, can carry a different credit cost. Finance teams tracking burn rate usually want a monthly consumption report broken out by channel.

Credit-based pricing is a model in which a buyer prepays for a pool of credits, then draws it down as different actions consume different credit amounts. The credit acts as a conversion layer that abstracts away varied unit costs across features. Customers manage one balance instead of several metered line items. Contracts typically define expiry windows, whether unused credits roll over, and terms for topping up before the pool runs out. This differs from usage-based pricing, which bills for consumption after the fact rather than drawing down a prepaid balance. Example: a support team's credits may deplete at different rates across channels such as voice and chat, since each action, like a voice minute handled by an AI voice agent versus a chat reply, can carry a different credit cost. Finance teams tracking burn rate usually want a monthly consumption report broken out by channel.

Related terms

Platform fee

A platform fee is the fixed, recurring charge a vendor bills for access to the core software environment, separate from usage-based charges and per-seat licences. It typically covers the hosting environment, core modules, standard support, and standard integrations. It usually excludes overage charges, premium support tiers, and professional services such as implementation or custom configuration. Buyers should ask vendors exactly which modules, support levels, and integrations sit inside the platform fee versus which are billed separately, since the label varies by vendor and bundling differs widely across contracts. A contact centre might pay a flat monthly platform fee for its ticketing and routing environment, then pay variable charges on top based on conversation volume or resolved cases. Reading the fee schedule line by line before signing avoids surprise invoices later.

Fair usage policy

A fair usage policy is the contractual clause that caps consumption under an otherwise "unlimited" or generously bundled plan. It defines what counts as excess and what the vendor may do once a customer crosses it: throttle performance, apply overage charges, or trigger a renegotiation of the contract. Vague language such as "reasonable use" leaves enforcement to the vendor's discretion. Buyers should insist the threshold be written as a specific number, not a general principle. Example: an "unlimited seats" support plan that caps each seat at a fixed number of conversations per month, with defined pricing or escalation once that ceiling is reached. Asking for the exact cap in writing before signing avoids a dispute later over what "fair" actually meant.

Usage-based pricing

Usage-based pricing charges customers for measured consumption of a value metric, such as conversations, minutes, messages, or tokens, rather than a flat per-seat fee. Contracts for tools like an AI support agent or AI voice agent usually combine a committed minimum volume with an overage rate for consumption above that threshold. Some agreements let unused volume roll over. Because support volume can spike sharply (a product recall driving a sudden surge in chat volume, for example), usage-based pricing shifts budget volatility onto the buyer. It differs from outcome-based pricing, which charges only for successfully resolved contacts. Buyers should check overage rates, rollover terms, and true-up timing before they sign.

Outcome-based pricing

Outcome-based pricing charges a customer only when a defined business result happens, not for seats provisioned or volume consumed. Common outcome units in support operations include a resolved ticket, a contained contact, or an avoided escalation. Because payment depends on the result, contracts need clear rules for measurement, attribution, and audit set in advance. Vendor and customer can define “resolved” differently, which creates dispute risk without agreed evidence. For an AI support agent handling full resolutions on its own, a company might pay per ticket resolved end-to-end, with AI QA scoring giving the audit trail that backs each outcome. This differs from usage-based pricing, which scales with activity no matter the result, and from per-seat pricing, which charges a fixed fee per licensed user no matter what gets delivered.

LLM token

A token is the basic unit a large language model, or LLM, reads and writes. A token is typically a word fragment, not a whole word. Both input and output tokens count toward usage. The prompt, any retrieved knowledge-base content, and the model’s reply all add up to the total. Usage-based AI pricing is commonly tied to token volume, so conversation length, system prompts, and retrieved context all affect cost. Example: passing a long call transcript to a model for quality scoring consumes far more input tokens than a short chat exchange does. A ten-minute call transcript might use thousands of tokens before the model even produces a response. Every model also has a fixed context window, which is the maximum number of tokens it can process at once. That limit controls how much transcript or history the model can consider, and it factors directly into latency.

OnClarity

5,000 free AI support resolutions for startups

Startups in the US, UK and Europe with under 200 staff get 5,000 free resolutions from OnClarity’s AI support agent as their trial.

Apply for the Startup Program

Open until 31 March 2027 or until 50 startups are approved.

OnClarity

5,000 free AI support resolutions for startups

Startups in the US, UK and Europe with under 200 staff get 5,000 free resolutions from OnClarity’s AI support agent as their trial.

Apply for the Startup Program

Open until 31 March 2027 or until 50 startups are approved.

OnClarity

5,000 free AI support resolutions for startups

Startups in the US, UK and Europe with under 200 staff get 5,000 free resolutions from OnClarity’s AI support agent as their trial.

Apply for the Startup Program

Open until 31 March 2027 or until 50 startups are approved.