Contents
- Fast answer
- Quick facts
- What this covers
- Why it matters
- Where to go next
- Outcomes
- Step by step
- How pricing now separates chatbots from support agents
- What actually counts as a billable resolution
- Cost math at realistic ticket volumes
- What changed recently and how to decide
- At a glance
- Mistakes to avoid
- FAQ
- Related guides
Fast answer
Start where the bottleneck is: a customer support chatbot mainly responds in a conversation, while a support AI agent can triage tickets, retrieve context, draft replies, classify urgency, route issues, suggest refunds or actions, and surface knowledge-base gaps when designed with approvals. Use a chatbot for front-door questions, collecting basic details and deflecting simple requests when the knowledge base is strong. Use an agent for ticket operations such as summarizing history, classifying ticket type, drafting responses, escalating edge cases, and creating internal notes. The core tradeoff is that support teams often buy chat widgets when the bigger bottleneck is back-office work, so comparing the two helps you automate the right layer without sacrificing customer trust. Keep sensitive actions reviewed, including refunds, cancellations, angry customers, legal, medical, or financial claims, and account changes. Measure quality rather than deflection alone, tracking first response time, resolution time, escalation accuracy, CSAT, QA pass rate, and knowledge-base gaps found.
Facts last verified 2026-07
Quick facts
- Intercom Fin price
- $0.99 per resolution; on non-Intercom helpdesks, $49/mo base including 50 resolutions
- Zendesk AI agents price
- About $1.50 per automated resolution committed, about $2 pay as you go
- HubSpot Breeze Customer Agent
- $0.50 per resolved conversation since April 2026
- Flat-fee chatbot example
- Zapier Chatbots Pro at $160/yr for 5 chatbots, no per-conversation meter
- Billable event risk
- Each vendor defines a resolution differently; only Zendesk Verified Resolutions are billable there
- Cheapest architecture at scale
- Flat-fee chatbot for FAQs, per-resolution agent for tickets, humans for escalations
On this page
What this page covers
A comparison visitor should understand the tradeoff, the best-fit scenario, and the next diagnostic tool to confirm the choice.
- 01Quick verdict
- 02Definitions
- 03Ticket triage
- 04Answer quality
- 05Escalations
- 06Metrics
Why does this matter now?
Support teams often buy chat widgets when the bigger bottleneck is back-office support work. Comparing chatbots and agents helps teams automate the right layer without sacrificing customer trust. A chatbot mainly answers in the conversation, while a support AI agent can triage, retrieve context, draft, classify, route, and take actions behind the scenes, so the two solve different problems. Choosing the wrong layer means paying for automation that does not touch where your agents actually lose time, or exposing customers to an unreviewed system that erodes trust.
Internal path
Where to go next from this page
These links are part of the A8gent learning and conversion path. Use them to move from concept, to diagnosis, to workflow build, to course.
What you should be able to do after this
- Separate chatbots from agents
- Choose first support workflow
- Protect escalation quality
- Measure support impact
How do you do it, step by step?
1. Find where the bottleneck actually is
Look at where your team loses hours: answering repetitive front-door questions, or triaging, summarizing, and drafting inside tickets. If customers ask the same simple things, a chatbot deflects them, but if agents burn time on ticket operations, a support AI agent targets the real cost. Measure this before buying, since the widget and the agent solve different bottlenecks.
2. Map the two workflows separately
Write out the front-door conversation flow a chatbot would handle and the back-office ticket flow an agent would handle. A chatbot answers common questions, collects basic details, and deflects when the knowledge base is strong, while an agent summarizes history, classifies ticket type, drafts responses, escalates edge cases, and writes internal notes. Seeing both flows on paper shows which layer to automate first.
3. Audit your knowledge base quality
Both a chatbot and an agent are only as good as the content they read, so check how current and complete your help content is. A chatbot answering from stale articles will confidently mislead customers, and an agent drafting from the same content will do the same at scale. Fix obvious gaps before automating anything customer-facing.
4. Define escalation and approval rules
Decide which cases must reach a human: refunds, cancellations, angry customers, legal, medical, or financial claims, and account changes. Give the chatbot clear handoff triggers and require approval for any agent action that changes an account or issues money. These rules protect customer trust while automation matures.
5. Compare cost against the value each creates
Weigh the price of a chat widget plus content upkeep against the price of an agent that acts across your ticketing system. A cheap chatbot that only deflects easy questions may leave the expensive work untouched, while an agent costs more but attacks the real time sink. Judge each against the hours it actually saves, not its sticker price.
6. Pilot on real tickets with review
Run the candidate on real historical tickets or a small live slice with a human reviewing every output. Watch how it handles ambiguous, emotional, and edge-case conversations rather than the clean examples in a demo. This pilot reveals whether it is ready for customers or needs tighter guardrails.
7. Measure quality, not just deflection
Track first response time, resolution time, escalation accuracy, CSAT, QA pass rate, and knowledge-base gaps the agent surfaces. A high deflection rate that lowers satisfaction is a loss, not a win. These metrics tell you whether to expand automation or pull it back.
8. Decide, then expand gradually
Pick the layer that matches your bottleneck and start narrow, such as one ticket type or one set of questions. Widen scope only as the quality metrics hold and reviewers trust the output. Many teams end up running a chatbot at the front door and an agent behind it once both prove out.
How pricing now separates chatbots from support agents
The clearest way to tell a chatbot from a support AI agent in 2026 is to read the invoice. Chatbots are priced flat or per seat: Zapier Chatbots Pro, for example, costs 160 dollars per year for 5 chatbots with no per-conversation meter. Support AI agents are priced per result: Intercom's Fin charges 99 cents per resolution, Zendesk's AI agents run roughly 1.50 dollars per automated resolution on committed plans and around 2 dollars pay as you go, and HubSpot's Breeze Customer Agent charges 50 cents per resolved conversation.
That pricing split reflects a real capability split. A flat-fee chatbot answers from your content and hands off anything hard, so vendors can afford to sell it like software. An agent that reads ticket history, executes procedures, and closes conversations end to end creates measurable labor savings, so vendors price it like labor. When a product bills per resolution, it is claiming to finish work, and you should evaluate it against that claim.
For buyers this means the build-versus-buy math changed. Per-resolution pricing gives you a precise ceiling for what a self-built alternative is worth: an agent assembled on n8n, from 20 euros per month on cloud or free self-hosted, plus direct model costs, competes against a bill of roughly 1 dollar per resolved ticket. At low volume, buying is obviously simpler. At tens of thousands of monthly resolutions, the per-outcome bill becomes a number that justifies serious engineering.
What actually counts as a billable resolution
The word resolution hides most of the pricing risk, because each vendor defines the billable event differently. Intercom bills 99 cents for three outcome types: a resolution, a procedure handoff, and a disqualification, and bills 9.99 dollars for a lead qualification outcome. Zendesk splits automated interactions into three tiers, where assisted escalations and contained resolutions are free and only a Verified Resolution is billable. HubSpot bills only when a conversation is resolved rather than per conversation started, which is exactly what changed in April 2026.
These definitions decide your bill more than the headline rates do. An agent that confidently marks conversations resolved when customers actually gave up will look cheap per ticket and expensive per happy customer. Before signing, get the vendor's written definition of the billable event, then audit a sample of billed outcomes monthly against your own quality review. Deflection that customers experience as abandonment is a cost, not a saving, even when the meter calls it a resolution.
Also check the floor charges. Fin deployed on a non-Intercom helpdesk carries a 49 dollar per month base that includes 50 resolutions, with additional outcomes at 99 cents. Committed-volume plans at Zendesk price resolutions lower than pay-as-you-go, which rewards accurate volume forecasting and punishes optimism. If your ticket volume is seasonal, model the January trough and the December peak separately before choosing between committed and usage pricing.
Cost math at realistic ticket volumes
Work an example with verified unit prices and your own assumptions. Suppose 2,000 monthly conversations and suppose the agent fully resolves 800 of them. On Fin that is about 792 dollars per month at 99 cents per resolution. On Zendesk committed pricing at roughly 1.50 dollars per verified resolution, about 1,200 dollars. On HubSpot Breeze at 50 cents per resolved conversation, about 400 dollars. The spread between the cheapest and priciest option at identical performance is roughly three to one, before negotiation.
Now compare that against the labor baseline. If those 800 conversations would have consumed human agent time at your loaded support cost, per-resolution pricing in the 50 cents to 2 dollars range is usually a fraction of the human cost per ticket, which is why adoption is broad despite meter anxiety. The genuinely important variable is the resolution rate itself: an agent resolving 15 percent of conversations changes little, while one resolving 40 percent restructures the queue, and vendors quote wildly different rates depending on knowledge-base quality.
A flat-fee chatbot changes this math only at the front door. If a knowledge-base bot deflects the easy 20 percent of contacts for a fixed yearly fee, it lowers the volume that ever reaches the per-resolution meter. That is why the cheapest architecture at scale is often layered: flat-fee chatbot for FAQs, per-resolution agent for real ticket work, and humans for everything the definitions above would count as an escalation. Price each layer separately and the stack usually beats any single product.
What changed recently and how to decide
The 2025 to 2026 period made outcome pricing the support-AI default. HubSpot's April 14, 2026 move from 1 dollar per conversation to 50 cents per resolved conversation was the loudest example, and Intercom's positioning of Fin as deployable on non-Intercom helpdesks turned per-resolution agents into something you can bolt onto Zendesk or other desks rather than a reason to switch platforms. Competition on the per-resolution price itself is now visible between vendors, which favors buyers who benchmark.
Decide by bottleneck and volume. Under a few hundred monthly conversations, a flat-fee or bundled chatbot plus a good knowledge base is usually enough, and per-resolution products cannot save you much because there is not much to save. From roughly a thousand conversations per month, pilot a per-resolution agent on one ticket category with human review, measure the true resolution rate yourself, and only then extrapolate the annual bill.
Finally, negotiate with the meter in mind. Per-outcome vendors know their pricing scales embarrassingly at high volume, and committed tiers, category exclusions, and definition adjustments are all negotiable at renewal. Bring your audited resolution data to that conversation. A team that knows its real resolution rate, its cost per resolved ticket, and its customer satisfaction on bot-closed tickets negotiates from strength; a team that only knows the headline price does not.
At a glance
Support chatbot vs AI agent pricing snapshot, July 2026
| Option | Model | Published price | Billable event |
|---|---|---|---|
| Intercom Fin | Per outcome | $0.99 per resolution | Resolution, procedure handoff, or disqualification |
| Fin on other helpdesks | Base plus per outcome | $49/mo including 50 resolutions, then $0.99 | Same outcome definitions |
| Zendesk AI agents | Per resolution | About $1.50 committed, about $2 pay as you go | Verified Resolution only |
| HubSpot Breeze Customer Agent | Per outcome | $0.50 per resolved conversation | Conversation resolved by the agent |
| Zapier Chatbots | Flat fee | Pro at $160/yr for 5 chatbots | None per conversation |
| Self-built agent on n8n | Platform plus tokens | From EUR 20/mo cloud or free self-hosted | Workflow executions plus LLM usage |
What mistakes should you avoid?
- Buying a chat widget when the real bottleneck is back-office ticket work
- Letting a chatbot or agent answer from stale support content
- Optimizing for ticket deflection at the expense of customer experience
- Failing to define escalation rules for sensitive or emotional cases
- Giving the system account-change or refund permissions too early
- Measuring only deflection instead of resolution quality and CSAT
FAQ
- What is the difference between a support chatbot and an AI agent?
- A chatbot mainly responds inside a conversation, answering questions and collecting details. A support AI agent can also triage tickets, retrieve context, draft replies, classify urgency, route issues, and take approved actions. The agent works behind the scenes on ticket operations, not just the front-door chat.
- Should support teams start with a chatbot or an AI agent?
- Start where the bottleneck is. If customers ask repetitive questions, a chatbot may help most, but if agents spend their time triaging, summarizing, and drafting, an AI agent creates more value. Measure where the hours actually go before choosing.
- Which is cheaper to run?
- A chatbot is usually cheaper up front but only pays off if it deflects real volume against a strong knowledge base. An agent costs more but can attack the expensive back-office work a chatbot never touches. Compare each against the hours it saves rather than its price alone.
- Which is easier to deploy safely?
- A chatbot confined to answering vetted questions is easier to launch with low risk. An agent that can act on tickets needs stronger escalation and approval rules before it touches accounts or refunds. Start the agent in a draft-and-review mode until quality holds.
- Can we start with one and add the other later?
- Yes, and many teams do exactly that. A common path is a front-door chatbot first, then a back-office agent once the knowledge base and review process are solid. Keep the escalation rules consistent so both hand off to humans the same way.
- Can a support AI agent update the knowledge base?
- It can suggest updates and flag gaps it hits while drafting answers. Publishing those changes should usually stay reviewed by a human until the workflow has strong quality controls. Treat the agent as a gap-finder, not an autonomous editor, early on.
Sources & further reading
Done for you
Want this built for your business?
Tell us the workflow. We scope, build, and ship the agent with guardrails and the numbers to prove it worked. The scoping call is free.
Free scoping call. You own the code.
Was this page helpful?

