Negative review recovery call: when to phone

A negative review is a signal, not an attack

A customer writing a negative review is usually not trying to damage the company. They could not get something resolved and had no other route — or they simply shared an experience. Reading the review as an attack is the first mistake, because it spoils the tone of the reply immediately.

The second mistake is more expensive: doing nothing. An unanswered negative review is read by other customers and shows how the company treats such matters — so one review is not one customer but dozens of potential ones.

This article sets out the rules for answering a negative review by phone: when a call is right and when it is not, what to check beforehand, how the script is built, what not to say, what to do about the review itself, and how to measure the result.

When a call is the right response

Not every negative review calls for a phone call, and in some cases a call makes things worse. The decision rests on three questions.

1. 1Is the customer identifiableIf the review can be tied to an order number, a name or contact details, a call is possible. For an anonymous review there is no basis for one.
2. 2Can the matter be resolvedA wrong delivery, a faulty product, incorrect information — these can be fixed. A subjective opinion — «I did not like it» — cannot, and a call adds nothing.
3. 3Does the customer want contactSome reviews say explicitly «do not contact me». That is a signal to respect, and the reply belongs in writing.

Where all three are yes, a call is the fastest and most effective channel. Where one is no, a written reply is more appropriate — and a written reply is still a reply rather than silence.

Before the call: check the facts

An unprepared call makes things worse, because the customer has to tell the story again — which means being annoyed a second time.

• The order or service history: when, what, by whom
• Previous contacts: has the customer already written about this, and what were they told
• The internal facts: what actually happened — this has to be asked of the team
• What can be offered: replacement, refund, redo, compensation — the limits should be clear in advance
• Who is calling, and with what authority

The fourth line matters most. If the person calling has nothing they can offer, the call disappoints the customer again: they spend their time and hear the same answer. Authority is granted before the call, not during it.

How the script is built

This script has nothing in common with a sales script: the goal is not agreement but understanding and resolution.

1. 1Who is calling and why«I read your review, which is why I am calling» — an open start sets the customer's expectation correctly.
2. 2An apology, unconditional«We are sorry about this experience» should contain no «if» and no «but». A conditional apology is not an apology.
3. 3ListeningThe customer has to talk and must not be cut off. This is the longest part of the call and often reduces the tension on its own.
4. 4A specific resolution and a date«We will look into it» is not an answer. What will be done, by whom, and when — all three.
5. 5Confirming the outcomeA short second contact once the resolution has happened. Skip this step and the whole call loses its effect.

What not to say

This list matters as much as the script, because one sentence can undo the entire call.

• «That does not happen with us» — denying the customer's experience
• «You misunderstood» — opening an argument
• «If you remove the review, we will...» — making compensation conditional on the review
• «That is not our fault» — even when true, that is not what the call is for
• «Our other customers are happy» — the comparison makes things worse
• A promise without authority: «we will definitely fix it» does double damage when it is not delivered

The third line deserves emphasis. Tying compensation to the removal of a review is against the rules of many platforms and becomes a second complaint in the customer's hands. The resolution is offered — the review is the customer's own business.

What to do about the review itself

The purpose of the call is not to get the review removed. That looks counter-intuitive and has a practical reason.

A good, open written reply to a negative review is worth more to other readers than the review itself. A reply showing how the company resolves a problem often makes a stronger impression than several positive reviews.

The practical sequence: the call and the resolution first, then a short written reply under the review — «we got in touch, and this is how it was resolved». If the customer chooses to update the review, that is their decision; it can be asked for and must not be demanded.

Who should make the call

This question changes the outcome substantially, and it marks the limit of automation.

• Someone directly connected to the matter — a branch manager, a service manager — produces the best result
• The person who caused the problem should not call: it turns the conversation defensive
• The AI agent does not make this call — judgement, apology and compensation are human authority
• Automation's role: detecting the review, creating the task, preparing the history and tracking the resolution
• The second contact — a short check after the resolution — can be automated

The general conditions for a conversation moving to a person are in AI-to-human call handover; here the exception is the rule — this call never starts with the agent.

Measurement

The main error in measuring this process is measuring the rating. A rating is an outcome, not a process.

• Response time: from the review to the first contact
• Contact rate: what share of negative reviews received a call or a written reply
• Resolution rate: how many cases closed with a specific resolution
• Second-contact rate: was the resolution verified
• Recurring causes: how many reviews share the same problem — the real value is here
• Retention: what share of customers who wrote a negative review bought again

The fifth line is worth pausing on. Most negative reviews come from the same few causes, and their list shows where the process breaks. Resolving one review keeps one customer; resolving the cause prevents the next dozen reviews.

Limits

A call does not erase a bad experience. The customer already lost something — time, money, convenience — and the call does not return it; it only decides whether the relationship continues.

The second limit is volume. In companies with many reviews, calling about each one is not possible; a filter is needed — resolvable, identifiable customer, high impact. The rest receive a written reply.

Where Vexvon supports this flow

Automation's role here is not the call but everything around it.

• A review or complaint signal can be recorded in the CRM as a lead or a case
• The single timeline on the customer record shows previous orders, calls and enquiries together — the preparation for the call is built from it
• Reminders create a task and a deadline for the responsible person, checked every minute
• Outcome codes and close reasons produce the list of recurring causes
• The verification contact after the resolution can be built as a campaign
• Monitoring comments and messages on social channels is configured separately

The structure of the customer record is on the CRM page, and monitoring on social channels on the monitoring page.

First step

Collect the negative reviews of the last three months into one list and ask a single question: how many share the same cause. Usually three or four causes explain most of them.

Then fix one of those causes in the process, and only after that build the calling flow. To talk through how that works in your own process, get in touch.