Plan requirement
| Subscription | Any plan |
| Access | Admin |
Reading what actually happened. The single most useful half hour in running an AI agent, and the one people skip.
Read them
- Open the conversations in the AI agents area.
- Filter to what you want to examine.
- Open a conversation and read it from the first message.
- Note the cause of anything that went wrong.
Which ones to read
- Handovers. Every one is a case the agent could not close, with the reason visible.
- Long conversations. Length usually means confusion.
- A random ten. The filters show you what you already suspect; random sampling shows what you do not.
Read from the start
The failure is visible at the end and caused at the beginning: an ambiguous question the agent guessed at, an article that half fits. Reading only the last exchange leads to fixing the symptom.
Write down the cause, not the case
"Article on returns does not mention the fourteen-day period" is a fix. "Agent gave a bad answer about returns" is a complaint. The first accumulates into a work list; the second does not.
Most causes are content
Missing article, outdated article, two articles disagreeing, an article assuming context. Expect the majority of your notes to be article work, and be suspicious of a review that concludes with only settings changes.
Make it a habit
Twenty conversations a week, by one person, with the notes going somewhere shared. That rhythm is what separates agents that keep improving from ones that are launched and left.
Share the good ones
Send the team an exchange where it worked well. Scepticism about AI agents is usually well founded and always corrosive, and a real transcript is the only convincing answer.
Comments
0 comments
Article is closed for comments.