Skip to main content
Best Web Developer — web design, development and digital growth agency
Language and currency EN RM MYR

Language

  • More languages coming soon

Currency

Prices on this site are shown in the currency you choose.

Trending topic

AI Chatbots for Customer Service: How They Work

The difference between a chatbot people tolerate and one they resent comes down to what happens when it does not know the answer.

  • 1 October 2026

Key points

  • A chatbot is only as good as the knowledge base behind it
  • Gathering the real answers takes longer than the technical build
  • Declining below a confidence threshold protects trust rather than wasting it
  • Handover must carry the conversation so customers never repeat themselves
  • An assistant should confirm honestly that it is automated when asked
  • Repetitive factual questions suit automation; complaints and judgement calls do not

The short version

A support chatbot matches an incoming question against a knowledge base the business wrote and approved, returns the matching answer, and escalates to a person when confidence falls below a threshold. The good ones decline rather than guess. The bad ones produce a confident wrong answer and lose the customer permanently.

Why the knowledge base decides everything

A chatbot can only be as good as the material behind it. Businesses that skip the knowledge base and hope the model infers the answers from general industry information get exactly what that suggests: answers that sound plausible and quietly contradict the actual policy.

The material needs to come from the business: real prices, real delivery times, real policies, real answers to the questions customers genuinely ask. Gathering that takes longer than the build, and it determines whether any of it works.

What happens when it does not know

This single behaviour separates useful chatbots from frustrating ones. Below a confidence threshold, the assistant should say plainly that it cannot answer and offer a person. That looks like a weakness and functions as the opposite: a customer handed over cleanly still trusts the business, while one given a confident wrong answer usually does not return.

The handover carries the conversation with it, so nobody asks the customer to repeat themselves.

Honesty about what it is

A chatbot should never claim to be human. Asked directly, it should say it is an automated assistant and offer to connect the person to someone. Beyond the trust argument, several jurisdictions now require that disclosure.

Where it genuinely helps

Repetitive, factual questions with documented answers: order status, opening hours, policy details, account basics. Those dominate most support queues. Complaints, judgement calls and anything emotionally charged belong with a person, and a well-configured assistant routes them there without argument.

Questions

Related questions

The things clients actually want to know — costs, timelines, ownership and what happens after launch.

Still not sure?

Ask us anything on a free 30-minute call. No pitch, no obligation.

A badly built one will. One answering from an approved knowledge base with a confidence threshold declines instead, which is the behaviour to insist on.

No. Asked directly it should say it is automated and offer a person. Several jurisdictions require that, and it protects trust regardless.

Complaints, anything emotionally charged, and anything needing a judgement call or a goodwill decision.

The technical build is rarely the long part. Gathering and approving the knowledge base usually takes longer and matters more.

They dislike wasting time. One that answers correctly in seconds and hands over cleanly when it cannot tends to go down well.

It removes the repetitive tickets so the team handles the ones needing judgement. Volume tends to grow faster than headcount anyway.

Free strategy session

Let’s build something worth finding.

Tell us where you want the business to be in twelve months. We will come back with a costed plan, a realistic timeline, and the numbers we expect to move — no obligation, no jargon.

  • 30-minute call, no pitch deck
  • Fixed-price proposal in 48 hours
  • You own everything we build

Talk to a developer

Not a sales team

Response time
Within 1 business hour
Where we work
UK, USA & the Gulf
Contracts
No lock-in, monthly rolling
Working since
2023
infobestwebdeveloper.org
Free consultation