All guides

Guide

The Same Day Ask: HVAC review request text templates and the rules that keep you safe

McGuire Flanigan · Updated October 22, 2026 · 7 min read

This HVAC review request text template goes out the day the job closes, names the tech and the work, and carries your direct Google review link, with one polite follow-up a few days later. Ask every customer, never offer anything for a review, and let a person answer any complaint.

The best time to ask for a review is the afternoon the tech leaves, while the house is cool again and the customer still remembers his name. The Same Day Ask is built around that moment. It's three moves, and you can run it by hand from your field software or let an AI agent draft it for your office to approve.

The Same Day Ask, in order

  1. The same day text. The day the job closes, one short text that names the tech and the work, with your direct Google review link.
  2. Your office approves it. A person reads the draft before it goes, at least until you trust the pattern.
  3. One follow-up, then stop. A few days later, one polite reminder to anyone who hasn't left a review, and that's the end of it.

Timing is the reason this works. In BrightLocal's 2026 survey of 1,002 US consumers, 74% said they only pay attention to reviews from the last three months, and 28% said they will always leave a review when they're asked. An old pile of five-star reviews from two summers ago does less than a steady trickle of new ones.

Who this is for and what you need first

This is for an HVAC company whose techs do good work and whose Google profile doesn't show it. Before you send a single request, set up three things:

  • Your direct review link. Google tells businesses to ask customers to leave a review through a link or a QR code. Copy the link from your Business Profile and test it on a phone.
  • A job-closed trigger. In your field software, find the status that means the work is done and the customer has been billed. That's when the text goes.
  • One owner for replies. Decide who reads replies to these texts. Complaints come in through review requests, and someone has to answer the same day.

Step one: the same day text

Send it between one and three hours after the job closes. Early enough that the visit is fresh, late enough that the system has had time to cool the house.

The template:

Hi [first name], it's [company]. Thanks for having [tech first name] out today to [the work, in plain words]. If you have a minute, a quick review helps a small business like ours a lot: [Google review link]

Three examples of the work line, written the way a customer would say it:

  • "replace the capacitor on your AC"
  • "get your furnace running again"
  • "do your spring tune-up"

Keep it under 300 characters. Never mention stars, never say "if you were happy", and never add an offer.

Step two: your office approves it

For the first few weeks, a person reads each draft before it goes. They check three things: the tech's name is right, the work line matches the ticket, and whether the job is flagged (a callback, a refund, a note from the tech).

If the name or the work line is off, they fix the draft. If the job is flagged, a manager calls the customer first, and the same request still goes out to that customer, in the same words. Every customer gets the same request; the flag only decides who talks to them first. After a few weeks of clean drafts you can let the plain version go out on its own and keep approval for flagged jobs, so the call happens before the text. Our trust page explains the default we start from: customer-facing messages stay drafts until someone approves them.

Step three: one follow-up, then stop

Three or four days later, if no review has come in, send one reminder:

Hi [first name], just following up on [tech first name]'s visit on [day]. If you have a minute for a review, here's the link again: [Google review link]. And if anything about the visit wasn't right, reply here and we'll make it right.

Then stop. A third message feels like pressure, and pressure is how a request turns into a bad review.

The last line of that follow-up matters. It gives an unhappy customer a private place to tell you before they tell Google.

The rules that keep you safe

Ask every customer. It's tempting to send requests only to the jobs that went well. Don't. The FTC's staff guidance on its reviews rule says that asking only customers you expect to be happy could be a deceptive practice under the FTC Act, even though general requests to all customers are fine. Ask everyone, in the same words. That includes a job that went badly: a manager calls first, then the same request goes out.

Never offer anything for a review. No discount, no gift card, no entry into a drawing. Google's own rules say incentives for reviews are strictly prohibited, and the federal rule that took effect in October 2024 bars paying for reviews that express a particular sentiment. A struck-out example of what not to send: "Leave us a review and get [amount] off your next tune-up."

Don't write the review for them. No suggested wording, no pre-filled stars. Your text names the work so they remember the visit, and that's all.

Answer complaints like a person. When someone replies with a problem, a person calls back. The agent's only job is to notice the reply and stop the follow-up.

How an agent runs it

Once the three steps work by hand, an agent saves the office the typing. Each afternoon it:

  1. Reads the jobs that closed today, with the tech and the work from the ticket.
  2. Flags any job with a callback, an open complaint or a refund note, so a manager calls that customer first. Flagged jobs still get the same request.
  3. Drafts the same day text for every job that closed today, using the template.
  4. Puts the drafts in one person's approval queue.
  5. Three days later, checks for new reviews and drafts the single follow-up for anyone who hasn't left one.

There's more on the tools and setup in our guide to AI for review requests in HVAC companies, and our review requests help page shows how the queue looks.

What to watch out for

  • Generic wording. In the same BrightLocal survey, 50% of consumers said generic or templated review responses put them off. The same goes for requests. Naming the tech and the work is what makes it read like a person.
  • Wrong customer, wrong phone. Landlords, property managers and second homes all break the "text the person who was there" assumption. Check the contact on commercial and rental jobs.
  • Texting rules. Only text customers who gave you their number for service messages, and honor any stop reply right away.

How to tell it worked

Before you start, write down the date of your newest Google review and how many reviews you got last month. Run the Same Day Ask for eight weeks. Then look at the same two numbers, and read the new reviews: if customers mention techs by name, the request is doing its job.

Questions operators ask

When should an HVAC company send a review request?

The same day the job closes, usually one to three hours after the tech leaves. The visit is fresh and the customer can still picture the tech who came out.

Can I only ask happy customers for reviews?

No. The FTC's staff guidance says asking only customers you expect to be happy could be deceptive. Ask every customer with the same message and handle complaints privately.

Can I give a discount for a Google review?

No. Google prohibits incentives for reviews, and the federal reviews rule bars paying for reviews that say something positive. Ask without offering anything.

How many times should I follow up on a review request?

Once. One reminder a few days later is polite. More than that feels like pressure and can turn a happy customer into an annoyed one.

See where AI fits in your operation

Thirty minutes on how the work actually moves. No pack of agents. No obligation to build. If we can help, we will show you the first paths. If we cannot, we will say so.

Sources

  1. Local Consumer Review Survey 2026, BrightLocal
  2. Google Business Profile review guidelines, Google
  3. FTC FAQs on the Consumer Review and Testimonials Rule, Davis Wright Tremaine
  4. Trust and Security, Cortex

Keep reading