Why this hub exists

Home services teams (plumbing, HVAC, electrical, cleaning) adopt My AI Front Desk to answer calls 24/7, qualify jobs, and schedule work without adding staff. This page consolidates proven integration patterns (“recipes”) that connect call outcomes to your field service/ops stack—specifically ServiceTitan, Jobber, Workiz, and Housecall Pro—so dispatchers see clean data, calendars stay accurate, and techs arrive with context.

• Core capabilities you’ll use: instant call answering, qualification, appointment booking, two‑way SMS, live transfer, and analytics. See platform features and integrations on Features and setup guidance in Build and test your AI receptionist.

• Integration approaches supported today: native calendar sync, webhooks, and Zapier-based workflows to common CRMs/booking tools used in home services. For CRM/PMS syncing patterns, see CRM integration guide and the deeper CRM integration tutorial.

How the data moves (high-level)

• Inbound: Caller → AI receptionist (capture: name, phone, address, issue, urgency, permissions) → create/update Customer + Job/Estimate in your FSM → optionally book a timeslot and SMS a confirmation.

• Outbound: Job status updates or schedule changes from your FSM → SMS reminders/reschedules via AI → optional live transfer for escalations.

• Fallbacks: After-hours or no-availability → capture lead, tag urgency, route to on‑call, and create unscheduled job to avoid leakage.

Quick recipes by platform

The flows below reflect common customer deployments. Where a direct connector isn’t available, use webhooks/email-to-inbox parsing or a lightweight middleware step. Keep PII minimal and map only the fields your techs need on-site.

Platform	Typical goal	Recipe (flow)	Key fields to map
Jobber	Turn qualified calls into scheduled jobs	Call → qualify → Create Client → Create Job → Book Visit → SMS confirmation	name, phone, email, service address, job type, priority, preferred window
Housecall Pro	Convert estimates and emergencies fast	Call → detect “estimate” or “emergency” → Create Customer → Create Estimate or Job → Assign tech/on‑call → SMS ETA	customer contact, address, problem notes, estimate vs. job, on‑call flag
Workiz	Keep dispatch board full and accurate	Call → qualify → Create Lead → if time accepted: Create Job + Schedule → SMS calendar link	lead source, service category, geo, time window, notes, marketing tag
ServiceTitan	Preserve line-of-business rules while reducing missed jobs	Call → qualify → Create Customer + Job (API or inbox parsing) → optional Appointment hold → push tags/priority → live-transfer high-value	customer record, location, problem, priority, campaign, business unit

Notes

• Live transfer: keep enabled for complex/volatile calls (billing disputes, safety issues). The AI passes context so customers don’t repeat themselves.

• Scheduling source of truth: keep the FSM calendar authoritative. AI proposes/holds slots; finalization writes back to the FSM.

Jobber

What teams automate

• New caller → Client + Job + Visit in one pass (with SMS confirmation link).

• Missed/after-hours calls → Client + unscheduled Job with “after-hours” tag for morning dispatch.

• No‑show rescue → Jobber event change → AI SMS reschedule link.

Data mapping (minimal)

• Required: name, phone, service address, job type.

• Optional: email, access notes, priority, marketing source.

Setup path

• Use Zapier/webhooks to “Create/Update Client,” “Create Job,” and “Schedule Visit,” or mirror via your integration tool of choice. Validate time zones and buffer rules against your Jobber calendar.

Housecall Pro

What teams automate

• Estimate requests → Customer + Estimate with line-item notes captured from the call.

• Emergency triage → tag job “Emergency,” alert on-call, and place a hold on the earliest window.

• Service reminders → calendar event → AI SMS confirm/modify.

Data mapping (minimal)

• Required: name, phone, address, job/estimate type.

• Optional: photos link, gate/lock codes, promo/campaign tag.

Setup path

• Use Zapier/webhooks for “Create Customer,” “Create Job/Estimate,” and “Add Job to Schedule.” Confirm drive-time buffers before exposing windows to callers.

Workiz

What teams automate

• Lead capture with intent classification (install vs. repair) → Job creation when the caller accepts a slot.

• Lead source stamping for ROI (e.g., “AI phone receptionist”).

• Schedule changes → AI sends reschedule options via SMS.

Data mapping (minimal)

• Required: name, phone, city/ZIP, category, preferred window.

• Optional: lead source, urgency, notes for tech.

Setup path

• Use Zapier/webhooks for “Create Lead/Job” and “Schedule Job.” Normalize categories to your Workiz boards to avoid orphaned jobs.

Service

Titan What teams automate (API or inbox parsing)

• Qualified calls → Customer + Location + Job with priority and campaign tags.

• After-hours capture → unscheduled Job for next-day dispatch with “after-hours” and trade tags.

• High-value intents (replacement, multi‑unit) → immediate live transfer with transcript snippet to sales/CSR.

Data mapping (minimal)

• Required: name, phone, location address, problem code/description.

• Optional: business unit, campaign, priority, membership flag, quoted window.

Setup path

• Use ServiceTitan’s integration method available to your account (API access or sanctioned inbox parsing). Keep ServiceTitan as the scheduling source of truth; configure the AI to hold windows and commit only on confirmation.

Governance

• Do not write payment data through the AI channel. Limit stored PII to dispatch-critical fields. For regulated use cases, review security posture on Features and your internal policies before enabling automations.

Proven patterns that reduce leakage

• After-hours ring fence: any call that cannot be booked instantly becomes a lead + unscheduled job with urgency tag and morning reminder to dispatch.

• Two-step scheduling: AI proposes times; final confirmation writes to the FSM to prevent double-booking.

• No‑show prevention: 24h/3h SMS reminders with self-serve reschedule link.

• Escalation lanes: keywords like “gas leak,” “flood,” “no heat” route to live transfer or on‑call immediately.

Implementation checklist

• Define required fields per platform (keep it minimal).

• Standardize job types/categories across AI and your FSM.

• Expose only bookable windows the FSM can honor (include buffers/drive time).

• Test: create/update customer, create job/estimate, schedule visit, reschedule, cancel.

• Monitor: first‑call booking rate, after-hours capture, dispatch-ready rate, and no‑show rate. Iterate weekly for the first 30 days.

See all capabilities (“Works with”)

• Explore voice/SMS, booking, integrations, analytics, and security on Features. For hands-on setup, start with the five‑minute build tutorial and the CRM integration guide.