Complaint handling process: step by step

Why a written complaint handling process matters

A complaint handling process is the agreed set of steps your business follows every time a customer complains, whether at a counter, on the phone, by email or in a public review. Without one, the outcome depends on who happens to pick up the complaint. With one, customers get a predictable response and managers get records they can learn from.

The eight steps at a glance

1. Receive the complaint on any channel.
2. Acknowledge it and set expectations.
3. Record it in one place with a category.
4. Assess severity and assign an owner.
5. Investigate what happened.
6. Resolve and agree the remedy with the customer.
7. Close and confirm the customer is satisfied or knows the final position.
8. Learn: review patterns and fix causes.

Step 1: receive

Decide which channels count as complaint channels: counters, phone lines, email, chat, messaging, letters and public reviews. Every staff member who may receive a complaint should know the first two things to do: listen without arguing and capture the facts. A complaint does not need the word "complaint" in it to count; "I've been waiting forty minutes and nobody has told me anything" is one.

Step 2: acknowledge

Acknowledge quickly and tell the customer what happens next and by when. An acknowledgement is not a resolution; it is a promise of attention. For written channels, a short message the same working day is a common target. For face-to-face complaints, the acknowledgement happens in the conversation itself.

Step 3: record

Record every complaint in one register, even ones resolved on the spot. Capture date, channel, location, customer contact (with consent), what happened in the customer's words, a category and the person handling it. Recording resolved-on-the-spot complaints matters because they are often the early signal of a pattern.

Step 4: assess and assign

Rate severity using a short scale, for example routine, significant and serious. Serious complaints involve safety, legal threats, discrimination, data exposure or large financial loss and go to a named senior person. Every complaint gets exactly one owner, even if several people help.

Step 5: investigate

Gather facts before deciding: the customer's account, staff accounts, receipts, CCTV where appropriate, order or system logs. Keep investigation proportionate. A cold coffee needs a conversation, not a file. A billing error across several customers needs records.

Step 6: resolve

Offer a remedy that fits the problem: an explanation, an apology, a correction, a replacement, a refund or a goodwill gesture. Explain the decision plainly. If you cannot give the customer what they asked for, say why and what you can do instead.

Step 7: close

Close a complaint only when the customer has accepted the remedy or has been told the final position and any further options. Record the outcome and the date. A complaint closed without the customer knowing is a complaint that comes back, often as a public review.

Step 8: learn

Once a month, review complaints by category, location and trend. Look for repeat issues and ask what caused them. This is where complaint handling turns into fewer complaints. Bring public reviews into the same review, because many customers never complain directly; they just write a review.

Who owns what

• Front-line staff: receive, acknowledge, resolve simple complaints on the spot, record.
• Store or branch manager: owns significant complaints and local fixes.
• Customer care team: owns written and phone complaints, tracks deadlines.
• Senior manager: owns serious complaints and policy decisions.
• CX or quality lead: runs the monthly pattern review.

A worked example

A customer emails that she was charged twice for one purchase. Care acknowledges within hours and promises an answer in two working days. The complaint is recorded as Billing, payment error, significant, owned by the care lead. Finance confirms the double charge from transaction logs. Care refunds, apologises and explains when the money will appear. The customer confirms receipt and the complaint is closed. At month end, three similar cases at the same store point to a card terminal fault, which is replaced.

Common mistakes

• Treating only formal written complaints as complaints.
• Not recording issues resolved on the spot.
• Several owners and therefore none.
• Closing without telling the customer.
• Skipping the monthly learning step.

Common questions

Checklist

• Channels defined.
• Acknowledgement target set.
• One register with categories.
• Severity scale and owners.
• Closure confirmed with customer.
• Monthly pattern review.

In short

Receive, acknowledge, record, assess, investigate, resolve, close and learn. Give each complaint one owner, confirm closure with the customer and review patterns monthly, including public reviews.

Doing this with Falcon

Falcon is not a complaint management system and does not log calls, emails or in-store complaints. It analyses the complaints customers make publicly in Google Maps reviews of your locations and Google Play reviews of your app, classifies them into themes, sub-themes and specific issues from your own taxonomy, keeps the exact quote behind each label and shows negative share by topic, location and month. Using the same categories in your complaint log and in review analysis lets you see whether private and public complaints point to the same problems.