Signals are behavioral and intent patterns that Chordia's Compass engine identifies across customer conversations. Each signal represents something specific that happened — or didn't happen — during an interaction. Unlike keyword matching or sentiment scores, signals are grounded in the structure of the conversation: what was said, in what context, and what it means for your operation.
sig.communication_clarity_likely

Communication Clarity Likely

Agent Performance
  |  
Universal

What This Signal Detects

Clear communication is not just about speaking plainly — it’s about confirming that the customer actually understands what was explained. An agent can deliver perfect technical accuracy about a billing cycle or policy change, but if the customer is still confused at the end of the explanation, the communication has failed.

This signal evaluates whether information was communicated clearly and whether customer understanding was confirmed during the interaction. It looks for conversations where the customer expressed confusion that was either addressed and resolved, or left unresolved by the end of the call.

Why It Matters

Miscommunication is expensive in ways that are hard to measure. A customer who doesn’t understand when their service will be restored will call back repeatedly for status updates. A customer who misunderstands their payment due date might miss the deadline and incur late fees, then call to dispute them.

Traditional QA focuses on whether agents follow communication scripts — did they explain the policy, did they provide the next steps — but it often misses whether the customer actually absorbed that information. An interaction can score perfectly on a checklist while leaving the customer completely confused about what happens next.

Clarity signals help teams understand which types of explanations consistently cause confusion. Maybe billing explanations are clear but technical support instructions are not. Maybe newer agents are great at policy knowledge but struggle to confirm customer understanding. These patterns are invisible until you track clarity systematically.

How It Works

Compass evaluates the flow of understanding throughout the conversation. It identifies when customers express confusion — through direct questions, requests for clarification, or statements indicating they don’t understand — and whether that confusion was addressed before the interaction ended.

The evaluation accounts for confirmation behaviors: did the agent check for understanding, did the customer acknowledge comprehension, or did confusion remain unresolved? A conversation where confusion was expressed and then cleared up scores differently than one where confusion was never addressed.

What Teams Do With This

Training teams use clarity signals to identify communication skill gaps. If certain agents consistently have low clarity rates, they need coaching on explanation techniques and confirmation behaviors, not just product knowledge.

QA teams incorporate clarity evaluation into their scorecards. Instead of just checking whether information was provided, they evaluate whether it was provided in a way the customer could understand and use.

Operations leaders track clarity trends across different interaction types. Complex processes that consistently generate confusion might need simplified procedures or better customer education materials, not just better agent training.

This signal is part of Chordia’s Quality Monitoring capabilities.