Handling customer complaints well requires more than a considerate reply. A dependable process makes it easy to raise a concern, gives the case an owner, investigates each issue fairly, explains the decision, delivers any approved remedy, and uses the evidence to improve service.
This guide covers that repeatable process for support teams: the response framework with illustrative wording for each stage, the records and technology behind it, complaint analysis, and difficult scenarios. For a tense or abusive interaction, use the separate difficult-customer guide.
Treat a complaint as evidence and a request for review
A complaint tells you that someone is dissatisfied with an experience, decision, or response. It can expose a service failure, a confusing expectation, or a concern that needs investigation. It is not automatically proof of fault, and it does not become less important because the customer describes it calmly.
Avoid calling every complaint a gift. The customer may have spent considerable effort reaching you. They need the concern addressed, rather than a lesson about how useful their frustration is to the business.
Make reporting accessible and explain what the team can consider. Publish the contact route, relevant process stages, expected updates, and review options. Do not require a customer to use the exact word “complaint” before recognizing a request to challenge a service outcome.
The Parliamentary and Health Service Ombudsman’s customer-focused principles, written for public bodies, support clear, accessible procedures, an ongoing contact point, and communication appropriate to the complainant. Use these as a process reference while following the requirements that apply to your organization.
Low complaint volume does not prove that customers are happy. Reporting may be difficult or people may choose another action. Rising volume can reflect a real failure, broader use of the product, or a newly accessible contact route. Investigate before declaring success or deterioration.
Give agents a useful mindset and real authority
Teach agents to understand the concern before defending the business. Acknowledge the specific experience, ask for clarification where needed, and distinguish the customer’s report from a confirmed finding.
Empathy does not require guessing motives or agreeing with an unverified explanation. “You were promised an update and did not receive it” addresses a concrete failure. If your team made that mistake, acknowledge it and apologize plainly.
Give agents a written decision guide: what they can correct, which remedies they can approve, what needs specialist review, and who owns exceptions. Without that authority, a friendly reply can still leave the customer waiting for a decision nobody is taking.
Explain the conduct procedure alongside the complaint process. Critical feedback and disagreement are different from abuse or threats. Staff need a clear way to obtain help, while the business still considers the underlying complaint appropriately.
Use a four-stage complaint-handling framework
The following framework preserves a straightforward flow: acknowledge, investigate, decide and act, then follow up. It is an illustrative operating model, not a formal standard or a promise that every complaint can be resolved the same way.
| Stage | Responsible role | What must be recorded |
|---|---|---|
| Acknowledge and agree the scope | Case communication owner | Concerns, desired outcome, contact method, urgency and next update |
| Investigate fairly | Investigator or relevant specialist | Evidence for each concern, gaps and findings |
| Decide and carry out the remedy | Authorized decision and action owners | Reasoned decision, approved action and completion evidence |
| Follow up and learn | Case owner and improvement owner | Outcome, remaining concern, review route and systemic action |
1. Acknowledge and agree what needs investigation
Capture the complaint in one usable record, even when it began in chat, a call, or a public message. If private account information is needed, explain the approved private route and preserve the context already supplied.
Identify each concern and the outcome requested. A customer might dispute a charge, complain about an earlier answer, and request an explanation of the policy. Treat those as separate questions within the case so the eventual response does not address only the billing detail.
Ask what would resolve the complaint from the customer’s perspective. A refund, correction, explanation, or restored workflow are different outcomes and may require different authority. Then ask the customer to correct your summary: delayed responses, repeated explanations, or an inaccurate promise can be concerns in their own right.
Illustrative clarification: “You have asked for the charge to be reviewed and for an explanation of why it appeared. I will check both. Is there another part of the complaint you want us to address?”
Name the communication owner and set a realistic update commitment. Triage urgent risk or harm through the appropriate process. An automatic receipt can confirm arrival; it should not claim that the complaint has already been investigated. You can promise a specific investigation or update; do not promise a remedy before checking eligibility and authority.
Illustrative first response:
Thank you for explaining what happened. You expected [result], but [reported problem] occurred, causing [impact]. I will review [relevant records / issue] and update you by [time and time zone]. Have I captured the main concern correctly?
Use words that fit the actual situation. Repeated generic apologies without action can add frustration. Our technical communication guide covers explaining problems in plain language.
2. Investigate the facts and the earlier service response
Review relevant conversations, transactions, product behavior, policy versions, and previous promises. Ask the customer only for missing information necessary to assess the concern. Explain why the information is needed and use approved handling for sensitive evidence.
Create an issue-by-issue record rather than a pile of screenshots. Separate what the customer reports, what records confirm, the working interpretation, and what remains uncertain. For each concern, capture:
- Expected result: What should have happened, including any promise made.
- Observed result: What the customer reports and what records confirm.
- Timing: Relevant dates and time zones.
- Previous action: What was already tried and what happened.
- Current impact: Whether the problem persists and who is affected.
- Evidence gaps: What remains uncertain and how you will check it.
Avoid asking for passwords, unnecessary personal information, or broad recordings of a customer’s workspace.
The Ombudsman’s fairness principles emphasize evidence-based investigation, proportionate handling, consistency, and fair treatment of staff as well as complainants. For disputed events, obtain an appropriate review rather than asking the person involved to be the sole judge of their own response.
Escalate when the case needs expertise, permissions, a formal review, or an exception decision. The escalation should move the investigation forward rather than simply transfer the customer to another queue. Include the complaint summary, desired outcome, confirmed evidence, attempted actions, reason for escalation, and next update commitment, and name both the decision owner and the person communicating it. Tell the customer why the specialist is involved without asking them to resend the same evidence. The support ticket escalation process covers a complete handoff; if a wider incident is involved, coordinate replies with the incident workflow so messages reflect the current confirmed state.
3. Explain the decision and deliver the approved action
Address every agreed concern. Explain the evidence considered, the finding, the reason for the decision, and what will happen next. If evidence is inconclusive, state the limit rather than inventing certainty.
If your team caused the problem, apologize for the specific failure and describe the approved corrective action. Do not blame another department, criticize the customer, or claim the matter is fixed before verifying it.
Illustrative confirmed-error response:
We reviewed [evidence] and confirmed [finding]. We made an error in [specific action]. I am sorry for [specific impact]. We have [completed corrective action] / will [approved next action]. You should now see [expected result]. Please let us know through [route] if the result differs.
Check authority before offering a refund, credit, correction, or exception. An internal policy needs to be applied through the process relevant to the case; it should not become a stock phrase that prevents review of a legitimate concern. When the requested remedy is unavailable, explain why and offer the legitimate next option.
Illustrative decision response:
We reviewed [request and relevant facts]. Our decision is [decision], because [clear, applicable reason]. The available option is [approved alternative, if any]. If you disagree or have additional evidence, [review / escalation route].
The Ombudsman’s remedy guidance describes responses including explanations, apologies, corrective action, and financial remedies appropriate to the circumstances. That provides a useful range of possibilities, rather than a rule that compensation always works or an apology is always enough.
Record who will complete the remedy and how completion will be checked. Promising an adjustment and confirming that it was applied are different milestones. Explain any review route available when the customer disagrees.
4. Verify the result and follow up
Check the outcome at a point that fits the action. Ask whether the corrected record or workaround addresses the original need. If a technical fix remains open, distinguish the temporary restoration from the permanent change. If engineering is still investigating, send the promised update even when there is no fix yet.
Illustrative follow-up: “The correction has been applied. Can you confirm that the displayed amount now matches the result we discussed? If anything still differs, reply here and I will continue the review.”
Do not treat silence as satisfaction. Follow the documented closure process, preserve uncertainty, and explain how to return to the case when appropriate. A follow-up should check the actual result rather than add an unsolicited promotional message.
Record any separate improvement action with its own owner. Closing the customer case should not erase a linked defect or process failure that still needs work.
What to say in common complaint situations
These patterns apply at any stage of the framework. Adapt the wording to the confirmed facts of the case.
| Situation | Useful response | What to avoid |
|---|---|---|
| You do not yet know the cause | Explain what is confirmed and what you will investigate next | Inventing a cause or fix date |
| A promised update was missed | Acknowledge the missed commitment and give a realistic next step | Repeating the same unsupported deadline |
| The customer has contacted several teams | Summarize existing evidence and name the owner | Asking them to start the story again |
| The requested remedy needs approval | Explain who will review it and when you will update | Promising approval in advance |
| The customer disputes your finding | Review additional evidence and explain the next review route | Arguing or repeating the conclusion without addressing the objection |
| The conversation becomes abusive | Apply your approved conduct policy and offer a clear boundary or alternative | Retaliating or dismissing the complaint solely because it is critical |
Use technology to preserve context and clarify the problem
A helpdesk or case system should show the concerns, evidence, commitments, decisions, and current owner. Relevant account history can help agents avoid repeated questions. Access to a CRM does not mean every detail should be copied into the complaint record.
The Ombudsman’s accountability principles connect clear explanations with reliable records of evidence and decisions. Keep internal diagnostic notes separate from the customer-facing decision, with access managed through your established process.
For a screen-based problem, choose the evidence format that answers the missing question. A screenshot can show a state; a recording can show a sequence; an agreed live conversation can clarify an ambiguous task. A straightforward complaint about a charge may need transaction evidence instead of video.
Screendesk provides customer recording links and helpdesk-connected video workflows. Use a focused capture or walkthrough where it helps, offer written alternatives, and exclude unrelated private information. A recording can show what happened during an attempt; it does not independently prove the cause or replace an authorized remedy decision. Developer context such as console logs and network capture requires the relevant setup and plan; it does not automatically come from every recording. For a reproducible technical issue, use a structured bug report to carry the evidence forward.
Automate bounded administrative work such as reminders and routing where your system supports it. Check that the accepting team receives the evidence and the customer still has a clear contact. A generated response or sentiment label should not determine whether the complaint is valid.
Keep a compact complaint record
This original template is an illustrative starting point. Adapt its fields and handling to your organization’s procedure rather than introducing a second record disconnected from the existing case system.
Complaint operating record Case reference and received date: Customer concerns and requested outcomes: Impact, urgency and appropriate route: Communication needs and agreed channel: Communication owner and next update: For each concern: Customer report: Evidence reviewed and remaining gap: Finding and reason: Decision owner / review required: Approved remedy, action owner and completion check: Outcome communicated and review route: Customer confirmation / disagreement / no response: Related improvement action, owner and review date:
Illustrative case: A customer disputes a subscription charge and says an agent promised a correction that never appeared. The reviewer checks the charge separately from the earlier promise. A finding that the charge matches the subscription does not automatically answer whether the team mishandled the explanation or commitment. The final response addresses both issues and records any remaining review. This is an invented example, not a customer success story.
Turn complaint themes into specific improvement work
Use consistent categories based on the concern: disputed charge, confusing invoice, export failure, missed update, or difficult access to support. Preserve the original account so a tag does not become a substitute for evidence. Separate topic, reported impact, finding, and remedy.
GOV.UK’s research-analysis guidance separates observations from interpretations and actions. Apply that discipline to complaint review: first capture what happened, then investigate the explanation, then choose the change to test.
Deduplicate repeated messages about the same case. State whether a report counts cases, distinct customers, affected transactions, or individual issues. A case can include several themes, so theme totals may exceed the number of cases.
Illustrative reporting example: In a fictional month’s 20 unique complaint cases, eight mention unclear invoices and five mention missed updates. Three mention both. The invoice theme appears in 8 ÷ 20 = 40% of that complaint-case set; it is not a claim that 40% of all customers had an invoice problem. The two themes overlap, so adding their counts would not give the number of distinct affected cases.
Share a short improvement brief with the relevant team: observed concern, case count and scope, supporting evidence, uncertainty, proposed action, owner, and a check of the result. Include severity as well as frequency. A serious one-off access problem may need attention before a common minor wording issue.
The Ombudsman’s improvement principles call for recording and analyzing complaint learning and feeding it back into service changes. Tell customers about completed changes where appropriate, while avoiding promises about work that has not been approved. The continuous improvement examples show how to turn a recurring obstacle into a focused experiment, and customer service best practices cover wider team expectations.
Review performance without rewarding premature closure
Review unresolved case age, missed update commitments, completed remedies, repeated contacts, and sampled decision quality. Read customer feedback alongside the record. A rapid closure can still miss part of the complaint, and a long investigation can reflect missing specialist capacity rather than poor agent communication.
Define each measure’s case cohort, clock, exclusions, and reporting period. Report open cases alongside completed cases so unfinished difficult work is visible. If using a complaint rate, choose the relevant exposure denominator and observation window; do not compare case counts alone across differently sized customer groups.
Use a learning review to identify where the process breaks: inaccessible intake, incomplete scope, missing evidence, delayed approval, or uncompleted remedy. Give staff feedback on what they could control and assign systemic fixes to the appropriate owner.
Questions that arise in difficult complaint cases
What if the requested remedy is unavailable?
Explain the decision and applicable reason, offer legitimate alternatives if any, and describe the review route. Do not invent a credit or promise an exception to make the conversation end.
What if the customer remains unhappy?
Check whether you addressed every part of the complaint and considered the relevant evidence. Explain the decision, remaining options, and any review route. Stay professional and follow your conduct and closure procedures; satisfaction cannot be guaranteed.
How quickly should a complaint be resolved?
Set expectations according to urgency, complexity, and the requirements relevant to your organization. Provide a realistic update commitment and keep it. Avoid a universal deadline that your team cannot support.
What if a customer becomes abusive?
Apply the approved conduct and safety process to the behavior. Preserve a fair review of the complaint itself and arrange an appropriate continuation route where available. De-escalation wording does not replace staff support and clear boundaries.
Does a well-handled complaint guarantee loyalty?
No. A fair response and completed action can help address the failure, but they do not establish future purchases or restored trust. Prevent recurring problems and review actual customer outcomes rather than assuming a recovery effect.
