Full-service restaurant review-response scripts - public replies to bad reviews about wait times, slow food, dishes that missed, and service attitude, written for the next guest reading the review

You are the customer service lead of a full-service restaurant. Write a set of Public Review Response Scripts for replying to negative reviews on review platforms. Start with the ground rules, then one response framework per review type.

Ground rules (state all three):
- The audience of a public reply is the future guest who scrolls past this review, not the reviewer - the goal is to reassure the next reader, not to appease this one
- Own only what is specifically described ("forty minutes for food to arrive"), never the vague accusation ("poorly managed," "never coming back") - accepting the latter stamps it as fact on your own page
- Reviews mentioning foreign objects, spoilage, or illness do not use these scripts: contact the guest privately to verify first; publicly post only "we have reached out to this guest and are working through it with them," admitting or denying nothing unverified

Four review types, each with a structure plus one example reply written with placeholders:

1. Long wait / queuing experience
   Structure: own the wait as fact → the demand-smoothing improvements already made (reservations, off-peak guidance - only what actually exists) → a verifiable alternative path for the reader
   Never write: "we were unusually busy that night" - readers only ever read it as an excuse

2. Slow food
   Structure: own the timing miss → attribute it to the flow (kitchen pacing, order clustering), never to an individual → what changed for peak hours
   Never write: naming the server or the kitchen crew on duty

3. Taste / portion not as expected
   Structure: own the experience on that dish → language separating "not to your taste" from "not done right" (when in doubt, respond as "not done right") → invite feedback naming the specific dish
   Never write: "that is simply how we prepare it"

4. Service attitude
   Structure: own the feeling → the follow-up already done (an internal review - say review, not punishment) → invite a return visit to see for themselves
   Never write: "the employee has been dealt with" - publicly punishing staff only unsettles readers

General requirements:
- Each reply under [N] words, with the first two sentences addressing the complaint directly
- The closing invitation carries no conditions (no "come back and try our signature dish" unless the review mentioned that dish)
- No personal phone numbers or private messaging handles in public replies

Constraints:
- The phrase "we sincerely apologize for the inconvenience" and its cousins are banned - none of the examples may contain template apologies
- No invented improvements: every improvement slot in the frameworks is a [what we actually changed] placeholder the service team fills with real, completed changes - nothing gets written that was not done
- No compensation offers (comps, free dishes, discount codes) inside public replies

Why it is written this way

The ground rule "who is the reply for" decides the quality of the whole set. Most review responses fail because the writer argues with the reviewer - explaining, apologizing, pledging - while the prospective guest reads only a business making excuses. Once the audience is fixed as "the next person scrolling past," the standard for every reply changes: not "is this reviewer appeased" but "after reading the review and the reply, does the next guest still dare to come."

"Own the specific, never the vague" is a line learned in the field. A guest writing "we waited forty minutes" has stated a fact you can respond to; a guest writing "this place is badly run" is handing you an accusation, and accepting it publishes it as confirmed fact on your own listing. The reply claims only what was described concretely and lets the vague part pass - not cunning, just refusing to stamp things that did not happen.

"We were busy that night" is banned outright because it is simultaneously the most common and the least effective reply: to a reader it always reads as an excuse, and it quietly tells everyone "this is our peak-hour experience, expect it." The correct posture on wait-time reviews is an alternative path - reservations, off-peak guidance, the waiting area - letting the next reader judge whether the trap is avoidable.

Routing food-safety reviews out of the scripts and into private verification is the most important exception in the set. With allegations of objects, spoilage, or illness, publicly admitting before verifying invites trouble, and publicly denying hands the guest a weapon; "we have reached out and are working through it" is the only safe public stance - readers see a responsible process instead of an unwinnable argument. The no-invented-improvements rule serves the same end: write an improvement that never happened, and the next guest who arrives expecting it writes the second bad review.

Variables