Guide · Updated
What is an AI support agent?
An AI support agent is a customer facing assistant that answers from your approved product knowledge, shows its source, follows a handoff policy, and records the questions it could not answer. It is not a chatbot improvising from memory. This guide covers the definition, what to automate first, and how to judge one before you buy.
What is an AI support agent?
An AI support agent answers first line customer questions from your documentation, help articles, pricing page, and support policies. For each question it finds the relevant page, explains the answer in plain words, links the source, and hands off to a person when the question is account specific or the docs do not cover it. If it cannot point to a source, it says so.
The word agent suggests it can also take actions, such as looking up an order or changing a plan. Some can. For most small SaaS teams, the valuable part is narrower: correct answers to documented questions, a clean handoff for everything else, and a list of what the docs are missing.
How is an AI support agent different from a chatbot?
A chatbot replies to messages. An AI support agent works inside rules: a defined knowledge source, a refusal rule, a handoff path, and a way to measure what happened. Without those four, you get something fluent in a demo that invents plan limits in production.
| Basic chatbot | AI support agent | |
|---|---|---|
| Knowledge | Whatever the model knows, plus a prompt | Your approved docs, searched per question |
| When unsure | Guesses | Says the docs don't cover it |
| Sources | None shown | Links the page it used |
| Handoff | “Contact support” | Passes the conversation to a person with context |
| After launch | Chat volume | Answer quality, handoffs, and missing docs |
Many products sold as agents are chatbots with a new label, and some products called chatbots behave like agents. Judge the behavior, not the name.
What should an AI support agent handle first?
Start with questions that are documented and the same for every customer: setup, integrations, plan limits, public billing rules, troubleshooting, and how a feature works. These make up a large share of support volume on most SaaS products, and each one has a page the agent can cite.
A useful exercise: export your last hundred conversations and tag each one “docs answer this”, “docs should answer this but don't”, or “needs a person”. The first group is what the agent takes on day one. The second group is your writing list, and it shrinks as you add articles.
What should it never handle alone?
Keep a person on anything that touches money already charged, account access, security, legal terms, or a decision. An agent can collect details and route these well, but it should not resolve them on its own judgment.
- Refunds, disputed charges, and credits
- Account access, ownership changes, and deleted data
- Security incidents and anything about another customer's data
- Contract terms, discounts, and exceptions to policy
- Angry or high value customers who need a person, not a faster answer
Write these rules down before launch. The handoff list is as important as the knowledge source.
What makes the handoff work?
A good handoff passes the whole conversation, what the agent already tried, and the customer's contact details to the right place, so the person doesn't start from zero. A bad one ends with “please email support” and makes the customer repeat everything.
Decide where handoffs land (your inbox, Slack, your helpdesk), who answers them, and how fast. Then read them weekly. Handoffs on documented topics usually mean the article is unclear; handoffs on undocumented topics mean the article doesn't exist yet.
How do you judge an AI support agent before you buy?
Put it on your own docs and ask it ten real questions from recent tickets, including two your docs do not cover. Score whether it cites the right page, stays faithful to that page, and declines the uncovered ones. A good agent is useful on covered topics and honest about the rest.
- Does every answer link a source you can open?
- Does it refuse when the docs are silent, or does it guess?
- Can you see which questions it could not answer?
- Where do handoffs go, and do they carry the conversation?
- What happens to its answers when your docs change?
- How is it priced when volume grows?
Question five gets skipped most often, and it decides whether the agent is still right three releases from now.
How is an AI support agent usually priced?
Pricing usually follows one of three models: a fee per resolved conversation, a fee per support seat with AI included or added on, or a flat plan with a monthly conversation allowance. Per resolution pricing scales with success, which sounds fair until a busy month arrives. Flat plans are easier to budget.
Whatever the model, check what counts as a conversation or a resolution, whether follow up questions count again, and what happens when you pass the allowance. Those details move the real cost more than the headline price.
Why is the agent only as good as your docs?
The agent repeats your docs, so its accuracy falls every time the product changes and the docs don't. Rename a setting or change a limit, and it keeps citing the old article. Thin docs produce thin answers, and conflicting docs produce conflicting answers.
That is why the work after launch is mostly documentation: updating articles when the code changes, and writing the articles that refused questions point to. How to find what's missing from your help center covers how to turn those questions into a list of pages to write.
Where does usedocs fit?
usedocs is a help center with an assistant that answers from it. Answers link the article they came from, weak matches decline instead of guessing, and handoffs reach your team by email with alerts in Slack, Discord, or Teams. It keeps the help center accurate with two loops: merged pull requests become proposed edits, and unanswered questions become drafted articles.
You review both in one queue, and nothing goes live without your approval. Pricing is one flat plan, $99/mo with 2,000 AI conversations a month after a 7 day free trial, no credit card.
FAQ
Is an AI support agent the same as a helpdesk?
No. It answers documented questions and hands off the rest. Keep a helpdesk or shared inbox for conversations that need a person.
Does an AI support agent need documentation to work?
Yes. It is only as trustworthy as the pages it reads. Thin or conflicting docs produce thin or conflicting answers.
Can it replace first line support?
It can take most repetitive documented questions. Account specific and high risk questions should still reach a person.
Does an AI support agent need citations?
For product support, yes. A visible source lets customers check the answer and lets your team see why an answer went wrong.
What should I automate first?
Documented questions that are the same for every customer: setup, integrations, plan limits, public billing rules, and troubleshooting.
How do I know if it's working?
Track the share of questions answered from docs, handoff rate, “not helpful” votes, and the questions it couldn't answer. Chat volume alone tells you little.
Use usedocs for this
usedocs answers from your docs with sources, says so when the docs can't answer, hands off to your team, and keeps the docs current from your code and customer questions.