Reviews, asked for properly and answered consistently
Review management is the work of earning reviews, responding to them and dealing with problematic ones. The constraint that shapes everything: you may ask customers for honest reviews, you may not incentivise them or filter out unhappy ones, and you cannot remove a negative review simply because it is damaging.
Reviews are the part of a business's online presence that it influences rather than controls. They appear beside the listing at the moment someone is deciding whether to call, they carry more weight with that person than anything the business says about itself, and the response underneath them is read by everyone who arrives afterwards.
Most businesses approach reviews in one of two unhelpful ways. Either nothing happens — no requests, no responses, and a profile where the only reviews are from people motivated enough to complain. Or something happens that should not: review gating that only asks satisfied customers, incentives offered in exchange, or purchased reviews. All three violate Google's policies, and the enforcement risk attaches to the listing itself rather than to whoever suggested it.
When this work makes sense
Questions worth asking any supplier
Does the process ask every customer, or only the happy ones? Filtering before the request is review gating and violates policy.
Is anything offered in exchange? Incentivised reviews are a policy violation regardless of whether the reviews are honest.
Who responds, and how quickly? An unanswered negative review is read by everyone who arrives afterwards.
Does anyone offer to remove genuine negative reviews? Nobody can do that, and the offer says a great deal about the provider.
Is there a consistent tone across responses, or does it vary with whoever happens to reply?
Deliverables
A review request process that asks all customers, compliant with Google's policies
Request timing and channel matched to how you actually finish serving customers
Response templates for common situations, written to be adapted rather than pasted
Monitoring so new reviews are seen rather than discovered later
Flagging of reviews that genuinely breach policy, with realistic expectations about outcomes
Guidance for staff on handling reviews that describe a real failure
Reporting on volume, rating trend and response rate
Built with
Process
The distinctive part of this work is what happens before any request is sent: we look at where in your process a customer is most satisfied, and put the request there. A request sent at the wrong moment — too early, too late, or by a channel the customer does not use — produces silence regardless of how good the service was. That timing question does more for review volume than the wording of the request ever does.
The standard nine stages — discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement, continuous improvement — apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Doing nothing, asking properly, or buying reviews
No active process
Fits: Nothing — this is the default rather than a choice
Limits: Your rating reflects only customers motivated enough to complain unprompted
Compliant request process
Fits: Every business with satisfied customers it is not currently asking
Limits: Slower; you will receive some negative reviews, which is the point
Purchased reviews
Fits: Nothing
Limits: Policy violation risking the listing; increasingly detected; and the risk lands on your business, not the seller's
Case studies
No published review management case study. Review counts and rating changes are easy to present selectively, and we would rather show nothing than a chart without context.
MBGDesk operates from 4 offices — India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Can you remove a bad review?
Only reviews that violate Google's policies can be removed, and only Google can remove them. We can flag those with a clear case. A negative review from a real customer describing a real experience stays, and the response beneath it becomes the thing that matters.
How do we get more reviews?
Ask every customer, at the point they are most satisfied, through a channel they actually use. Most businesses with few reviews are not being refused — they are not asking, or asking at the wrong moment.
Can we offer a discount for a review?
No. Incentivised reviews violate Google's policies whether or not the review is honest, and the enforcement risk sits with your listing.
What about only asking customers we know are happy?
That is review gating and it is also a violation. The request has to go to everyone. In practice businesses that ask everyone tend to end up with better ratings than they feared, because satisfied customers are the majority and were simply never asked.
Should we respond to every review?
Yes, including the positive ones, and especially the negative ones. The response is read by future customers more than by the reviewer. A calm, specific reply under a critical review often does more good than the review did harm.
Someone left a fake review from a competitor.
Flag it with whatever evidence exists. Removal is not guaranteed and the process is slow. Meanwhile a measured public response saying you have no record of the transaction is usually more effective with readers than silence.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.