The dinner rush is a scheduling problem disguised as a phone problem. Between six and nine, every person capable of answering the phone is doing something a customer is already waiting for. This is a playbook for that window specifically.
Decide what a phone call is allowed to interrupt
Most kitchens have never made this decision explicitly, which is why it gets made badly under pressure. Write down the order of priority: a guest at the pass, a guest at the door, the phone. Then make sure the phone has somewhere to go when it loses.
Standardise the answers before you standardise the answering
Ninety per cent of rush-hour calls are a handful of questions. Write the answers down once, and make sure every version of the answer matches:
- What is the collection time right now, and what is it when you are slammed?
- Do you deliver to that postcode, and what does it cost?
- Which dishes are off tonight?
- Do you have a table, and by when do you need it back?
- What do you do about allergies, and who is allowed to answer that question?
The last one matters more than the rest. Allergen answers should have exactly one approved wording and one named person who can go beyond it.
Make the order capture identical every time
Orders go wrong at the point of capture, not the point of cooking. Whoever or whatever takes the order should always collect, in this order: items and quantities, options and modifiers, collection or delivery, time, name, phone number. Then read it back with the total.
Reading the order back with the price is the single highest-value habit on this list. It catches the wrong dish, the wrong quantity and the wrong expectation in one pass.
Confirm in writing
A text with the items, the total and the collection time removes an entire category of dispute. It also gives you a record when someone arrives at nine claiming they ordered something else at seven.
Have a defined escape hatch
Some calls need a person: a complaint, a large group, a supplier problem, anything about an allergy that the standard wording does not cover. Decide in advance who that person is on each shift and how the call reaches them. An escalation path that exists only in principle will not survive a Friday.
Then choose your fix
- A dedicated person on the phone during the rush, if your volume justifies the hours.
- Online ordering, which moves some of the volume but rarely removes the questions.
- An AI assistant that answers, prices from your menu and captures the order — provided you can see what it said and it hands over cleanly when it should not answer.
Whichever you pick, the playbook above is what makes it work. Software applied to an undecided process just automates the confusion.