Industries · HVAC
After-hours calls go to voicemail. No-cool emergencies book themselves.
AgentRigor answers, qualifies, books, and confirms before the owner wakes up — versioned and regression-tested like firmware, not a chatbot you trust on faith.
- prompt.version
- v0.7.3
- tools.bound
- telephony · crm · calendar
- eval.sweep.last
- 142 / 142 · 0 regressions
- call.type
- no_cool
all evals green · no regressions on last push
The overnight loss
Every missed call after 9 pm is a job that rolled to a competitor.
HVAC revenue is time-critical. The homeowner with a no-cool call at 10 pm is not waiting until morning — they’re booking whoever picks up.
- A no-cool call at 10 pm hits voicemail. The caller books the next shop that answers.
- Refrigerant questions and emergency callbacks pile up until someone opens the inbox Monday morning.
- Seasonal demand spikes — first heat wave, first freeze — arrive before the dispatch board can absorb them.
- Slow callbacks don't just lose the ticket; they lose the review.
What the agent does
Four deterministic steps. No improvising on the calls that matter.
The agent is wired to your existing dispatch stack — telephony, CRM, calendar — so the team starts the morning with a booked board, not a call-back list.
Answer the call
Picks up after-hours (or reads the web-form drop), captures service type (no-cool, refrigerant, water heater, maintenance), urgency, and address band.
Qualify in one exchange
Asks the questions your dispatcher would: equipment age, refrigerant type if relevant, last service date. Confirms whether this is a same-day emergency or a scheduled slot.
Book on your dispatch board
Writes the appointment into the calendar and CRM the team already uses — ServiceTitan, Jobber, Google Calendar. No shadow schedule.
Confirm by SMS + email
Sends the customer a confirmation with the time, the tech name, and a reply-to for rescheduling. Owner wakes up to a booked board.
From the case study
A two-person HVAC shop stopped losing weekend leads to voicemail.
Before
- After-hours calls land in voicemail. The caller hangs up and books the next shop that picks up.
- Monday morning the owner works the inbox by hand — a quote request is a six-hour round trip.
- Weekend leads are the highest-intent ones. They are the ones being lost.
A 24/7 lead-response agent now picks up after-hours, qualifies, books, and confirms while the owner is off the clock. Eight weeks since go-live, the inbox is empty on Monday morning.
Run trace
v0.7.3- prompt.version
- v0.7.3
- eval.sweep.last
- 142 / 142 · 0 regressions
Is this the right fit?
A short checklist before the scope call.
We run a fixed-fee two-week pilot, so we qualify on our end too. These are the signals that predict a clean engagement.
Good fit
- 5–30 techs in the field
- After-hours call volume above 10 per week
- ServiceTitan, Jobber, or Google Calendar already in the stack
- Owner or dispatcher manually works the call queue today
Not a fit yet
- No inbound call volume (email-only inquiries)
- Real-time safety dispatch only — this agent is not a 911 substitute
- Team hasn't mapped their routing rules yet (we map them in week one, but the operator needs to be in the room)
Start the HVAC pilot
Two weeks. Fixed fee. Tell us the workflow.
Book a scope call — we’ll map your after-hours routing rules, wire the agent to your dispatch stack, and have it qualifying leads and booking jobs in your calendar in two weeks. Flat fee. No SOW.