Picture a Sunday night at 10:40 pm. A homeowner in Mesa searches “AC stopped cooling”, calls a five-truck HVAC shop, and gets a human on the second ring. The human listens, takes the name and the address, promises a callback in the morning, and writes the call down on a notepad next to the bed. By 7 am the notepad has four entries on it. By 8:30 am the owner has transcribed them into the dispatch board — roughly six to eight minutes per call, with the trade vocabulary, the ticket size, and the symptom half-remembered. That transcription window is where most of the value goes missing: tickets arrive in the queue, but the qualification that priced them and the urgency that ranked them has been flattened into a single line of freeform notes.
Where manual entry loses jobs
The loss does not look like a missed call. The phone was answered. The ticket was created. The tech rolled. What changed is the order in which the ticket landed — and, just as often, the order was reversed. A slab-leak diagnostic and a capacitor swap both arrive at the dispatch board as “1 ticket”, and on a Monday morning the ticket board does not remember which one came in at 11 pm and which one came in at 7 am. The tech who could have taken the slab-leak has been routed to the capacitor swap first. The slab-leak waits until the afternoon, by which point the homeowner has called a competitor.
Manual entry also drops qualification data on the floor. The after-hours person who answered the call heard the homeowner say: rusted tank, three-year-old warranty, water on the garage floor, has been running for two weeks. The morning dispatcher typed: water heater issue, asap. The ticket board does not know that this job is a warranty candidate, an emergency, and a 25-to-45 minute diagnostic. It knows one job, ranked by arrival time.
What the AI captures on the call
The intake conversation the AI walks through is the same conversation a triage tech would run if a triage tech were sitting by the phone at 10 pm on a Sunday. The intake script templates on the scripts page ship this verbatim, ordered Q&A by trade and call type. The two template families the AI defaults to are emergency HVAC (no-cool / no-heat on the first ring) and slab-leak plumbing diagnostics. For each, the AI collects: trade vertical, symptom with timeframe, ticket size band (single-visit vs multi-day), urgency (down-now, today, this-week), homeowner contact, address, gate code, pets-on-site, warranty status, and prior service history. Each answer is timestamped so the morning queue can rank tickets the way the conversation actually unfolded.
The capture happens in less than ninety seconds of caller time. The AI does not drone through a script — it adapts the next question to the answer it just heard. If the homeowner says “rusted tank” the next question is warranty status, not unit age. If the homeowner says “two weeks” the urgency field drops to “this-week” automatically. The intake ends with a confirmed timestamp, a readout of what the AI understood, and a confirm-to-text of the ticket summary to the homeowner’s phone.
What lands in ServiceTitan, Housecall Pro, and Jobber
The output of the AI call is a structured payload, not a transcript. Three fields matter for the dispatch board, and the integrations deliver them differently per platform.
ServiceTitanreceives a job record created under the matching customer (matched on phone number, created if new), tagged with the trade vertical, urgency band, and ticket-size estimate from the intake. Job notes carry the structured intake fields in named keys, not a freeform blob, so the dispatcher and the tech both see the same picture. The job lands in the dispatch board ranked by urgency, then by created-at. Trade-vertical routing rules respect ServiceTitan’s technician skill tags, so a slab-leak does not auto-route to a tech tagged only for water-heaters.
Housecall Proreceives a job with the customer contact synced (matched on email or phone), the appointment window proposed by the AI as a soft-hold, and the intake summary attached as a job description with the trade-vertical tag set. Tag rules on Housecall Pro feed the tech-facing app and the office pipeline view, so the slab-leak tag floats to the top of the morning queue alongside the AI’s urgency ranking.
Jobberreceives a work order tied to a client (matched on phone, created if new), with the property address and the gate code, the trade-vertical and urgency as line-item properties, and the AI’s proposed window as the request date. Jobber’s work-order view then surfaces the intake fields in the description block, in the same order the AI asked about them, so the tech on the way to the door sees the same prioritization the morning dispatcher did.
Across all three, the homeowner receives a confirmation text with the same ticket-summary readout the dispatcher sees. That parallel copy — dispatcher and homeowner reading the same prioritization — is what closes the perception gap that usually shows up when a tech arrives looking lost in the morning queue.
The closing-the-gap payoff
The change that owners describe on a discovery call is not a big number on the income statement. It is the morning queue. Tickets arrive pre-ranked, pre-qualified, and pre-tagged, so the owner spends Monday morning assigning dispatch based on the qualification the AI heard on the call — not the few words the after-hours person remembered at 7 am. The tier-by-tier comparison on the pricing page covers the volume caps and integration depth for Solo, Multi-Truck, and Shop Network so an owner can match the rollout to the shape of their dispatch board.
The smaller, quieter wins are upstream: warranty candidates arrive flagged, not surfaced two weeks later when the homeowner calls back to ask; the after-hours person who used to take the Sunday calls stops losing Sunday nights, so their capacity is freed for the morning’s actual workload. The end state is the same dispatch board, same tech count, same ad spend — but the queue it sees at 7:30 am is the queue the calls actually produced, in the order the calls actually arrived.