How to Respond to a Negative Facebook Recommendation

Marketing, 2026-11-14

A negative Facebook recommendation feels worse than a bad Google review. On Facebook, the customer's friends and neighbors see it. They can react and comment on it. The post can keep going around for days. On Google, the review sits on your listing. Mostly, people already searching for a store see it. Both matter, but your reply should not be the same.

Here is a plan you can use today. It gives you a reply format that works on both sites. It covers how to handle each one. It tells you when to move to a private message. It tells you when to keep your reply public. The goal is not to win the argument. The goal is to make the next shopper who reads that thread feel okay about walking into your store.

Why do Facebook recommendations need a different reply than Google reviews?

A Google review is a rating on your business listing. A Facebook recommendation is a post on someone's personal page that mentions your store. That changes three things.

  • Who sees it: Google reviews are read by shoppers comparing stores. Facebook recommendations are read by the reviewer's friends, plus anyone who checks your page. Your reply speaks to both groups.
  • How long it lasts: a Facebook post can be shared, screenshotted, and commented on. A careless reply can travel further than the original complaint.
  • Tone: Facebook feels more personal. A stiff, corporate reply reads worse there than on Google.

So your Facebook reply should be a little warmer and a little shorter than your Google reply. On Google, you can add a sentence about how you do things. On Facebook, keep the public part short and move the details to a message.

What should the first public reply actually say?

Use four parts: say you're sorry for their experience, take responsibility, give one clear next step, and sign with a name. Keep it under about 80 words. Here is a template you can adapt.

"Hi [Name], thank you for telling us. I'm sorry the delivery arrived later than we promised and that you had to call twice to get an update. That is not how we want a delivery to go. I'd like to look at what happened on your order and make it right. Please send me a message here or call me directly at [number] and ask for [name]. — [Your name], [Store name]"

Notice what the reply does not do. It does not argue about the timeline. It does not explain your warehouse situation. It does not ask the customer to remove the post. Those moves look defensive and keep the thread alive longer.

For a Google reply, you can add one short line of background if it is a fact, such as "Our delivery window is usually two to three weeks, and we clearly missed that here." Do not add that line on Facebook. It invites an argument in the comments.

When should you move the conversation to a private message?

Move to a message as soon as the reply would need order numbers, employee names, refund amounts, or anything a stranger should not read. That is usually the second exchange.

  1. Reply publicly once, using the four-part format above.
  2. Send a private message the same day. Say who you are, restate the problem in one sentence, and ask one question.
  3. If the customer replies publicly again, respond publicly with one short line: "Thank you, I've sent you a message so we can sort out the details." Then keep the rest private.
  4. If they never reply to the message, add a short public follow-up after a few days: "I've reached out directly and am glad to help whenever you're ready." That shows anyone reading that you followed up.

One caution: messages from a business page on Facebook sometimes land in a hidden folder. If the customer says they never got your message, ask them to check their message requests, or offer a phone number instead.

When should you leave the reply public instead?

Sometimes public is the right place. Leave the exchange in the open when the complaint is about a policy, not a specific order. Examples are a restocking fee (a charge for taking back returned goods), a special-order return, or a delivery charge. Other shoppers have the same question, and a calm public answer helps them.

Also stay public when the recommendation contains a factual error that could mislead buyers, such as a claim that you do not honor warranties. Correct it once, politely, with the actual policy. Do not repeat the wrong claim back in detail. If the post turns into an argument, stop replying. You have said your piece, and more replies only push the thread higher in people's feeds.

Do not delete a negative recommendation unless it clearly breaks the platform's rules. Deleting it, or asking friends to pile on, often leads to a screenshot and a worse second post.

What should happen inside the store after you hit reply?

The reply is only half the job. Before you type, pull the order. Know the promised delivery date, the actual date, the salesperson, and whether a deposit or balance is involved. A reply written without the file open tends to promise things you cannot deliver.

  • Assign one person to own the conversation. Two employees replying to the same thread looks chaotic.
  • Write down what the customer says the problem is, in their words, and compare it to the order notes.
  • Decide your fix before you offer it: a delivery credit, a repair visit, a swap, or a refund. Know your limit.
  • Log the complaint by type, such as delivery timing or communication, so you can spot a pattern. If three recommendations in a month mention late deliveries, the problem is the schedule, not the reviews.

If the customer updates the recommendation after you resolve it, thank them publicly in one line. That update does more for the next shopper than any advertisement.

Key takeaways

  • Reply once in public with four parts: say you're sorry, take responsibility, give one next step, sign your name. Keep it under about 80 words on Facebook.
  • Move to a private message as soon as order details, money, or employee names come up. Leave a short public note that you did.
  • Keep it public when the complaint is about policy or contains a factual error. Stop replying once it becomes an argument.
  • Pull the order before you write, and decide your fix before you offer it.
  • Track complaints by type so you fix the cause, not just the post.