Capacity Pricing Explained (2026)
Capacity publishes tiers but no prices — the structure is a platform fee plus usage-based AI agent charges metered four different ways, per response, per minute and per message.
| Plan | Price | Billing | What you get |
|---|---|---|---|
| Core | Talk to sales | platform fee plus usage, quoted | Knowledge base, helpdesk, AI Agent Builder, data indexing, 250+ integrations, analytics and up to 100GB storage |
| Pro | Talk to sales | platform fee plus usage, quoted | Everything in Core plus live chat, inbox, real-time Agent Assist, conversation intelligence, AQA, the developer platform and up to 1TB storage |
| Enterprise | Talk to sales | platform fee plus usage, quoted | Everything in Pro plus campaigns, CRM, advanced workflows, an optional HIPAA package and up to 2TB storage |
| Chat and Email AI Agents | Per response | usage-based, volume discounts available | Metered on responses generated rather than conversations received or agents employed |
| Voice AI Agent | Per minute | usage-based, volume discounts available | Voice automation metered by minute — the meter most likely to dominate for phone-heavy operations |
| SMS AI Agent | Per message | usage-based, volume discounts available | SMS automation metered per message, separate from chat and email response pricing |
A platform fee and four meters
Capacity states its pricing structure clearly even though it publishes no numbers: your investment includes a platform fee plus usage-based pricing for AI Agents, so you pay for what you use.
What makes it more complicated than that sentence suggests is that "usage" is measured four different ways. Chat AI Agent bills per response. Email AI Agent bills per response. Voice AI Agent bills per minute. SMS AI Agent bills per message. These are separate meters with separate rates, and they do not share an allowance.
For a single-channel deployment that is simple enough. For an organisation running automated support across chat, email, voice and SMS — which is the deployment Capacity is designed for — there are four independent usage lines accruing at once, plus the platform fee underneath.
What the tiers actually contain
| Core | Pro | Enterprise | |
|---|---|---|---|
| Knowledge base, helpdesk, AI Agent Builder | ✓ | ✓ | ✓ |
| Data indexing, 250+ integrations, analytics | ✓ | ✓ | ✓ |
| Live chat, inbox, real-time Agent Assist | — | ✓ | ✓ |
| Conversation intelligence, AQA, developer platform | — | ✓ | ✓ |
| Campaigns, CRM, advanced workflows | — | — | ✓ |
| Optional HIPAA package | — | — | ✓ |
| Storage | 100GB | 1TB | 2TB |
The storage row deserves more attention than it usually gets. Capacity's function is indexing your knowledge — documents, policies, product data — so the AI can answer from it. Storage is therefore a measure of how much corpus the system can reason over, not a background infrastructure detail. Organisations with large document estates may find storage, rather than features, is what sets their tier.
Agent Assist is the second dividing line. Core automates customer-facing interactions; Pro adds real-time assistance to your human agents. Those are different value propositions, and knowing which one you are buying determines whether Core is sufficient.
The HIPAA problem
The optional HIPAA package is available only on Enterprise. That is a common packaging pattern and it produces a specific outcome: a small healthcare support team that needs nothing from Enterprise except compliance still buys Enterprise.
If that is you, raise it explicitly and early. Vendors frequently have room to move on compliance packaging for customers who are otherwise a Pro-sized deployment, but only if you ask before the quote is written.
Negotiating against no published price
Capacity's volume discount language — the more you use, the less you pay per interaction — is a statement of intent rather than a rate. Nothing is quantified publicly, on any tier or any meter.
That makes preparation the only leverage available. Before the sales call, model four numbers: monthly chat responses, monthly email responses, monthly voice minutes and monthly SMS messages. Then ask for the platform fee and each of the four unit rates as separate figures, along with the volume thresholds where discounts begin.
A blended monthly quote is easy to accept and impossible to evaluate. With four meters running, you need to know which one is driving your cost, because that is the one to negotiate and the one that will grow.
Beware the figures floating around
Third-party pricing pages carry numbers attributed to Capacity that on inspection belong to other vendors — per-agent rates and session-bundle prices that match competitors' published pricing rather than anything Capacity has stated. Treat any specific figure you find online with suspicion unless it comes from Capacity directly.
Who should and should not buy this
Capacity fits mid-sized and larger organisations with a substantial knowledge estate and genuine multichannel support volume — the profile where indexing documents and automating across chat, email, voice and SMS produces measurable deflection. The AI Agent Builder and 250+ integrations point at teams that want to configure rather than code.
It fits poorly for small teams with single-channel support, where the platform fee plus a usage meter is more structure than the problem requires. It fits poorly for buyers who need to compare prices before engaging with sales, since none exist publicly. And it fits poorly for anyone who needs a predictable flat monthly cost, because four simultaneous usage meters is the opposite of that.
Capacity publishes tier contents but no rates. Confirm the platform fee, all four unit rates and volume thresholds directly with Capacity before budgeting.
What the pricing page doesn't show
- Four different AI meters run simultaneously — per response for chat, per response for email, per minute for voice, per message for SMS. A multichannel deployment is being billed four ways at once, and the channels do not share an allowance.
- No published rates on any tier or any meter means there is no anchor for negotiation and no way to model cost before a sales conversation.
- Storage tiers of 100GB, 1TB and 2TB are among the few concrete differentiators between plans. On a product built around indexing your document corpus, storage is a functional limit rather than a technicality.
- The HIPAA package is optional and Enterprise-only, so any healthcare deployment is on the top tier by default regardless of size or feature needs.
- Volume discounts are stated but not quantified. 'The more you use, the less you pay per interaction' is a negotiating position, not a rate card.
