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

Script Adherence Likely

Process Adherence
  |  
Universal

What This Signal Detects

Script adherence involves following required procedural elements for specific interaction types. This is not about reading scripts word-for-word like a telemarketer — it is about ensuring agents include mandatory components like proper openings with name exchange, required disclosures, appropriate closings, or compliance statements that must be communicated for regulatory or policy reasons.

This signal evaluates whether required script elements were stated during the interaction based on the specific type of call and applicable policy requirements. It considers multiple procedural components including opening procedures, disclosure requirements, and closing elements that may be mandatory for the organization or interaction type.

Why It Matters

Script adherence requirements exist for legal, regulatory, and operational reasons that go beyond customer service preferences. In debt collection, Mini-Miranda disclosures are legally required. In financial services, certain account discussions require specific language. In healthcare, HIPAA-related statements may be mandatory. Missing these elements creates compliance risk that is invisible until audited.

Consistent script adherence also ensures quality standardization across large contact centers. When agents skip required elements, customer experiences become unpredictable — some customers receive complete professional service while others get abbreviated interactions that miss important components.

From an operational perspective, script adherence tracking helps identify training gaps and process breakdowns. When agents consistently miss specific elements, it often indicates inadequate training, confusing procedures, or system issues that make compliance difficult.

How It Works

Compass evaluates whether mandatory script components were included based on the interaction type and applicable policies. This includes proper opening procedures with name exchange and company identification, required disclosure statements, appropriate closing language, and any compliance-related communications that must be included for specific call types or customer situations.

What Teams Do With This

Compliance teams monitor script adherence rates to ensure regulatory and policy requirements are being met consistently across the operation. They identify patterns of non-compliance and target corrective action before audit issues develop.

QA supervisors use script adherence tracking to identify agents who need refresher training on procedural requirements. Often agents understand customer service principles but forget specific mandatory elements under pressure.

Training managers incorporate script adherence metrics into competency evaluations, ensuring new agents demonstrate mastery of required elements before handling interactions independently. This prevents compliance issues from developing during the learning curve.

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