Community supermarket customer service rep - 30-minute response checklist for complaints posted in the neighborhood chat group; screenshot first, verify facts second, only two group posts ever ("we see it, answer by X" and the correction), food-safety talk never happens in the group
You are the customer-service supervisor at a
community supermarket. The store runs several
neighborhood chat groups (a few hundred members
each). A customer has just posted a complaint
with photos into the group - a wrong shelf
price, a product quality problem, or a staff
attitude issue - and hundreds of people are
watching. Write me a do-this-now checklist for
the first 30 minutes.
Four time blocks; for each, list the actions,
the owner, and the judgment criteria:
Minutes 0-5:
- Screenshot for the record: the customer may
delete the post; capture it before anything
else
- Pin down facts: pricing complaints get an
immediate check (photo's tag vs. register
price); product complaints get a lot-code and
date check; attitude complaints get the duty
roster
- First group reply, and only three sentences
are allowed: we've seen it, the duty manager
is checking, we will answer by [reply
deadline]. No arguing, no follow-up questions
in the group, no promising outcomes
Minutes 5-15:
- Direct-message the customer: concrete
remedies are negotiated one-on-one, never
bargained over in front of the group
- Send one factual summary each to the duty
manager and the supervisor of the staff
member involved - no retelling beyond the
screenshots
Minutes 15-30:
- Facts verified; post the second (and final)
group message. The tier decides its wording:
· Clear factual error (wrong price) → correct
it publicly in the group, with the right
price attached
· One-off product issue → resolve by DM;
the group gets one line, "we've contacted
the customer and taken care of it"
· Food safety or personal safety → the group
gets only "we've contacted the customer and
are handling it directly with them." Any
discussion of fault stays out of the group -
hundreds of people keep conclusions, not
process
After minute 30 (wrap-up):
- Archive the four-piece record: screenshot /
fact-check result / remedy offered / customer
response
- Weekly, reconcile that week's group
complaints against the store complaint log;
the second occurrence of the same issue in
the group goes to the manager as a fix item -
do not wait for the third
Constraints:
- Never argue right-or-wrong in the group, even
when the photo itself is misleading - a
correction may be posted; a debate may not
- Once you post "we've DM'd you," you must post
the outcome inside the promised window; going
silent is worse than not replying
- Personal details customers post in the group
(names, phone numbers) never leave your
screenshot folder
- Template lines must be plain spoken language;
"your feedback is important to us" is banned
Why it is written this way
A group complaint and a desk complaint are different species: a desk complaint has an audience of one, while a group complaint ferments in front of hundreds of people with every passing minute. That is why the first item is a screenshot, not a reply - an upset customer deletes the post, and once it is gone every claim you make is unsupported. The screenshot is what makes the "fact-check result" box in the archive real.
Allowing exactly two group posts is the most counterintuitive part of the checklist. The instinct is to explain in the group immediately, but an explanation invites debate, and a debate becomes entertainment for onlookers. Post one does three things only (seen it, checking, answer by X); post two delivers facts and outcome. Everything negotiable gets squeezed into direct messages; the public channel carries conclusions only.
The food-safety tier exists because of how group memory works: hundreds of people will not retain "the affected lot has been pulled and the inbound inspection records are complete," they will retain "this store had a safety problem." The determination happens in private; "we've contacted the customer" is the last safe sentence the group will hold.
The weekly reconciliation with the store log is what closes the loop. One well-handled response means nothing if the same issue surfaces every week - the group's regulars notice. That is the quiet value of group complaints: they are the store's most public error counter. Use it.
Variables
| Variable | Description |
|---|---|
| Reply deadline | The answer-by time promised in the first post - sized to what the store can actually verify (most checks finish in 1-2 hours); shorter reads better, but only if honored |
| Group watchers | Who monitors the group by day and by evening - two shifts, two names; a deadline without a name behind it is decoration |