Every operator remembers the first 1-star review that felt unfair. Mine came in on a Saturday night, about a sandwich made with the wrong bread, and I spent twenty minutes writing a reply that explained exactly why the customer was wrong. I'm glad I never posted it.
Here is what I've learned since, running our own stores: the reply to a bad review is not really for the person who wrote it. It's for everyone who reads your profile afterwards, deciding whether to order from you. Rahul wrote about why reviews are a growth engine and not a chore. This post is the practical half of that: how fast to answer, five templates you can fill in tonight, what never to write, and when to stop replying in public and pick up the phone.
Speed matters more than polish
A negative review with no reply reads like nobody is minding the store. The same review with a calm, specific reply posted the same day reads like a store with a manager who cares. The customer who wrote it is still annoyed, but the person reading it next is looking at how you handle a problem, and that's what they're really judging.
The trouble is timing. Bad reviews land when you're busiest: right after the lunch rush, or late on a Friday when the closing shift is short. By the time anyone looks, it's three days old and the customer has stopped checking. So we aim to reply within the hour, and to get the manager the bad news even faster. Fast and decent beats slow and perfect.
Before you write anything, do three things. Read the review twice. Check the order, the time and who was on shift, if you can. And decide what you can honestly fix. Then write.
Five fill-in templates
Swap in the bracketed parts. Keep it short, use the customer's name if they gave one, and mention one specific detail from their review so it's obvious a person read it. Never paste the same reply twice on the same profile; readers notice.
1. Wrong or missing order. The most common bad review we see, and the easiest to fix.
Hi [Name], I'm sorry your [order / catering tray] came out wrong on [day]. That's on us, not you. I'd like to make it right — please call me at [store number] and ask for [manager name], or reply here and I'll reach out. — [Your name], [role] at [store location]
2. Long wait or slow service. Don't make excuses about staffing. The customer doesn't care, and readers see it as a shrug.
Hi [Name], thank you for telling us. Waiting [time they mentioned] for [what they ordered] isn't the experience we want at [location]. We've shared this with the [lunch / evening] team and we're looking at how we staff that window. I'd love the chance to show you a better visit — ask for me next time. — [Your name]
3. A rude or unhelpful staff member. Take it seriously in public, handle the person in private.
Hi [Name], I'm sorry about how you were treated on [day]. That isn't how we expect anyone on our team to speak to a guest. I'm looking into it with the shift manager directly. If you're willing, please call me at [store number] so I can hear the full story. — [Your name], [role]
4. Food quality or cleanliness. Food safety concerns go straight to a phone call. Never argue them in a review thread.
Hi [Name], thank you for raising this. We take [food quality / cleanliness] seriously and I've asked our manager to check [the specific item or area] today. I want to understand exactly what happened — please contact me at [store number or email] so we can talk it through. — [Your name]
5. The review you think is unfair, or not about you. Wrong store, wrong restaurant, or a version of events your team disputes. Stay factual and keep it short.
Hi [Name], thank you for the feedback. We couldn't find an order matching [day / details] at our [location] store, and we'd like to get to the bottom of it. Please call me at [store number] so I can look into it properly. — [Your name]
Notice what all five have in common: an apology or a thank-you, one specific detail, a real name, and a way to reach a real person. That last part matters most. It moves the conversation somewhere you can actually solve it.
What never to write
These are the replies I've seen operators post in frustration, and every one of them makes the review worse than it was.
Never argue the facts in public. Even if you're right, a back-and-forth in the review thread looks defensive to every reader. Template 5 is as far as you go.
Never blame a staff member by name. It doesn't make the customer feel better, and it tells future hires how you'll treat them.
Never share order details, phone numbers or anything personal about the customer. "Our records show you ordered at 9:42 and paid with a card ending in…" is a privacy problem, not a defense.
Never offer a refund or a free meal in exchange for deleting or changing the review. Make it right because it's the right thing to do, then let the customer decide what to do with their review. Google's own policies prohibit offering incentives for reviews, and a reply that reads like a trade looks bad to everyone.
Never reply while you're angry. Write the draft, close the app, read it again in an hour. That's the twenty minutes I'm glad I wasted.
Never leave it with no reply at all. Silence is the worst template.
When to take it offline
A public reply has one job: show readers you're responsive and point the customer to a person. Anything that needs details, back-and-forth or a fix belongs on the phone. Move it offline when the review involves food safety or an allergy, a dispute about money, a specific employee, a catering order for an office or event, or a customer who has replied more than once and is getting angrier.
The catering one deserves a word. A bad review from a catering customer isn't one unhappy diner; it can be an office that orders every month, and a $500+ order you either keep or lose. The manager should call that customer the same day, not reply in a thread.
After the call, one short public follow-up is fine if the customer agrees: "Thanks for speaking with me today, [Name]. Glad we could sort it out." Some customers update their review on their own once they've been treated well. Others don't, and that's fine too. The readers can see you showed up.
How we run this across our own stores
Doing all of this by hand at one store is manageable. Across several stores, with managers on different shifts, it falls apart fast. Reviews pile up unanswered, and the 1-star that needed a phone call sits for a week.
So we split it. The Nisra Reviews Engine posts an on-brand AI reply to every Google review within the hour, using the review's own details rather than a pasted line. The moment a 1–3 star review lands, the store manager gets a text, so a human can make the call and decide whether anything needs taking offline. It also sends customers an SMS review request 24 hours after an order, which keeps a steady flow of recent reviews coming in alongside the occasional bad one, and there's a per-store and portfolio rating view so you can see which location needs attention.
The templates above are the same structure we use: speed from software, judgment from the people who run the store. Use them by hand, use a tool, or both. Just don't leave the bad ones sitting there.