HVAC
“AC stopped cooling in the waiting room. Tomorrow afternoon?”
The AC call is already in the inbox. AI drafts the repair, the site, and the window. A person still says it is a job.
This is
AI field operations for cooling and heat calls that already live in the inbox.
This is not
- Not a packaged HVAC edition.
- The model does not create the job or pick a tech.
- There is no customer portal.
The hop
Summer does not wait for a spreadsheet.
The request is a sentence. The delay is the hop, screenshot, sheet, guess, then “are you coming?” in the same chat.
01
The call lands on a personal phone
A customer writes the way they already write. If that WhatsApp is the owner’s, the week is off when the phone is off.
02
Someone retypes the unit and the window
Address, “waiting room,” tomorrow afternoon, something is always off. The crew member guesses which rooftop.
03
Done is a photo in a group
Filter, readings, signature, or nothing. The customer asks again in the thread that started the work.
The draft
Same gate. Different sentence.
If afternoon is only 82% sure, you see it. If “AC repair” is not in your catalog, software rejects the guess. The thread stays next to the draft.
Draft
“AC stopped cooling in the waiting room. Tomorrow afternoon?”
- Service
- 96%
- Site
- 88%
- When
- 82%
- Problem
- 97%
AC Repair
Waiting room
Tomorrow afternoon
AC not cooling
The path
First message to job done.
01
They write the cooling call
No portal. “AC stopped. Waiting room. Tomorrow afternoon?” That is enough. Filters, boilers, and no-heat land the same way.
02
Queries owns the thread
WhatsApp, SMS, email, and voice sit in one inbox tied to the business. AI drafts HVAC repair, site, and window. You still see the raw message.
03
A person converts it
Approve, edit the site, or leave it as a conversation. The model does not invent a job or pick a tech.
04
The crew closes on a phone
You assign by hand. They open the job, run your checklist, photos, signature. The customer is told it is done.
In the office
The desk sees a request, not a group chat.
Needs you, AI handling, ready to convert. Link a customer when you have one. Assign the tech and the window from the jobs list, late and unassigned sit up front. Insights stay with owners and admins; dispatchers stay on the inbox.
Queries · one inbox
In the field
The visit is still the product.
The crew does not get a second inbox. They get the job: site, briefing, status, maps, then the checklist you configured, filters, readings, photos, signature. AI started the record from a message. It does not replace the van.
FAQ
Straight answers for this trade.
No. The architecture is generic field operations. The first sales conversations are HVAC-shaped because that is how the request already arrives, “AC stopped”, not because we ship a packaged edition.
No. It drafts service, site, window, and the problem, each with confidence. Software checks the service against your catalog. A person still approves.
It can suggest from the message and your catalog. If the service is not something you offer, the draft does not invent it. You still read the thread.
A one-off request still has to become a job someone owns. We do not ship a standing maintenance series as a packaged edition.
Other trades
Same path. Different sentence.
Bring a real cooling call to the next conversation.
Tell us how a request becomes a job today. We walk the inbox-to-job path if it fits.