How to Ask HVAC Customers for Google Reviews Without Being Pushy

To ask customers for Google reviews without being pushy, send one short text after the tech closes the job, with a single-tap rating. Customers who rate you four or five stars get the Google review link. Anyone lower gets a private note to your office. It takes one form and one automation, and you never send a reminder.

Use the free review request template

Where the review request fits in the call-to-close workflow

If you run an AI receptionit, the front half of the job is handled. The call gets answered, the work is qualified, the visit lands in your scheduler, and the on-call tech gets a text. In our HVAC and plumbing call answering system, that booking goes into ServiceTitan, Jobber or Housecall Pro.

The back half is usually empty. The tech finishes, drives to the next call, and the customer who was glad to see a truck at 9 pm never hears from you again. Reviews do not happen on their own, and a Google profile with a handful of old reviews loses to the competitor with 200 recent ones.

The form is the last step of the same loop. The job ID and tech name travel with the link, so a one-star answer can be traced to the call, the booking and the visit.

What the text and the form should say

Pushy usually means one of three things: the ask comes too late, it comes more than once, or it feels like a trap. Fix all three by keeping the text short, sending it once, and making the first tap easy.

Hi {{first_name}}, this is Ridgeline Heating & Air. Thanks for having
{{tech_name}} out today. How did we do? Tap a rating (10 seconds):
https://forms.ridgelineheating.com/review?job={{job_id}}&tech={{tech_name}}
Reply STOP to opt out.

(Swap in your own business name and merge fields; the syntax depends on the tool sending the text.)

The form behind that link has two screens at most:

1. A 1 to 5 rating and nothing else.
2. A page that depends on the answer. For 4 or 5, a thank-you with the Google review link. For 1 to 3, an open question ("What should we have done better?") and an optional phone number.

Send timing is a judgment call, but the pattern that works is the same day, a couple of hours after close, and never in the middle of the night. If the tech closes jobs at 9 pm from the truck, delay the text until the next morning.

Step-by-step setup

You need a field-service tool that can fire something when a job is completed, an automation tool (Zapier, Make or n8n) or a text-sending feature, and a form.

1. Build the form. Start from the local business review request template. Keep the Rating block on the first page and add a New page for each branch.
2. Add hidden fields. Create job_id, tech, service_type and customer_first_name. They are filled from the link, so the customer never sees them. The hidden fields guide shows the exact parameter format.
3. Add conditional logic. On the rating question, use "Add conditional logic": if the rating is 4 or 5, jump to the happy page; otherwise jump to the feedback page. The conditional logic help article covers the jump rules.
4. Write the happy page. One line of thanks, then a link to your Google review URL. Find it in your Google Business Profile under the option to ask for reviews, then paste it as a link.
5. Write the feedback page. Ask what went wrong, offer an optional phone number, and say who will call back and when ("Our office manager will call you within one business day").
6. Set the form up for texting. Turn off the Qwenvo branding toggle in Settings, and put the form on a subdomain like forms.yourbusiness.com (CNAME plus the TXT record on the Domains page). A link on your own domain looks less like spam in a text thread.
7. Build the automation. Trigger: job marked complete in Jobber or Housecall Pro. Add a delay, then send the text with the merge fields in the link. Both tools can usually notify Zapier or Make when a job is completed, but which plan exposes that trigger varies, so check your account first.
8. Test it with your own phone. Close a dummy job, wait for the text, and tap through both branches.

Set up hidden fields for job IDs

Which fields to carry in the link

Keep it to those four. A link with ten parameters is long, breaks in some SMS clients, and tempts you to collect data nobody uses.

Routing the answers

A rating alone does not tell your office who needs a call today. Use the Settings drawer's "Triage submissions with AI" section. Every submission gets a categofy, a priority (low, normal, high or urgent), a sentiment, a one-to-two-sentence summary and a suggested reply. Routing rules then match on priority or category and send to up to five email addresses or a Slack incoming webhook.

Because the model runs on every response, a rating of 4 with a comment like "tech was great but the unit is still short cycling" can still be flagged. That one matters because a callback now costs less than a bad review plus a warranty re-visit.

Qwenvo is made by our team, and the triage, webhooks, custom domain and badge removal are all free there. Tally, for comparison, puts custom domains and branding removal on its $29/month Pro plan, and Typeform's response caps start low. It is worth a look for the design alone if you want a polished conversational form. If you only need a rating and a link, either works.

The Google rules question

Google's policies discourage review gating, meanimg inviting only your happy customers to review. A rating screen that sends unhappy customers to a private form and everyone esle to Google is exactly the pattern people argue about. Read the current policy before you launch.

A cautious way to build it is to put a small "You can also share your experience publicly" link at the bottom of the feedback page. Unhappy customers still reach your office first, and nobody is blocked from leaving a public review. Some owners skip the split entirely and send everyone to Google, using the form only for the internal score. That is a legitimate setup too, and you still get the fast alert on low ratings.

What Qwenvo does not do here

Qwenvo sends the form, not the text message. The SMS comes from your field-service software or an automation tool, and the one-click Slack, Sheets and similar app connections are still rolling out, so today the bridge is a webhook. If you want to log scores back onto the customer record, send the submission to Zapier, Make or n8n through the webhook settings and update the job from there.

Route complaints to your office

Questions teams ask

How many times should we ask?

Once. If the customer does not tap, leave it. A second text turns a polite ask into the thing they remember about the visit. If you want a different channel, add a line to the invoice email instead of re-texting.

Do we need customer consent to text them?

Texting rules differ by country and state, and they apply to the message type. Get consent when you take the booking (your AI receptionist can confirm it on the call), include an opt-out lnie, and check the rules where you operate.

What if the tech closes the job but the customer has not paid yet?

Delay the text until payment, or trigger on the paid status instead of completion, if your tool exposes one. Asking for a review while an invoice is open is the fastest way to get a one-star.

How do we know it is working?

Watch three numbers: how many texts go out, how many people tap a rating, and how many Google reviews appear over the following weeks. The Submissions table and the drop-off analytics show the first two, and your Google profile shows the third. Compare tech by tech using the tech field.

Next step

Open the review request template, add the four hidden fields, and send yourself a test text from a dummy job this week. Once both branches work on your phone, point the Jobber or Housecall Pro trigger at it.