When new hires get their first complaint, they usually start by explaining. The noise was within permitted hours. The work was done right and only the paperwork is missing. Our processing room couldn't possibly have let that through. They may not be wrong. But the person complaining isn't waiting for an explanation. They're waiting to hear what will change.
The semiconductor fab, construction site, co-op and IT company maps in First Run include several quests where customers, residents, members and auditors raise complaints. This article uses them to set out the order of complaint handling, and the answers that get you through the moment but come back bigger later.
Four answers right after a complaint
The complaint-handling options in the quests usually take one of four shapes.
- Explain and ask for understanding: give reasons why there's no problem on our side.
- Tidy up the surface: fill in the records, or use compensation to get the complaint withdrawn.
- Promise big and put it off: next quarter, later, we'll be thorough.
- Check the facts, make a visible change and report back on the results.
Only the last one is Excellent. Why the other three fall short shows up a little differently in each quest.
An explanation doesn't replace action
This is the construction site's Noise and Dust Complaints quest. Residents of the neighbouring complex have complained to the district office about early-morning concrete-breaking noise and dust, and the district office wants an action plan.
- Send residents a formal letter explaining that the site works within its permitted hours, and asking for patience until completion: Poor
- Visit the resident who complained, offer money and ask them to withdraw the complaint: Poor
- To stop the weekday-morning complaints, move all concrete breaking to the weekend and hang a banner announcing it: Risky
- Check the readings and hear residents out, change the breaking hours, step up dust control and report back with a named contact: Excellent
The first answer may be true, but there's no action in it. As the feedback puts it, residents want something to change, not an explanation. With the second, the cause is still there, so other residents keep complaining, and all that's left is the impression you tried to buy silence. The third does act, but without asking the residents. More of them are home at weekends.
The Excellent answer has an order: check the facts, make changes people will notice (water spraying, dust screens), give them a contact, and share the results. Sharing the results with the district office and supervision lets everyone involved tell the same story.
Records can't be made after the fact
In the fab's Customer Audit Finding quest, the auditor flags two things. Two operators on a critical step have expired training certifications, and one SPC chart has an out-of-control (OOC) point with no action recorded.
- Explain that the work was done correctly and only the paperwork is missing, so quality isn't affected: Poor
- Have the team fill in the missing records before the closing meeting so the audit report stays clean: Poor
- Accept the findings and commit to retraining every operator on the line next quarter: Risky
- Accept the findings, contain now, check for the same gap elsewhere, and send causes and actions with dates: Excellent
To a customer, the record is the only evidence the work actually happened. So the feedback on the first answer, that without records you can't prove quality either, holds for complaint handling in general. The second answer gets through the meeting most neatly, but it's falsifying records, and once it comes out the trust you lose dwarfs the original finding.
The third answer is a shape new hires often pick: accept it and promise big. But waiting until next quarter with no containment leaves the same risk running, and retraining everyone doesn't match the cause. What to notice in the Excellent answer is that it looks for the same gap without being asked. The fastest way to win back a customer's trust isn't fixing the one item they flagged. It's showing you've checked the places they didn't flag.
Keep the evidence, promise a date
At the co-op store, a member comes back with a piece of hard plastic she found in minced meat. Her child nearly ate it, and she is upset. This quest is covered in detail in Co-op and grocery onboarding scenarios, and for complaint handling there are two things to remember. Refund her to close it quickly and throw the object away on the spot, and the only clue to the cause is gone. And "We'll get back to you later" is a different promise from "We'll have the results to you by this date". With a date, the other person can wait.
Answer public criticism in public
In the co-op's member relations quest, after a study session on food additives, a members' voice card goes up on the board: "It only told one side. Wasn't it just an ad for the co-op's own brand?" A few people on the planning committee say it's just a complaint and should be ignored.
- Take the card down from the board: Poor
- Gather the data and print a point-by-point rebuttal in the newsletter saying the additive worries are a misunderstanding: Risky
- The writer left contact details, so get in touch privately, apologise and invite them to the next session: Good
- Thank the member and answer publicly in the newsletter with how the next session will change (an outside speaker, several viewpoints, members co-planning it): Excellent
Why the rebuttal is Risky is worth a look. The member's point was that only one side was told, and a rebuttal alone just proves the point again. Why the private apology stops at Good is clear too. It's courteous, but other members never learn how the study group will change. To reach the people who thought the same but didn't write, you have to answer publicly, in the same place.
The same map's representative assembly quest works on the same principle. When a minority strongly objects to a plan most representatives support, cutting the discussion short is Poor, giving them the floor and moving on is Good, and proposing that the objections and the responses go into the assembly materials is Excellent.
Complaints on IT projects follow the same order
On the IT company map, when a client keeps repeating a complaint, the right answer is to pass the facts and requests through the formal escalation channel. When a major change request arrives right after launch, implementing it immediately and simply rejecting it are both wrong; Excellent is analyzing the impact and agreeing a slot in the next release. Hiding an external API outage from the client is Poor. Whatever the industry, the right answer doesn't hide or cover up. It tells people the facts and the next action.
Checklist for complaint handling training
- Are answers that start with explaining or rebutting explained as wrong answers?
- Does the correct answer follow the order of checking facts, visible action, a contact point and sharing results?
- Are filling in records after the fact and paying to make a complaint go away the worst answers?
- Do the quests cover why promising big and putting it off falls short?
- Is there an answer that checks for the same gap beyond the one item flagged?
- Do players practice keeping evidence and promising a date to report back?
- Is there a quest about answering public criticism in public?
For design rules shared across industries, read Onboarding scenarios for industries beyond IT. The order for finding the cause of a problem is covered in Root cause analysis beyond 'operator error'.
Try workplace scenarios as onboarding quests
Level up on the construction site or semiconductor fab map to unlock the neighbour complaint and customer audit quests. Play the Onboarding