Table of Contents
- Key takeaways
- What is AI customer support?
- What does the evidence say about AI customer support?
- What AI customer support handles well
- Where AI customer support fails, and why
- 1. Missing knowledge: the answer is not in the content
- 2. Stale knowledge: the content is out of date
- 3. No route to a person: the customer is trapped
- 4. High-stakes answers: the bot commits the business
- Should AI answer this question? A decision table
- What AI customer support costs
- The stack: which tool does which job
- Where SiteGPT fits in the stack
- How to start with AI customer support without the common failures
- Frequently asked questions
- Basics
- What is AI customer service?
- What is the difference between a chatbot and AI customer service?
- Is AI customer service the same as an AI agent?
- Results and limits
- Does AI customer service actually work?
- Why do customers dislike AI customer service?
- Can AI replace customer service agents?
- Cost
- How much does AI customer service cost?
- Will AI customer service get cheaper?
- Setup and risk
- How long does AI customer service take to set up?
- Is a business responsible for what its AI chatbot says?
- Can AI customer service handle regulated data?
- Sources

- AI customer service handles repeated, documented questions well: policies, product details, how-to steps, and pre-sales questions.
- It fails on four points: missing knowledge, stale knowledge, no route to a person, and answers that commit the business to money or legal terms.
- Customers punish failure fast. In a 2026 Gartner survey, only 27% would try a chatbot again after a bad experience, and 87% said access to a human is essential.
- The fix is scope, not a bigger model: ground answers in your own content, keep it current, decline when the content has no answer, and hand off with the transcript.
- Most teams run AI customer service as a stack. A helpdesk holds the tickets, a knowledge-trained answer layer handles routine questions, and people take the rest.
Key takeaways
Question | Short answer | Where it is covered |
What does AI handle well? | Repeated questions that your help content already answers | What it handles well |
Where does it fail? | Missing or stale knowledge, no human route, high-stakes commitments | Where it fails, and why |
How do customers react to failure? | Only 27% would try a chatbot again after a bad experience (Gartner, 2026) | What the evidence says |
How is it priced? | Per outcome (Fin, $0.99 each) or a flat plan with a message quota (SiteGPT from $59 a month billed monthly) | What it costs |
Which tool does which job? | Helpdesk for tickets, knowledge-trained answer layer for routine questions, people for exceptions | The stack |

What is AI customer support?
Form | What it does | Who sees it |
Rule-based chatbot | Follows scripted buttons and flows a person wrote | The customer |
Agent assist | Suggests replies, summarizes tickets, and routes them for the support team | The agent only |
AI agent or answer bot | Answers the customer directly from your content and hands off when it cannot | The customer |
What does the evidence say about AI customer support?

- Interest is not use. 49% said they would have used a chatbot if the company offered one. Only 7% used a chatbot or digital assistant in their most recent service interaction.
- One failure loses most users. Only 27% would try a chatbot again after a negative experience. Gartner's advice to service leaders was to "prioritize reliability over reach".
- A route to a person is expected. 87% said access to a human agent is essential when a company uses GenAI in customer service.
What AI customer support handles well
Question type | Example | Why AI fits |
Policy questions | "What is your return window for sale items?" | The answer is written down and rarely changes |
Product details | "Does the large size fit a 15-inch laptop?" | Product pages and spec sheets hold the answer |
How-to steps | "How do I export my invoices?" | Help articles already list the steps |
Pre-sales questions | "Which plan includes the API?" | Pricing and feature pages answer it, and the bot can collect a lead |
Order or account lookups | "Where is my order?" | Works only when the tool is connected to the order system |
Questions in other languages | A French question about an English help article | Language models translate the answer at reply time |

