Plumbing leak
Town, fixture, active water, shutoff status, photo status, access note, tenant or owner approval, and emergency threshold.
View plumber intakeAI dispatch assistant for contractors
Do not automate dispatch until the handoff is safe.
An AI dispatch assistant should not guess arrival windows or push jobs into the schedule blindly. The first win is cleaner triage: capture the caller, classify urgency, collect job facts, and send the owner or dispatcher one approval-ready handoff.
Dispatch handoff preview
UrgencyActive leak, no-cool, outage, blocked access, storm damage, or routine quote.
ReadinessTown, address, customer, job type, photos, access, system clue, and missing fact.
Human ruleNo price, diagnosis, arrival promise, safety advice, or dispatch commitment without approval.
Next actionCall now, request missing detail, stage a task, or route to the approved emergency path.
Dispatch-ready, not dispatch-reckless
The assistant should make the next human decision obvious.
For contractors, the expensive failure is not only a missed call. It is a half-captured lead that reaches the owner without urgency, service-area fit, photos, access notes, or a clear boundary around what the customer was promised.
Estimate the missed-call leakNo-cool call: Leland, 7:42 PM
Captured: customer, phone, town, system age, vulnerable-resident flag
Missing: model photo, breaker check, prior service history
Rule: prepare callback, do not promise tonight until owner approves
Where it fits
AI dispatch sits between call answering and field-service software.
ServiceTitan, Jobber, Housecall Pro, CallRail, answering services, and AI phone agents can all help with part of the path. Cape Fear Agent Co. focuses on the connective tissue: the approved rules and handoff structure that keep dispatch decisions trustworthy.
| Layer | What it does | What can go wrong | Cape Fear workflow fix |
|---|---|---|---|
| Phone or lead source | Customer calls from Google, LSA, website, voicemail, text, or a tracking number. | Source, urgency, and caller expectation disappear before the owner sees it. | Tag the source and collect the first job facts before the lead cools off. |
| AI or receptionist intake | Answers, asks questions, collects details, and summarizes the request. | The script captures generic notes but misses trade-specific dispatch clues. | Use trade-specific question paths for leak, no-cool, outage, roof, restoration, garage door, and storm cleanup calls. |
| Dispatch decision | Decides whether to call now, stage for morning, request photos, or route to emergency coverage. | The system promises timing, pricing, or a visit before a human approves capacity. | Keep dispatch promises approval-gated and make the next human action explicit. |
| Field-service record | Adds a task, note, customer record, job draft, calendar hold, or review queue. | Bad automation creates dirty records or hides the missing facts. | Stage the handoff first, then decide what is safe to write into ServiceTitan, Jobber, Housecall Pro, CRM, or inbox. |
Trade paths
Dispatch questions should change by call type.
A useful dispatch assistant is narrow enough to know what matters for each trade and careful enough to avoid unsupported field judgment.
HVAC no-cool
Town, system type, thermostat clue, breaker clue, vulnerable-resident flag, previous customer status, and approved callback priority.
View HVAC intakeElectrical issue
Outage scope, breaker behavior, smell or heat flag, affected area, safe photo request, and no DIY safety advice unless approved.
View electrician intakeRoof or storm damage
Storm timing, leak location, interior impact, tarp mention, photo status, access constraints, and no arrival promise without capacity.
View roofing intakeRestoration call
Active water, affected rooms, source status, insurance mention, standing water, photos, and approved emergency escalation.
View restoration intakeGarage door repair
Door stuck open or closed, vehicle trapped, spring or opener clue, photo prompt, access, and callback-ready urgency signal.
View garage door intakeImplementation order
Start with a review queue before writing into dispatch.
The safest first build is usually not full auto-dispatch. It is a staged handoff where the owner or dispatcher can approve the next step, tune the rules, and decide which records can be created automatically later.
- choose one urgent call type worth testing first
- write the intake questions and do-not-promise boundaries
- route the handoff into an inbox, CRM note, task, or owner review queue
- review a handful of real handoffs before automating schedule writes
- expand only after the missed facts and escalation rules are clean
Field software
ServiceTitan, Jobber, Housecall Pro
Stage notes, tasks, job drafts, or review queues before allowing an assistant to touch production dispatch.
View integration pathPhone layer
AI receptionist comparison
Compare phone answering tools by what they produce after the call, not just whether they pick up.
Compare optionsStart
Dispatch workflow audit
Send one messy dispatch path. Cape Fear maps the first safe handoff and the rules that should stay human-approved.
Request audit