Lesson 3 of 6 · 7 min

Ask every customer, and catch unhappy ones fast

Give every customer the review link, and let unhappy customers hear from the owner first.

Read the lesson

Goal: Send every customer the review link. Add a short survey that alerts the owner when a customer is unhappy.

You need: Core or above. Screens: Review requests & settings, Surveys, Workflows, Analytics → Surveys.

Why this matters

An unhappy customer who cannot reach the owner goes public. A quick call from the owner often fixes the problem first. The customer feels heard, the owner learns what went wrong, and many write a fair review anyway.

An older idea was to send happy customers to Google and unhappy ones only to the owner. That is review gating. Google does not allow selectively asking happy customers for reviews. The FTC's 2024 rule on consumer reviews bans review suppression. So the rule here is simple: every customer gets the review link. The survey only adds a fast owner call for unhappy customers.

There is a second trap. A high score can hide a complaint. A customer gives 9 out of 10 but writes that the crew scuffed a wall. If nobody reads the comment, the owner never hears about the scuff. Weekly reading catches these mixed answers.

The idea: one link for everyone, one call for the unhappy

The flow has two parts. The survey never decides who gets the link.

First, every customer gets the review link from the review request in Lesson 2. It goes out after every job, whatever the customer thinks. Many customers never answer a survey, so the link must not wait for one.

Second, a short survey goes out the next day. A high score needs no extra step, because the customer already has the link. A low score sends a short apology text. The owner also gets a task and an alert.

Fig 1

One link for everyone, one call for the unhappy

  1. Job marked complete
  2. Review request with the linkEvery customer, with the Lesson 2 settings
  3. Survey 24 hours laterOne score, one comment
  4. Is the score low?YesApology text, plus an owner task and alertNoNo extra text; the customer has the link
  5. Good score but a bad comment?YesThe weekly read sends it to the ownerNoNo extra step
  6. Every customer got the review link
The review link goes to every customer first. The survey only adds an owner call for unhappy customers.

The owner task is the part that matters. The owner calls within one business day. The owner listens, fixes what is possible, and writes down what happened.

Then once a week, someone reads every survey answer. They look for mixed answers: a good score with a bad comment. Those go to the owner too.

Fig 2

The weekly survey read

  • Open Analytics, then Surveys
  • Read every comment, not only scores
  • Flag good scores with bad comments
  • Send flagged answers to the owner
  • Check that every low-score task was done
Ten minutes a week catches what scores hide.

The owner call

The call is where the value is. Give the owner a short script, so the call does not turn defensive.

  1. "This is Carol from Northside. I saw your note and wanted to call myself."
  2. "Can you tell me what happened?" Then listen, and do not explain.
  3. "I'm sorry that happened. Here is what I can do." Offer a fix the owner can afford, such as a return visit.
  4. "Thank you for telling me. It helps us get better."

The owner never asks the customer to change or remove a review. The owner never offers money for a better review. Fix the problem and let the customer decide.

Fig 3Example numbers

The low-score path, as the customer sees it

  1. note4 hours after the job: the review request with the link
  2. noteNext day, survey answer: 3 out of 10, "Tech left a mess"
  3. Northside Plumbing · 2:15 pmWe're sorry the visit fell short, Ray. Carol will call you tomorrow.
  4. Customer · 2:40 pmOk. Mornings are best.
  5. noteNext morning: Carol calls, listens and books a return visit
Ray got the review link like every customer. The low score adds an apology and the owner's call, not a gate.

After the call, the owner writes one line on the task: what happened and what they did. Over a few months, those lines show where the business needs work. Lesson 6 shows how to read them.

Scale and plan limits

On Core, this build uses 2 of the 10 active automations: the survey workflow and the low-score workflow. The built-in review request is a setting, not a workflow. If it runs as a workflow instead (Lesson 2), it counts too. If the client already runs 9, there is no room. Turn one off, or move the client to Growth for unlimited workflows.

For weekly regulars, use the Lesson 2 rule for both messages: about once a season.

For a multi-location business, send the low-score task to each location's manager, not to one owner. Name the right Owner on each task, so the call happens fast.

