What to do next
The mechanics matter less than the psychology, so start there. Happy customers don't review you because they're ungrateful — they don't review you because the moment passes. Satisfaction peaks in the hours right after the job (the fixed leak, the clean install, the handled problem) and decays fast; by the weekend, reviewing you has the emotional urgency of returning a library book. Meanwhile the unhappy customer's motivation doesn't decay — grievance self-renews. That asymmetry is why unmanaged review profiles skew negative even for excellent businesses. An automated request isn't gaming anything; it's correcting a sampling bias, catching the satisfied majority inside their brief window of motivation.
The execution details that improve response: the right channel depends on the customer base; text is often faster to notice, while email may suit records and longer messages. The link must go directly to the review form — every additional tap adds friction. The message should read like a person: "Thanks for having us out today — if you have 30 seconds, a Google review really helps a small business like ours: [link]." One polite follow-up three days later to non-responders adds meaningful conversion; more than one is pestering. And timing should key off the job actually completing in your system — which is why this automation works best when your job-completion event can trigger it, another small argument for connected systems.
Two boundaries to respect. Don't gate — the practice of asking happy customers publicly and routing unhappy ones to a private form violates Google's policies and risks your profile. Send to everyone; your service quality is the filter. And don't incentivize — payment for reviews breaks both policy and, in many places, law. You don't need either trick: volume and recency are what move local rankings, and a steady automated trickle beats a guilt-driven blast every time. Review flow is also a revenue-side automation — it compounds into rankings and close rates rather than saving hours — and a healthy automation roadmap balances both sides. A FrictionList audit prices the two categories together, so "we have 12 reviews and our competitor has 200" sits on the same ranked list as "we spend six hours a month chasing invoices," compared by what each actually costs.
Quick answers
When should you send a review request?
Within 2–24 hours of job completion, by text, with a direct link to the review form. Satisfaction decays within days; the window is short.
What percentage of customers leave a review when asked automatically?
There is no reliable universal rate. Track requests sent, link clicks, and published reviews for your own business.
Is it against Google's rules to ask for reviews?
Asking is allowed and normal. Review gating (filtering who gets asked by sentiment) and offering incentives are prohibited.