Start with the deflating truth: almost nothing escalates.
A one-star review saying "worst meal of my life, posting photos next" will, in the overwhelming majority of cases, be followed by no photos, no local Facebook group thread, and no further contact. People are angry at nine o'clock and busy by Tuesday. If you have spent a Friday night in a mild panic about a review that then did absolutely nothing, that's the normal outcome, and treating every angry review as a crisis is how managers burn out on this work.
So the useful question isn't which reviews sound bad. It's which ones have a live thread still attached — an unanswered email, a promised call, a person who thinks they're mid-conversation with you. Escalation almost always runs through an unclosed loop rather than through anger.
Here are seven markers, ordered by how much they're actually within your control.
1. They say they tried to raise it at the time
"We mentioned it to the waitress and nothing happened." "We asked to speak to the manager and were told he was busy."
This is the strongest single marker and it's top of the list because it's entirely yours to fix. A guest who complained in the room and got nowhere has already had one attempt at resolution fail. The review is the second attempt. If that also produces nothing, the third attempt is wherever they think someone will listen.
It also means there is a factual account inside your building, from a member of staff who almost certainly remembers, which makes this the easiest of the seven to actually resolve rather than merely respond to.
2. There's an open channel you haven't closed
They've emailed. They've messaged the Facebook page. They rang and were told someone would call back. Any review that arrives alongside a direct contact you haven't answered is the highest-risk configuration there is, because the guest is now watching a specific inbox.
Check the shared mailbox before you write the public reply. Answering publicly while ignoring the email they sent on Saturday is a distinctive way of making things worse.
3. Money is in dispute
A guest who wants a refund and hasn't received one has a concrete, unresolved grievance with a number attached. Grievances with numbers persist; grievances about atmosphere fade.
Decide the refund question before you reply, not in the reply. "We'll look into it" on a disputed £74 bill is heard as no.
4. Allergen, illness or injury language
"My daughter was unwell that evening." "There was glass in the salad."
This one leaves the reputation category altogether. It doesn't matter how politely it's written or how many stars it carries — it's a safety matter with a documentation trail, and it goes to a process the same day. The playbook for the in-the-room version is here; the harder retrospective version is here.
Do not draft a clever reply. Escalate first.
5. Multiple named failures in a single visit
"Waited 25 minutes for drinks, starters came with the mains, the toilets were filthy and the bill was wrong."
Four specifics in one review is not a bad night for one guest; it's a description of an under-managed shift. This one escalates less often than the first four, but it's the one most likely to be true in a way other guests will confirm — which means it's a preview of what next week's reviews say.
6. A named member of staff
Specifically naming a server or manager raises the stakes for everybody. It exposes the individual publicly, it makes the reply harder to write, and it makes your team's willingness to tell you about bad tables depend on how you handle it.
Reply about the behaviour, never about the person. Handle the individual conversation privately, afterwards, and don't quote the review at them in front of anyone.
7. Claims of a pattern
"This is the third time." "Everyone in the area says the same."
Worth checking rather than worth worrying about. Sometimes it's rhetorical. Sometimes it's a regular you've quietly lost three times over, in which case there's a booking history and a name you can look up, and the reply writes itself once you have.
The part that isn't a signal
Photos, video, "I'm reporting you", threats to go to the press, mentions of TikTok. All of it feels like the dangerous kind. Almost none of it goes anywhere, and none of it should change your response, because the correct response to a serious complaint is already the same as your response to a threatened one: answer quickly, take it private, close it properly.
What you can't do anything about is which review a stranger decides to amplify. That's genuinely unpredictable, and building a process around predicting it produces a lot of anxiety and no benefit. Build the process around closing loops instead. That you control.
What to actually do this weekend
Three things, and they take about ten minutes:
Read the shared inbox before the reviews. The escalation risk lives there, not in the star ratings.
Sort the weekend's negatives into three piles. Safety language — escalate now, don't reply yet. Unclosed contact or money in dispute — reply today with a decision in it. Everything else — normal reply, in the next 24 hours. The five-question version of this triage is here.
Name the person who owns the pile. Not "the team". A name, for the weekend, with the phone that receives the alerts. The undefined-owner problem is the one that eats every review process.
And one thing to stop doing
Stop responding to the tone. A politely written review saying "we told the manager and nothing was done" is more dangerous than a furious one about cold chips, and the polite one is the one that gets a warm generic reply and no investigation.
The words that matter aren't the angry ones. They're the ones describing a conversation you didn't finish.