Where AI customer support fails, and why
1. Missing knowledge: the answer is not in the content
- Why it happens: the help center has gaps, or the bot is allowed to answer from general model knowledge.
- Fix: instruct the bot to answer only from your content and to say so when it does not know. The guardrails are covered in stopping chatbot hallucinations.
2. Stale knowledge: the content is out of date
- Why it happens: the bot was trained once and never re-synced, or two pages contradict each other.
- Fix: re-sync on a schedule and after every pricing or policy change, and remove contradictions before launch.
3. No route to a person: the customer is trapped
- Why it happens: the team measures containment and hides the handoff to protect the number.
- Fix: show a way to reach a person in every conversation and pass the transcript along, so the customer does not repeat the question.
4. High-stakes answers: the bot commits the business
- Why it happens: the bot is allowed to answer questions where a wrong reply costs money or creates a legal commitment.
- Fix: route refunds, billing disputes, and policy exceptions to a person or a fixed scripted flow.
Failure point | What the customer sees | Root cause | Fix |
Missing knowledge | A confident wrong answer | Content gap, no instruction to decline | Answer only from content, decline otherwise |
Stale knowledge | An old price or policy | No re-sync schedule | Scheduled refresh and a contradiction check |
No route to a person | A loop of unhelpful replies | Containment as the only metric | Visible handoff with the transcript |
High-stakes answers | A promise the business will not keep | No limit on what the bot may answer | Person or fixed flow for money and legal matters |
Should AI answer this question? A decision table
If the question... | Pick... | Why |
Is answered by a current help page | AI answers and links the source | This is the work AI customer service does best |
Is not covered by any page | AI declines and offers a person | A guess is the most expensive failure |
Needs data from an order or account system | AI only if the tool is connected to that system, otherwise a person | Content alone cannot know a customer's order |
Commits money, safety, or legal terms | A person or a fixed scripted flow | A generated reply should not make the commitment |
Comes from a frustrated customer, or the bot already failed twice | Hand off with the transcript | Speed matters more than containment |

What AI customer support costs
- Per outcome: Fin charges $0.99 per outcome, at most once per conversation, plus helpdesk seats. Fin does not charge when it cannot answer or the customer asks for a person.
- Flat plan with a quota: SiteGPT Growth costs $129 a month billed monthly, or $79 a month billed yearly, for up to 10,000 GPT-4.1-mini messages or 1,000 GPT-4.1 messages. A message counts the visitor's question and the AI's reply.
Resolved conversations a month | Fin at $0.99 per outcome | SiteGPT Growth, billed monthly |
250 | $247.50, plus seats | $129 flat, up to 10,000 messages |
500 | $495, plus seats | $129 flat, up to 10,000 messages |
1,000 | $990, plus seats | $129 flat, up to 10,000 messages |
2,000 | $1,980, plus seats | $129 flat, up to 10,000 messages |
The stack: which tool does which job
Layer | Job | Tool |
1. Helpdesk and inbox | Holds tickets, assigns them, and reports on the team's work | Zendesk, Freshdesk, or the Intercom helpdesk |
2. Knowledge-trained answer layer | Answers routine questions from your website, files, and cloud drives on a widget or chat channel, then hands off | |
3. In-helpdesk AI agent | Replies inside the helpdesk's own messenger and can run actions the helpdesk connects to | Fin or Zendesk AI agents |
4. Knowledge source | Holds the help articles and policies the AI trains on | Your help center, website, and documents |
5. People | Handle refunds, disputes, complaints, and anything urgent | Your team, working from the helpdesk or chat tool |
Where SiteGPT fits in the stack
- Handoff: human support works on every plan. By default the AI escalates when the visitor asks for a person, when the situation is urgent, or when the visitor is frustrated after an answer that did not help.
- Channels: Slack, Crisp, Messenger, Google Chat, Freshdesk Messaging, and Zoho SalesIQ from Growth. The Zendesk AI Agent, which answers inside Zendesk Messaging and hands conversations to agents, needs Scale or above.
- Freshness: Starter is manual refresh only. Growth refreshes monthly, Scale weekly with a daily sitemap scan, and Enterprise daily.
- Limits: there is no Intercom or HubSpot integration today, and Starter has no chat integrations. Teams that need every conversation to start and end inside one helpdesk are better served by that helpdesk's own AI agent.
How to start with AI customer support without the common failures
- List the 20 questions customers ask most often and mark which ones a current help page answers.
- Fix or write the missing pages before connecting any tool.
- Write the handoff rules: when the visitor asks, when the content has no answer, and when money or legal terms are involved.
- Test the bot with three kinds of question: answerable, unanswerable, and ones that should go to a person.
- Launch on the answerable topics only, then review escalations and unanswered questions every week.



