Most service businesses send their post-job customer survey at the wrong moment, ask the wrong questions, and then quietly stop sending them when the response rate falls under 5%. The problem isn't survey fatigue. It's that the default behavior of survey tools was built for B2C SaaS — quarterly NPS, emailed at 9am Tuesday — and it doesn't translate to the way service work actually ends.
This is the playbook we wish someone had handed us before we built Canopy. It's opinionated, it's short, and it works for plumbers, HVAC techs, electricians, cleaners, and restoration contractors alike.
The five timing rules
- Fire within 2 hours of job-close, not the next morning. The window where the customer feels gratitude (or frustration) most acutely is the first ~6 hours after you leave. By the next morning, the memory has faded into "fine" — which is neither a 5-star review nor a recoverable detractor.
- SMS first, email second.Service-business customers are mobile. Email open rates for post-job surveys hover around 15-20%; SMS open rates are 90%+. Use email as the fallback when you don't have a verified phone.
- Wait for the actual completion event, not the dispatch close.Many CRMs mark a job "closed" when the tech taps Done in the field. For multi-day or permit-dependent work (electrical, restoration), the customer's experience isn't complete until the inspection passes or the adjuster signs off. Survey after the real end, not the system end.
- Never survey before payment lands.If you ask for feedback before the invoice is paid, you're training the customer to associate the survey with the bill. Wait for payment confirmation, then fire.
- If you missed the window, don't catch up. A survey sent 5 days after the job hurts more than it helps. Either skip it or send a quarterly "how have we been doing" check-in — different copy, different intent.
The three-question template
Long surveys get abandoned. Three questions is the sweet spot — long enough to actually learn something, short enough to finish in 30 seconds.
Question 1: NPS
"On a scale of 0 to 10, how likely are you to recommend [Your Company] to a friend or family member?"
This is the load-bearing question. It segments customers into promoters (9-10), passives (7-8), and detractors (0-6). Everything downstream — alert routing, public review request, recovery workflow — keys off this score.
Question 2: The reason
"What's the main reason for your score?"
Open text. Don't put a dropdown here. The free-text response is what tells you whether the detractor is upset about pricing, communication, workmanship, or scheduling — each of which has a completely different fix. Modern surveys can also feed this into AI sentiment + topic clustering so you don't have to read every response yourself.
Question 3 (promoters only): The ask
"Would you mind sharing that on Google?" — with a one-tap link to your Google review page.
Crucially, this question only appears for customers who scored 9-10. Detractors should never be routed to a public review. Instead, their score should trigger an internal alert to your manager so you can fix the issue before the customer thinks to leave one unprompted.
Handling a detractor (the 48-hour rule)
You have roughly 48 hours between a bad service experience and a 1-star public review. The customer hasn't cooled down yet; the story is still fresh; and they haven't decided whether to post anything yet. This is your recovery window.
The recovery script is simple:
- A real human (manager, owner, or assigned account rep) calls within 4 hours of the detractor response.
- They open with "I saw your response to our survey and I wanted to call you personally before anything else happens." That single sentence does most of the work — it signals you read the feedback, you care, and you're taking action.
- Listen first, fix second. Most service-business detractors are unhappy about communication (no callback, no ETA, no update) rather than the work itself. Hearing them out is often the entire fix.
- Offer a concrete remediation — re-do the work, send a different tech, comp a service. Then deliver on it within the week.
We wrote a longer version of this — including the exact script and when to offer a refund vs a re-do — in our companion post on how to recover unhappy customers before they leave a bad review.
What to automate (and what to keep manual)
Automate everything up to and including the detractor alert. Triggering the survey, scoring the response, routing the result, timing the request — all of it should happen without your team thinking about it. Field-service work is busy enough.
Keep the recovery call manual. The single biggest mistake we see is teams that auto-respond to detractors with a generic "sorry to hear that" email. That doesn't recover the customer; it confirms to them that you don't actually care. The whole point of the alert is to get a human on the phone — automating that step away defeats the purpose.
Tools that automate this
Canopy was built specifically for the workflow above. We integrate with the CRMs and field-service tools you already use (HubSpot, Pipedrive, Salesforce, HousecallPro, ServiceTitan) so the survey fires on the actual job-close event — not a manual export. We send SMS-first with email fallback, route detractors to Slack/SMS/email before they think to review you, and use AI to summarize patterns across responses so you don't spend Saturday morning reading feedback.
If you run an HVAC, plumbing, cleaning, electrical, or restoration business, we have a trade-specific overview that walks through how the timing rules above translate to your specific workflow.