A plumbing AI receptionist should not paste a paragraph into a generic inbox and call that an integration. It should send a structured record into the system the team already checks, preserve what the caller actually reported, and assign one approved next action to one accountable role.
Send the caller, address, issue, current condition, requested timing, promise state, call type, next action, and owner as separate fields. Then create or update the approved CRM record and notify the person responsible for review. The handoff can automate delivery; it should not quietly invent a technician, route, price, or arrival promise.
| Summary field | CRM or dispatch destination | Control rule |
|---|---|---|
| Caller and callback number | Contact or customer identity | Search for an existing record before creating a duplicate. |
| Service address and access facts | Service location | Keep the service location separate from a billing or caller address. |
| Issue and current condition | Lead, request, or job description | Preserve the caller's facts; do not replace them with an unsupported diagnosis. |
| Call type | Repair, estimate, after-hours review, or routine follow-up | Use the plumbing company's own categories and required fields. |
| Promise state | Customer notes or commitment field | Record whether price, technician, route, or arrival time was—and was not—promised. |
| Next action and owner | Task, queue, or notification | Assign a named role with an acknowledgment expectation and fallback owner. |
| Recording and transcript link | Source-record attachment or URL | Keep it available for ambiguity, complaint, and quality review. |
| Call state | Safe automated action | Decision that stays owned |
|---|---|---|
| Standard repair request | Create or update the approved service request and assign dispatcher review. | Technician fit, route timing, and customer commitment. |
| Estimate request | Create or update the lead and assign the estimator callback task. | Scope, pricing, and estimate appointment type. |
| Approved after-hours urgency cue | Send the summary to the named on-call review path and flag it visibly. | Emergency response, technician selection, and arrival promise. |
| Existing customer or open-job update | Attach the call to the matched record and notify its current owner. | Whether the existing work order, schedule, or commitment changes. |
| Uncertain match or incomplete intake | Place the summary in an exception queue. | Record merge, classification, and next action. |
The record type should follow the company's existing operating rule. A first-time caller requesting a repipe estimate may become a lead. A known customer reporting a new leak may need a service request attached to the customer record. A confirmed appointment may qualify for a job only after the company's required booking facts and availability rules are satisfied.
Do not create a dispatch-ready job merely because the caller wants service. If crew fit, territory, equipment, route capacity, price, or urgency still requires judgment, create the review task and preserve the call instead.
No silent failures. Match on callback number, service address, and a recent-call window before creating a new record. Keep a unique call ID so retries update the same handoff. If the CRM, webhook, or dispatch destination fails, retain the summary, retry delivery, alert the fallback owner, and show the exception until a human acknowledges it.
A workflow is not complete because an automation returned “success.” It is complete when the intended record exists, the correct owner can see it, and the next action is either acknowledged or visibly overdue.
ServiceVoice AI helps field-first plumbing companies capture structured call facts and route approved next actions while keeping dispatch, pricing, and customer commitments under accountable human ownership.