All templates
OperationsSOPUS edition

Customer Complaint Handling Procedure template

A customer complaint handling procedure is the written process your team follows when a customer says something has gone wrong — how to take the complaint, how to de-escalate, what each person is authorized to resolve on the spot, when to escalate, and how every complaint gets logged. It gives frontline staff a script for one of the hardest moments in the job.

Free to use
US-focused
Updated 13 July 2026
UK version →

Complaints handled well are cheap and often win the customer back; complaints handled inconsistently become refund disputes, one-star reviews, and chargebacks. The difference is rarely the goodwill budget — it is whether the first person who hears the complaint knows what they are empowered to do.

This template gives you a ready-to-edit procedure: intake and de-escalation steps, resolution authority limits, handling for written and online complaints, the categories that always escalate, and the log that turns individual complaints into operational fixes.

The template

Full text, ready to adapt.

Highlighted fields are placeholders — replace them with your organisation's specifics. A starting point, not legal advice.

Customer Complaint Handling Procedure

SOP · Operations

1. Purpose and scope

This procedure sets out how {{org.name}} receives, resolves, and learns from customer complaints across [channels — in person, phone, email, social media, review platforms]. It applies to all customer-facing staff and managers.

A complaint is any expression of dissatisfaction about our products, service, staff, or premises — whether or not the customer uses the word "complaint".

2. Roles and responsibilities

  • All customer-facing staff: acknowledge and attempt first-contact resolution within their authority limits, and log every complaint.
  • Manager on duty ([role]): handles escalations on shift, approves remedies above staff limits, and decides whether a complaint needs the complaints owner.
  • Complaints owner ([name/role]): reviews the complaint log [frequency], responds to written and review-platform complaints, and owns this procedure.
  • [Name/role]: handles complaints alleging discrimination, harassment, or harm — these are never resolved at the counter.

3. Taking the complaint

  1. 1Stop what you are doing and listen without interrupting. Let the customer finish before responding.
  2. 2Thank them for raising it and apologize for their experience — apologizing for how they feel is not an admission of fault.
  3. 3Ask questions until you can repeat the problem back accurately: what happened, when, and what they have already been told.
  4. 4Ask what outcome they are looking for. It is often smaller than you expect.
  5. 5Fix it on the spot if it is within your authority: [list — e.g. replace the item, remake the order, refund up to $[amount]].
  6. 6Escalate to the manager on duty if the remedy exceeds your authority, the customer remains dissatisfied, or the complaint involves safety, allergens, staff conduct, or discrimination.
  7. 7Log the complaint before the end of your shift: date, customer, issue, action taken, and whether follow-up is owed.

4. De-escalation basics

  • Lower your voice and slow down as the customer gets louder — matching volume escalates, contrast de-escalates.
  • Move the conversation away from other customers where you can: a quieter corner, the end of the counter, a call-back.
  • Use the customer's words back to them ("so the order arrived cold, twice") — feeling heard defuses more anger than any refund.
  • Never argue the customer's motive, quote policy as a wall, or say "calm down" — explain what you can do, not what you cannot.
  • If a customer becomes abusive or threatening, disengage and get the manager on duty; staff safety outranks the complaint. [State the house rule for when to ask a customer to leave and when to call 911.]

5. Resolution authority

First-contact resolution is the goal, and it only works when limits are explicit. Frontline staff may resolve complaints up to $[amount] per customer per visit using [remedies — replacement, refund, comp item]; the manager on duty may authorize up to $[amount]; anything above that, or any pattern of repeat claims from the same customer, goes to [name/role].

Every remedy is logged with its value. The log is what lets you keep limits generous — abuse shows up in the data, not in tighter rules for everyone.

