The operator ran three sites and the complaint was only at one of them. Collection reviews, consistently, for about four months:
Said ready at 7:04. Got there 7:10, waited another 12 minutes. Why tell me it's ready?
Stood at the counter for 15 minutes watching my bag sit on a shelf while nobody acknowledged me. Food was cold by the time I got home.
Third time this has happened. Just stop sending the message.
What makes this a useful case is that the site was not slow. Average time from order to food-complete was 19 minutes, within a minute of the other two sites, both of which had no complaints at all. The kitchen was performing.
The thing that was broken was a notification.
What was actually happening
They timed thirty collections over a week. The sequence at the problem site:
| Step | Elapsed | What the guest knew |
|---|---|---|
| Order placed | 0:00 | Quoted 20–25 min |
| Mains plated | 15:30 | — |
| "Ready" pressed | 16:00 | Told it is ready |
| Sides and drink added | 18:40 | — |
| Bag sealed, receipt stapled | 20:10 | — |
| Moved to collection shelf | 21:30 | — |
| Guest arrives | 22:00 | Expects to collect immediately |
| Guest acknowledged | 26:00 | Waiting at an unstaffed counter |
| Handed over | 27:00 | Waited 5 minutes past "ready" |
The guest's complaint is a twelve-to-fifteen minute wait. The actual wait at the counter averaged five minutes. Both are true, and the discrepancy is the whole story: the clock the guest is running started when the message arrived, and the order was not finished for another five and a half minutes.
The kitchen was pressing ready when the food was ready, which is a reasonable reading of the button. Everything after that — sides, drinks, bagging, stapling, shelving — was invisible work happening after the promise had been made.
Then the guest's own travel time, around six minutes, sat on top of it. They left immediately, arrived to an order that had been genuinely complete for about thirty seconds, and still waited because nobody was at the counter.
So a site running a 19-minute kitchen was generating reviews describing a 27-minute collection, and three of those minutes were real while the rest was arithmetic the guest did in their own head.
Why this complaint is so much angrier than a slow order
A quoted 25 minutes that takes 30 produces mild annoyance. A promised ready now that takes 12 more minutes produces the reviews above, and the gap in intensity is out of all proportion to the five minutes involved.
Three reasons, and they compound.
The guest has already committed. They put their shoes on and got in the car. The cost of the wait is not the wait; it is standing in a shop having been told to come.
They have nothing to do. A wait at a table is spent drinking something. A wait at a collection counter is spent standing in a doorway, in the way, holding a phone, with nobody to ask.
It reads as a lie rather than a delay. This is the important one. A late order is a kitchen under pressure, which guests forgive readily because everyone understands a busy Friday. A message saying ready when it is not ready is received as being deliberately misled, and nobody forgives that — hence why tell me it's ready, which is a complaint about honesty rather than speed.
The change
One rule, no new systems, no additional labour.
Ready means the sealed bag is on the collection shelf. Not the food plated. Not the mains out. The complete order, bagged, receipt on, physically sitting where a guest can see it.
That was the entire intervention at the kitchen end. The button moved from the pass to the shelf — literally: the tablet was relocated so pressing it required standing at the collection point, which made the rule self-enforcing in a way a briefing would not have.
Two smaller supporting changes came with it:
A named five-minute window instead of a moment. The message changed from "your order is ready" to "your order is ready for collection — we'll hold it hot for you". Small, but it stops the guest's clock being a stopwatch.
Someone's job to look up. The counter was not unstaffed out of neglect — it was round a corner from the pass. They moved the shelf so it was visible from the till, and gave the till the explicit job of acknowledging anyone standing at it within ten seconds, even if only to say that's yours, one moment.
The acknowledgement change mattered nearly as much as the button. Four of the five minutes guests spent waiting were spent unacknowledged, and an acknowledged wait is a different experience from an ignored one.
What changed
Five weeks, same site, same kitchen, same labour:
| Before | After | |
|---|---|---|
| Order to food-complete | 19:00 | 19:20 |
| "Ready" to handover | 11:00 | 1:40 |
| Collection reviews mentioning the wait | 14 in 8 weeks | 2 in 5 weeks |
| Collection reviews mentioning being ignored | 9 | 0 |
Note the first row. The kitchen got marginally slower — twenty seconds — because the ready press now came later in the sequence. Every operational metric that looks like speed was flat or slightly worse. The complaints went away anyway, because the complaints were never about speed.
The review language moved as well, which is the part worth watching:
Ordered at 6:40, ready when they said, in and out. Exactly what you want.
The general point
A status notification is not a report. It is a commitment, and the guest prices it as one.
Which means the question for any ready-type message is not is this accurate about the kitchen but what will the guest do in the next sixty seconds, and will the thing they expect be true when they get here. Those are different questions and only the second one shows up in your reviews.
Worth checking on your own system this week: what exactly triggers your ready message, and how many steps remain after it fires. If the answer is more than one, you have some version of this.
Where this is not the answer
If "ready" to handover is already under two minutes, this is not your problem and the wait in your reviews is real. Look at the kitchen, the quote time, or the order-bunching that overwhelms a particular window.
If the complaint is about what was in the bag rather than when it arrived, this is a different and more damaging failure, and the fix is upstream in packing rather than anywhere near the notification. A missing item costs you more than a late order and the review signature is distinct.
If it is only Friday, you may be looking at a load problem wearing a process costume — check whether the ready-to-handover gap widens with volume before you move any buttons. Laying complaint times over the rota settles that in an afternoon.
One site, one quarter. Three of their sites ran the same system and only one generated the complaint, because only one had the shelf round a corner. The lesson is the question, not the fix.
OMMU separated the collection complaints that named the notification from the ones that named the wait, which is the split that pointed at a button rather than a kitchen. Thirty timed collections and a notepad finds it too — the step that is easy to skip is timing from the message rather than from the order.