Every other bad review you receive is written by someone who gave you money. They ate something, they waited for something, they had an opinion about a server. There is a transaction in there, and inside the transaction there is usually something you can learn.
The wrong-hours review is the exception. Nobody ate. Nobody was served. A family got in a car, drove twenty minutes, parked, walked to a dark door, and then stood on the pavement at seven on a Sunday deciding where to go instead.
That review is the angriest you will get all year, and it is about nothing you cook.
Why it rates so much lower than it should
A cold main is a disappointment inside an evening that still happened. A closed door is the evening not happening, and it arrives with a specific set of extra costs the guest attributes entirely to you.
They were going somewhere. Often a birthday, an anniversary, somebody visiting. There was a plan and you were in it, and the plan is now a conversation in a car park about whether anything else will have a table. The practical consequences — the drive, the parking charge, the increasingly stressed phone calls — all accumulate on your name.
Hence the phrasing, which is unmistakable once you have seen a few:
Drove 25 minutes with my parents for Mother's Day lunch. Google said open 12-5. Locked and dark. No sign, no note, nothing on their page. Thanks for ruining the afternoon.
Note what is absent: any claim about the food. There is nothing to apologise for in the usual way and nothing operational to investigate. The defect is a field on a webpage.
And it is contagious in a way ordinary bad reviews are not. One wrong Christmas Eve or one unlisted refurbishment closure does not produce one review. It produces a cluster of them inside a day, from everyone who made the same journey — and a cluster is what lands hardest on a rating and shows up fastest in how you are described to strangers.
Three failures, in the order they happen
Special hours were never entered. The single most common. Regular hours are correct, nobody ever added the bank holiday, and a profile with no exception quietly tells everyone you are open as usual. The dangerous ones are not Christmas — everybody remembers Christmas — but the awkward middle tier: the late-August bank holiday, Easter Saturday, the early close for a private function, the Monday you take off in January.
A temporary closure outlived the closure. A kitchen flood, a refurbishment, a two-week holiday. Someone sensibly marks the business temporarily closed and nobody un-marks it, because the person who did it is not the person who reopens. You then spend a fortnight invisible, which does not generate reviews at all — it generates nothing, which is worse and much harder to notice.
Regular hours went stale. You stopped doing Monday lunch in February. The profile still offers it. Every Monday since, a few people have arrived at half twelve to a closed door, and because it is only a few a week nobody ever connected them into a pattern.
The calendar, which is the actual fix
A ten-minute check on a random Tuesday does not prevent this, because the failure is not a state you can inspect — it is a date you have not thought about yet.
What prevents it is doing a year in one sitting. Once, in a quiet half-hour:
- Open a calendar and list every date in the next twelve months when you are not open as normal. Every bank holiday, your annual close, Christmas and New Year with each day's actual hours, Easter, any day you know you shut for a private event.
- Enter all of them as special hours now. They sit dormant until their date. This is the whole trick: special hours are a thing you can do in advance, and almost nobody does.
- Put one recurring reminder in a shared calendar, fourteen days before each one, that says check the special hours entry is right. Plans change; the entry needs confirming, not creating.
- Write down who owns this by name, and who owns it when that person is away. An unowned field is a field that is wrong within six months.
The point of doing a year at once is that it converts an ongoing act of vigilance into a task with an end. Vigilance fails in August.
The four places that disagree with each other
Your hours exist in more places than you think, and guests do not care which one you consider authoritative:
- The Google Business Profile — regular hours and special hours, separately
- Your own website footer, and any page template that hard-codes it
- The booking system, which has its own availability calendar
- The delivery platforms, each with their own
- The sign on the door, which is the only one guests trust once they have arrived and been let down
When you enter a year of special hours, do all of them in the same sitting. A profile that says closed and a website that says open is not better than both being wrong; it is a guest who checked the website.
Catching it when it happens anyway
Two habits, both cheap.
Search for yourself from a phone that is not signed in, on mobile data, once a week. Not your laptop with the business account logged in — that view is not the guest's view. Thirty seconds. You are looking for one thing: does anything say temporarily closed, and do today's hours match reality.
Treat "we were closed" as its own review category. When one arrives, do not file it with service complaints. It is a defect report, and the first question is not how to reply but how many other people made that journey today. Then check whether the entry that caused it is still wrong, because it usually is.
Replying to one
This is the rare review where a short, specific, unreserved reply works better than anything careful.
You're right, and that was our mistake — our bank holiday hours were wrong on Google and you made the journey for nothing. They're corrected now. If you'll give us another go, ring and ask for Dani and lunch is on us.
Three things make it land: you concede the fact immediately, you say what was wrong rather than referring vaguely to an error, and you name a person. Do not explain that Google sometimes displays old information. The guest knows who types the hours in, and so do the people reading.
The general craft of replying without making it worse holds here too — this is simply the version where you have no partial defence and should not look for one.
Why this one is worth more than it looks
Most review problems are operational, which means fixing them costs money, labour, or a difficult conversation with a chef. Noise needs panels. Slow service needs hours on the rota. Cold food needs a route changed or a plate replaced.
Wrong hours cost a half-hour, once a year, by one named person. It is the highest-return thirty minutes in your reputation, and it is almost always undone — not because operators do not know it matters, but because the work has to happen in March for a Saturday in August, and nothing about March makes that feel urgent.
OMMU flags profile fields that have gone stale and tells you when a review mentions a closure, so the pattern surfaces the first time rather than the fifth. A diary reminder and a spare phone does the same job, provided somebody's name is on it.