Closing the loop with a customer means contacting them a second time, after the thing they complained about has been fixed, to say what was done. Most complaint handling ends one step earlier: the customer is called, the apology is made, a remedy is offered, and the case is closed. The customer never finds out whether the rota was changed, the machine was repaired, the team was briefed or the policy was restored. From their side the apology was the end of it, and the next visit is the test of whether anything happened. A second contact, short and specific, is what turns a complaint into evidence that the business listens, and it is the step almost nobody takes.
This article explains why the loop usually stays open, what the second contact has to contain, when it happens for each kind of fix, who makes it, how to keep a case open until the fix is done without the list filling up, and what to do when there was no fix to report.
The apology is not the loop
A typical case, handled well by most standards. A customer at a salon says the colour was not what was agreed and the stylist was dismissive about it. The manager calls the next day, listens, apologises, offers a free correction. The customer books it. The correction happens. The case is marked resolved.
What the customer knows: the business apologised and redid the work. What the customer does not know: whether the stylist was spoken to, whether the consultation process was changed, whether this happens to other people. The remedy fixed the customer's hair. It did not tell the customer that the problem was fixed.
That second thing is what customers actually want from a complaint. They raised it because they expected to come back, and they want the next visit to be different. The apology says the business is sorry. Only the second contact says the business did something.
Why the loop stays open
The case is closed at the wrong moment. If resolved means the call was made and the remedy offered, nobody is holding the case when the fix is done, and nobody is prompted to call.
The fix happens somewhere else. The rota is changed by head office, the machine is repaired by a contractor, the briefing is given by the manager. The person who made the first call is not the person who did the fix and often does not hear that it happened.
Nobody owns the second contact. The first call has an owner because the customer is waiting. The second call has no one waiting for it, so it has no one making it.
It feels unnecessary. The customer accepted the remedy and seemed satisfied. Calling again seems like reopening a closed subject. It is the opposite, but it does not feel that way from the branch.
What the second contact says
Three sentences, specific, in the order the customer cares about.
What was done. "We have changed the morning rota so there are two people on from eight." "The card machine was replaced on Thursday." "We have gone back to taking table orders at that branch; it should never have stopped." "The team has had a session on checking the colour against the consultation card before starting." Not "we have taken your feedback on board".
That it was because of them. "Your message was the one that made us look at it." Customers rarely hear this and remember it when they do.
That the door is open. "If you are in again and it is not right, the same code goes straight to us." This is not a request for a review, a rating or a return visit. It is a reminder that the line exists.
Nothing else. No survey, no offer, no asking whether they are now happy. The second contact is a report, and it works because it asks for nothing.
When the second contact happens, by kind of fix
Replace or redo
Shortly after the redo. The customer has been back and the work has been done again. A message or a call within a day or two: was the second visit right, and here is what we changed so it does not happen again. If there was no process change, say that the team was told and leave it there.
Repair or replacement of something physical
When it is done. The customer who said the changing room lock was broken or the card machine kept failing gets a two-line message the day the repair is completed. This is the easiest loop to close and the most often forgotten, because the repair happens weeks later and the case was closed at the apology.
Rota or staffing change
When the change takes effect, not when it is decided. "From next Monday there is a second person on the morning shift." If the customer visits in that window and it is better, they will connect it to their message. If they are told before it happens and it does not happen, the second contact has made things worse.
Briefing or coaching
The same day or the next. "The team has been talked to about acknowledging people in the queue." Short, no names, no detail about individuals. The customer does not need to know what was said to whom, and the team's privacy matters here.
Policy restored or clarified
When the branch is doing it again. "Table service is back at that branch; the gap was a local decision that should not have been made." This one is also worth telling the branch team, since the customer's message is the reason the policy came back.
No fix possible
See below. There is still a second contact.
Who makes it
The owner of the case, which is usually the branch. The branch made the first call, the branch knows the customer, and a second call from the same person lands as continuity.
Where the fix was made above the branch (a rota budget, a system change, a policy), head office tells the branch that the fix is done and the branch makes the call. The customer should not hear from a different person each time, and head office should not be making branch-level calls across a group.
Where the first contact was made by the area manager or head office because the branch was the wrong caller, the second is made by the same person.
Keeping the case open until the fix is done
This is the mechanical part, and it is why the loop closes or does not.
Resolved means the fix is done and the customer has been told. Not the apology, not the remedy accepted, not the fix scheduled. If that definition is in place, a case with a rota change pending stays open with a date, and whoever owns it is prompted on that date.
The case carries the fix and the date. When the first call ends with "we will add a second person from the first of the month", that date goes on the case. The owner sees it come up. Head office sees it if it passes.
The open list does not fill up if the cases on it are real. A case waiting for a repair date is not clutter; it is a customer who has not yet been told. If the list is long, that is information about how long fixes take, which head office should want to know.
A case the customer reopens after the second contact (they came back, it was not fixed) is the most useful case in the system. It means either the fix did not hold or it was never made.
Outhentik keeps cases this way: a case has an owner, a state (Open, Contacted, Resolved, Reopened) and a clock, and Contacted is a separate state from Resolved, so a case that has had its apology but not its fix is visible to head office as still open.
When there was no fix
Some complaints are about something that cannot be changed: a wait on one unusually busy afternoon, a policy the business has decided to keep, a product that has been discontinued. The loop still closes, with a different message.
Say what was looked at. "We checked the rota for that afternoon and it was fully staffed; it was an unusual day."
Say what the decision was and that it was a decision. "We have kept the no-substitutions policy because of allergen control, and we should have explained that at the counter."
Say what, if anything, changes. Often the thing that changes is how the branch explains the policy, which is a fix in its own right.
A customer who is told the honest answer, even an unwelcome one, has been closed with. A customer who was apologised to and then heard nothing assumes the apology was the whole response.
What not to do
Close the case at the apology. Everything in this article follows from not doing this.
Call before the fix is in place. A promised rota change that has not yet happened is a second promise, and a second promise not kept is worse than the first.
Describe what was said to a named staff member. The customer gets "the team was briefed". What happened with an individual is between the manager and that person.
Use the second contact to ask for anything. A review, a rating, a return visit, a survey. The moment it asks for something it stops being a report and becomes a pitch, and the customer notices.
Send a template. "Thank you for your feedback, we have taken steps to address your concerns" is not a second contact. It is a sign that nobody did anything.
Let head office make branch-level follow-up calls across the group. It does not scale past the first region and the customer hears from a stranger.
Treat the second contact as optional for small cases. The cases that seem small are the ones where the customer least expects to hear back, and where hearing back has the largest effect.
What to expect
Most second contacts are short. A message rather than a call is fine for repairs and rota changes; a call is better where the first contact was a call and the complaint was about people.
The open list will be longer than before, because cases now stay open until the fix is done. That is the correct length.
Fixes that take a long time will become visible, by branch and by kind. Head office will learn which contractors are slow and which rota changes sit in a queue, which is information it did not have when cases closed at the apology.
A customer who has been closed with can still leave, and can still post a review anywhere they like. The second contact gives them the account of what was done. It does not decide what they say elsewhere, and should not be presented internally as if it does.
Frequently asked questions
What does it mean to close the loop on a customer complaint?
Contacting the customer a second time, after the thing they complained about has been fixed, to say what was done. The apology and the remedy are the first contact. The second contact is the report that the problem behind the complaint was addressed.
When should you follow up with a customer after a complaint?
When the fix is in place, not when it is promised. For a repair, the day it is done. For a rota change, when it takes effect. For a briefing, the same or next day. For a redo, shortly after the second visit.
What should you say when following up after fixing a complaint?
What was done, specifically. That their message was the reason. That the line is still open if it is not right next time. Nothing else: no survey, no offer, no request.
Who should contact the customer after the fix?
The same person who made the first contact, usually the branch. Where head office made the fix, it tells the branch and the branch makes the call, so the customer hears from one person throughout.
Should a complaint case be closed after the apology?
No. Resolved should mean the fix is done and the customer has been told. A case waiting on a repair or a rota change stays open with a date, and the owner is prompted when the date comes.
What if nothing could be fixed?
Still close the loop. Say what was checked, what the decision was and why, and what if anything changes as a result, which is often how the branch explains the policy. An honest unwelcome answer closes a case. Silence after an apology does not.
Try Outhentik free for 7 days, no credit card required
Outhentik gives head office a direct line from customers at every branch: every message read the same way, a case with an owner for each customer who asks to hear back, and a daily view of which problems repeat and where. A case stays open past the apology until the fix is done and the customer has been told, and head office can see which ones are still waiting.