Home services / AI phone + messaging workflow
The leak does not care that the office is closed.
For plumbing, HVAC, electrical and field service teams: capture the issue, location and urgency, book routine work and route emergencies to the on-call path your operation approves.
The call that matters
“The basement is taking on water. I need to know someone has the address.”
The job is not to imitate a person. It is to understand this request, use the right source, complete the allowed step and make uncertainty visible.
What customers actually ask
Begin with the requests already repeating.
These are useful starting points because the answer, action and owner can be defined before launch.
- 01
What is happening, where is it and when did it begin?
- 02
Is the address inside the service area and does a routine slot exist?
- 03
Does the request match a defined urgent or on-call route?
- 04
Can the technician receive the access details, symptoms and customer preference before arrival?
What the workflow does
Four moves. One accountable outcome.
Triage
Collect location, issue type, timing and the urgency signals you define.
Book
Schedule routine work against connected service areas and availability.
Dispatch
Notify or transfer to the configured on-call route when criteria are met.
Document
Create the customer, job or callback record with structured details.
What has to be connected
The answer needs an owner and a source.
Supported.tech should receive only the information and permissions required by the selected workflow.
Service map
Trade, location, coverage area, job type, duration and booking rules.
Dispatch calendar
Technician or team availability, travel constraints and appointment windows.
Customer and job record
Address, access, issue description, assets and permitted notes.
On-call route
Defined urgent signals, operating hours, alert owner and fallback behavior.
A responsible first rollout
Prove one route before adding another.
The workflow should turn a scattered call into a schedulable job or a reliable urgent handoff—without pretending to diagnose equipment or replace emergency services.
- 01
Start with routine work
Use one trade, service area and appointment class before urgent dispatch.
- 02
Write safety language
Identify situations where the caller must contact emergency services or a qualified person.
- 03
Test geography and time
Boundary addresses, after-hours requests, holidays and no-capacity days matter.
- 04
Inspect dispatch quality
A booking is not complete unless the right job, address, window and notes reach the field team.
Bring a real request
We will map the first useful route.
Tell us what customers ask, where the current answer lives and who should own the exception. That is enough to design a serious first test.
Map my first workflowHear it handle a real request.
Hear it work →Useful answers
Frequently asked questions.
Can it decide whether a job is an emergency?+
It can detect signals and follow rules your operation approves. It does not independently determine safety and is not an emergency service.
Can it book by service area?+
Yes, when geography, job type, duration, travel and technician rules are represented in the connected scheduling path.
Can it create a work order?+
A verified connection can create the permitted customer or job record with mapped fields and a tested duplicate check.
What should the technician receive?+
The verified contact and address, issue in the customer’s words, relevant assets, timing, access notes and any promised next step.