Best Practices· 6 min read

How to Read Your Chatbot Conversations (And What to Look For)

Twenty minutes reading real transcripts beats a month of dashboards. Here is what to actually look for, and the four patterns worth acting on.


Dashboards tell you a number went up. Transcripts tell you why, and they are the only place the actual words your customers use are written down.

Here is what to look for.

1. Questions you did not expect

The single most valuable thing in the pile.

Every business has a mental model of what customers want to know, and it is always slightly wrong. You will find people asking about parking, or whether you take card on site, or whether you can work around a tenant — things nobody internally thought to publish.

Each one is a sentence to add to your website. Not for the bot: for everyone.

2. Answers that made you wince

You will know them when you see them. Usually one of three kinds:

3. Where people gave up

Look for conversations that just stop.

Something happened in the message before. Often it is a wall of text, or a clarifying question that felt like an obstacle rather than help. Sometimes it is a perfectly good answer that simply was not the one they wanted.

Abandonment is quieter than a complaint and it is far more common.

4. The same thing asked twice

If someone rephrases a question, the first answer did not land. That pair — the two phrasings and the two answers — is a precise, free description of a gap in your content.

What not to over-read

One angry conversation. It is one conversation. Look for the pattern before you rebuild anything.

Short conversations. Someone asking one thing and leaving with the answer is a success, not a failure. Short is often exactly right.

Your own test conversations. Exclude them. You already know the answers, which makes you the worst possible test user.

Turning it into a habit

Ten minutes, weekly. Read a handful, note one thing to fix, fix it.

The businesses that get real value from this are not the ones with the cleverest configuration. They are the ones where somebody reads the transcripts.

Related: what to do in your first week and chatbot metrics that matter.

Frequently asked questions

How many conversations should I read?
Twenty is plenty to start. Patterns show up faster than people expect, and reading all of them is only realistic in the first couple of weeks anyway.
What am I looking for?
Questions you did not expect, answers that were wrong, points where people gave up, and anything they asked twice in different words.
Should I read them or use analytics?
Both, but read first. Metrics tell you something changed; transcripts tell you why.
How often is worth doing this?
Daily for the first week, then weekly. Monthly is enough once the gaps stop appearing.

Keep reading

How to Read Your Chatbot Conversations (And What to Look For) · SpideyChat