"Ignore" is a decision that gets made once and then never revisited, which makes it the weakest part of every triage system including ours. The pile is real and necessary. Treating it as a bin rather than a queue is what causes trouble.
Three things end up in there, and only one of them should stay.
What is genuinely fine to leave alone
A plain star rating with no comment. A two-word positive. A review so vague it contains nothing to respond to — "meh". Reviews from guests who plainly went to a different venue with a similar name and said nothing damaging.
These require no action. They are not a problem. About half of most venues' ignore pile is this and it can be left indefinitely.
What should be reported, not ignored
This is the category that gets mishandled, because reporting feels like effort with low odds and ignoring feels free.
Platforms will remove content that breaks their rules, and the rules are narrower than owners hope but wider than they assume. Broadly, reportable content includes:
- Reviews from someone who was never a customer, where you can say why
- Content about a different business
- Personal attacks on a named individual, or content identifying a staff member
- Off-topic content — political statements, advertising, a rant about a neighbouring shop
- Obvious coordinated activity: several reviews in a short window with similar phrasing, no history, and no bookings to match
- Extortion — "remove the charge or this stays up"
What is generally not reportable, however unfair it feels: a genuine customer's inaccurate account, a one-star with no explanation, a review about a visit you cannot trace, a complaint about prices.
Report the first list. Do it once, factually, without arguing the substance — platform moderation is assessing a policy breach, not adjudicating what happened. And record the date you reported it, because the single most useful thing when a review is not removed is being able to escalate with a history rather than starting again.
For the extortion category specifically: report it, do not reply, and keep a screenshot. That is one of the few situations where a review is also potentially a matter for someone other than the platform.
What should be on a watch list
The interesting category. Reviews you correctly chose not to answer, that would change meaning if they happened again.
A single vague complaint about a member of staff being "off". One mention of a draught by the door. One review saying a dish tasted different. Individually, each is genuinely not actionable — reacting to every isolated comment is how operators end up chasing noise, which is the failure mode described in the Friday pattern that was not real.
But "one mention" only stays one mention if somebody is counting. And the reviews most likely to become a pattern are exactly the ones too small to act on in isolation, which means the ignore pile is where your next pattern is currently sitting.
The ten minutes a month
Open the pile. You are asking two questions.
Has anything in here happened again? Three isolated comments about the same thing across three months is not three isolated comments. This is the entire value of keeping the pile, and it is why the pile has to be readable rather than just unread.
Has anything become more serious? A vague complaint from six weeks ago reads differently once a second guest has described the same interaction more specifically. Reviews do not change, but their context does.
Then act on anything that has crossed either threshold and leave the rest.
Answering a review you originally ignored
Occasionally worth doing, and there is a right way. Do not reply to a four-month-old review as though it just arrived — the timestamp is public and it looks strange. Reply to the newest instance of the theme, and let that reply address the pattern:
"You're the second person to mention the draught by the front door this month, which is fair — we've ordered a screen for it."
That serves everyone who raised it, reads as attentive rather than belated, and puts the useful information where future readers will actually see it.
Why this is the part that decays first
The ignore pile has no deadline. Nothing goes wrong today if it is not reviewed, which is precisely why it stops being reviewed — and unlike the reply queue, nothing visible accumulates to remind you. There is no guest waiting and no unanswered count on a dashboard.
Most operators do this once, find it valuable, and never do it again. The honest position is that a monthly discipline with no forcing function does not survive a trading year, which is why we built the counting into OMMU rather than the reminder: the small single mentions are tallied as they arrive, and the second or third one surfaces on its own without anyone having to remember to look.