Not every customer interaction ends with “thank you, have a great day.” Many require additional steps — information to be sent, callbacks to be made, internal research to be completed, or fulfillment processes to begin. The conversation might feel resolved in the moment, but the customer’s need is only partially met until those follow-up actions happen.
This signal identifies interactions that require proactive follow-up from the organization. It catches conversations where an agent promised to send information, scheduled a callback, committed to internal research, or where the resolution depends on pending fulfillment or processing. The signal does not flag every unresolved issue — it specifically identifies cases where the organization has a responsibility to reach back out.
Follow-up commitments are trust statements. When an agent says “I’ll have our specialist call you back within 24 hours,” the customer stops worrying about the problem and starts watching the clock. If that callback doesn’t come, the trust is broken — and often permanently.
The challenge is that follow-up commitments live in conversation transcripts, not in CRM systems. An agent might promise to research a billing discrepancy and email the findings, but if that promise never makes it into a ticket or task, it simply disappears. The customer remembers, even if the organization forgets.
Tracking follow-up signals across your operation reveals the gap between what gets promised and what gets delivered. It also identifies which types of issues consistently require follow-up, helping teams build better processes to manage those commitments upfront.
Compass evaluates whether the interaction involved commitments for future action from the organization. This includes explicit promises like callbacks or information to be sent, as well as implicit follow-up needs like pending fulfillment or cases where the issue was resolved but processing is still required.
The signal distinguishes between interactions that naturally end (“your payment went through”) and those that end with organizational obligations (“I’ll email you the confirmation once it processes”). Context matters — the same conversation can trigger the signal or not depending on what commitments were made.
Operations managers use follow-up tracking to identify commitment gaps. If callbacks are being promised but not scheduled, or information is being offered but not sent, the signal surfaces those operational breakdowns before they become customer complaints.
Customer success teams monitor follow-up rates to prevent customer effort. When commitments are tracked and fulfilled consistently, customers don’t need to call back to check on status or remind the company of promises made.
QA teams use this signal to evaluate whether agents are making commitments they cannot keep. Sometimes the issue is training — agents don’t know how to schedule callbacks properly. Sometimes it’s system — the tools to fulfill commitments are not readily available during the interaction.
This signal is part of Chordia’s Signal Intelligence 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.
