A small support team does not need an agent that closes tickets by spending the company's money. It needs one that answers from the help center, drafts the rest, and stops when the customer wants a refund, a credit, or an account change. The build diary sits at build an AI customer support agent. This page is the buying cut for a small business. Compare products in customer support tools.
Key takeaway: If you already pay for Zendesk or Intercom, start with Zendesk AI or Intercom Fin inside that desk. Use Claude or ChatGPT to draft macros from policies a person approved. The bot does not refund and does not change logins.
Research reviewed: October 30, 2026. This is desk research by the AI Savr editorial team. We did not run a private lab test, and we did not invent scores, traffic numbers, or hands-on results. Confirm live prices on the vendor page before you buy.
What may a support agent do without a person?
It may answer questions that are already in a help center you trust, and it may draft a reply for a repetitive how-to. It may not issue a refund, apply a credit, change an email or password, cancel a subscription, or promise a deadline you did not write down. Those actions need a human. Give the agent least privilege so its login cannot press those buttons. Give it a stop condition: low confidence, an angry thread, or any money or account word hands the ticket to a person. An approval gate covers anything that would still be sent outside the help center text. This article does not claim a share of tickets resolved. Vendors advertise outcomes. You should measure your own queue after a month, and you should not copy a percentage from a product page into a plan.
| Request | Agent may | Human must |
|---|---|---|
| How-to from the help center | Answer or draft | Spot-check new articles |
| Order status | Read a status you exposed | Handle exceptions |
| Refund or credit | Stop and assign | Decide and perform it |
| Email, password, or plan change | Stop and assign | Verify and change it |
Support tools that can hand off
Zendesk AI inside the desk you already use
Zendesk AI belongs on the shortlist when the queue already lives in Zendesk. Use it to suggest replies and routes from your own help content. Turn off any action that could refund or edit the customer record until a person has done that job in the product and you have watched it. Least privilege means the AI user cannot be an admin.
Choose it when: Zendesk is already the system of record and you want drafts in the same ticket.
Leave it when: you do not run Zendesk and would be buying a whole desk only for a bot.
Price and access: Zendesk sells AI with its own plans. Read the current Zendesk page. This article does not quote an add-on price or a resolution rate.
A real use: Let it draft a shipping answer from the help center. A ticket that says refund is assigned to a person and the draft is not sent.
Intercom Fin when the inbox is Intercom
Intercom Fin is the matching choice when conversations already sit in Intercom. Let it handle questions your help center answers. Configure the handoff for billing, refunds, and account changes so a human owns those threads. Do not treat a vendor marketing claim about volume as your forecast.
Choose it when: Intercom is the inbox and you can point Fin at articles a person maintains.
Leave it when: your team lives in another desk, or you cannot clearly block refund actions.
Price and access: Intercom publishes Fin's commercial terms on its site. Confirm them before you buy. Do not reuse a per-resolution figure from a secondary write-up.
A real use: Fin answers a password-reset how-to that the article already explains. A request to change the account email is handed to a teammate who can verify the customer.
Claude for the policy the bot must obey
Claude is useful before you turn a bot on. Paste the refund policy and ask for a refusal list in plain language. A person edits it. The list becomes the instruction: draft how-to answers, stop on money and account changes. Claude is not the system that should hold a refund permission.
Choose it when: you need a short policy the support tool will follow and a human will edit.
Leave it when: you wanted Claude to sit in front of customers with your billing login.
Price and access: Read Claude's pricing page for the seat that will draft internal policies. Customer-facing use may be a different product and a different contract.
A real use: Ask for ten example customer lines that must escalate, including partial refunds and login changes. Put the edited list in the help desk configuration.
ChatGPT for macro drafts, not live refunds
ChatGPT can rewrite a macro so it sounds like your company, using only policy text you paste. It should not invent a remedy. Staff paste the edited macro into the help desk. They do not paste full customer records into a personal chat account.
Choose it when: you are cleaning a handful of replies your team already sends.
Leave it when: the chat is connected to customer data and a send button with no approval.
Price and access: Check OpenAI's current plans. A company workspace with admin controls is a different conversation from a personal Plus seat. Confirm both on OpenAI's pages.
A real use: Rewrite a return macro so it tells the customer a person will review the refund. It does not say the refund is already done.
Turn on answers before you turn on actions
A small team should earn trust on help-center answers before any automation touches the customer record.
- List the ten questions you actually get. Mark which ones the help center already answers word for word.
- Write the stop list. Refunds, credits, cancellations, email changes, password changes, and legal threats go to a person.
- Connect the desk you already pay for. Zendesk AI or Intercom Fin. Do not add a second inbox to get a bot.
- Remove refunds from the bot's permissions. If the role can do it, the role is too strong. That is least privilege.
- Read every handoff for two weeks. Fix the article or the stop rule. Do not publish a resolution percentage you did not measure yourself.
Support agents sound sure when they are wrong
They will answer from an old article, miss a plan exception, and apologize by offering a credit you did not authorize. That last failure is why money and account changes stay human. A handoff that still sends the bot's last guess is not a handoff. Small teams feel bad automation faster than large ones, because the same person sees the customer again tomorrow.
A three-person shop
The owner turns on drafts inside the current help desk and leaves refunds as a saved view for themselves. Claude is used once to write the stop list, not as a second bot. After a month they know which articles are missing. They still do not let the agent cancel plans. If phone calls are the real front door, the next read is AI receptionists, which also refuses to invent a per-minute price.
Questions worth asking before you buy
Ask whether the AI user can be denied refund and account permissions, whether you can force a handoff on phrases you list, and where transcripts are stored. Ask if those transcripts train a model on the plan a small business can actually buy. Reject a pitch that leads with a resolution percentage you cannot audit.
For companies that need more than a subscription
A custom support agent is justified when the answer lives in an internal system the help desk cannot see, and even then refunds stay human. Scope that with AI Savr. Bring the stop list. Off-the-shelf Zendesk or Intercom is the cheaper path when the job is standard help-center answers.
If an off-the-shelf tool cannot meet your data, approval, or security rules, talk to AI Savr about a custom AI agent. Use the directory to compare live tools first, and vendors can submit a product.
Frequently asked questions
What is the best AI support agent for a small business?
Use Zendesk AI if you already use Zendesk, or Intercom Fin if you already use Intercom. Use Claude or ChatGPT only to draft policies and macros. The agent may answer from the help center. A human handles refunds, credits, and account changes.
Can the bot issue a refund if the policy is clear?
No. A person issues the refund. The bot can stop and assign the ticket. A clear policy is what the person follows, not a permission for the bot.
Should I buy a new help desk to get AI?
Not if the current desk already holds the queue. Add AI there, or wait. A second inbox splits the work a small team cannot spare.
What does least privilege mean here?
The bot's user cannot refund, credit, cancel, or edit the login. It can read help content and draft. If the role is an admin, it is too strong.
Are vendor resolution rates trustworthy?
Treat them as the vendor's claim, not as your forecast. This article does not repeat a percentage. Measure your own tickets after a careful trial.
Where is the tool list?
The customer support tools collection on AI Savr, plus the article on building a support agent if you want the implementation diary.
Read next
- Receptionists for calls and booking
- The approval gate behind any agent
- Sales follow-up that a human sends