Use cases / Plumbing / Dispatch & scheduling
Inbound call triage into job cards
The office spends mornings calling people back to ask what's wrong and where they are.
The business case
This one is mainly a time-saved case, so we don't claim revenue. Assumptions (illustrative): 30 inbound service calls per week, about 4 min saved each, staff time valued at $30/h, running cost $100/mo, setup $2,000.
| Case | Hours saved / mo | Value of time − running cost |
|---|---|---|
| Conservative | 4.3 h | $30 |
| Expected | 8.7 h | $160 |
| Optimistic | 13.0 h | $290 |
Time saved only matters if it gets used on billable work. Track the before and after.
Requirements & gating
- Voice AI: Retell AI and Vapi document custom tool and function calls, call transfer, and webhooks (Retell:
call_ended,call_analyzed). verified Bland and Synthflow feature details: not verified - Jobber: public GraphQL API using OAuth. A custom integration can connect to up to 5 Jobber accounts without App Review; beyond that it must pass Marketplace review. verified
- Housecall Pro: the public API and webhooks are MAX plan only, and the owner generates the API key. Webhook events include
estimate.sent,job.completed,lead.created,invoice.paid. verified - ServiceTitan: API access is partner-gated (Request Access, then a verification that takes roughly 3–5 business days). ServiceTitan tells customers not to give third-party developers admin access or API keys, and to contact ServiceTitan Integrations first. Plan for this before you quote. verified
Check what the app already does first:
- ServiceTitan and Housecall Pro may sell their own AI call answering, which would compete with this build: not verified. Ask the owner what they already pay for.
Build steps
- Get transcripts from the voice-AI agent (or a call-recording tool with transcripts; CallRail features: not verified).
- The LLM extracts JSON: name, phone, address, problem, urgency, access notes. Missing fields return null.
- Write a draft request or lead (Jobber request, Housecall Pro
POST /leads). ServiceTitan only after partner approval. - A dispatcher confirms every card before it's scheduled. Don't auto-dispatch.
Test cases before go-live
- Transcript with no address: address is null, not guessed.
- Two problems in one call: both are captured in the summary.
- Caller misspells a street: dispatcher sees the raw transcript next to the card.
Tool names are examples, not endorsements. Check current features, plan tiers, and pricing before quoting a client.
Sample prompt
From this call transcript, extract the customer name, address, callback number, problem summary, urgency (emergency/soon/routine), and access notes. Return JSON. If a field is missing, return null and do not guess.
Pitch it to the owner
"Calls arrive as pre-filled job cards for dispatch to check and assign."
Lead with the outcome, not with "AI," and show the business case using their own numbers.
What can go wrong
- Hallucinated addresses or numbers. A human confirms before anyone is sent out.
- Texting consent: Under the TCPA, automated texts generally need prior express consent, and marketing texts need prior express written consent. Honor STOP right away and keep consent records.
- Twilio/10DLC (2026): new A2P 10DLC campaigns must include public privacy policy and terms URLs (required since June 30, 2026), a verifiable opt-in, and opt-out language. Third-party lead generation and affiliate marketing are forbidden use cases. verified
- Reactivation defaults to email. Texting past customers is marketing. Use SMS only where written consent is documented.
- Call-recording consent: some states, including California, require all parties to consent (this list is not exhaustive). The safe default is to disclose recording and the automated assistant at the start of every call.
- AI voices: the FCC's February 2024 declaratory ruling (FCC-24-17) treats AI-generated voices as 'artificial voice' under the TCPA, so outbound AI calls generally need prior express consent. Further AI disclosure rules were only proposed in 2024. Keep builds inbound unless counsel approves. verified
- Failure modes: hallucinated details, missed escalations, and integrations that break silently. Add a human fallback, daily error alerts, and a weekly transcript review.
Not legal advice. Texting, calling, and recording rules vary by country and state and change over time. Have the client confirm compliance with qualified counsel before launch.
Suggested price
$1,500–$3,500 setup
Starting estimate only, not verified against market rates. Adjust for scope and support.