Build it in ServiceAgent

  1. Check the link for everyone. Open Settings → Service Catalog → Review requests & settings. Make sure every finished job gets the review request, as set up in Lesson 2. If the client uses the Review Request Post Job workflow instead, check that it is published.
  2. Create the survey. Open Surveys. Make a short survey with one score question and one comment box. Keep it to two questions.
  3. Send it after the job. In Workflows, start from the Post-Service Survey quick-start template. It sends a survey 24 hours after Appointment Completed. Adjust the delay for the trade.
  4. Build the low-score path. Create a workflow with Trigger Type → Low Score Received. Add three steps. First, Send SMS with a short apology that says the owner will call. Second, Create CRM Task: Title "Call unhappy customer", Owner set to the owner, due in 1 day, Priority HIGH. Third, Send Notification to the owner.
  5. Leave high scores alone. Do not add a second link text for high scores. The customer already has the link from the review request.
  6. Test the workflows. Click Test in each builder. This simulation is free and sends nothing. Check that no step stops or replaces the review request.
  7. Publish both. Click Publish. On Core, each switched-on workflow counts as 1 of the 10 active automations. This build uses 2.
  8. Set the weekly read. Add a weekly task for yourself: read all answers in Analytics → Surveys. Send mixed answers to the owner.
  9. Check it works. Book and complete a test job on your own contact. Check that the review request arrives. Then answer the survey with a low score. Check you got the apology, and that the owner got the task.
Fig 4

Who does what when a score is low

  1. ServiceAgentSends every customer the review link
  2. ServiceAgentSends the survey the next day
  3. CustomerGives a low score
  4. ServiceAgentSends an apology; creates a HIGH task and alerts the owner
  5. OwnerCalls within one business day
  6. OwnerWrites one line on the task
  7. OperatorReads all answers each week
  8. OperatorSends mixed answers to the owner
ServiceAgent sends the link to everyone and alerts the owner. The owner calls within one business day. You read every answer weekly.

Worked example: Cedar HVAC

Cedar HVAC has 9 techs and runs on Growth. Assume an example of 120 finished jobs a month. Every customer gets the review link and the survey. Of the 120, 8 give a low score.

Texts per month, each one segment:

  • Review request with the link: 120 × 2 credits = 240
  • Survey text: 120 × 2 credits = 240
  • Apology to unhappy customers: 8 × 2 credits = 16
  • Owner alerts: no text cost, because the alert is a notification
  • Text total: 496 credits
Fig 5Example numbers

Cedar HVAC texts a month

Review request with the link: 120 × 2 credits240
+Survey texts: 120 × 2 credits240
+Apologies: 8 × 2 credits16
Text credits a month496
Plan about 4 credits per customer, plus about 1 credit per workflow run.

Each workflow run also uses about 1 credit. The survey workflow runs 120 times and the low-score workflow 8 times. That adds about 128 credits, for about 624 in all. Growth includes 6,000 plan credits a month, so this fits easily.

Survey answers also feed the monthly report. The share of low scores is an early warning. It moves weeks before the public rating does.

The owner makes 8 calls a month. At 10 minutes each, that is 80 minutes. Those calls are where they learn the most about their business.

Common mistakes

  • Holding back the link from unhappy customers. That is review gating. Fix: the review request goes to every customer, whatever the score.
  • Sending the link only after a survey answer. Customers who skip the survey never get it. Fix: send the link with the review request after every job.
  • No weekly read. Mixed answers slip through. Fix: a weekly task to read Analytics → Surveys.
  • No owner named on the task. The task sits. Fix: a named Owner and a due date.
  • A long survey. People stop answering. Fix: one score, one comment.

Do this now

Write three texts and one note: the review request, the survey invite, the apology and the owner's call note. Keep each text under 160 plain characters. Build the low-score path in your practice account and run the check in step 9.

Practice the conversation

  1. Operator When a customer is unhappy today, how do you find out?
  2. Owner Usually from a one-star review.
  3. Operator We will send a two-question survey after each job. If the score is low, you get a task to call them the next day.
  4. Owner Can we just not send those people to Google?
  5. Operator No. Google does not allow that, and the FTC bans hiding reviews. Everyone gets the link.
  6. Owner Then what is the point?
  7. Operator You reach them first. A quick call often fixes the problem before they write anything.
  8. Owner Who reads the comments?
  9. Operator I do, every week. A good score with a complaint still comes to you.

Quick check

  1. Every customer gets the review link after each job. A customer gives a high score but writes that the crew scuffed a wall. The owner never hears about it. What do you add?
    • Hold back the link from anyone who mentions a problem
    • Drop the survey and send only the link
    • A weekly read of survey answers, to catch mixed ones for the owner
    • AI Review Auto-Reply for text replies
  2. 150 customers a month get the survey question and the review link, each 1 SMS segment. 10 unhappy customers also get a 1-segment apology. How many text credits is that?
    • 310
    • 320
    • 600
    • 620
  3. A customer gives a low score. Why must they still get the review link?
    • It costs fewer credits
    • Every customer must get the link; holding it back is review gating
    • The workflow cannot run without it
    • Unhappy customers rarely use it

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community