Guest experience and reviews

Slow service: fixing it before it becomes a complaint

Spot delays early, set ticket-time standards, tell guests the truth with ready-made scripts and decide what to offer, for UK restaurants and pubs.

Ava research teamPublished 7 min read

On this page
  1. Why slow service turns into complaints
  2. Where the delay actually comes from
  3. Set ticket-time standards and watch them
  4. Keep the host at the door
  5. Delivery tickets compete with your tables
  6. Telling guests honestly: three scripts
  7. What to offer, and when
  8. Example: one Friday night
  9. Debrief, then fix the cause
  10. Frequently asked questions
  11. References

Key takeaways

  • Most slow-service complaints are about not being told, rather than the wait itself. Tell guests early, give a real time and keep to it.
  • Set target times for each stage, from greeting to bill, and give one person the job of watching them during service.
  • Staff shortages are more common in hospitality than elsewhere: 11.6% of accommodation and food businesses reported one in October 2026, against 8.3% of all businesses[1].
  • Consumer law implies a term that a service is performed within a reasonable time[2]; a fair, prompt remedy usually ends the matter.

Why slow service turns into complaints

Guests forgive a busy kitchen far more readily than they forgive being ignored. The complaints that reach email inboxes and review sites usually describe the same pattern: nobody said anything, the server avoided the table, a second table that sat later got food first, and the bill then took another twenty minutes. Each of those is a communication failure that sits on top of an operational one.

That gives you two separate jobs. The first is to reduce delay by finding where it really comes from. The second is to catch delay early and tell the table before they have to ask. Most venues work hard on the first and leave the second to chance, which is why a twelve-minute delay can still produce a one-star review.

Where the delay actually comes from

Stages of a meal where delay builds, and where to look first
StageTypical warning signUsual causeFirst fix
Greeting and seatingGuests standing at the door with no eye contactHost also running drinks or phonesProtect the host role at peak; route phones elsewhere
First drinksTable seated over five minutes with no drinks orderBar backed up with tickets from the floor and deliveryPre-batch the top three drinks; a runner from the bar at peak
Food order to first courseTicket on the rail beyond your targetKitchen overloaded at one moment, a section short, or one slow dishStagger seating; simplify or 86 the slow dish
Between coursesPlates cleared, no dessert menu offeredServer section too largeSmaller sections or a dedicated dessert run
Bill and paymentGuests waving for the billCard machines shared or not chargedOne machine per section; offer the bill with dessert

Walk the service with this table for two busy nights and note where guests waited. Many managers find the kitchen is not the main problem; the slow points are seating, first drinks and the bill.

Set ticket-time standards and watch them

  1. Agree target times for each stage

    For example: greeted within one minute, drinks order within three, drinks on the table within six, starters within fifteen of ordering. Set your own figures from your menu and kitchen, and write them down.

  2. Make delay visible

    Use the kitchen display or the printer timestamp so tickets that pass the target stand out. On paper systems, write the order time large on every ticket.

  3. Give one person the watching job

    At peak, the duty manager or head server watches the clock on every table, not the servers, who are too busy to notice. Their job is to spot a ticket running late and act.

  4. Agree trigger points

    Decide in advance what happens at five minutes over target, at ten and at fifteen: who goes to the table, what they say and what they can offer.

  5. Review weekly

    Pull the ticket times or your notes from the week and look for repeat offenders: the same dish, the same section, the same hour.

Short-staffing makes this harder, and it is common. In October 2026, 11.6% of UK accommodation and food businesses reported a shortage of workers, compared with 8.3% across all businesses[1]. There were an estimated 70,000 vacancies in accommodation and food service in July to September 2026[3]. If you know a section will be short, cut covers at the booking stage rather than hoping the floor copes.

Businesses reporting a shortage of workers, 5 to 18 October 2026
Businesses reporting a shortage of workers, 5 to 18 October 2026Comparison. Accommodation and food: 11.6%; All UK businesses: 8.3%.11.6%Accommodation and foodAccommodation and food: 11.6%8.3%All UK businessesAll UK businesses: 8.3%Businesses reporting a shortage of workers, 5 to 18 October 2026Comparison. Accommodation and food: 11.6%; All UK businesses: 8.3%.11.6%Accommodation and foodAccommodation and food: 11.6%8.3%All UK businessesAll UK businesses: 8.3%

Source: Office for National Statistics, 2026[1]

Show the data
ItemValue
Accommodation and food11.6%
All UK businesses8.3%

Keep the host at the door

Delay often starts before anyone sits down. The host who greets guests is usually the same person who answers the phone, checks the booking system, seats walk-ins and runs drinks when the bar is behind. Every call taken at 7.45pm is a minute when guests stand unacknowledged at the door and seated tables wait for their menus.

  • At peak, the host's only jobs are greeting, seating and pacing. Phones go to a second person, to voicemail with a clear message, or to a call answering service.
  • Some venues route peak-time calls to an AI phone assistant such as Ava, which answers everyday questions and takes booking requests, so the host stays with the guests in front of them.
  • Give walk-ins an honest wait time and take a mobile number so they can wait at the bar or outside, rather than hovering by the door.
  • Hold back one or two tables at each peak slot for overruns and walk-ins, so a late table does not push the whole evening behind.

