Fair usage policy
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.
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.
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.
Per-seat pricing
Per-seat pricing charges a fixed fee per named or concurrent user over a billing period, no matter how much that user does. Named-seat licensing assigns access to one specific person. Concurrent licensing caps how many people can log in at once, a limit teams sometimes share across shifts. Its main appeal is budget predictability: finance can forecast cost from headcount alone, which keeps procurement simple. The friction shows up with AI software like Agent Assist or an omnichannel inbox, where agents resolve conversations without ever occupying a seat. Per-seat pricing can undercharge for AI-driven work, or push teams to ration logins during a seasonal peak, only to true up seat counts after volume drops. See usage-based pricing and outcome-based pricing for models built around actual work performed.
