The no-heat call comes at 9pm
Humbrook builds an AI receptionist for HVAC contractors that answers when the truck is on a job and the office is closed. It gets the address and the problem, texts the caller back with a confirmed time, and puts a service call on the schedule.
The call reaches a demo receptionist, not a salesperson. A project starts over email.
What actually happens to the phone
The week a cold snap lands, every furnace quits at once and the next caller gets voicemail.
A caller with no heat at night is not choosing a company. They are dialing down a list, and whoever answers first with a real appointment gets the job.
Tonight 9:52 pm
Glenn W. called with no heat upstairs.
Booked the first service window tomorrow, 7:30 am.
He says the thermostat is showing nothing at all.
Answers
It picks up when the line is busy or the office is closed, states plainly that it is an AI assistant, and asks what the equipment is doing.
Sorts
A no-heat call and a no-cool call get different questions, since the wrong one wastes the tech's first ten minutes on-site.
Books
The address, the equipment as the caller describes it, and the earliest open service window go straight onto the schedule.
Confirms
The caller gets a text confirming the service call, and the tech shows up with the job already on the board, not a callback owed.
Asked something it was not set up for, it says so and passes the caller through rather than guessing.
Where the schedule actually lives
What the build can reach depends on the platform, and the honest ceiling is printed on the card.
- Two-way sync
Housecall Pro
Housecall Pro has an open API, so Humbrook builds a real two-way sync between the phone system and the job schedule.
- Calendar-level
ServiceTitan
ServiceTitan's integration runs through a gated partner-request portal. Humbrook confirms that status before quoting anything, and unless the contractor is an approved marketplace partner, builds this at the calendar level, text-confirmed, around ServiceTitan, not as a live sync into it.
Where a booking tool has no open way in, the receptionist books on a calendar and sends the details on. Nothing here claims a connection that is not there.
What owners ask first
The shop already has a dispatcher. Why add this?
A real dispatcher handles a job already in progress better than any system. Your receptionist takes the calls that come in while that dispatcher is on another line or off the clock, not the ones already covered.
A no-heat emergency at night, is a bot safe to hand that to?
An emergency needs a human fast. On an urgent call, the receptionist gets the address and a callback number first, then texts or calls whoever is on-call. It does not try to solve it alone.
Does it plug into ServiceTitan?
Only at the calendar level unless the shop is an approved ServiceTitan marketplace partner. The receptionist books the service call and sends the confirmed detail by text, and a person enters it in ServiceTitan.
Questions this raises
What happens to a missed call?
Where a missed call actually goes, and what an AI receptionist does with it instead of voicemail.
How much does a custom AI phone agent cost?
Humbrook quotes one fixed price per build by email, and the vendor bills go straight to the client.
The service call still needs a schedule, even after hours
Humbrook builds the receptionist that answers, sorts a no-heat call from a no-cool call, and puts the job on the schedule before the caller tries the next contractor. It is paid for once and it runs on the shop's own accounts.
It answers as a demo business in this trade, so the hours, services and prices it quotes belong to that business. Everything underneath is the real thing: it listens, checks a live calendar, and writes the booking down.
No form, and no call needed to start.