An agent that answers wrongly sounds exactly like an agent that answers correctly. That is the whole problem.
On a web page the customer can see where the text sits. She can see whether it is a pricing page or a blog post from last year, and often when it was last changed. In a phone call none of that exists. One voice arrives, in one tone, and everything it says carries equal weight – the price you approved last week and the sentence someone wrote in an internal note last autumn.
So the question is not whether your agent answers well. It is where the answer came from, and who owns that place.
The five places an answer can come from
| Source | Good for | How it fails |
|---|---|---|
| The system instruction | Rules, tone, what the agent must never say | Grows long and contradicts itself without anyone reading it end to end |
| Uploaded documents | Price lists, terms, procedures | Nobody has any relationship with them after week three, and the version is rarely dated |
| A lookup in a back-office system | Order status, free appointments, balance – whatever changes hourly | Requires integration, and fails loudly when the system is down |
| Your website | What the customer could have read anyway | May have been ingested once, and does not refresh itself |
| The model itself | Ordinary language and coherence | It fills the gaps. It does not know that it is doing so |
The first four are sources someone chose. The fifth was chosen by nobody. It steps in the moment the others do not cover the question, it sounds exactly as certain as the rest, and in the log it looks like any other answer. The day someone asks what the agent actually said, that is the row that is hardest to account for.
Row three deserves a note. It is the most expensive one to put in place, and far fewer calls need it than people assume.





