guide

Do You Need an AI Agent on Top of Your Help Desk?

Help desk is the only category here that splits three ways, and that is the whole problem

By AR · Published 16 August 2026 · 8 min read

This question has one honest answer and it is not the one being published. Search it and you get guides from Fin, from Crescendo, from Twig, from My AskAI. Every one of them sells the agent that goes on top. Their answer is yes.

The reason the question is hard is not that the vendors are lying. It is that help desk is the only category in this directory where the built-in AI means three genuinely different things, and the pricing pages describe all three with the same vocabulary.

Three products, one phrase

"Help desk with AI" describes a product that resolves a ticket without a human, a product that writes a good answer from your documentation and moves nothing, and a product that drafts a reply for an agent to check and send.

Those are different purchases with different economics. The first can reduce headcount. The second reduces how long a reply takes to write. The third reduces how long it takes to type. Only the first is what people mean when they say AI agent, and it is the minority of the category.

Which one each help desk actually ships

What its built-in AI doesPlatformsPublishes a price
Can change something in your systemsissues the refund, updates the order, closes the ticketZendesk AI Agents, Zoho Desk, Pylon, Plain, Kustomer, Gladly Sidekick, DevRev3 of 7 (43%)
Answers from your documentationa good answer, but nothing in your systems movesFreshdesk with Freddy AI, Help Scout, Hiver, Re:amaze4 of 4 (100%)
Drafts for a human to senda person still reads it and presses sendHappyFox, Front, SupportLogic3 of 3 (100%)

Classified from each vendor’s own documentation, not from its marketing page. Where the two disagree, the tool page says so.

The second column is the answer to the question in the title. If your help desk sits in the top row, its built-in AI is doing the job a separate agent would do, and buying one is paying twice unless you have a specific reason the built-in one fails. If it sits in either of the other two rows, no amount of configuration turns it into a resolving agent, and the separate purchase is the only route.

Notice the third column too. Every platform in this category whose AI does not resolve publishes its price. Fewer than half of the ones that do resolve are willing to. The capability that would let you skip the separate purchase is the one you have to phone somebody about.

Count the meters, not the seat price

The seat price is the number everyone compares and it is the smaller half of the bill. What decides the total is how many separate meters run at once, and that varies more between these fourteen than the seat rate does.

Plain runs one. Foundation is $35 a month for a seat and Horizon is $299 for three, and the Ari agent is included on every tier. There is no second line item, because the agent is the product rather than an attachment to it.

Front runs four. Seats at $25, $65 and $105, then Copilot at $20, Smart QA at $20, Smart CSAT at $10, and Autopilot from $0.05 a conversation. Every one of those is published, which is more than most of the category manages, and a team that buys the bundle is still paying on two axes at once.

Zendesk runs two and states both: $19, $55 and $115 an agent, and Copilot a further $50. Freshdesk runs three, with Freddy including the first 500 sessions and charging $49 per 100 after that, plus Copilot at $29 an agent. Re:amaze charges $0.85 a resolution past an allowance of five, ten or twenty per user, which is small enough that $0.85 is the real rate rather than an overage.

HappyFox publishes $24, $49 and $99 an agent and does not price its AI at all. The seats are on the page and the meter that matters is not, which is the pattern the top row of the table is full of.

Where paying twice actually happens

The first case is straightforward. You buy a resolving help desk and bolt a resolving agent onto it, usually because the agent was evaluated before anyone checked what the help desk had shipped in the previous eighteen months. Several platforms in the top row added autonomous resolution recently enough that an evaluation from last year is out of date.

The second is subtler and more common. You buy a separate agent to sit on a help desk in the documentation row, which is correct, and then keep paying the help desk's AI add-on as well. Two meters, one job. The add-on was bought to answer questions and the agent now answers them.

When the built-in one is genuinely enough

If most of your volume is questions whose answers already exist in writing, a documentation-answering AI on the help desk you already run will handle a large share of it, and it will do so at a published price you can forecast.

The case for the separate agent gets strong when your volume needs something to happen. An order changed, a subscription cancelled, a refund issued. That is the line the classification above is drawn on, and it is a better shortlist filter than any feature comparison, because a feature list will tell you a tool has a Shopify integration without telling you whether it can write to it.

The question to ask either vendor

Ask both the help desk and the agent vendor to name one thing their AI changes in a system of record, and to point at the documentation for it. Not the marketing page. The vendors in the top row can do this in a sentence. The ones that cannot are telling you which row they are in.

Classified from each vendor's own documentation rather than its marketing page, because on this question the two frequently disagree. Where they do, the tool page publishes both.

Frequently Asked

Is my help desk's built-in AI good enough, or do I need a separate AI agent?

It depends which of three things your help desk's AI actually is. Half the help desks in this directory ship AI that can resolve a ticket by changing something in a system. The rest either answer from your documentation or draft a reply for a human. If yours resolves, a separate agent is probably paying twice. If it answers or drafts, no configuration turns it into a resolving agent and a separate purchase is the only route.

Why does everyone say I need a separate AI agent on my help desk?

Because almost everyone publishing on this question sells one. Searching it returns guides from agent vendors, including the largest one in the category. That does not make them wrong, but none of them classify what the help desks have already shipped, and several help desks added autonomous resolution recently enough that a comparison written last year is out of date.

How do I tell whether a help desk's AI actually resolves tickets?

Ask the vendor to name one thing its AI changes in a system of record and point you at the documentation for it, not the marketing page. A tool that resolves can answer in a sentence: it issues the refund, it updates the order, it closes the ticket against a rule. A tool that answers from your knowledge base will describe the quality of its answers instead.

Am I paying for AI twice?

Two ways this commonly happens. You bought a separate resolving agent on top of a help desk that already resolves. Or you bought a separate agent onto a documentation-answering help desk, which is correct, but kept paying that help desk's AI add-on afterwards for a job the agent now does. The second is the more common one and it is easy to miss on an invoice.

Tools Mentioned

Full reviews, pricing tiers and where each one breaks.

You Can Also Look Into

WRITTEN BY AR · UPDATED 2026-08-16

I read the fine print. Vendor pricing pages, billing definitions, terms, funding filings and acquisition notices — then I do the arithmetic nobody publishes: what a platform actually costs at your volume, what its headline metric is really counting, and who owns it now. I do not run benchmarks, and no page here pretends otherwise.

Editorial policy