AI Shortlist · Guides
AI support pricing looks cheap per unit and expensive per month. The only way to know which one you're getting is to run the deflection math on your own ticket volume.
| Model | How it works | Best for |
|---|---|---|
| Per resolution | A few cents to ~$1.50 for each conversation the bot closes without a human | Lumpy volume; low commitment |
| Per seat | A monthly price per support agent on the plan | Stable teams already paying for a helpdesk |
| Platform + usage | Base fee plus metered conversations | High volume after the bot is proven |
Rates change often and vary by vendor and contract size — always re-check the current published terms before signing.
Work out what one human-resolved ticket costs you today:
| Realistic deflection | What it needs |
|---|---|
| 10–25% | Good FAQs and a clean help centre — most teams land here |
| 30–45% | Strong documentation plus order/account lookups wired in |
| 50%+ | Narrow, repetitive support (few question types, low edge-case count) |
Anyone promising 80% deflection has either a very narrow product or a very loose definition of "resolved".
• Paying per resolution without measuring resolution. Ask how they count a "resolved" ticket — and whether you can see the transcript.
• Hiding the human exit. If customers cannot reach a person in two clicks, angry tickets cost more than the bot saves.
• Training on stale docs. The bot is only as current as your help centre. Budget an update habit.
• Ignoring containment quality. A fast wrong answer is worse than a slow right one.
• Annual contracts before proof. Run one paid month first.
Buy when your monthly human cost for a repetable ticket category is at least 3× the projected bot spend — and only after you know your real ticket volume. Below that, answer your own FAQs better; it's free and it also improves the bot later.