Platform fee
Related terms
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.
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.
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.
Total cost of ownership
Total cost of ownership (TCO) is the full cost of acquiring, running, and eventually replacing a system over a set multi-year period, not just its subscription or usage fee. For an AI deployment, TCO includes license or usage fees, implementation, integration with existing systems, data preparation, staff training, ongoing admin time, change management, and exit or migration costs. Buyers routinely leave out several of these lines when they compare vendors, which makes license price alone a misleading basis for a decision. Consolidation is a practical TCO lever. Replacing separate ticketing, chat, chatbot, and voice tools with one platform, such as an AI support agent running across an omnichannel inbox, removes duplicate integration work, duplicate admin overhead, and duplicate training cycles. A contact center comparing five point tools against one consolidated platform over a multi-year period should weigh total cost of ownership across all these categories, not just each tool’s sticker price. The cheaper-looking option on paper can cost more once implementation, integration, and admin time get added in.
