Product quality complaints are defect reports

When you reply to a review about product quality, you are often looking at the first sign of a product problem: a batch of shoes that peel, a charger that fails, a cake that was dry. The reply has two jobs: help this customer get a remedy, and make sure the problem reaches someone who can fix it. Arguing about whether the product is good helps neither.

Structure

  1. Thank them and apologise for the problem.
  2. Restate it specifically: product and fault.
  3. Explain the route: exchange, warranty, return or service.
  4. Give a contact and, if relevant, what to bring.

Example: clothing or footwear

We are sorry the sole of your shoes came apart after a few weeks. That should not happen. Please bring them and your bill to any of our stores, or contact [business email], and we will look at a replacement or repair under our warranty.
Example reply: footwear

Example: electronics

Sorry the earphones stopped charging within a month. Our service desk at [Area] can help you raise a warranty claim. If it is easier, call us on [business number] first.
Example reply: electronics store

Example: food

Thank you for telling us the cake was dry. We are sorry; that is not how it should be. We have shared this with our bakery team to check that day's batch. Please contact us at [business number] so we can make it right.
Example reply: bakery

Example: jewellery

We are sorry the clasp on your chain loosened. Please visit the store with your bill and our team will look at a repair. If you have any concern about purity, we can arrange a check at the store.
Example reply: jewellery store
Jewellery replies

Replying to jewellery store reviews.

Choose words carefully

  • Say "that should not happen" rather than "this product is defective" before you have checked.
  • Avoid "customer misuse" in public, even if you suspect it.
  • Do not make safety claims you cannot support.
  • If there is any safety risk, such as overheating, burns or an allergic reaction, escalate before replying.

When safety is involved

Reviews that mention injury, illness, fire or contamination need escalation to the right people, often including legal or quality teams, before a reply is posted. The public reply should be brief and caring, with a direct contact, and nothing that speculates about the cause.

Escalation

Escalation paths for serious complaints.

Escalation paths for serious complaints

Free review snapshot

Want this done for your own reviews?

No commitment. We use your details only to send your snapshot and follow up. Privacy policy

Route it to the people who can fix it

Product complaints need to reach buying, suppliers or production, not just the store. Group quality complaints by product, category, supplier and store; if one store has more, check storage and handling there too.

Product improvement

Review analysis for product improvement.

Review analysis for product improvement

Brands and retailers

If you sell other brands, the customer still bought from you. Help them with the claim and pass the feedback to the brand. Avoid replies that say "please contact the manufacturer" with nothing else.

Common mistakes

  • Arguing that the product is good.
  • Blaming misuse publicly.
  • Sending the customer to the manufacturer alone.
  • Speculating about safety causes.
  • Fixing the customer but not the product.

Common questions

Should we offer a replacement in the reply?

Mention the normal remedy under your policy; handle specifics privately.

What if the item is out of warranty?

Say what you can do, such as a paid repair, and give a contact.

Should quality teams read reviews?

Yes, grouped by product and fault.

Can we ask for photos?

Ask privately, not in the public reply.

Checklist

  • Apology and specific restatement.
  • Remedy route explained.
  • Contact given.
  • Safety cases escalated.
  • Complaint routed by product and supplier.

In short

Treat product quality reviews as defect reports: apologise, restate the fault, explain the warranty or return route with a contact, escalate safety issues, and route patterns to the teams who can fix the product.

Doing this with Falcon

In Falcon, reply drafts come from playbook templates matched to the review's theme and sentiment, not free-form AI. Each draft is checked for length and brand voice, personal data such as phone numbers or emails, compensation offers that need manager approval, and the channel's length limit. Negative and 1-2 star reviews are suggested for reply first, owners are suggested from the taxonomy, and reviews can be assigned, noted and tracked as tickets. Falcon does not post to Google; replies are posted in Google Business Profile, and Falcon marks a review done when the reply appears there.