Ask for the review on the day it was earned.
Every company knows it should ask for reviews. Almost none of them do it consistently, because asking is a small task that belongs to whoever has just finished a long day. This asks for you, on the day the job landed, in words you would actually have used. It asks every customer rather than only the ones you expect to be pleased, partly because selectively asking happy people breaches the platforms' own policies, and partly because it is the fastest known way to build a review profile nobody believes. Unhappy answers come straight to you, privately, while there is still something you can do. And every review that appears in public gets a reply.
The problem
The job goes well. The customer says so out loud, in the doorway, to your face. Nobody asks them for a review, because the person standing in that doorway did the work, has three more jobs today, and feels like asking is something the office ought to handle. The office does not know the job went well. So the single best moment to ask, which lasts roughly a day, passes. Every time. The only people who reliably leave reviews are the ones annoyed enough to go and find out where to leave one.
Which gives most small companies the profile they have: eleven reviews, four of them from one good fortnight in 2023, and two angry ones at the top purely because they are the most recent. 74% of consumers only want reviews written in the last three months. So that profile is not a slightly weaker version of a good one. To most people reading it, it is functionally no reviews at all.
The second cost is bigger. The customer who was unhappy and too polite to say so to your face says so anyway, eventually, in public, to everybody, at the precise moment you can no longer do anything about it. Nothing in an ordinary business asks a quiet question while a complaint is still just a conversation. So the first anybody hears about the damp patch is in writing, in front of your next forty prospects.
And yes, your CRM has a button for this, and some will fire a message when a job is marked complete. If that is honestly all you need, use it. We would rather tell you that than sell you something. What the button does not do is know whether the job actually went well, leave a sensible gap before asking the same person again, give an unhappy customer anywhere private to go, tell anybody when a one-star review lands, make sure reviews get answered, or notice that it stopped sending back in March.
How it works
Five things happen, and the first one is the only reason this works better than the button you already have.
- The trigger is the job going well, not the job being marked doneCompletion plus payment, with no open complaint, no callback booked and no unresolved variation, and after a short delay so the customer has lived with the work for a day. A request that arrives before the invoice, or while somebody is waiting for the snag to be fixed, does more damage than not asking at all. The conditions are yours and they are the thing that gets tuned most in the first month.
- Everybody gets asked, in the same wayNo filtering by who you expect to be pleased. Selective solicitation breaches Google's own review policies and, more practically, produces a profile that reads as bought: forty reviews, all five stars, all within six weeks. The ask is one short message in your wording, with the link going straight to the review box rather than to a page the customer has to navigate.
- The message offers two doors, equallyLeave a public review, or tell us privately what went wrong. Both are offered to every customer with the same prominence, which is the honest version of this and the only one that is allowed. The difference it makes is not who is asked but where an unhappy person lands: most will take the private door if it is genuinely open, because what they actually want is for somebody to fix it.
- A bad answer becomes an alert, not a ticketAnything negative reaches a named person immediately with the job, the customer and what they said, rather than appearing in a weekly digest. The window where a complaint is still a conversation is measured in hours. This is the step that pays for the system, and the public reviews are close to a side effect of it.
- A reminder once, then it stops, and the reply gets writtenOne reminder after a few days to people who did not respond, then silence, and that person is not asked again for a long time regardless of how many jobs you do for them. Meanwhile new reviews across your platforms are watched, and each one comes back with a drafted reply for somebody to approve, because 80% of consumers say they are more likely to use a business that answers all of its reviews and almost nobody does.
Most unhappy customers are not trying to damage you in public. They just want somebody to fix it.
What it's built from
Three pieces. This is the smallest system on the list and it is deliberately not padded, because the value here is in the timing and the conditions rather than in the stack.
- n8n, the part that decidesSelf-hosted on European infrastructure, and the actual product. The trigger conditions, the delay, the suppression windows, the reminder rule, the escalation on a bad answer and the watch on your review platforms all live here as something you can open and read. When you decide not to ask customers on warranty callbacks, that is one rule changed in one place.
- Twilio, the channel people answerText, because an emailed review request lands with forty others and a text lands alone, and because the link needs to open on the phone the person is holding. It carries the compliance floor: opt-outs honoured at the point of request, quiet hours respected, nothing arriving at seven on a Sunday.
- HubSpot, or whatever holds the jobWhere the completion, the payment and the complaint history live, which is what the trigger reads. It is also where the result is written back, so a customer's record shows what they were asked, when, what they said and whether anybody replied. Pipedrive, a job management tool or your field service software all work the same way.
What it's worth
Do this with your own numbers rather than ours. It takes a minute, and it is the only version of it worth believing.
- You complete 60 jobs a month and currently ask for a review when somebody remembers, which is perhaps twice.You are leaving around 58 asks a month on the table. Not 58 reviews, but 58 chances, which is a different and much larger number than the one most owners picture.
- Asking everybody at the right moment gets a response from one in four, and most responses are positive because most jobs go fine.Around 15 responses a month where there were two. Within a quarter the profile is current rather than historical, which is what the 74% who only read recent reviews are actually checking.
- The published finding holds that one extra star is worth 5 to 9% of revenue for an independent business.On 1.2 million euros of turnover that is between 60,000 and 108,000 a year, from a system that takes a week to build. This is the single best return on the list and it is also the one people skip.
- Two customers a month are quietly unhappy and currently say nothing to you.24 a year. Some of them write it in public months later, and all of them stop calling you. Reaching them on day one costs a phone call and saves the account.
These are illustrations using published averages and round numbers, not results we are reporting. Your job volume, response rate and starting rating will move every line, and the star-rating figure comes from a study of restaurants, so treat it as the shape of the effect rather than as your number.
The research behind those assumptions
Published figures rather than ours. The first four come from an annual consumer survey, the last from an academic study that found a way to measure the revenue effect properly.
- 97%of consumers read reviews when they are choosing a local business. BrightLocal, Local Consumer Review Survey
- 74%only want reviews written in the last three months, which is why a good profile from 2023 counts for very little. BrightLocal, Local Consumer Review Survey
- 31%will only use a business rated 4.5 stars or better, up from 17% the year before. BrightLocal, Local Consumer Review Survey
- 80%say they are more likely to use a business that replies to all of its reviews. 42% say they are unlikely to use one that never replies. BrightLocal, Local Consumer Review Survey
- 5-9%more revenue per additional star, in a study that isolated the rating itself from the underlying quality. Luca, Reviews, Reputation, and Revenue
A week of work, against five to nine percent of revenue per star. This is the best return on the list and the one people skip.
What it costs
This is sold as one system at the automation price on the services deck, and it sits at the very bottom of that range: three tools and about a week. It is the smallest thing we build, and it exists partly so that there is a way to find out what working with us is like without committing to a month. What moves it at all is how messy the trigger is. If the job tool knows when a job completed and whether it was paid, this is quick. If completion is a note in a WhatsApp group, the first job is giving it somewhere to be recorded.
The running cost is a few cents per message plus a small hosting line, so a company doing sixty jobs a month is spending less on this per month than one review is worth. There is no per-seat licence and no per-review fee, which is the shape most reputation products are sold in and the reason they get expensive precisely when they start working.
Outside the build price is somebody watching it, which is the care retainer. On a system this small that sounds like overkill right up until you look at the failure mode: a review request that silently stops sending is indistinguishable from a quiet quarter, and nobody ever investigates quiet.
What goes wrong, and what happens then
Every one of these is in the build because it happens, not because somebody raised it once in a workshop.
- The request goes out while a complaint is openThe worst thing this system can do, and the trigger conditions exist to prevent it. An open complaint, a booked callback, an unresolved variation or an unpaid invoice all suppress the ask until they clear. Asking a customer to praise you in public while you still owe them a repair is how a private annoyance becomes a public one.
- A regular customer is asked every monthSuppressed per person on a long window regardless of how many jobs they give you. The second request to the same customer in a quarter is an irritation, and the third is why people block the number.
- A one-star review appearsAlerts a named person within the hour with the job history already attached, and the reply is drafted for approval rather than posted automatically. Nothing here replies to a public review without a human reading it first. The speed of the response is most of what other readers judge.
- Somebody answers the private door angrilyIt escalates immediately with everything attached, and nothing automated contacts that customer again. A complaint that gets a templated apology is a complaint that becomes a review.
- The link goes to the wrong placeChecked on every send, and links go directly to the review box rather than to a profile page. Every extra tap between the message and the box loses a share of the people who meant to do it, and on a phone that share is large.
- It quietly stops sendingMonitored, with a weekly number showing asks sent, responses, ratings and replies outstanding. A system like this failing produces no error anybody sees. It produces a slow month, and slow months get blamed on the market.
- Somebody texts STOPHonoured immediately, recorded against the contact, and nothing in the system messages them again. Not a setting and not optional.
Still wondering
The questions this one raises.
No. Google's review policies prohibit selectively soliciting positive reviews, and the practice is risky beyond the policy: a profile of forty five-star reviews collected in six weeks reads as bought, including to the people you were trying to persuade. This system asks everybody and gives unhappy customers a private route that is offered just as prominently as the public one. That is the version that is both allowed and more effective.
Often, and if that is all you need then use it. The button fires when a job is marked complete, which is not the same as the job having gone well, and it stops there. It does not check for open complaints, hold a gap between asking the same person twice, give an unhappy customer anywhere private to go, alert anybody when a bad review lands, get your replies written, or tell you when it stopped working.
Within about a day of the work being finished and paid for, after the customer has lived with it briefly but before the feeling has faded. Earlier than that and they have not seen the result yet; a week later and the response rate falls off sharply. The exact delay is tuned for your kind of work in the first month, because a kitchen and a boiler service are not the same curve.
You hear about it within the hour with the job history attached, and a reply is drafted for you to approve rather than posted automatically. Some bad reviews are deserved and the right reply says so. What matters to everybody reading afterwards is not the one-star review, it is whether the company answered it like a grown-up and how quickly.
Google is the one that matters most for local businesses and is where the request points by default. Trustpilot, Facebook and the trade-specific platforms work too, and sending everybody to one place rather than splitting across three is usually the better strategy. Monitoring covers whichever platforms you care about regardless of where the asks are pointed.
One message and one reminder, then it stops, and that person is not asked again for a long time. The thing that makes review requests annoying is not that they exist, it is being asked repeatedly, at the wrong moment, or while something is still unresolved. All three of those are conditions in the trigger rather than things anybody has to remember.
About a week. It is the smallest system we build, and it exists partly so that there is a sensible way to find out what working with us is like before committing to something larger. If it goes well, the same pipeline is usually the foundation for the next thing.
Keep looking
Discover more automations
- The inbound response systemEvery enquiry answered inside a minute, whether it came by call, form, WhatsApp or email. Qualified, booked and owned by somebody.
- Quote to cash, without the chasingEstimate out, followed up until it is answered, then scheduled, invoiced, reconciled and chased if it goes unpaid.
- The schedule that defends itselfConfirmations and reminders both ways, rescheduling people can do themselves, and gaps backfilled from a waitlist.
Find out what your reviews are costing.
Tell us how jobs get marked complete and what your profile looks like now. We will come back with what a week of work would change.