Customer complaint process map

A swimlane map of a complaint from intake to closure, across the customer, customer service, quality, the owning department and management. The investigation phase deliberately sits outside customer service's lane, because a complaint that is only ever handled by the people who receive complaints never changes anything.

Open this map in the editor

Opens a copy in the editor and saves it in this browser. No account, nothing sent anywhere.

What is in this map

19 steps across 5 swimlanes and 5 phases, with 4 decision points.

Swimlanes (who does the work): Customer, Customer Service, Quality, Department Owner and Management
Phases (left to right): Intake, Assessment, Investigation, Resolution and Closure

Why map this process

Complaint handling has two jobs that pull against each other: satisfy this customer quickly, and find out why it happened. The first is customer service's; the second belongs to whoever owns the process that failed. Companies that treat complaints as a service function do the first well and never do the second, which is why the same complaint keeps arriving.

Drawing the handoff into the quality and department-owner lanes is what makes the second job real. It also makes visible the tension between the two clocks (the customer is waiting on a resolution that may be faster than the investigation), which is a legitimate design decision the map lets you make deliberately rather than by default.

Every step in the map

This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.

Every step in the Customer complaint process process map, in the order the editor numbers them.
#	Step	Shape	Swimlane	Phase	Goes to
1	Customer submits complaint	Start	Customer	Intake	2
2	Log complaint in register	Registry	Customer Service	Intake	3
3	Acknowledge receipt within 2 days	Process	Customer Service	Intake	4
4	Classify severity and category	Process	Quality	Assessment	5
5	Serious or safety related?	Decision	Quality	Assessment	6 (No), 7 (Yes)
6	Assign to department owner	Process	Department Owner	Assessment	8
7	Escalate to management review	Process	Management	Assessment	8
8	Investigate root cause	Process	Department Owner	Investigation	9
9	Verify evidence and history	Process	Quality	Investigation	10
10	Complaint valid?	Decision	Quality	Investigation	11 (No), 12 (Yes)
11	Explain decision to customer	Process	Customer Service	Resolution	15
12	Agree remedy and timeline	Process	Department Owner	Resolution	13
13	Deliver fix or compensation	Process	Department Owner	Resolution	14
14	Communicate resolution to customer	Process	Customer Service	Resolution	15
15	Customer accepts outcome?	Decision	Customer	Closure	16 (No), 17 (Yes)
16	Escalate unresolved complaint	Process	Management	Closure	8 (Reopen)
17	Systemic cause identified?	Decision	Quality	Closure	18 (Yes), 19 (No)
18	Raise corrective action (CAPA)	Process	Quality	Closure	19
19	Close complaint and record outcome	End	Customer Service	Closure	End

The decision points

Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.

5. **Serious or safety related**?

Owned by Quality · Assessment
- No → step 6
- Yes → step 7
10. Complaint valid?

Owned by Quality · Investigation
- No → step 11
- Yes → step 12
15. Customer accepts outcome?

Owned by Customer · Closure
- No → step 16
- Yes → step 17
17. Systemic cause identified?

Owned by Quality · Closure
- Yes → step 18
- No → step 19

Notes on specific steps

These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.

2. Log complaint in register: Capture channel, date received, product or service, order reference and customer contact in one record.
3. Acknowledge receipt **within 2 days**: The acknowledgement clock starts at the logged receipt date, not when someone picks the case up.
5. **Serious or safety related**?: Define the triggers: injury or safety risk, regulatory exposure, high value, or a repeat of an earlier complaint.
17. Systemic cause identified?: Raise a corrective action when the same root cause appears across more than one complaint.

Making it yours

The assessment step is where you set severity, and severity should drive two things: who investigates and how fast the customer is answered. Encode both in the branch labels off that decision. If you are in a regulated sector, the Notes column on the intake step is the right place for your reporting deadline: it is read by the person who logs the complaint, which is the only moment the deadline can still be met.

What to watch out for

Resolution and root cause are separate outcomes with separate owners. A map that closes the complaint when the customer is satisfied cannot record that the cause is still open, and the cause is the expensive part.
The escalation path to management needs a trigger, not just an arrow. 'Serious complaints go to management' is not a process; a decision with a stated threshold is.
If the complaint reveals a product defect affecting other customers, that is a different process; reference it as a step rather than growing this map into a recall procedure.

Frequently asked questions

Should every complaint go through investigation?

No, and the map should say which do. The assessment decision is where that judgement is made, and having it explicit is what stops the answer being 'whichever ones customer service had time for'. Low-severity complaints being resolved and logged without investigation is a legitimate design; being unable to say which were which is not.

How does this connect to root cause analysis?

The investigation phase hands off to it. This map handles the complaint; the root cause analysis map handles the underlying failure, which usually outlives the complaint and involves a different group. Keeping them separate stops a customer waiting on a five-why session.

Where does the customer's acknowledgement fit?

Immediately after intake, in the customer service lane, before assessment. It is drawn as its own step because it is the one commitment with a deadline the customer can observe, and folding it into intake removes the ability to measure whether it was met.

Open the map and start editing

The editor loads this chart with the spreadsheet underneath it. Change a cell and the diagram redraws — no drawing, no signup.

Open this map in the editor