Customer complaints handling SOP
A complaint is information about where the business is falling short, and it is only useful if it is recorded and acted on. This template gives you a consistent path from the first contact to a closed case, with an owner for every step and a record that survives the person who handled it. It is written for small teams without a dedicated support function. The worked example follows a complaint about a late delivery from receipt to resolution. The rule that matters: never promise a resolution you cannot make, and always say when the customer will hear next.
A consistent way to receive, record and resolve a customer complaint, so the same standard applies every time and a resolution is never lost.
SOP-006 · Rev 1.0
[CUSTOMER COMPLAINTS HANDLING SOP]
A complaint is information about where the business is falling short, and it is only useful if it is recorded and acted on. This template gives you a consistent path from the first contact to a closed case, with an owner for every step and a record that survives the person who handled it. It is written for small teams without a dedicated support function. The worked example follows a complaint about a late delivery from receipt to resolution. The rule that matters: never promise a resolution you cannot make, and always say when the customer will hear next.
1. PURPOSE
> Note — One sentence on why this procedure exists.
[PURPOSE]
2. SCOPE
> Note — What counts as a complaint here.
[SCOPE]
3. RECEIVING
> Note — How a complaint is captured, whatever the channel.
[RECEIVE]
4. RECORDING
> Note — The record that makes the complaint resolvable and reviewable.
[RECORD]
5. RESOLUTION
> Note — The steps to resolve, and who approves what.
[RESOLVE_1]
[RESOLVE_2]
[RESOLVE_3]
6. ESCALATION
> Note — When a complaint goes up, and to whom.
[ESCALATE]
7. REVIEW
> Note — How complaints are reviewed for patterns.
[REVIEW]
Free to use in your own documents, including commercially.
Purpose
[PURPOSE]
Scope
[SCOPE]
Receiving
[RECEIVE]
Recording
[RECORD]
Resolution
[RESOLVE_1]
[RESOLVE_2]
[RESOLVE_3]
Escalation
[ESCALATE]
Review
[REVIEW]
Worked example
Purpose
To resolve every complaint to a clear, recorded outcome within a stated time, so no issue is lost and the same standard applies each time.
Scope
Complaints received by email, phone or in person about products or service. Pricing disputes go to the owner directly.
Receiving
The person who takes the complaint records the date, the channel, and the customer's words, and confirms they have heard the issue.
Recording
The complaint goes on the shared tracker with the date, the issue, the customer's contact, and who owns it.
Resolution
The owner investigates within one working day and confirms the facts with the customer if anything is unclear.
The owner decides the resolution within its limits — replacement, refund or a straight answer — and tells the customer what will happen and when.
The case is closed on the tracker with the outcome and the date, and the customer is told it is closed.
Escalation
If a complaint is not resolved in five working days or concerns a safety issue, it goes to the owner personally, who answers it directly.
Review
The owner reviews closed complaints monthly for patterns and fixes the cause rather than only the case.
These documents are starting structures for you to build on, not professional or legal advice. Anything that will have legal or contractual effect, or that varies by jurisdiction, should be reviewed by someone qualified in the relevant place.
Why this process gets written down
This procedure is written because the task is repeated, it matters when it goes wrong, and it should not depend on one person's memory. The worked example above shows the same structure filled in for a real case, so you can see what a complete version looks like before you write your own.
Related variants are listed in the document's control area and on the SOP template page.
Turn a folder of documents into something a team can actually find and follow
Every template on this site is free and stays free. The kit is what turns a folder of documents into a system you can actually run: a register with numbers, owners and review dates; who reviews what and how often; a numbering scheme that still works at fifty documents; and the thirty-day sequence for getting a team to use any of it, which is where most of these projects die.
Opens a short sponsor step, then brings you straight back to this page with the kit open. Nothing you have entered goes with you.