Dialog Fluency

Dialog Fluency measures whether the conversation between the user and the bot flows clearly, naturally, and without unnecessary friction. It is worth 20% of the Inquio Score™.

What it measures

Inquio reads each conversation and judges whether the bot was able to keep the dialog understandable, relevant, and easy to follow.
A conversation contributes positively when the bot:
  • responds to what the user actually said
  • keeps track of context from earlier turns
  • asks clear follow-up questions when information is missing
  • avoids unnecessary repetition
  • recovers when the user corrects or clarifies their request
  • guides the user toward a useful next step
A conversation drags the score down when the bot:
  • repeats the same question or answer without making progress
  • asks for information the user already provided
  • misunderstands the user and continues on the wrong path
  • jumps to a different topic without explanation
  • gives confusing, contradictory, or overly long replies
  • leaves the user stuck in a loop

Dialog Fluency is about the quality of the interaction. Whether the bot’s answer was factually correct is measured by Resolution Accuracy, and whether the bot resolved the request without a handoff is measured by Containment Quality. A bot can be correct and contained, but still frustrating if the conversation is hard to follow.

How it affects your Inqio score

DimensionWeight
Resolution Accuracy40 %
Containment Quality25 %
Dialog Fluency20 %
Safety and Compliance15 %

Reading your grade

ScoreGradeWhat it means
90-100AConversations are clear, coherent, and easy for users to complete.
80-89BThe dialog mostly flows well, with recurring friction in one or two areas.
70-79CThe bot can hold a conversation, but users regularly need to clarify, repeat, or work around it.
60-69DA substantial share of conversations include confusion, repetition, or dead ends.
0-59FUsers cannot reliably move through the conversation without getting stuck.

The trend arrow next to the score compares this report card with the previous one for the same bot. See Trends and benchmarks for how the comparison period is chosen.

What usually drives a low score

  • Repeated questions. The bot asks for the same information more than once, even though the user already provided it.
  • Weak context handling. The bot does not use information from earlier in the conversation and treats the request as if it were new.
  • Poor recovery from misunderstanding. The user corrects or clarifies the request, but the bot continues on the wrong path.
  • Conversation loops. The bot and user move through the same steps again and again without reaching a result.
  • Unclear next steps. The bot gives an answer, but the user does not know what to do next.
  • Overly long replies. The bot gives too much information at once, making it harder for the user to find the relevant part.

How to improve it

  1. Open Issues and Recommendations and filter to issues tagged as affecting Dialog Fluency.
  2. Start with the issue that has the highest impact and the largest number of affected conversations.
  3. Read several of the affected conversations in full.
  4. Look for the exact turn where the user becomes confused, repeats themselves, corrects the bot, or stops progressing.
  5. Check whether the problem is missing context, a bad follow-up question, unclear wording, or an unnecessary loop.
  6. Fix the conversation path before polishing individual messages. Most fluency problems come from flow design, not wording alone.
  7. Re-upload a fresh dataset after the change and compare the trend arrow on the next report card.

Where to find it

  • Bot Report Card — the Dialog Fluency tile, with score, grade, and trend. Click the tile for the breakdown.
  • Bot Report Card → Benchmark comparison — your score against the average for your industry.
  • Issues and Recommendations — the specific conversations behind the score.
  • Conversations — the affected conversations where users repeat themselves, correct the bot, or fail to progress.