top of page

What to do with negative feedback after you have said sorry

Sep 29
4 min read

“Your team gave me three different answers.”


That message is painful to receive. It can also be more useful than a vague compliment. It tells you where to look: the customer had to repeat themselves, the answers changed, and the organisation did not feel like one team. The question now is what you do beyond apologising.


I have worked in customer support long enough to know that negative feedback can land heavily with the colleague who receives it. Sometimes the complaint is fair. Sometimes it leaves out context. Either way, the person handling it needs enough support to respond thoughtfully, and the business needs a way to learn from it. A defensive reply helps neither.


First, understand the actual harm

Read the message for the customer's experience, not just the accusation.

What were they trying to do.

What did they expect.

Where did the journey break down.

What happened because of it, lost time, money, confidence, access, or an important deadline.


Check the case history before replying. If another teammate has already promised an action, acknowledge it. If a decision depends on a policy, verify the current policy. Do not make the customer explain everything again merely because their case passed between colleagues.


A useful response can be plain: “I can see you were given different information about the next step. I am checking the account history and the current rule now. I will update you by 3 pm with what we can do.” The time should be one you can meet. If you cannot resolve it by then, send a progress update rather than disappear.


Harvard Business Review's reporting on service recovery suggests that repeated apologies are a poor substitute for an active plan. An apology can acknowledge the problem; the rest of the conversation should show what happens next.


Resist the urge to litigate a review

Public reviews are read by people beyond the original customer. A reply should protect privacy, recognise the concern and offer a practical route to resolution. Avoid posting case details or turning the response into a point-by-point rebuttal. If a claim is inaccurate, you can correct it calmly with information you are permitted to share.


Research discussed in Harvard Business Review found that replying to customer reviews was associated with improved ratings in the setting studied. That is a reason to take responses seriously, not a guarantee that any particular reply will win someone back. The tone and the follow-through still matter.


Some complaints will require a remedy: correcting a charge, restoring access, replacing an item or explaining a decision with care. Acknowledge what is within your control and escalate what is not. Do not promise a policy exception before the person authorised to approve it has decided.


Find the pattern behind the incident

After helping the customer, ask why the problem happened. Was the rule unclear, did a handoff lose context.

Did the system show stale information or was the team short of capacity. Did a colleague follow a published SOP that no longer matched the process.


This is where Oomphio's interest in procedures meets customer experience. During my time in remote support, I saw how changing teams and scattered knowledge could lead well-meaning people toward different answers. A complaint about inconsistency may be evidence about the information system, not merely the person who sent the last message.


Bain & Company's work on closing the feedback loop describes bringing the customer's voice into the organisation, so people who can improve the work hear it and act. A simple version for a smaller team is enough: tag the theme, assign an owner, investigate a sample of cases, change the relevant rule or process, and check whether the same complaint recurs.


Suppose three customers report confusing renewal charges. The first case may call for an individual correction. Together, the cases might reveal an unclear email, a misleading screen or an SOP that tells agents to use different dates. Track the pattern and fix the source. Otherwise, the support team will keep performing excellent recovery from a problem the business keeps creating.


Care for the colleague as well

Feedback can be specific without becoming personal. A team lead should ask what information the colleague had, what they decided and what support they needed. If they missed a clear, current instruction, coach the decision. If the instruction was absent or wrong, fix the system. If a customer is abusive, the organisation should have a clear boundary and a route for staff to get help.


Make it easy to share a difficult case without fear that every report becomes a judgement of competence. The people closest to customers often see the first signs of a wider issue. If they expect blame, the organisation loses that early warning.


Close both loops

The first loop is with the customer: acknowledge, investigate, act and update them. The second is inside the team: identify the cause, improve the process and tell colleagues what changed. When appropriate, tell the customer that their feedback led to a specific improvement. Do so only when the improvement has actually been made.


Negative feedback will never feel pleasant, nor does every complaint prove that the business was wrong. But it offers an invitation to compare the experience you intended to deliver with the one somebody actually had. Take the person seriously, investigate fairly, and make the next customer's journey a little better.



Further reading and source notes


 
 
 

Comments


bottom of page