What it means
A team may replace an item or correct an invoice, then close the case without checking whether the fix reached the customer, and a follow-up step can reveal an incomplete remedy. Define which cases merit a check and what evidence counts before producing a rate.
Record the promised follow-up date, responsible person, channel and question, and distinguish an attempted contact from a confirmed customer response. Respect communication preferences and privacy, because not every customer wants repeated calls, and a customer who asked for email should not receive repeated calls merely to raise a completion metric.
Service recovery describes the full response and a recovery plan names steps, whereas this measure focuses on the later verification contact. A fast follow-up can still miss the underlying issue, while a customer who does not answer should not be coded as satisfied.
Separate completed, attempted, overdue, declined and not-required cases, and review unresolved remedies and repeat complaints beside the completion rate. The denominator should be a fixed, eligible case cohort, not whatever remains open in the software at report time.
If a customer declines further contact, record that choice and exclude or classify it according to a policy set before reviewing results. Choose the follow-up point with the customer where practical, since a next-day check may suit a replacement delivery while a technical repair may need a week of use before anyone can judge it.
Record the agreed time, not only an internal target chosen afterward. The person making the check needs the case history, so ask whether the promised remedy worked and whether any new issue arose without making the customer retell the entire complaint, because a generic satisfaction survey can miss a specific unfinished fix.
Mark the difference between contact and outcome. A message sent, a customer response received and a verified remedy are separate events, and they should stay separate even if a tool stores them all under a single 'resolved' state.
A case may involve more than one promised remedy, so if a replacement arrived but the promised credit has not, one completed check should not mark the whole recovery as finished, and each commitment should be recorded under a case-level rule that reflects the customer's actual outcome. Use an escalation when the follow-up shows a repeat problem, and reopen or link the original case so the team can see what was promised, what failed and which owner must act now.
An apology without a new practical plan is not completion, and a customer who says the fix failed needs a named owner and next update, not merely a note that the follow-up was performed. Review overdue checks by team and severity, report both timing and customer-confirmed outcomes, audit a sample of completed records, and close the learning loop by summarising recurring failed remedies for product, operations or finance teams, because a checkbox can be filled even when no meaningful follow-up happened.
In practice
Real-world examples.
Example
A retailer replaces a faulty appliance and promises a call two days after delivery. The agent records the call, the customer's answer and the outcome, so the case closes only after the check is documented.
Example
A telecoms provider corrects a billing error and promises an email check at the next statement. The follow-up shows the correction appeared but a late fee remained, so the case is reopened rather than counted as resolved.
Example
A repair company classes its cases as completed, attempted, overdue, declined or not required. A customer who declined contact is recorded under the declined category and handled under the policy set before results were reviewed.
Formula
Calculation
Verified follow-up completion rate = eligible cases with a documented promised check made within the window / eligible recovery cases due for follow-up x 100. Report customer-confirmed resolution separately.
Worked example. A fictional repair firm has 10 eligible recovery cases due for a next-day check, and 8 of them received a documented check within the window.
- Follow-up completion rate = 8 / 10 x 100 = 80%.
- If only 7 of those 8 customers confirmed that the fix worked, confirmed resolution = 7 / 10 x 100 = 70%.
The two figures answer different questions, so a high completion rate should never be quoted as a satisfaction result.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Blue Harbor Service, an invented repair firm. It promises a next-day check after resolving ten customer failures. Seven customers confirm the fix, one reports a repeat fault, one declines contact and one cannot be reached.
The firm records the categories instead of calling nine or ten cases successful. The repeat fault is linked to the original case and assigned an owner, and the unreachable customer is retried under the agreed rule. The example is illustrative only.
Watch out
Common mistakes.
- Counting an internal ticket note as a customer follow-up.
- Marking an unanswered contact attempt as confirmed resolution.
- Removing overdue cases from the denominator to improve the rate.
Questions
People also ask.
Does completion mean the customer is happy?
No. It records the follow-up step; satisfaction or remedy success needs separate evidence.
Should every case get a call?
No. Define severity and preferences, and use a suitable channel.
What if the customer does not answer?
Record an attempted contact and follow the agreed retry rule without claiming success.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%