> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aresdeploy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Automated Review Requests After a Job Is Done: Timing, Copy, and Compliance
> How to time, word, and follow up on automated review requests after a job is completed, including SMS opt-out language and compliance basics.
**Key takeaway:** An automated review request is a text or email triggered when a job is marked complete, asking the customer for a Google review while the work is still fresh. Timing, wording, and opt-out compliance determine whether it gets ignored or answered.
The short answer: trigger the request within a few hours of job completion, keep the message to one clear ask with one link, include opt-out language on the first text, and send at most one polite follow-up before you stop. Everything past that is tuning.
An automated review request is defined as a system-triggered message, usually SMS or email, sent to a customer shortly after a job status changes to complete, asking them to leave a public review. A manual ask means a technician or office staff member remembering to ask in person or by phone, which happens inconsistently even at well-run companies.
## What is an automated review request, and how is it different from asking manually?
Manual asks depend on a person remembering to do it, on a good day, with a customer who isn't rushing out the door. Automated requests fire off a trigger, usually a job status change or an invoice marked paid, and don't depend on anyone's memory. A request sent at the wrong moment, worded wrong, or missing compliance language does worse than no request at all. This page covers the mechanics. For the broader strategy of why reviews matter and how they fit into your marketing, see Get More Google Reviews for a Service Business.
## When should you send the review request after a job is done?
Timing is the single biggest lever. Send it too early and the customer hasn't had time to notice whether the work holds up. Send it too late and the job has faded from memory.
The trigger event matters as much as the delay. Tying the request to "job marked complete" in the field means it can fire before payment is settled, which sometimes creates friction if a billing question is outstanding. Tying it to "invoice paid" is cleaner in practice: the transaction is closed, and the ask reads as a satisfied-customer follow-up rather than something bundled with a payment reminder.
| Trigger point | Typical delay | Best for | Watch out for |
| ------------------------- | -------------------- | ------------------------------------------- | ---------------------------------------------------------- |
| Job marked complete | Immediate to 1 hour | Same-day jobs, quick fixes, emergency calls | Fires before payment settles; can feel premature |
| Invoice paid | Immediate to 2 hours | Most residential service jobs | Requires payment and job-complete to be linked in your CRM |
| End of day / next morning | 12-20 hours | Multi-day jobs, larger installs | Customer may already be busy with next-day life |
| Manual override by tech | Same visit | High-trust, high-touch jobs | Doesn't scale, depends on the individual |
For most home service businesses, "invoice paid, same day" is the trigger that performs most consistently, because it's tied to a clean transaction boundary rather than a subjective judgment call about when the job is "really" finished.
## What should the review request message actually say?
One ask, one link, no upsell buried in the same text. That's the whole formula. A message that also mentions a referral discount or a seasonal promotion dilutes the single action you're asking for.
An SMS review request template, first message to that contact:
> Hi `{{contact.first_name}}`, thanks for choosing us for your job today. Mind leaving a quick Google review? \[link] Reply STOP to opt out.
An email version, less time-pressured, can carry slightly more context:
> Subject: How did we do?
> Hi `{{contact.first_name}}`, we just wrapped up your job and wanted to check in. If you have a minute, a Google review helps other homeowners in your area find us. Here's the link: \[link]. Thanks for your business.
A few rules hold across variations:
* Use the customer's first name and the specific service if your CRM has that field populated; a generic "thanks for your business" reads as a mass blast.
* Keep the SMS version under 160 characters so it doesn't split into two segments.
* Never mention an invoice balance or attach a payment link in the same message as the review ask.
* Test two or three variations rather than shipping one and assuming it's optimal.
## How many follow-ups should you send if there's no response?
One, maybe two, and only if the first went unanswered with no explicit decline. Sending a request every few days looks like spam and damages the relationship the review was supposed to reinforce.
A workable cadence:
1. Initial request, tied to the job-complete or payment trigger.
2. If no click and no reply after 3 to 5 days, one follow-up: "Hey, just following up, no worries if you're busy. Here's that link again: \[link]."
3. If still nothing after that, stop. Don't re-add them to a later campaign asking for the same thing.
As a hypothetical illustration: a two-truck plumbing company sends the first request the evening an invoice is paid, then sends one reminder five days later to anyone who hasn't clicked through. That's the entire cadence, no third message.
## What compliance rules apply to automated review request texts?
The first SMS a contact receives from your business needs opt-out language, plainly. "Reply STOP to opt out" or equivalent, included in that first message, is standard practice under US SMS marketing compliance frameworks, and most CRMs and messaging platforms, including GoHighLevel, will flag or block sends that skip it. Once someone has opted in, follow-ups don't always need the full disclosure repeated, but a lightweight reminder costs nothing.
A few practical guardrails:
* Only text numbers that have interacted with your business through a job, quote, or booking. Cold outreach asking for a review is a riskier category entirely.
* Respect quiet hours; a review request at 7am or 9pm is a common source of complaints even with correct opt-out language.
* Honor STOP replies immediately and permanently. A contact who opts out should not reappear in a campaign next quarter.
This is general practice guidance, not legal advice. Confirm your specific obligations with someone who knows your jurisdiction's requirements.
## How does Ares automate this end to end?
Ares runs review requests as one part of its post-job automation inside GoHighLevel: when a job or appointment status changes to complete, or an invoice is marked paid, Ares sends the SMS or email request automatically, with opt-out language built into the first message to any new contact. Follow-up cadence is handled the same way; a single reminder goes out if there's no response, then the sequence stops.
Because Ares also runs lead follow-up and appointment booking (see follow-up sequences and booking automation) on the same GoHighLevel backbone, the review trigger sits on the same timeline as the rest of the customer's journey rather than as a separate bolted-on tool. Ares also monitors and responds to incoming reviews, a related but separate capability. Pricing for the platform, including this automation, is \$299 a month standard or \$100 per seat for enterprise.
BrightLocal's consumer research consistently finds that most people check reviews before choosing a local service business, which is why the mechanics matter. Getting them right doesn't guarantee a five-star review, but getting them wrong reliably guarantees no review at all.
## Frequently asked questions
Within a few hours of the job being marked complete or the invoice being paid works best for most home service jobs. Same-day, while the work is still fresh, beats waiting until the next day for most job types.
The first SMS to any contact needs clear opt-out language like "Reply STOP to opt out." Follow-ups to an already-opted-in contact don't always require it repeated, but including it costs nothing.
SMS generally gets read faster and gets higher response rates. Email works as a lower-pressure alternative if a contact doesn't have a mobile number on file.
No. Requests should be gated behind a status that reflects a completed, non-disputed job. If there's an open complaint, hold the request and resolve the issue first.
You can send them manually or through basic SMS tools, but triggering off job status, tracking opt-outs, and managing follow-up cadence at real volume needs a CRM like GoHighLevel behind it.
Yes. More than one follow-up, or re-requesting from customers who already declined, reads as spam and can prompt opt-outs that hurt future messaging deliverability.