Automating Google Reviews: Ask Without Chasing

Most business owners in Israel explain their review count with the same line: "people just do not write." It sounds right and it is almost always the wrong diagnosis. A customer driving out of a garage with a fixed car will happily write two lines. They need three things: someone to ask, the ask arriving while they still feel something, and one link to click. In practice it arrives three days later, verbally, from whoever was free, and only to the customers it feels comfortable to ask. That is not an audience problem, it is a missing process.

The manual ask fails at three fixed points

Timing. The feeling that makes someone write fades fast. A day later they are inside the next day and the request is a chore, while the same request two hours after service lands on someone still pleased.

Who receives it. When a human picks who to ask, they pick the pleasant customers. That skews the picture, and it means asking a tenth of your customers instead of all of them.

Friction. "Look us up on Google and write something" is four actions: open, search, identify the right business among three with similar names, find the write button. Every step drops people. The direct review link you copy from your Google Business Profile makes it one action.

What reviews actually do, and why this is not about image

Google itself explains that local ranking rests on relevance, distance and prominence, and that review count and rating feed prominence. Between two similar businesses at the same distance, the one with more good reviews wins the position, and the local result shows only three before anyone clicks "more".

The other side is not algorithmic. Someone searching "garage in Petah Tikva" sees a rating, a review count and short quotes before reaching any website, because the Google Business Profile is the real landing page of most local businesses in Israel. A business with 19 reviews from two years ago looks half closed even when it is busy. We covered this logic in the guide to AI for SEO. A steady stream of reviews is an acquisition asset, not decoration.

The arithmetic nobody runs

Take a service business handling 140 customers a month. Manually you ask around 20, five or six write, and that is roughly 65 reviews a year at best. Now change the coverage only, so the request reaches all 140. Even at a conservative one in ten, that is 14 a month. Example numbers to replace with your own, but the ratio holds: only the number of people asked changed.

The rule you must not break: no filtering who gets asked

This is where businesses get into trouble, usually in good faith and on someone's advice. The common mechanism is a screening question, "how was the service?", after which good answers get the Google link and bad ones are routed to an internal form. It looks like customer service and it breaks Google policy, which forbids both selectively soliciting positive reviews and discouraging a negative one. The same family includes incentives, a discount, a gift or a raffle in exchange for a review, and reviews written by employees, relatives or a paid service, which are also exposure under consumer protection law.

What is allowed: ask every customer how it went, unrelated to reviews, and fix whatever went wrong because it needs fixing. The review request then goes to everyone in the same wording, regardless of the answer. In the compliant version the unhappy customer gets a fix and a chance to write; in the forbidden one they get a form that buries the complaint.

What a request that works looks like

It arrives in the right window, and every service type has a different one. Garage, restaurant, salon: the same day, hours after. A treatment inside a course: after the second or third session, once there is improvement. A renovation or an insurance claim: one to two weeks after completion.

It is one message, not a process. Their name, one sentence recalling what was done, a direct ask, a link. No intermediate form, no landing page, no five-question survey.

It asks for a description, not for stars. "We would love a few words on what we did for you" produces a review with substance, which is what the next searcher reads. "Give us five stars" produces a rating with no words.

It has stop rules. Not twice to the same person, not to anyone with an open complaint, not to someone who already wrote, and not on every visit for a customer who returns every six weeks.

What it costs on WhatsApp, and what the law says

A request sent after the conversation closed is business-initiated, so it must go out as a pre-approved template, billed by Meta directly and separately from your subscription with us. Review requests are usually classified as marketing rather than service templates, and the Israeli marketing rate as of August 2026 is about $0.0353 per message, roughly 0.106 shekels, so 140 requests come to about 15 shekels a month. Inside a conversation the customer opened it is a service message, but read the 2026 Meta pricing update before leaning on that, because the category changes in October.

One legal caution. The Communications Law restricts advertising material sent without consent, and a review request is not an offer to buy, but attach a coupon or a "time for your next appointment" line and the whole message becomes marketing. Send it clean, once, only to customers who received service, with a way to opt out.

How this is set up, and where the agent stops

The process runs off the status on the customer card, not off a list someone exports once a month. When an enquiry moves to "done", a timer starts by service type and the request follows. Everything stays on the card: when it was sent, whether it was answered, whether we asked before. That is what our CRM is built around, and it is what prevents the duplicate ask. How often such an automation runs is not metered or billed by triggers, so you can define a separate rule per service type.

When the customer replies, the support agent takes over: "where do I click", "I have no Google account", "I wrote it and it is not showing". Those are what make people give up halfway. An agent reply counts as one message against the monthly quota, and a reply to a voice message or an image counts as one, just like a text reply, which matters because plenty of customers send a screenshot instead of explaining.

The agent also drafts the replies to reviews, and a human approves before anything is published. A negative review has four rules: one reply and not a debate, no details even when you are right, an offer to continue privately, and in healthcare no public confirmation that the person was ever there.

Where the agent stops: it does not draft a review for a customer, does not ask anyone to change or remove an existing one, offers nothing in return, and does not continue with someone who has started writing a complaint. That enquiry moves to a human with the full conversation, because an unhappy customer is not an automation task.

What it costs and where to start

The request goes out over WhatsApp, so the entry point is the Standard plan: 490 shekels a month plus a one-time 1,990 shekel setup, both excluding VAT. It covers up to 2 channels including WhatsApp, booking across 2 calendars, 1,800 AI messages a month with 0.38 shekels beyond that, and 5 changes a month, so wording or timing can change without opening a project. Several branches with a Google profile each, or Instagram and in-chat payments, means Business: 990 shekels a month with a 2,990 shekel setup.

Setup is up to 14 business days from receipt of your materials: the Google Business Profile link, the service types and the timing window per type. It is paid in one payment before work starts, the subscription begins the day the agent goes live, and Meta's message costs go directly to Meta.

Frequently asked questions

Can we send only our happy customers to Google? No. Google policy forbids soliciting reviews selectively from people who said they were satisfied, and forbids discouraging a negative one. The tool that asks "how did it go?" and sends only the happy answers to the Google link is exactly that violation. Incentives, discounts or gifts in exchange for a review are prohibited too. The compliant version is one uniform rule: everyone who received service gets the same request.

What does it cost to send review requests over WhatsApp? A request sent after the conversation closed is business-initiated, so it goes out as an approved template billed by Meta directly, separately from your subscription with us. Review requests are usually classified as marketing templates, and the Israeli marketing rate as of August 2026 is about $0.0353 per message, roughly 0.106 shekels, so 140 requests cost around 15 shekels. Inside a conversation the customer opened, it is a service message.

What do we do about a negative review, and can it be removed? A genuine review cannot be removed, not even for money. You can report one that violates policy, such as spam or content unrelated to the service, and Google removes it only if it finds a violation. What you control is the reply: one reply, short, no argument and no details. In healthcare you may not confirm publicly that the person was there, so the reply states general policy.

Which plan covers this and how long does it take to launch? A review request over WhatsApp needs a WhatsApp channel, so the entry point is Standard: 490 shekels a month plus a one-time 1,990 shekel setup, both excluding VAT, with up to 2 channels, calendar booking, 1,800 AI messages and 5 changes a month. Several branches with a Google profile each, or Instagram as well, means Business. Setup is up to 14 business days from receipt of all your materials, and the subscription starts on go-live day.