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.hold_occurred

Hold Occurred

Process Adherence
  |  
Universal

What This Signal Detects

Hold time is dead time. Every minute a customer spends on hold is a minute their problem remains unsolved, their time is being wasted, and their perception of your service deteriorates. But hold time is not just about the customer experience — it’s also a diagnostic indicator of operational efficiency.

This signal identifies any interaction where hold time occurred, from brief holds while agents research information to extended holds during system lookups or supervisor consultations. It captures both planned holds (when agents warn customers they’re being placed on hold) and unexpected silence periods.

Why It Matters

Hold time is one of the most universally frustrating aspects of customer service, yet many organizations track it poorly. Average hold time reports miss the distribution — some customers wait seconds while others endure multiple minutes. Those outlier experiences drive disproportionate complaint volume and churn.

For supervisors and workforce planners, hold patterns reveal operational stress points. Excessive holds in certain call types indicate knowledge gaps, system performance issues, or process bottlenecks that need addressing. Hold frequency can predict when agents are overwhelmed before traditional metrics like abandon rate spike.

Hold occurrence is also a quality indicator. Skilled agents minimize hold time through better preparation, more efficient system navigation, and proactive customer communication about wait expectations.

How It Works

Compass identifies when hold periods occurred during the interaction, regardless of duration. This includes explicit holds where agents informed customers they were being placed on hold as well as extended periods of silence that function as unannounced holds.

The signal recognizes various hold scenarios: research holds, system lookup delays, supervisor consultation holds, and transfer preparation holds.

What Teams Do With This

Supervisors use hold occurrence data to identify agents who consistently place customers on hold, often indicating training opportunities around system navigation or process efficiency. They can provide targeted coaching on hold avoidance techniques.

Workforce management teams analyze hold patterns across different interaction types to identify process bottlenecks. If holds spike during certain procedures, it signals system issues or training gaps that need operational attention.

QA managers incorporate hold frequency into agent evaluation criteria, recognizing that minimizing customer wait time is both a service and efficiency skill that can be developed through coaching.

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