Conversations

Analyze how your bot handles conversations: how many are deflected, misunderstood, or escalated to agents.

👉

This dashboard shows how your chatbot is handling real conversations — whether it's solving problems, needing help from a human, or getting stuck.


Key Metrics (Last 2 Weeks by Default)

You’ll first see three main numbers that help you understand how well your bot is doing:

Metric

What It Means

All Conversations

Total number of conversations closed (after 15 minutes of no user activity).

Deflected Conversations

The bot handled the conversation without any handover to a human — and reached at least one “deflection tag.”

Handovered Conversations

The bot couldn’t finish the conversation alone and asked a human to take over.

You can also see how these numbers changed compared to the previous period, and a timeline view (daily, weekly, or monthly).

Conversation Types Breakdown

Every conversation is automatically placed into one of these categories — depending on what happened during the interaction.

🧍 Handovered Conversations
The bot asked for help and a human agent stepped in.

  • Ticket Handover: A support ticket was created and send to human agent via plateforms such as Zendesk.

  • Live Chat Handover: The user was transferred to a live agent in real-time.

  • Advanced Builder Handover: Same as live chat, but triggered from a Use Case built on the Advanced Builder.

🤖 Automated Conversations

Handled entirely by the bot — no human involvement.

  • Deflected Conversations: The bot successfully answered the user’s question.

    • Action Deflection: The user got something done (e.g., updated info, booked service).

    • Information Deflection: The user got the info they needed.

    • Advanced Builder Deflection: The deflection came from a legacy (Advanced Builder) flow.

  • Misunderstood Conversations: The bot didn’t understand the user — and triggered a fallback or "I didn’t get that" message.

  • Neutral Conversations: The conversation didn’t trigger a handover, a deflection, or a misunderstanding — it remained unclassified

Every conversation is tagged with only one type based on what happened — even if multiple things occurred inside it. An unique conversation can not be handovered and deflected at the same time


Next page