Delivery tickets compete with your tables

Delivery, takeaway and click-and-collect accounted for 20.9% of all consumer spending with restaurants in September 2026, with deliveries taking nearly three quarters of it[4]. Those orders land on the same pass as dine-in food. On a busy night a burst of delivery tickets can push every table's starters back by ten minutes without anyone on the floor knowing why.

  • Give dine-in tickets priority at peak, and say so to the delivery platform by extending prep times or pausing.
  • Set a cap on delivery orders per fifteen minutes during your busiest hour.
  • Put a separate packing station in place so delivery work does not take the pass.
  • Show the kitchen's delivery load on the floor manager's screen, so the floor knows a delay is coming before tables feel it.

Telling guests honestly: three scripts

Small delay (five minutes over): 'I wanted to let you know your mains are about ten minutes away. The kitchen's very busy and I didn't want you wondering. Can I get you another drink meanwhile?'

Larger delay (ten to fifteen minutes over): 'I'm sorry, your food is running late. One dish needed re-cooking and it's about fifteen minutes away. I'll keep you posted, and the drinks are on us while you wait.'

Kitchen problem affecting the room: 'We've had a problem in the kitchen and everything is running about twenty-five minutes late. I'm telling every table now. If that doesn't work for you, I completely understand and there's nothing to pay for what you've had.'

Three rules sit behind every script. Go before they ask. Give a realistic time, adding a few minutes rather than shaving them. Go back when you said you would, even if there is no news. Guests who are kept informed rarely complain later; guests who were told 'it's coming' three times usually do.

What to offer, and when

Decide the menu of remedies before service, so a server does not have to find a manager for every gesture. A clear ladder stops both over-giving and the awkward table where nothing was offered at all.

  1. Up to five minutes over target: an update and an apology. Nothing else is needed if the guest is informed.
  2. Five to fifteen minutes: a drink, bread or a side on the house, offered by the server without asking permission.
  3. Over fifteen minutes, or a course forgotten: the manager visits, and the delayed dish or course comes off the bill.
  4. Food that is wrong as well as late: remake it at once, remove it from the bill, and the manager checks back.
  5. Whole room affected: tell every table, offer the option to leave without paying for food not yet served, and record what happened.

There is also a legal floor. Under the Consumer Rights Act 2015, where no time is fixed, a contract for a service is treated as including a term that it will be performed within a reasonable time, and what is reasonable is a question of fact[2]. In a restaurant that rarely becomes a legal argument, but it explains why a guest who waited an hour for a main course expects something back.

Example: one Friday night

Example (fictional): A 60-cover bistro seats 22 covers between 7.30pm and 7.45pm because the booking system allowed it. At 8.05pm the kitchen display shows six tickets past target. The floor manager tells all six tables, gives each a realistic time, sends bread to four and comps one dessert. The next week the GM caps seating at ten covers per fifteen minutes and moves two regular bookings to 7pm. Ticket times at the peak fall back within target, and the same weekday's complaint emails stop.

The fix in the example was not more staff or a faster kitchen. It was pacing the bookings so the kitchen never received the burst in the first place, plus a floor manager who acted before guests had to ask.

Debrief, then fix the cause

  • After every service with a delay, note which stage was slow and why, in two lines in the shift log.
  • Look for patterns over a fortnight: one dish, one section, one time slot, one staff shortage.
  • Fix the cause in the booking pacing, the menu or the rota, not by asking the team to try harder.
  • If a guest emails, answer the same day using your complaint email templates.

Slow service often overlaps with other pressure points. See family-friendly dining for keeping tables with children on time, and QR code menus for whether digital ordering helps or hinders at peak.

Frequently asked questions

How long is too long to wait for food in a restaurant?

There is no fixed legal limit. What matters is what is reasonable for your style of venue and whether you told the guest. Set your own target times for each stage and act as soon as a table passes them.

Should we take slow food off the bill?

Use a ladder agreed in advance: an update for small delays, a gesture for moderate ones, and removing the delayed course for long waits or forgotten dishes. Consistency stops arguments at the table and later by email.

Can a guest refuse to pay because the service was slow?

A guest who has eaten generally has to pay, but consumer law implies a term that a service will be performed within a reasonable time. A fair reduction offered promptly usually resolves it.

Does service charge have to be removed if service was slow?

A discretionary service charge can be removed at the guest's request. Make sure staff know how to do it without argument, and that any service charge and tips are handled under your tipping policy.

References

  1. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 166 dataset (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2015). Consumer Rights Act 2015, section 52: Service to be performed within a reasonable time (opens in a new tab) ↑

  3. Office for National Statistics (2026). VACS02: Vacancies by industry (October 2026) (opens in a new tab) ↑

  4. NIQ (CGA by NIQ) (2026). Restaurants' delivery sales strengthen in September after tough summer (Hospitality at Home Tracker) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo