Sending a manager a link to a review is not an escalation. It is a forwarding. The manager now has to open it, read it, work out what you want, and decide whether it is theirs — four steps, on a phone, probably mid-service, and any one of them can end the sequence.
A message that produces action has four components and they fit inside a text.
The four components, in order
One: what happened, in a fragment. Not the review, your summary of it. "1-star, cold food, Friday 8pm." Eight words carrying the day, time, theme and severity.
Two: whose it is. By name, even in a one-to-one message, because "can someone" is the single most reliable way to guarantee nobody does. If the message is going to one person, naming them still changes how it reads.
Three: what you want done, as a verb. "Check the pass timings." "Call her." "Nothing needed, just so you know." This is the component most often missing, and its absence is why forwarded reviews sit unactioned — the manager cannot tell whether they are being informed or instructed.
Four: by when. "Before Friday." "Tonight." "No rush." Without it, the manager applies their own deadline, which is after everything else they are doing.
Assembled
1-star Fri 8pm, cold food — third this month. Dan, can you check pass timings on Fri service before this week? Not urgent tonight.
Twenty-eight words. Theme, frequency, owner, action, deadline, urgency. The manager can act on it without opening anything.
Compare:
Have you seen this? [link]
Which requires the manager to reconstruct all six.
The frequency detail is doing more work than it looks
"Third this month" is the difference between a complaint and a pattern, and it is the part a manager cannot supply for themselves. They saw one bad review; you are telling them it is the third. That single clause converts an annoyance into a finding, and it is the reason the message gets acted on rather than absorbed.
It also requires somebody to have been counting, which is the recurring practical constraint in all of this.
The two habits that stop managers reading
Sending everything. A manager who gets six review texts a week stops reading review texts, and this happens within about a fortnight. The threshold is lower than people expect — roughly two a week is the point at which they remain individually salient.
Which means the discipline is subtraction. Most reviews should not generate a message to anybody. Only two categories genuinely need one: something requiring action within 24 hours, and a theme that has crossed from noise into pattern.
Sending without a resolution step. A message that never gets acknowledged teaches the manager that these are broadcasts. Ask for a reply of any kind — "seen" is enough — and the exchange becomes a small obligation rather than a notification. This is also where night-to-morning escalations break, and it is why group chats fail: no individual is required to answer.
What not to put in it
The review text. Quoting a guest's words in full makes the message long and shifts the manager into reading mode. Your summary is more useful than the original, because it already contains the judgement.
Your feelings about it. "This is exactly what I've been saying about Fridays" converts an operational instruction into a criticism, and the manager will spend their reply defending rather than acting.
More than one thing. Two issues in one message means one gets handled. If there are two, send two messages, or wait and put both in the weekly brief instead — which is where most of them belong.
The Sunday version
A weekly message to a manager is a different shape, because nothing in it is urgent. It has three parts and takes about forty words:
This week: wait-time mentions up (7 vs 2-3 previous weeks), all Fri/Sat evening. Worth two minutes at Monday pre-shift. One good one — guest named Maria, read it out.
Drift, action, and something positive to say to the team. The last part is not decoration: a manager whose review messages are exclusively bad news begins managing the messages rather than the operation.
Where this stops being a writing problem
Getting the message right takes about ninety seconds. Deciding whether a review warrants one — which requires knowing whether it is the first or the third — takes counting that nobody has done by Friday evening.
That is what OMMU actually replaces: the count runs continuously, so a review that is the third of its kind arrives already carrying that fact, as a text with the four components in it rather than a link and a question mark.