CUSTOMERS CALLING BACK AFTER RESOLVED CALLS
Is Your CSAT Score Hiding a Promise Problem?
The After-Call Failure Chain Diagnostic Workbook
A promise problem occurs when the CSAT survey captures the moment of commitment the customer felt heard, the agent was helpful, the call ended positively, but the outcome that was promised never materialised. The score stays high. The experience deteriorates. The customer calls back. The agent is scored again, often positively.
This workbook audits the after-call failure chain: the sequence of structural breakdowns between a commitment made on a call and a commitment delivered to the customer.
The Loop This Promise Failure Is Creating
Promise failures follow a predictable three-link chain. In Link 1 (The Promise Is Vague), agents use non-specific language 'someone will be in touch', without a timeframe or owner.
In Link 2 (The Promise Isn't Logged), the commitment was made clearly but not recorded anywhere a third party can action or track.
In Link 3 (The Promise Isn't Owned), the action was logged but sits in a shared queue with no named owner, deadline, or escalation trigger.
Each link is a system design decision. And when a promise fails, the customer who calls back to chase it often reaches a new agent who handles it well and scores highly. Your CSAT data now contains a positive score generated by a negative experience.
What's Inside the Workbook
Section 1: Your Promise Landscape.
Maps the top five commitments agents regularly make to customers and assesses whether a system or process tracks delivery for each. Examines how the centre finds out when a promised action has not been completed reactively through customer callbacks, proactively through team leader or quality processes, or not at all.
Section 2: The After-Call Failure Chain.
The three-link framework: Promise Is Vague, Promise Isn't Logged, Promise Isn't Owned, with four observable behaviours per link. Identifies which link is weakest in your centre and asks for the evidence supporting that assessment.
Section 3: The Survey Timing Problem.
A six-item rated scale examining whether your survey is sent before promise failures are visible, whether customers who called back to chase a failed promise were also surveyed on that call, and whether you have any mechanism to link a survey response to whether the promised action was completed. Includes the 5-day delay question: if you delayed your survey by five working days, what would happen to your score?
Section 4: The Repeat Contact Signal.
Estimates what proportion of repeat contacts are customers chasing something promised on a previous call, examines how promise-chase contacts are coded in your system, and calculates what elimination of promise-failure repeat contacts would do to both volume and CSAT.
What You'll Be Able to Do After Completing This Workbook
-
Identify which link in your after-call failure chain is weakest and what system design change would address it
-
Estimate what proportion of your repeat contact volume is generated by customers chasing undelivered commitments
-
Assess whether your survey timing is capturing promise failures — or firing before they are visible
-
Calculate the contact volume and CSAT impact of eliminating promise-failure repeat contacts
Who This Workbook Is For
This workbook is for contact centre leaders who have high CSAT scores and rising repeat contacts and suspect the gap is in what happens after the call ends. It is particularly relevant if:
-
Agents promise callbacks, letters, or actions that customers frequently chase
-
Wrap-up time is compressed and after-call actions are frequently incomplete or generic
-
You do not have a reliable way of knowing whether a commitment made on a call was delivered before the customer had to chase it
-
Repeat contact coding does not distinguish between new issues and promise-chase contacts
Frequently Asked Questions
01
Do I need detailed wrap and after-call data to complete this?
No. The workbook works with operational knowledge your sense of how promises are tracked, what happens when they fail, and what proportion of repeat contacts appear to be promise-chasing. Estimates are supported throughout. The absence of tracking mechanisms is itself a diagnostic finding.
02
What are the three failure chain links?
Link 1 is The Promise Is Vague agents use non-specific language without timeframes or named owners. Link 2 is The Promise Isn't Logged the commitment was made clearly but not recorded for tracking. Link 3 is The Promise Isn't Owned, the action was logged but sits in a queue without a named owner, deadline, or escalation trigger. Most centres have at least one active link; many have all three.
03
What is the hidden CSAT distortion?
When a customer chases a failed promise, they often reach a new agent who handles the chase well and receives a high CSAT score for a call that only existed because of a previous failure. Your CSAT data now contains a positive score generated by a negative experience. The failure is invisible in the data. The customer remembers both.
04
What does the 5-day delay question reveal?
It asks: if you delayed your satisfaction survey by five working days after promised actions are typically completed, what would happen to your score? If the honest answer is 'it would drop noticeably,' your current survey is measuring the moment of commitment, not the delivery of it. The gap between those two scores is your promise failure rate.
The workbook scores out of 45. A score of 0–14 indicates low promise risk. A score of 15–29 indicates moderate promise risk at least one link in your after-call chain is broken and your CSAT is absorbing the impact without reflecting it. A score of 30–45 indicates high promise risk, a significant proportion of your contact volume is being generated by undelivered commitments.
What is the scoring range?
05
READY TO BREAK THE LOOP?
The diagnostic found the problem. The intervention fixes it.
Your score tells you where the system is failing. The full BTL Co. intervention gives you the structured methodology to redesign it with phase-by-phase guidance, facilitation tools, and a measurement framework that proves the change is working.
This is where the evidence you've built becomes a case for action.