The reply I actually sent on a Friday night, the reply I got wrong for years, and why the advice everyone repeats about apologizing and taking it offline is half wrong.
Get StartedDrafted in your voice from the actual review. Nothing posts until you tap.
This one came in on a Friday night. I answered it as the person responsible for the shift, not as a founder.
Waited in drive thru for 25 minutes and when I finally got to the window my food was wrong. I ordered a spicy sandwich meal and they gave me an original. Fries were cold. Nobody apologized. I had my kids in the car. Won't be back.
I'm sorry. Twenty-five minutes is too long, and the bag should have been a spicy sandwich, not an original. That's on us, not on you, and it's not what I expect from this store. I was the Operating Partner on that shift. I have already gone through that window with the team that ran it, including the bag-check before the food leaves. If you are willing to give us another chance, please ask for me next time you come through and I will take care of the meal. Chase
That is how you answer a negative restaurant review when your name is on the shift. You name the wait. You name the wrong sandwich. You do not argue the timer. You do not write "we strive for excellence."
What happened next was not on Google. Saturday huddle, I did not read the review out loud. I put one person on calling line times before lunch and I stood on bag-check for the first peak. The spicy versus original miss was a listen-back miss.
I do not know if that guest came back. I know what changed the next day. If you cannot say that second sentence, you did not answer the review. You decorated it.
I built Replio because that one star landed at 9pm and the useful part of it was still buried when lunch started.
Thank you for your feedback. We show a 6-minute window time during the interval you mentioned and we take a lot of pride in our service. We are sorry you feel that way. Please reach out to the store so we can discuss.
I thought I was protecting the team. I was fact-checking a guest on my own listing. Everyone else reading that review learned two things: we care more about our timer than their dinner, and if you write a one star we will argue with you.
Here is what it cost. The team learned that the work was winning the comment thread. The listen-back and the bag-check did not change. The next one star was the same one star with a different name on it.
Most pages about answering restaurant reviews are written by people who have never had their name on a sign. The mistake is not tone. The mistake is treating the review as a reputation event instead of a shift report.
Eleven years inside the store taught me something that sounds wrong in a marketing meeting and obvious at 6am.
One negative review is a guest. Three guests, same store, same complaint, same window, whether that is cold food, a wrong order, or a drive-thru wait, is an operating report. Software that treats those as the same row in an inbox will give you a pretty response rate and the same cold fries on Tuesday.
The other thing a blog will not tell you: a lot of the useful guest feedback arrives after 9pm, on DoorDash or Uber Eats, when the people who can change the make are already gone. Answering it at 9:12 from the couch does not fix lunch. Putting it in the morning brief, with a person's name on it, does.
That is why Replio is a daily coaching brief and a human tap, not another review dashboard. Speed of reply without an owner makes the store look responsive and stay broken.
Every guide says the same three things. Respond within 24 hours, apologize, take it offline. The third one is bad advice and the other two are incomplete.
Take the make-good offline. A refund, a return visit, a phone number. Do not take the acknowledgment offline. The next fifty people deciding whether to pull in are reading that thread. "Please DM us so we can make this right," with no specific sentence attached, looks like you are hiding.
The version that works: "The mobile order sat. That is on us. I have the person who ran that window today. If you want this made right, call the store and ask for me."
A fast empty apology at 11pm is worse than a specific reply at 6:15am from the person who can change the lunch deployment. Late and specific beats fast and blank. If it is a one star with an order and a name attached, do not let it rot. If it is a one star with no text, do not wake someone up to say you are sorry they feel that way.
"Sorry for your experience" is a template. "I'm sorry the wait did not match what the app promised" is an apology. A blanket apology on a review you have not checked is a public confession and a lesson for the next guest who wants a comp.
Restaurant review reply templates are harmful if you mean fill-in-the-blank scripts, so this page does not publish any.
Templates are why every quick service reply on Google sounds like the same district manager wrote it. Guests skip them. Teams paste them. The floor does not move. If a reply could have been written without reading that review, it is not a reply.
A spine is useful. A template is not. The whole method is five lines:
Replio drafts in your voice from the actual review, then nothing posts until someone on your team taps. If this page handed you fill-in-the-blank scripts, I would be arguing against my own product.
Two answers for each. What goes in the public reply, and what happens on the floor.
Public: say the food sat. Do not say "quality." Floor: ticket to handoff, bag hold, expo, and a delivery order sitting in a bag. Do not open the reply by blaming DoorDash.
Public: name the item. "The sandwich in the bag was not the one you paid for." Floor: listen-back and bag-check. "We strive for accuracy" is not an answer to a wrong order.
Public: own the wait they described, especially if the board or the app told them something else. Do not paste your window-time report back at them. Floor: one person calling line times out loud at peak.
Public: one sentence of ownership. Do not diagnose their mood in public. Floor: pull the interval and the leader on that shift, then coach. Do not ask the guest to describe the person on Google.
This is the one operators dread and almost nobody writes the real answer to.
Do not repeat the claim as if you have already found it true. Do not put their last name back on the internet. Do not announce discipline on the listing. Do not call the guest a liar.
You named someone on my team. I take that seriously. I am the Operating Partner here, I will handle it with them directly, and I want to make this right with you. Call the store and ask for me.
If I have already checked the interval and it does not match what was written, I still do not litigate it on Google. If it does match, the public reply stays short. The work is at shift change.
What actually happens on the floor: I do not drop it in the group chat. I do not read it at huddle. I read it once, privately. I pull who was on that window, headset, or expo. I look at the order if there is one. I talk to the named person before they walk onto the floor, in an office, not in the alley. I tell them what was written. I ask what happened. I decide from that interval, not from the star.
If it is a coaching miss: one standard, one next shift, one follow-up. If it is a firing offense: the listing is not the announcement. If it does not check out: I protect them in the building and I am still decent to the guest in the reply. Those are different jobs.
At huddle I coach the standard, greeting, listen-back, bag-check, and I leave the name out.
The other direction belongs here too. If a review names someone for getting it right, I say that name the next morning. If names only come into the office on a one star, the team learns to fear guest feedback instead of using it.
That is the bridge from answering a negative review to fixing the thing. Replio exists for the second job. The reply is the first tap, not the work.
Type your restaurant. Pick your location. Get a real coaching brief built from your actual Google reviews. No signup, no card.
Replio drafts a response to every review across every platform in your own voice, and puts the repeat complaint in front of you before lunch. Nothing posts until someone on your team taps.
Get StartedLive with your real reviews in minutes. $199 per location per month.
Respond to every negative review that contains a specific detail you can name back. Those replies are read by future guests deciding whether to pull in. A one star with no text is different, because there is nothing to name, and a generic apology on an empty star teaches the next guest that a blank one star gets a response.
Fast enough that it does not rot, specific enough that it means something. The usual advice to reply within 24 hours is a desk-job service level. A blank apology at 11pm is worse than a specific reply at 6:15am from the person who can actually change the lunch deployment. Late and specific beats fast and empty.
Usually you do not. There is nothing to name back, so any reply is a template by definition, and a public apology for an unexplained star invites the next person who wants a comp. If that rating is part of a repeating pattern at one location, that belongs in the operating conversation, not in a public reply.
No. Fill-in-the-blank templates are why every quick service reply on Google reads like the same district manager wrote it. Guests skip them, teams paste them, and nothing on the floor changes. Use a spine instead: name the specific thing, own what is yours, offer the make-good offline, and stop.
Nothing useful happens on the internet. Do not repeat the claim as though you have already found it true, do not put the person's last name back online, and do not announce discipline on the listing. Keep the public reply to one short sentence of ownership and move the work to shift change.
You cannot delete a review yourself. You can report it to Google for a policy violation such as spam, a conflict of interest, or a review not based on a real experience, and you can appeal a decision you disagree with. Removal is not guaranteed and appeals are slow, so treat removal as the long shot and the public reply as the reliable move.
A draft in your voice is useful. A post without a human tap is not. Replio drafts from the actual review, and nothing publishes until someone on your team taps.