← Back to Blog
Pricing
9 min read
Apr 16, 2026
AI Response vs Per-Seat Pricing: What Your AI Really Costs in 2026
Per-seat AI pricing hides your real bill behind seat minimums. Per-resolution pricing hides it behind definitions of "resolution." AI response pricing is cleaner — but only if you understand what counts. Here's how each model actually works, and which one aligns cost with value.
Three pricing models, three very different bills
If you've been shopping AI platforms in the last year, you've probably seen quotes that don't look anything like each other. That's because vendors are using three fundamentally different billing units, and the cheap-looking number at the top of the page can balloon fast depending on which one you pick.
The three you'll run into:
- Per-seat. You pay per human who logs into the dashboard. Think Intercom, HubSpot Service Hub, Drift, Salesforce Service Cloud.
- Per-resolution. You pay every time the AI "resolves" a conversation. Think Intercom Fin, Ada, Breeze Agent, Salesforce Agentforce.
- Per AI response. You pay per AI reply the agent generates. That's the model Kazozo uses.
None of these is secretly evil. But each one aligns cost with a different thing, and mismatches produce ugly surprises at renewal.
Per-seat pricing: the seat-minimum trap
Per-seat is the familiar SaaS model — $X per user per month. The pitch is clean: you only pay for the team members who need access. The trap is two-fold:
Seat minimums. Many vendors require 3, 5, or 10 seats to unlock the tier that has the AI. A 5-seat minimum at $90/seat is $450/mo whether you have two people or five. If your goal is "get an AI on my website" — a customer-facing capability, not an internal one — per-seat is asking you to pay for people who don't need dashboard access to deliver the feature you want.
The AI isn't the seat feature. When you buy a seat on an old-school support tool, the seat is the thing. When you buy a seat on an AI-ified support tool, you're paying for the seat and usage fees on top. The seat math looks cheap compared to per-response pricing, right up until you realize the AI resolutions are billed separately.
Per-seat makes sense when your actual job is giving your team access to a shared CRM. It stops making sense when the job is "put a conversational AI on my website and phone."
Per-resolution pricing: the definition problem
Per-resolution pricing sounds value-aligned — you pay when the AI actually solves something. In practice, "resolution" is defined by the vendor, and the definition matters a lot.
Common definitions seen in the wild:
- A conversation the AI handled without escalating to a human (even if the customer left without an answer)
- A conversation where the customer clicked "resolved" (but most customers never click)
- A conversation that didn't create a support ticket in the next 7 days (proxy for deflection)
- Any conversation with at least one AI reply, regardless of outcome
Pricing ranges from roughly $0.50 to $1.50+ per resolution. The spread matters. A site doing 3,000 qualified conversations a month at $0.99/resolution is $2,970 — before seats.
The subtle kicker: resolution-based pricing rewards the vendor when the AI doesn't escalate. That's usually fine, but it can nudge product decisions toward "keep the customer in the AI" rather than "hand off cleanly." Always ask: what happens on escalation? Is that conversation still a billable resolution? You'd be surprised how often the answer is "yes."
Per AI response pricing: what it is and what to check
Per-AI-response is cleaner: the agent generates a reply, you pay for that reply. One AI reply = one billable unit. It's the model Kazozo uses.
The advantages:
- Unambiguous. A response is a response. There's no definitional fuzziness.
- Aligned with the work. You're paying for the AI to do its job, not for humans who aren't using it.
- Predictable from volume. If you know your monthly conversation volume, you can estimate cost without calling sales.
Things to check before signing any per-response contract:
- What counts as "the AI responded"? An AI reply with text, yes. An auto-greeting? Usually no. Make sure the vendor answers this in writing.
- Are responses capped, metered, or included? On Kazozo: Starter includes 500 AI responses/mo at $249, Growth includes 2,000 at $499, Pro includes 6,000 at $999. Overages are predictable — $0.40/response on Starter, $0.30 on Growth, $0.22 on Pro.
- Does the agent still respond when you hit the cap? It should — no one wants a hard stop on customer conversations. Confirm overage behavior.
- Are internal-user responses billable? If someone on your team triggers an AI reply during testing, does that count against your allotment? Usually not, but verify.
Cost comparison: a realistic 5-person SMB scenario
Imagine a home-services business doing 1,500 website conversations a month and 300 inbound phone inquiries. You want AI handling both. Here's how the three models shake out:
Per-seat (Intercom-style)
- 5 seats × ~$99/mo = ~$495/mo just to unlock the AI tier
- Plus per-resolution fees on the AI conversations layered on top
- Typical all-in: $1,500–$3,000/mo at that volume
Per-resolution only (Ada-style, no seats)
- 1,500 conversations × $0.99/resolution = $1,485/mo on chat alone
- Voice typically billed separately at $1–$2/answered call
- Definitions vary; escalated-but-not-resolved conversations may still bill
Per AI response (Kazozo)
- Growth plan: $499/mo flat, 2,000 AI responses included (overages $0.30/response)
- No seat minimums; no separate AI reply credits; Voice Agent is Pro plan
- If you bust the included responses, overages are pennies per reply
At this volume, per-AI-response is 2–6× cheaper than per-seat with resolution overlays, and it's the only one where the bill is obvious before renewal. The ROI calculator lets you plug in your actual volume.
How to audit your AI bill (or a quote you're evaluating)
Before you sign any AI platform contract, get five things on paper:
- The billing unit, defined precisely. "Conversation," "resolution," "response," and "message" all mean different things to different vendors.
- What doesn't count. Auto-greetings, template replies, human-agent messages, internal team traffic — get the exclusions in writing.
- Seat minimums and billing tier thresholds. If the AI lives behind a higher tier, the real floor is "tier × min-seats" not "$X per seat."
- Overage pricing. If you exceed the included amount, what's the per-unit cost? Is it tiered? Does it reset monthly?
- Escalation behavior. When the AI hands off to a human, does the conversation keep billing? Stop billing? Get bundled? This affects your total more than you'd expect.
If the sales team can't answer any of these in a single email, that's your answer: the pricing model isn't clean enough for an SMB budget.
When per-seat is still the right call
Being fair: per-seat isn't always the enemy. If your entire team lives inside a shared CRM — SDRs working the pipeline, reps running sequences, managers pulling reports — per-seat charges for the thing you're actually using. Intercom, HubSpot Service Hub, and Salesforce are all good CRMs; their per-seat models make sense if the CRM is the product.
What doesn't make sense is paying a per-seat premium to unlock a customer-facing AI feature. That's a mismatch between billing unit and the job to be done.
The bottom line
AI response pricing isn't automatically the cheapest — it's the most legible. You can read your bill and know exactly why it's what it is. Per-seat and per-resolution models can work out fine, but only when you've asked the five audit questions above and written the answers into the contract.
If you want to see per-response pricing running on your actual volume — for both chat and voice — book a 20-minute demo. We'll pull your real traffic numbers and show you what the monthly bill would look like on Starter, Growth, and Pro.