Agent introduced self identifies whether the agent provided their name, role, or department identification near the beginning of the interaction. This goes beyond checking for a scripted greeting — it evaluates whether the customer learned who they were speaking with.
The signal recognizes different introduction styles: formal (“This is Sarah from Technical Support”), casual (“Hi, I’m Mike and I’ll be helping you today”), or role-focused (“You’ve reached our billing department”). What matters is that personal or departmental identification occurred, not the exact format.
Customer trust starts with knowing who they’re talking to. When agents skip introductions, interactions feel impersonal and transactional. Customers cannot build rapport with someone they cannot identify, and they have no reference point if they need to call back about the same issue.
From a service perspective, proper introductions set expectations about expertise and authority. A customer speaking with “John from Technical Support” has different expectations than someone speaking with “Sarah from Billing.” Without this context, customers may request actions outside the agent’s scope or become frustrated when the agent cannot help with certain issues.
Introduction consistency also affects brand perception. When some agents introduce themselves professionally while others jump straight into business, the customer experience becomes inconsistent. This variation signals lack of training standardization and process discipline.
Compass evaluates the opening portion of the interaction for name exchange, role identification, or department statements. It accounts for different conversation flows — some customers interrupt with urgent issues, others require verification before introductions happen.
The signal focuses on whether identification occurred within the natural flow of the conversation opening, not whether it happened in the first ten seconds. Context matters: an emergency call may appropriately defer introductions until the urgent issue is addressed.
QA teams use introduction tracking to ensure greeting consistency across the operation. Teams with low introduction rates often have agents who feel pressured to jump immediately into problem-solving, missing this basic relationship-building step.
Training teams identify whether introduction gaps stem from scripting issues, time pressure, or agent preference. The coaching approach differs: scripting problems need clearer guidelines, time pressure needs workflow adjustment, preference issues need behavior reinforcement.
Customer experience teams track introduction rates as a baseline professionalism metric. Consistent introductions correlate with other professional behaviors, making this signal a useful indicator of overall service standards across different teams or shifts.
This signal is part of Chordia’s Quality Monitoring capabilities.
We'll walk you through real interactions and show how each signal traces back to specific conversational evidence — so your team can act on what actually happened.
