Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

I sent a customer a wrong AI answer. How do I know when to trust it?

You sent the wrong answer. Not the machine — you. The tool produced text; you chose to send it to a customer without checking. That is the fact. No amount of blaming the software changes it. This is not really a question of whether the tool is reliable. It is reliable for some things and useless for others, and nothing in the interface tells you which is which in the moment. The actual failure is that you stopped asking. You let the tool's confidence stand in for your own verification, because checking felt slow and sending felt fast. You cannot make the tool perfect. You cannot know in advance every place it will fail. But you can decide, every single time, what you will check before you send. That decision is yours alone. It takes seconds, and it is always available to you.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The reader needs a short, fixed list of what always requires a human check — but the real work is breaking the habit of mistaking the tool's confidence for your own, so coaching carries more weight.
How the two dials adapt to you →
What’s really going on

Trust the tool for retrieval, not for judgment. It can fetch what a policy says; it cannot know if that policy fits this customer's case. Check any number, date, or promise against the source before you send it. The agent-assist drafts. You sign. That is the whole rule.

🔒 What you’ll build togetherUnlock by starting
A moveBefore sending anything with a number, date, policy term, or promise in it, stop and find the source yourself — not the tool's summary of it.
A moveWrite down the three categories of answer you will never send unverified: prices, deadlines, exceptions to policy. Keep the list where you can see it.
A moveAfter any wrong answer goes out, do not stop at apologizing to the customer. Go find exactly where the tool went wrong, so you know its blind spot.
A moveBefore you hit send, ask yourself plainly: did I check this, or did it just sound certain? Answer that out loud if you have to.
A movePick one rule for this week — no send without a second look at the source — and test whether you actually keep it.

What changes unlock by starting

  • You catch wrong answers before the customer does, not after.
  • You have a fixed, short list of what always needs a human check.
  • You stop confusing the tool's confident tone with your own certainty.
  • Customers and your manager start trusting your answers again, because you've earned it back.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.