6. Written and online complaints

  1. 1Acknowledge emails, letters, and review-platform complaints within [number] business days, naming who is handling the matter.
  2. 2Investigate before replying: check the complaint log, POS records, security camera footage [if held], and speak to the staff involved.
  3. 3Respond within [number] business days with what you found, what you will do, and one direct contact for anything further.
  4. 4On public review platforms, keep replies short and civil, never share personal details, and move the conversation to a private channel. Never pressure a reviewer to delete a review — offer to fix the problem instead.
  5. 5If the customer remains dissatisfied after the response, escalate to [name/role] for a final reply.

7. Complaints that always escalate

Any complaint suggesting someone was or could have been harmed — an injury on the premises, an allergic reaction, a product fault — goes to [name/role] the same day and is handled under the relevant safety procedure, including preserving the product or evidence. Do not offer a remedy that could look like closing the matter down before it is investigated.

Complaints alleging discrimination or harassment by staff are escalated to [name/role] immediately and handled under our HR procedures, not resolved at the counter with a refund. Complaints that arrive as chargebacks, demand letters, or from a lawyer go straight to [name/role] — respond through the right channel, not from the shop floor.

8. Logging, trends, and review

Every complaint goes in the complaint log at [system/location]: date, channel, category, remedy, cost, and owner. [Name/role] reviews the log [frequency] for repeat categories — three complaints about the same thing is an operational fault, not three unlucky customers. Logs are retained for [period] and feed into training, supplier reviews, and product changes.

This procedure is reviewed [frequency, e.g. annually], after any complaint that escalates to a formal dispute or chargeback, and whenever channels or authority limits change. Owner: [name/role]. Next review due: [date].

Make it yours

How to adapt this template.

1

Set the frontline authority limits first — a procedure without a refund limit staff can use unsupervised will fail on the first busy shift.

2

List your actual channels in the scope section, including review platforms, and name who monitors each one.

3

Rehearse the intake and de-escalation steps at a team meeting using your last three real complaints as scenarios.

4

Set up the complaint log before publishing the procedure, and make logging take under a minute — or it will not happen.

5

Agree with [HR/owner] exactly where discrimination and safety complaints go, and put a real name on it.

6

Check your state's rules on refund and return policy disclosure and make sure your posted policy matches what this procedure promises.

A document is not a system

Turn this template into trained, proven behaviour

A policy in a drawer proves nothing. In TrainedTeam this template becomes assigned training with knowledge checks, e-signature acknowledgments, version history, and an audit-ready record of who completed what, when.

Customer Complaint Handling Procedure template FAQs

Is a customer complaint procedure legally required in the US?

For most businesses, no — it is best practice rather than statute, although some regulated sectors have their own complaint handling rules. What every business has is exposure when complaints are handled badly: state consumer protection laws, chargebacks, and FTC action against unfair or deceptive practices all start where resolution failed. The procedure earns its keep by ending complaints at first contact.

Should frontline staff be allowed to give refunds?

Yes, up to a stated limit. First-contact resolution is cheaper and calmer than escalation, and a small, clear authority limit — with everything logged — costs less than the escalations it prevents. Review the log to check the limit is not being abused before tightening it.

How should we respond to negative online reviews?

Once, briefly, and politely: acknowledge, state what you are doing, and offer a private channel. Never share the customer's details, argue the facts in public, or pressure the reviewer to take the review down — federal law protects honest reviews, and the FTC has acted against businesses that try to suppress them. A gracious public reply is read by every future customer; the reviewer is almost the secondary audience.

What should we do if a complaint mentions an injury or allergic reaction?

Treat it as a safety incident, not a service complaint: escalate to [name/role] the same day, preserve the product and records, and follow the relevant safety procedure. Do not settle it at the counter — you need to know whether anyone was harmed and whether other customers are at risk before anything that looks like closing the matter.

What if the customer files a chargeback or threatens to sue?

Move it off the shop floor immediately. Chargebacks are answered through your payment processor's dispute process with the transaction records and your complaint log as evidence; legal threats go to [name/role] and, where needed, your attorney. The complaint log you kept at the time is usually the document that decides both.