Automated review requests after every job
Ask for a review automatically after every job.
Read the lesson
Goal: Send a review request after each finished job, at the right delay. Do not wear out regular customers.
You need: Core or above for review requests. Screens: Settings → Service Catalog → Review requests & settings, and Workflows.
Why this matters
Most happy customers will leave a review. They just need someone to ask at the right moment. The right moment is soon after the job, while the result is fresh. A week later, the customer has moved on.
When the office asks by hand, it asks when it remembers. That means busy weeks get no requests, even though busy weeks have the most happy customers. Automation asks every time.
There is a second risk: asking too often. A weekly lawn customer who gets a request after every mow will soon reply STOP. Then the business cannot text them about anything. Regulars need a different rule.
Review requests are on Core and above. AI replies to reviews need Growth (Lesson 4).
The idea: the right trigger, the right delay, the right frequency
Three settings decide how well requests work.
| Setting | Choices in ServiceAgent | What to pick |
|---|---|---|
Request Mode | Manual or Automatic | Automatic for one-off jobs |
| When to send | After Job or After Appointment | After Job, when the job is marked complete |
| Delay | 0 to 168 hours | 2 to 24 hours for most trades |
After Job sends when a job is marked complete. That is the safest trigger, because the work is done. After Appointment sends after the appointment time, even if the job ran late.
The delay depends on the trade:
- Plumbing and electrical repairs: a few hours. The fix is clear right away.
- HVAC installs: 24 hours. The customer wants to feel the system run.
- Roofing: 24 to 72 hours. Let the crew clean up and the customer look.
- Cleaning: 2 to 4 hours, so the customer sees the result that day.
How long to wait after the job
- 0 hoursJob marked complete in Jobs; After Job fires
- 2 to 4 hoursCleaning, and plumbing or electrical repairs
- 24 hoursHVAC installs: the customer feels the system run
- 24 to 72 hoursRoofing: the crew cleans up, the customer looks
- 168 hoursThe most the delay allows (7 days)
Frequency depends on how often the customer books. One-off customers get a request after each job. Regulars get one about once a season.
There is no repeat-customer skip in Review requests & settings. So for businesses with many regulars, you control frequency another way. The build steps show both methods.
Pick the request setup for the business
- Look at how customers book
- Does the business have many weekly or recurring regulars?YesRequest Mode: Manual; tag regulars; ask once a seasonNoRequest Mode: Automatic; After Job; delay by trade
- Someone marks each job complete in Jobs
- Every customer gets the review link
What the request should say
ServiceAgent sends the request, but the words still matter. Keep it short, personal and easy.
- Name the person and the job. "Hi Linda, thanks for choosing Northside Plumbing for your water heater today."
- Ask one thing. "Would you share how it went? It takes a minute."
- Make it easy. One link, straight to the review page.
- Sign it as a person. "Carol, Northside Plumbing" reads better than "The Team".
A review request that sounds like a person
- noteWater heater job marked complete at 1:00 pm
- Northside Plumbing · 5:00 pmHi Linda, thanks for choosing Northside today. Would you share how it went? It takes a minute: link. Carol
- Customer · 6:12 pmDone! Hot water again, thank you.
Never offer a discount or a gift for a review. Paid reviews break the review sites' rules and the FTC rule. Never write the review for the customer.
Who marks the job complete
After Job depends on one action: someone marks the job complete in Jobs. Decide who does it for each business size.
- Owner-operator: the owner marks it at the end of each job, from their phone.
- Fleet on Core: techs may not have logins. The office marks jobs complete when the tech calls in. Or move to Growth so each tech has a login.
- Multi-location: each location's office marks its own jobs. Check this in the first week.
Build it in ServiceAgent
For businesses with mostly one-off jobs:
- Open the settings. Go to
Settings→Service Catalog→Review requests & settings→Settings. - Set the mode. Set
Request Modeto Automatic. - Pick the trigger. Choose After Job.
- Set the delay. Enter the hours for the trade, for example 4.
- Make sure jobs get marked complete. After Job only fires when someone marks the job complete. Show the office where to do it on
Jobs.
Automatic requests for one-off jobs
Review Request Settings
For businesses with many regulars (cleaning, lawn, pool):
- Set
Request Modeto Manual. Automatic would ask after every visit. - Tag the regulars. Add a tag such as
regularfrom theTag library. - Ask once a season. At each season's start, use
Send Requeston the review requests page for the regulars. One-off jobs in between get a manual request from the office. - Or use a workflow. For more control, start from the starter recipe Review Request Post Job in
Workflows→Create. Add aConditionthat skips contacts taggedregularorasked-this-season. AConditionreads a field typed as text, so check how tags read in this account. Test it withTest, thenPublish. On Core, it counts as 1 of 10 active automations.
For every business, check it works. Book a test job on your own contact. Mark it complete. Check the request arrives after the delay. Check it shows in Requests and in Analytics → Marketing.
Worked example: Northside Plumbing and Green Acre Lawn
Northside Plumbing has 8 techs and runs on Core. Most jobs are one-off repairs. Assume an example of 200 completed jobs a month.
- Settings: Automatic, After Job, 4-hour delay.
- Texts: 200 requests × 2 credits = 400 credits a month, if each is one segment.
- Core includes 2,000 plan credits, so this fits.
Green Acre Lawn and Landscape has 5 crews and runs on Growth. Assume an example of 150 weekly regulars over a 30-week season.
- After every visit: 150 × 30 = 4,500 requests a season. That is 9,000 credits, and many regulars will opt out.
- Once a season: 150 requests. That is 300 credits, and nobody feels nagged.
The once-a-season rule costs 30 times less and keeps the customer relationship safe.
Green Acre regulars: every visit vs once a season
Watch the first two weeks closely. Count requests sent in Requests, and new reviews on Google. Requests may go out while no reviews come in. Then check that the link opens the right review page on a phone.
Common mistakes
- Automatic requests for weekly regulars. Some reply STOP and lose all texts. Fix: Manual mode, and one ask a season.
- Nobody marks jobs complete. After Job never fires. Fix: make "mark complete" part of every close-out.
- A delay of several days. The moment passes. Fix: hours, not days, for most trades.
- Requests on Launch. Review requests start on Core. Fix: check the plan before you promise them.
Do this now
For one client, write down: one-off or regular business, the trigger, the delay, and the frequency rule. Then set it up in your practice account and run the final check.
Practice the conversation
- Operator When did your team last ask a customer for a review?
- Owner We hand out cards sometimes.
- Operator We will text every customer a review link a few hours after each job is marked complete.
- Owner My lawn regulars see us every week. They will get sick of it.
- Operator Right. Regulars get one ask a season. One-off jobs get one ask each.
- Owner What does it cost?
- Operator Two credits a text. For your season, about 300 credits for the regulars.
- Owner And the bad reviews?
- Operator Every customer gets the link. The next lesson adds a quick check so unhappy customers reach you fast.
Quick check
- A lawn company mows 60 weekly regulars. Its review request goes out after every visit. Some regulars reply STOP. What do you change?
- Ask each regular about once a season
- Keep every request, but send by email
- Turn requests off until the season ends
- Add a second request a day later
- A plumbing client completes 250 jobs a month. Each gets one 1-segment review text. How many credits is that?
- 250
- 375
- 500
- 750
- Review requests are set to After Job, but none are going out. What is the most likely cause?
- The delay is too short
- Nobody is marking jobs complete
- The business is on Growth
- The review link is missing
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.