The questions people ask before buying AI support

20 questions, each on its own page, with the answer first and the explanation below. We answer them the same way when the answer doesn’t suit us.

Differences

  • What is the difference between a chatbot and an AI agent?

    A chatbot answers from what’s written in your documentation; an AI agent also checks the account of the person asking and can take actions in your systems. So a chatbot handles questions whose answer is the same for everyone, and an agent also resolves the ones that depend on that specific customer.

  • What is the difference between a knowledge base and a help center?

    A knowledge base is the content, the articles themselves, while a help center is the public website where those articles are published, with search and navigation. People use the two terms interchangeably and that’s usually fine. The difference matters when you compare tools, because some sell one, some sell the other, and they don’t cost the same.

  • Does an AI helpdesk replace my support team?

    No. An AI helpdesk takes over a specific part of the work: repeated questions, what’s already documented, and much of what gets solved by checking one fact about the account. Hard cases, angry customers and anything nobody has seen before still belong to a person, and they’re usually why you hired that person.

  • Can an AI agent see each customer’s plan and data?

    Yes, if you connect it. An AI agent only sees what you give it: with documentation it answers from documentation, and with read access to your API it can check the plan, usage or last invoice of the person asking and answer with that fact. That access is what separates an agent from a chatbot that only reads articles.

What it can do

  • Does an AI chatbot make up answers when it doesn’t know?

    Yes, it can, and that’s called a hallucination: the model writes an answer that sounds believable because it’s built to produce convincing text, not to admit it’s missing a fact. No system is right every time, so what matters is how it fails. "I don’t know, let me get a person" is acceptable; inventing a billing figure is not.

  • Can an AI agent act without me reviewing it?

    Yes, and you decide how far it goes. The sensible split is by what can be undone: lookups change nothing and can run on their own; changes you can reverse can run on their own if they’re logged; and anything you can’t undo, like canceling, deleting or refunding, should be confirmed by a person, because if the agent gets it wrong there, nobody will notice in time.

  • Can I see which actions an AI agent has run?

    Yes, and you should be able to: if a vendor won’t show you, that’s reason enough to rule them out. Every action the agent takes has to be logged with what it did, on which account, when and in which conversation. Without that log you can’t review a mistake, you can’t answer a customer who complains, and you won’t pass a mid-sized customer’s security questionnaire.

  • Can an AI agent change a customer’s plan?

    Yes, if you give it that action, although it isn’t always a good idea. An upgrade can be undone, and some companies automate it. A downgrade or a cancellation moves money and doesn’t undo itself, so the sensible setup is for the agent to prepare it and a person to confirm it.

  • Can an AI chatbot handle complex technical support?

    It can handle part of it: the initial diagnosis. An AI agent recognizes the error, checks the state of the account and rules out known causes before the case reaches anyone. What it can’t solve is the problem nobody has seen before, which is what complex technical support is, and why a third tier exists.

  • Which languages does an AI agent answer in?

    An AI agent can answer in practically any language. What changes the result is the language of your documentation: if your articles are only in English, a customer who asks in German gets a translation of that content, not content written for them. That’s usually enough, but it’s worth knowing.

Getting started

  • How long does it take to get an AI support agent running?

    One to two weeks to have it fully running. Answering from your documentation takes a few hours: what you already publish gets indexed and it starts replying. What takes longer is connecting the queries to your API so it can check the account of the person asking, and that depends on your engineering team more than on the vendor.

  • Do I need to integrate all my tools before I start?

    No, and it’s better not to. With your documentation indexed, the agent already resolves the questions that don’t depend on the account on day one, with nothing connected. Integrations are added in order of what people ask most, and two or three usually cover most of it: subscription status, usage, and the last order or invoice.

  • Do I need a help center before I can use an AI knowledge base?

    No. Your articles can live anywhere readable, like a portal, a docs repository or internal documents, and the system indexes them the same way. The only requirement is that the answer is written down somewhere: if it doesn’t exist, there’s nothing to index.

  • Do I need the official WhatsApp Business API to support customers on WhatsApp?

    Yes, if you’ll be answering with a team or an automated system. Neither the regular app nor the WhatsApp Business app lets you connect tools in a supported way, and workarounds risk Meta shutting down the number. You get the official API through an authorized provider, who handles the verification.

Pricing

  • What counts as a conversation when you pay per resolution?

    A conversation is the whole thread with one customer, not each message: if they write five times about the same thing, it’s still one. What varies between vendors is when that thread is cut and what counts as resolved, and those two definitions affect your bill far more than the unit price on the website.

  • What happens if I go over my plan’s conversation limit?

    Depending on the vendor, one of two things: the agent stops answering until the next billing cycle, or it keeps answering and you’re billed for the excess. The first leaves a volume spike to your team; the second, an invoice you didn’t expect. With Intake, the agent pauses until the next cycle, your team keeps answering and there are no extra charges.

  • Is Freshdesk cheaper than Zendesk?

    Yes, Freshdesk is usually cheaper per user, especially on entry plans. The gap narrows on the higher plans of both, and it disappears if what pushed you to switch was the cost of AI, because both charge for it separately and in a similar way.

  • Is Intercom more expensive than Zendesk?

    It depends on how many people answer and how much you use the AI. Intercom charges per user plus per resolution by its AI agent; Zendesk charges per user plus its AI add-on. With a small team and a lot of automated volume, Intercom usually costs more; with a large team and little AI, it’s the other way around.

Choosing and migrating

  • Can you migrate from Zendesk to Freshdesk without losing the history?

    Yes, you can, and both platforms have tools for it, although not everything moves over intact. Tickets, contacts and articles migrate well. Automations, custom fields with logic behind them and historical reports almost never arrive the same, which is why a migration takes weeks, not an afternoon.

  • Which helpdesk should I choose with three people in support?

    With three people, choose the helpdesk that best does two things: shows who owns each conversation and what’s pending, and lets you answer without switching to another tool to look something up. Almost every tool does the first; the second is where they differ, and it’s what you feel every day.

Try it without dropping what you use