Intake writes the job the board already knows — so the office that books it and the truck that runs it never diverge.
One native job. Office to dispatcher to back office.
Bring Angi, Thumbtack, the website, SMS, and the phone into one thread so the office works the lead once.
Fold every side channel into the same HVAC job — not a lead in one tool and a visit in another.
The gain is one native job object from front office through the dispatcher into back office — not an Avoca layer on another platform, not a ProBook overlay the office reconciles later.
Run inbound and outbound voice as the CSR surface — press-1 trees are what the agent replaces, or the flow it already sits on.
Take the no-cool, or work an unsold list, and write the job instead of a transcript someone retypes.
We are building the prototype surface with design partners. A flow stays a draft until the shop has heard it on a real line.
What the agent replaces — or the flow it already sits on.
An IVR is a published flow, not a menu somebody rebuilds by hand every season. We are publishing these with design partners, with the agent either behind one key or in front of the whole tree.
| Scenario | First pass | Hands to | What it writes |
|---|---|---|---|
| Peak no-cool | Voice agent | A CSR, on the same call | One job on the property |
| Membership tune-up | Voice agent | Nobody — it books the window | The tune-up on the member record |
| After-hours | Voice agent | The on-call desk, by rotation | The same job, flagged after-hours |
| Unsold estimate | Outbound agent | A CSR when the answer is yes | Activity on the job already open |
A scenario picks the destination, and a person and an agent are two destinations on one flow. Either one writes the same job.
Totals do not tell a shop which turn failed. We are building these against design-partner call logs, one named turn at a time.
A flow should learn from what the tech found on the property, not from how the call sounded. That is the direction we are building toward, not a feature that ships today.
A flow writes the job. A person still applies the dispatch.
Configure the flows that hold both. A voice agent or a person on the desk writes the same job.
Put no-cools, memberships, and after-hours on one contact-center record the truck will open — not a phone stack the office reconciles later.
Let a customer pick a slot by service area, zone, and tech capacity — a clean booking that is already a job, before it hits the board.
Attach the property and the zone before anyone retypes the window onto dispatch.
Front office intake writes the same job. The AI proposes who takes it and when; a person still applies the dispatch.
Nothing goes to the field until the shop says yes. That applied assignment is what back office and the truck run.
Match the visit to a tech who is free, in zone, and cleared for that work — then propose the name instead of guessing from a whiteboard.
Fit the visit into a real open slot on that tech’s day so the promise time is something the shop can keep.
Keep the same job record from intake through the truck — no second ticket reinvented in dispatch.
A person accepts the proposal so nothing goes to the field until the shop says yes.
The AI dispatcher proposes who, when, and which job. A person still applies the dispatch. Open the AI dispatcher →
They live on the same record. This page owns intake to the board.
A walkthrough of the inbox, a voice turn, the contact-center desk, a booking, and the dispatcher proposing — a person still applies it. One conversation, not a self-serve signup.
Angi, web, SMS, and the call in one thread.
Inbound and outbound — press-1 is what they replace or sit on.
Flows that host agents and people on the same job.
A window by zone and capacity — already a job.
The AI proposes. A person still applies it.
