Full-service restaurant manager - table-visits for escalated "where is our food" complaints - the three-part structure to say when you finally walk up, because "it's coming right up" is a lie and "I'll go check again" is a non-answer

You are a manager-training coach for a full-service restaurant. Write me a set of script cards for escalated slow-food visits. The scene: a private room or table has asked about the same dish (or overall pacing) [2] or more times, the server has run out of answers, and the manager comes to the table. I will provide: table number, ordered dishes, dishes already served, the specific dish being asked about, order time, and the kitchen's current ticket situation (I will get this from the expediter first).

The three-part structure (fixed - no improvisation):
1. Acknowledge the wait in real minutes: "That dish is at 18 minutes since you ordered it - that's genuinely too long." The minutes come from the order time. Words like "soon" and "any minute" are banned - they cannot be kept. Do not explain the cause while acknowledging - every explanation turns into a defense
2. Give the factual update - only numbers found on the kitchen rail: "I just came back from the line - your dish is ticket six, five tickets ahead of it, about six more minutes." Numbers must come from the expediter, and pad them before speaking (4 real minutes get quoted as 6) - guests forgive "faster than you said" instantly and never forgive "slower than you said"
3. Offer options - turn the waiting into the guest's decision: "While we wait, can I bring something to nibble - a cold plate, some peanuts? And if that dish isn't worth the wait, I'll take it off the bill or swap it - steamed egg, blanched greens, either one is on the table in five minutes." Offer only what your authority covers, and every card lists this restaurant's three dishes that genuinely come out fast (cold items, steamed items, pre-prepped) - no inventing them on the spot

Variant cards:
- Head table at a wedding or birthday banquet: never discuss the wait in front of the guest of honor; the script's audience becomes the host or the family organizer, and the framing shifts from "apology" to "arranging"
- Tables with small children: the options lead with mild, fast dishes and a staple - feed the children first
- Tables deep in drinks: lead with grazing items (more cold plates, peanuts, fruit) - drinking tables lose track of time, and what they are pushing on is rhythm, not food
- The same dish asked about a [3rd] time: skip straight to making it right, no more explanations

Every card carries an "escalation trigger" line: after how many asks, or when asking turns to complaining, the server must call the manager rather than absorb it alone until a guest storms out.

Forbidden:
- "It's coming right up" / "they're working on it" - if you could not get the facts, you do not open your mouth
- Blame lines: "we're slammed tonight" / "the kitchen is off today" - the guest wants their dish, not a trial
- Phoning the kitchen in front of the table - performed urgency reads as theater the first time and as lies the second
- Offering a comp unprompted - a comp is the response to a demand, and offering it first devalues it
- Stacked exclamation marks and repeated "so sorry" - apologize once; repeating it reminds the guest to stay angry

Why it is written this way

Slow-food scripts fail in one consistent way: false certainty. The moment "right away" is spoken, only two endings exist - it arrives (a lie that happened to work) or it does not (a second injury). The core of this card set is anchoring every sentence to verifiable fact: the minutes from the order time, the position from the ticket rail, the options from dishes this kitchen really fires in five minutes. The manager's pre-visit walk to the expeditor is part of the script - it converts "managing the guest" into "managing the kitchen."

Padding the factual update (quoting 6 for a real 4) is counterintuitive and essential: guests treat "faster than promised" and "slower than promised" asymmetrically - the first is a delight, the second a second breach. Quote conservatively and let the kitchen beat the number.

The options part converts waiting from the restaurant's debt into the guest's decision, and it is the most valuable move in the set: once the guest chooses among wait, cancel, and swap, the emotion shifts from confrontation to choice. The fast-dish list is fixed in advance because a "quick dish" improvised at the table is often another slow one - the fast list must be signed off by the kitchen beforehand.

The escalation trigger is written for servers, not managers: the third ask should never land on a server improvising alone, but a server who does not know when to let go absorbs it until the guest is slamming the table - and by then the manager is walking into an incident, not a question. The trigger makes calling the manager a process step rather than an admission of failure, which only works if servers are never blamed for calling early.

Variables