A negative review versus your records: what you may use publicly

The hardest negative review is not the harshly worded one, but the one that describes something different from what your records show. A customer writes that nobody responded, while the history contains three messages. They write that you promised a refund, while the conversation says ‘we will check’. The instinct is always the same: paste in an excerpt and show what really happened. That is the worst thing you can do at this point—and the issue is not tone, but whose data you are about to publish.

First, establish what actually happened

A public review almost never includes a case number. Usually, you have a first name or alias, an approximate date, a product name and one sentence about what went wrong. You need to find the specific case from this information before posting any response. Replying from memory is risky in both directions: you either admit to something that did not happen or deny something that did.

1. Start with a time window.The review date marks the end of the period, not the beginning. Go back two to four weeks and search within that window.
2. Search by what you have, not what is missing.The name in the review may be incomplete. A fragment of a distinctive phrase, the product name or an order number—if the customer supplied one—will be more effective.
3. Check every channel, not just chat.The same person may have started in chat, returned through a form and requested a phone call. These may be three separate threads.
4. Verify that it really is the same case.If the match relies only on a first name and approximate date, treat it as a hypothesis. A public reply cannot rest on a hypothesis.
5. Check whether the records still exist.Message retention may be shorter than a customer’s memory. An absent record does not mean the conversation never happened—it means you cannot reconstruct it.

Once you have found the case, read the event timeline rather than just the message content. You need five things: when the first question was asked, when the first substantive answer arrived, how many times the case changed owner, whether there were unexplained gaps between messages and the exact wording of any commitment. Very often, the review turns out to be accurate but to concern a different stage from the one the team remembers. We describe the layer that makes this possible in our article about a customer-service ticketing system.

A discrepancy does not mean the customer is lying

A team that sees something different in its records from what appears in a review almost always concludes that the customer is exaggerating or making things up. That conclusion is convenient and usually false. Three mechanisms explain most such discrepancies, and none requires bad faith on the other side.

• You remember different things because you measure different thingsYou measure time from the first response. The customer measures from the moment the problem stopped blocking them. Three messages without a resolution are remembered as silence.
• The conversation took place in several placesChat, a form, a phone call and a social-media message create separate threads. The customer has one case; you have four, and none shows the whole story.
• The promise was made verballyThe most disputed statements are never recorded because they were made during a phone call. ‘The refund should go through this week’ is remembered as a deadline, not a prediction.

The practical consequence is that your records help you understand the case, not win it. If your first thought after reading the event timeline is ‘we have it in writing’, that is precisely the moment when a public reply begins to cause more harm than the review itself. We describe the procedural side—how such a case should move through statuses and deadlines—in a separate article on handling complaints.

What you must not write in a public reply

A reply under a review is read not only by its author, but by everyone who arrives on that page a year later. Everything you write about the specific case ceases to be information exchanged between you and the customer—and the person concerned did not decide to disclose it. This is the heart of the problem, which is why the table below is not a list of stylistic tips.

↔ Scroll the table sideways to see all columns.

This article describes a communication practice and is not a legal opinion. Whether specific information may be disclosed publicly depends on the nature of the data, the legal basis for processing and the context of the case. Establish this with a lawyer familiar with your industry or your data protection officer, then add the conclusions to your process as firm rules rather than recommendations.

A reply that reveals nothing without sounding evasive

The biggest concern is this: if you cannot state the facts, every response will sound like corporate padding. That is true only when the reply tries to settle the dispute. A public response is not meant to settle anything—it should show that the case has an owner and that somebody is already dealing with it. You can say this specifically without describing a single event.

1. Sentence one—acknowledgement, not judgement.Briefly confirm that the review has been read and taken seriously. Avoid ‘we are sorry you feel that way’, because it judges the reaction rather than addresses the case.
2. Sentence two—what you have already done.‘We have reviewed what happened on our side’ is specific and reveals nothing. This sentence distinguishes a genuine reply from a formula.
3. Sentence three—an invitation with an address.Give a specific channel and person: an email address, phone number or form. Do not say merely ‘please contact us’; say ‘write to this address—Karolina will reply’.
4. Sentence four—what happens after contact.Give a response timeframe, not a promise of resolution. The customer should know how long they will wait before deciding whether to write at all.
5. Sign with a first name.A reply signed with the first name of the person who wrote it reads differently from one signed with the company name. It is the only element of personalisation that costs nothing in data terms.

• The reply does not contain a single sentence describing the course of the case.
• It contains no figures—no amount, number or order date.
• It does not use ‘however’ or ‘on the other hand’—these signal that a correction is about to begin.
• The reply works equally well whether the customer is right or not.
• The same wording could appear under any other review about a similar problem.

The final point can be surprising, but it is the best test. If the public reply could be attached to another case without changing its meaning, it discloses nothing individual. If it could not be moved because it contains details, those details are precisely the problem. Personalisation belongs in the private channel, not in a thread that remains in search results.

Moving the case to a private channel

The public reply ends with an invitation, so the real work begins only afterwards. This moment is often neglected: the customer writes to the stated address and lands in a general inbox where nobody knows it concerns a review. The message arrives without context, and all the care taken in the previous step goes to waste.

Before publishing the invitation, prepare the ground: add an internal note to the case stating that a public review concerns it, assign it to one person and choose a status that will prevent it from closing quietly. The customer’s message will then enter a prepared context rather than an unassigned queue.

Silence is a separate issue. Many customers will not respond, and that is not a failure. Adding ‘we are following up on our request to contact us’ below the review after a week looks like pressure on the author and is often perceived that way by readers.

• Choose one waiting period—ten working days, for example—and stick to it without sending reminders.
• Close the case internally with an unambiguous reason: no response after the public reply.
• If you have confirmed the customer’s identity from the earlier case, one direct contact attempt is acceptable—a second is not.
• Do not contact someone you merely suspect of writing the review.
• Treat conclusions from an unconfirmed case as a signal to examine the process, not as a fact about the customer.

What to change in the process so the discrepancy does not return

An individual review is an event. A recurring discrepancy between what a customer remembers and what your records show is a process defect—and you can remove that defect without doing any work on reviews. Every change below concerns what happens before the review, during ordinary service.

• Every agreement reached by phone is added to the case in writing on the same day—this removes the most common source of disputes over promises.
• State commitments with a date or do not make them: ‘we will check’ without a deadline is remembered as a deadline.
• Attach contact from the same address or number to the existing case instead of opening a new thread.
• An internal note records the reason for a decision, not only the decision itself—in three months, this will be the only way to understand the course of events.
• Set message retention deliberately: a short period protects data but removes the ability to reconstruct an older case.

It is also worth reviewing cases that ended in public criticism once a quarter and looking for a shared stage, not a shared person. The common denominator is almost always a handover between people, an unstaffed weekend or a period when you are waiting for a supplier and nobody tells the customer. Your own measurements will signal such a problem before a public review does—we explain the mechanics in our article on measuring customer satisfaction.