HVAC
Missed-call text-back for HVAC — the same-minute SMS that books the job before a competitor calls back.
For owners running one to fifteen trucks
An HVAC phone is the business. After-hours no-heat emergencies in January and no-cool breakdowns in July are the calls that pay for the year, and they are also the calls most likely to hit voicemail when every line on the dispatch board is buried. Missed-call text-back fires a same-minute SMS from your forwarding number the moment a call goes unanswered — lead reads it within minutes, taps the booking link, and is in your CRM before the next shop on Google has time to answer. HQ Growth Systems is operator-built: the text-back and the AI answering were live on our own trucks before they were sold to anyone else.
The math
The missed-call math specific to HVAC.
HVAC has two peak moments per year, and both of them arrive fast. A no-heat call at 11pm during a January cold snap is not a patient lead who will wait until morning — it is a homeowner with a family in a cold house, dialing the first number that picks up. If that call hits your voicemail, the lead dials the next result on Google before the greeting finishes.
Cooling-season surges run the same math in the opposite direction. A Saturday in July when every tech is on a job and the dispatcher is managing four calls at once is exactly when the tune-up call or the compressor-out emergency goes to voicemail. By Sunday morning the lead has moved on. The dispatcher does not know the call existed.
The third failure mode is the voicemail-to-competitor dial-back. A lead who left a Friday-afternoon voicemail gets a Monday-morning callback from the dispatcher — and explains, with audible irritation, that they already booked with someone who texted them back Friday. The job is gone. The appointment slot on Monday is wasted. The dispatcher logs a missed opportunity and moves on to the next call.
Same-minute recovery
Missed-call text-back — the same-minute SMS that books the job.
Every unanswered call fires a same-minute SMS from your forwarding number with a booking link. The lead does not have to call back, wait on hold, or navigate a voicemail tree. They read the text within minutes, tap the link, and book a slot in your CRM — without the dispatcher touching a phone and without the lead dialing a second number.
The forwarding number that sends the text is yours. The message voice is yours. The booking link lands in your scheduling system, not a third-party intake queue. The lead is in your CRM with a booked slot before the dispatcher has even seen the missed-call notification.
The timing is the point. A same-minute text arrives while the lead is still in the moment — still standing in front of the broken furnace, still sweating through a no-AC weekend. A Monday callback arrives after they have already booked with someone who responded first.
What it covers, and what it doesn't
Text-back and AI answering — two parts of the same bench.
AI answering covers the calls that ring through — picks up by the second ring, runs the conversation in an HVAC voice, captures the lead into the CRM, and routes no-heat or no-cool emergencies straight to the on-call tech. Missed-call text-back covers the calls that do not ring through — the ones that hit voicemail because every line was busy, because the lead hung up before the second ring, or because the weekend surge swamped even the AI.
The two together close the gap. AI answering handles the conversation; text-back handles the lead that did not wait for one. Neither replaces the dispatcher on a live job — the dispatcher is still the one who manages the board, routes the tech, and handles the jobs already in flight.
- When text-back fires — a busy trunk, a recognized number that hit voicemail, the dispatcher on a job, a Saturday-morning surge when every line is occupied.
- What's in the SMS — a booking link in your brand voice, sent from your forwarding number, landing in your scheduling system.
- What it is NOT — text-back is not a callback script and not a replacement for human dispatch. It recovers the lead that would otherwise disappear before the dispatcher is free.
Why the bench
Operator-built, run on our own trucks before it ships to yours.
HQ Growth Systems was not built in a marketing meeting. It came out of running HQ Plumbing and HQ Property Maintenance firsthand — every workflow on the bench was built because the dispatcher needed it, the on-call tech needed it, or the owner needed it before any of it was ever sold to another shop.
The missed-call text-back was wired up because a no-heat call at 11pm during a winter cold snap hit voicemail and was gone by morning. The AI answering was wired up because the cooling-season Saturday surge buried every line and leads were disappearing before the dispatcher had time to call back. Both were live on our trucks before they shipped to anyone else's.
Every workflow that ships to your trucks is the workflow that is already running on ours. If something is still being tuned, we say so — we do not sell a playbook we have not run.
“The no-heat call at 11pm does not wait for a callback. So we built the text-back, ran it on our own trucks first, and then shipped it.”
Run the same bench on your trucks
See if the bench fits your shop.
Tell us your truck count, your after-hours coverage, and your missed-call rate — we’ll come back within one business day with the tier that fits, and tell you when none of them fits. No slide deck.