Guide
Assign guest complaints to store managers
Assigning a guest complaint means one named manager owns one specific action at one store, with a due time and a way to see that it happened.
Definition: complaint assignment is the handoff from a guest comment to a person who can change the operation. It is not a group chat ping, and it is not a reply on Google.
Tracking across locations tells you where a theme lives. Assignment tells you who moves it this week. If you need the roll-up, use the guest complaint tracking guide. This page is the handoff.
Why assignment fails
Most complaint handoffs die in one of four ways:
- The team will handle it, so no name is attached.
- The note lives in a thread the next shift never opens.
- The owner is a title, not a person on that store's schedule.
- The action is talk to the team, which nobody can verify.
A Business Owner can read every review and still watch the same complaint return, because reading is not assignment.
What to write in the handoff
Keep the record short enough that a manager will read it before the next peak:
- Theme: wait, accuracy, temperature, cleanliness, hospitality.
- Store name.
- The guest words, quoted, not paraphrased into something softer.
- The action in observable language.
- Owner name.
- Due time.
- Proof required, if any.
One problem. One store. One name.
If three stores share the theme, write three assignments. A market-level note without a store owner is how the quiet store stays quiet.
How the manager gets the work
In Replio, assignment is a screen, not a promise that a text went out. A manager joins once from a join link and signs in with a phone number (one-time code) or an email invite. The work appears as an in-app notice: a new action at that store.
Do not tell a prospect that every manager gets an email or a text. Those channels are not on for every group.
Rex can point at the pattern and suggest a next step. He does not assign the work. You or another leader does. See how Rex works.
What done looks like
Done means a person confirmed the action. A photo can be required. Status language on the record should stay plain: unassigned, assigned, in progress, ready to verify, verified.
Verified means the work was seen, not that guests stopped complaining. After close, keep reading the same theme. If it returns, assign again. That loop is how to stop recurring restaurant complaints.
If you want help standing this up across locations, talk with our team.
$79/mo or $828/yr per location. Whole team included.
Frequently asked questions
Who should own a guest complaint at a restaurant?
The person who can change the break, usually the store manager or the leader of that station. A district note or a group chat mention is not ownership. Write one name, one store, one action, and a due time. If two people think they own it, nobody does. Escalation stays with you. The floor work stays with them.
How do you assign a complaint without a new login maze?
Replio is a web app. A manager joins once from a join link and signs in with a phone one-time code or an email invite. The assigned work shows as an in-app notice, such as a new action at that store. Do not promise a text or an email unless your group has those channels turned on.
What proof should a manager submit?
Proof is whatever lets a second person see that the action happened. A photo can be required to close an action. A checklist or a written note can be enough when a photo does not apply. Do not accept handled as a close. If you cannot tell what changed, the complaint is still open.
How is this different from tracking complaints across locations?
Tracking answers which stores share a theme. Assignment answers who will act at one store this week. You need both. The tracking page is the roll-up. This page is the handoff. Rex can suggest the next step. You approve. Replio keeps the named owner. See how Rex works if you want that loop in one place.