- Preserve the facts
- Separate suspicion from evidence
- Choose the reporting path
- Respond and track the outcome
What makes a review suspicious rather than simply negative?
A harsh review can feel unfair without being fabricated. The person may use a different public name, refer to a visit arranged by someone else or describe an interaction that was never entered into the customer system. Before making a public accusation, check the available records and ask the relevant staff privately. The purpose is to understand the event, not to assemble a case against every dissatisfied person.
Keep observations separate from conclusions. A review mentioning a service you do not offer is a concrete observation. The statement that a competitor wrote it is a conclusion requiring evidence. A sudden cluster of similar comments may warrant closer review, but similarity alone does not identify the author. Use language such as suspected or unable to verify internally until the evidence supports something stronger.
Which Google policy should you compare it with?
Google's Maps contribution policy requires genuine experiences and prohibits fake engagement and rating manipulation. Its policy covers practices such as paid reviews, content posted through multiple accounts to manipulate a rating and certain conflicts of interest. It also prohibits incentives for posting or changing reviews and selectively soliciting positive feedback. Check the current policy category that fits the actual content or behavior rather than treating every low rating as removable.
The policy review is an editorial and platform-management task. This article does not determine whether a statement is unlawful or advise on a legal dispute. If the concern involves threats, private information or a serious allegation, route it to the appropriate responsible person in the business and seek qualified help where needed. A general marketing response should not make legal conclusions or disclose customer records.
What should your internal review record contain?
Create a compact record for each item under review. Include the review link, the date you noticed it, the visible text and rating, the business location involved and a screenshot if useful. Record the suspected policy category and the specific fact that supports it. Keep the person responsible for the case and the next action visible. This is a suggested working method, not a Google requirement for every ordinary report.
Add only the internal context needed to assess the issue. For example, note that the service described is not offered or that the stated visit date falls outside the business's operating history. Avoid circulating complete customer files when a short factual note is enough. Store the record where appropriate staff can access it, and keep it separate from public reply drafts. The fact that something is useful internally does not make it suitable to publish.
How does the ordinary reporting process work?
Google lets a business report a review from its Business Profile or through the Reviews Management Tool. Choose the reason that matches the suspected violation. The management tool also provides status information and, for eligible decisions, a one-time appeal route. Google's guidance says disagreement with a review is not itself a reason for removal. Follow the current interface and instructions, because the available steps can change.
After reporting, record the submission and status in the internal log. Avoid having several staff members run separate versions of the same case without coordination. A single owner can keep the facts consistent and distinguish a pending review from a decision. If an appeal is available, focus on the relevant policy issue and supporting facts rather than a long account of how upsetting the review has been. Removal remains Google's decision.
What if someone demands payment to remove reviews?
Google provides a separate reporting channel for negative-review extortion involving demands for money, goods or services. Its guidance says not to engage with or pay the people making the demand, and to preserve communications and links to the suspected reviews. Use that channel when there is an actual extortion attempt, not merely because a review is unfavorable.
For the business's internal response, assign one person to collect the relevant messages and coordinate the report. Preserve dates, sender details and the demand as received rather than editing screenshots into a dramatic presentation. Restrict access to staff who need it. Keep ordinary customer-service responses separate from the extortion case so a genuine customer complaint is not swept into an unsupported accusation. This is operational guidance, not a guarantee of removal or a legal remedy.
Should you reply while a review is being assessed?
Decide based on the content and the business's ability to respond calmly. A public reply can help other readers understand that the business is attentive, but it should not expose private information or invite an argument. Google reviews replies against its policies, posts approved replies publicly and notifies the reviewer. Write with that public audience in mind.
A restrained original example for an unverified interaction is: We would like to understand what happened. We cannot identify the visit from the details here, but our team can review it through our usual contact channel. Please contact us with the date and service involved. Adapt the wording and channel to the business. Do not add an accusation, an invented investigation result or a promise that the review will disappear.
If the business recognizes a genuine service failure, a different response is appropriate. Acknowledge the issue you can responsibly discuss and move detailed resolution into a private channel. A suspected-policy workflow should not become an excuse to dismiss valid feedback. The public reply and the internal improvement can proceed separately from any platform report.
How would this work in a realistic example?
Consider a hypothetical repair shop that receives a one-star review describing an overnight hotel stay. The manager records the review and confirms that the business is a repair shop, then checks for a plausible mistaken-location explanation. The report focuses on the mismatch between the described experience and the listed business. It does not claim to know the reviewer's identity or motive. This is an original illustrative example, not a Dappr client incident.
Now change the facts: the review describes a delayed repair, but the public name does not match the invoice name. That is not the same evidence. The manager checks whether someone else booked the repair and asks the staff who handled the work. The case may become a genuine complaint rather than a fake-review report. The distinction prevents an unfamiliar name from being treated as proof of deception.
Finally, imagine a message arrives offering to remove several new reviews for payment. Preserve that message and use the extortion-specific process described by Google. Do not merge the three situations into a single canned response. The useful workflow is a decision tree based on evidence, with the reporting route chosen after the facts are understood.
How do you prevent your own review program from creating problems?
Use a neutral request that invites honest feedback from eligible customers. Do not buy reviews, offer a discount for a rating or ask staff and friends to pose as customers. Avoid a process that sends happy customers to Google while diverting unhappy customers away from public feedback. Those practices conflict with Google's review policies and undermine the reliability of the information.
Assign responsibility for reviewing the request process, not only replying to individual comments. Check the wording in emails, texts, printed cards and staff instructions. A well-intentioned employee can create a problem by promising a reward or requesting a particular rating. The business should make the acceptable approach clear and review it when its tools or campaigns change.
What should a reputation report show?
A useful report distinguishes new reviews, replies, suspected-policy reports, pending decisions and final outcomes. Do not count every reported review as a removal or every negative review as fake. Record what the business learned from genuine complaints and which operational changes followed. A reputation program should help the business respond consistently, not manufacture a cleaner-looking score.
Dappr can discuss reputation workflows and how they connect with its own CRM where appropriate to scope. Any engagement should state who approves public replies, who handles sensitive cases and what reporting is included. The business remains responsible for accurate facts and customer handling, while Google retains control over review moderation.