Verified AI assistant connections for plumbing contractors — emergency intake structure, service history recaps, internal standards retrieval, and on-call handovers — with unverified paths named.
4 verified-connection workflows11 verified connectionsReviewed 25 Aug 2026
Written for: Plumbing contractors, service coordinators, and on-call leads handling emergency and scheduled work.
Short answer
Plumbing contractors can use documentation-verified connections to mail, CRM, documents, chat, and calendars to structure intake, recap service history, retrieve internal standards, and produce on-call handovers. Job data does not always need a manual export: ServiceTitan, Housecall Pro, Jobber, Workiz, and Service Fusion publish official Zapier and API paths, FieldEdge is partner-gated, and commercial plumbing on BuildOps runs through a customer-built API integration.
Three workflows to start with
Step 1
Emergency intake
Mapping inbound requests onto your intake checklist and listing what the caller still has to be asked.
Step 2
Service history
Cited, chronological recaps of prior work with unresolved items and gaps stated explicitly.
Step 3
Customer explanation
Explaining estimate line items with every figure copied exactly, from text a person supplies.
Phone intake, published plumbing code, and dispatch decisions stay outside all of it.
What this guide covers
This guide covers documented connections between general-purpose AI assistants and the applications a plumbing contractor already uses, plus the vendor-documented automation and API paths published by residential field-service platforms and commercial plumbing service platforms. It does not claim a native ChatGPT, Claude, or Gemini connector for any plumbing product, and it never puts an assistant between a caller and a dispatch or safety decision.
How plumbing software connects
These are vendor-documented automation and API paths, separate from Connector Scout's native AI-platform connection records. Nothing here is a verified ChatGPT, Claude, or Gemini connector: an automation route runs through a third-party platform, an API route is an integration your business builds and controls, and a built-in vendor AI feature is neither. Plan requirements, approvals, and permissions come from each vendor's own documentation and can change.
Where AI actually helps
Plumbing operations are dominated by two moments: the emergency call, where information is captured badly under pressure, and the repeat visit, where information already captured is never read. Both are handled by retrieval and structuring over your existing mailbox, CRM, documents, and chat. What an assistant must not do is decide urgency, interpret code, or explain pricing it cannot see — and this guide keeps those out of scope explicitly. Where those workflows need job data, the software you already run usually publishes a documented Zapier or API path, so an export is the fallback rather than the default.
Emergency intake is inconsistent, so technicians arrive without knowing shutoff status.
Repeat visits start cold because prior findings are never surfaced.
Estimate line items are re-explained by hand, differently every time.
Internal standards and approved-product lists are unsearchable in the field.
On-call handover is a chat scroll, so promised callbacks get lost.
Open jobs and unpaid invoices age without anyone reading the report.
Commercial contracting work — recurring service, backflow, projects — runs on different software from residential service.
Plumbing software you can connect to AI
Service plumbing runs on field-service platforms with documented Zapier integrations and plan-gated APIs; commercial plumbing contracting runs on platforms whose route is a customer-built API integration. In both cases the assistant sits downstream of the system of record, working with the events and fields the vendor exposes. None of these products has a native ChatGPT, Claude, or Gemini connector.
Why an automation path is two hops
An automation route is always two hops: the vendor's Zapier integration moves supported data into Zapier, and a separate Zapier integration for a model provider runs the LLM step. The software vendor does not certify ChatGPT, Claude, or Gemini — the bridge is Zapier's.
Major plumbing platforms with documented integration paths, covering residential service and commercial contracting. Not a ranked market-share list.
Software
Best fit
AI connection path
What you can do
Access / caveat
ServiceTitanServiceTitan states that more than 100,000 contractors and service professionals trust the platform.
Established and multi-location residential and light-commercial plumbing contractors.
Third-party automation (separate verification)API/custom implementation (technical review)Official ServiceTitan–Zapier integration (open beta) that can pass ServiceTitan data to third-party applications and perform documented write actions, plus customer-built apps on the ServiceTitan API.
Draft the follow-up after an emergency call is closed — a written recap of what was done and what was recommended, never a live triage decision.
Summarize service history on a property before a repeat visit, from the job data the trigger supplies.
Chase estimates that have not converted with a draft built from the estimate record.
Flag job and invoice exceptions, and write results back through documented Zapier actions such as creating a task, job note, or attachment.
The Zapier integration is in open beta and provided as is; it requires a Client ID and Secret and the Works or a legacy package per current documentation.
Customer-built apps require Works or Enterprise Plus.
ServiceTitan prohibits tunnelled apps where a third party holds the customer's app key — keep custom integrations customer-owned or certified.
Housecall ProHousecall Pro states it serves more than 200,000 service pros across 50+ industries.
Small and midsize residential plumbing service teams.
Third-party automation (separate verification)API/custom implementation (technical review)Official Zapier integration, plus a public API and webhooks available on the MAX plan.
Structure new and scheduled job intake into your dispatch checklist format, leaving priority to the dispatcher.
Summarize a completed repair from the supported job event for the customer record.
Draft the follow-up where a technician recommended additional work, reviewed before sending.
React to selected webhook events in an AI workflow you build and host yourself.
The public API and webhooks are MAX-only.
The Zapier connection authenticates with a Housecall Pro API key.
Only the documented fields and actions are available — it is not a full mirror of your account.
JobberThe Jobber Developer Center states the platform serves more than 350,000 home service pros.
Small and growing plumbing contractors.
Third-party automation (separate verification)API/custom implementation (technical review)Official Zapier integration, plus a GraphQL API with OAuth for approved custom integrations.
Classify inbound work requests — leak, blockage, fixture replacement, no water — so the coordinator triages a structured request rather than raw text.
Draft quote and invoice follow-up from the documented quote and invoice triggers.
Produce a job-close summary when a job or visit closes, using only technician-authored detail.
Query or mutate only the objects your granted OAuth scopes cover in a custom integration.
Zapier is currently listed on the Connect and Grow plans.
Custom integrations use OAuth 2.0 with Jobber scopes.
An app connecting to more than five paying accounts requires Jobber approval.
WorkizWorkiz states it serves more than 120,000 home-service pros.
Call-heavy residential service plumbing teams.
Third-party automation (separate verification)API/custom implementation (technical review)Official Zapier integration that authenticates with Workiz Developer API credentials, plus a REST API.
Use the documented triggers — new invoice, job status updated, new job, new customer, new estimate — for service summaries and exception triage.
Draft follow-up on unconverted estimates from the estimate data the trigger supplies.
Read Open API resources including customers, jobs, estimates, invoices, techs, and availability into a workflow you build.
Zapier and the Open API both require Service Fusion Pro per current documentation.
Only the documented triggers and resources are available; nothing else is exposed.
FieldEdgeIncluded because its route is partner-gated rather than self-serve, which changes the planning work.
Established multi-truck HVAC, plumbing, and electrical contractors.
API/custom implementation (technical review)Partner-gated FieldEdge API and Marketplace integration path. There is no documented self-serve, no-code connection.
Pass selected service-history and operational data into an LLM step inside an approved partner or customer implementation.
Scope the data set with FieldEdge rather than from public documentation, because endpoint detail is gated.
The public developer portal states it provides API access to integrated partners.
Partner authentication documentation describes partner apps installed through the FieldEdge Marketplace using OAuth/JWT with sandbox testing.
Confirm partner or API entitlement with FieldEdge before scoping an AI workflow.
BuildOpsIncluded because its plumbing page documents commercial workflows — emergency service, recurring maintenance and backflow tracking, projects and job financials — that residential platforms do not model.
Commercial plumbing contractors running emergency service, recurring maintenance, and project work in one system.
API/custom implementation (technical review)Customer-built integration on the BuildOps public API, which supports REST endpoints and webhook callbacks. The developer center states public API access is invite-required through your implementation manager or customer success manager.
Turn selected service and project events into internal handoff summaries between the call desk, the field, and project management.
Build a pre-visit recap from service history your integration already reads.
Summarize recurring service, backflow, or inspection records into reminder and exception lists where those records are available through your implemented API or reporting path.
Produce variance or exception notes from job and project financial events your access covers.
Public API access is invite-required; request it through your BuildOps implementation or customer success contact.
Expect engineering work for authentication, permission scoping, and monitoring; do not assume every field is exposed.
OpsAI is built into BuildOps. It is a vendor AI feature, not an external ChatGPT, Claude, or Gemini connector.
Backflow and inspection compliance decisions stay with a licensed person — an LLM may summarize records, never certify them.
Major plumbing platforms with documented integration paths, covering residential service and commercial contracting. Not a ranked market-share list.
ServiceTitan
ServiceTitan states that more than 100,000 contractors and service professionals trust the platform.
Established and multi-location residential and light-commercial plumbing contractors.
AI connection path
Official ServiceTitan–Zapier integration (open beta) that can pass ServiceTitan data to third-party applications and perform documented write actions, plus customer-built apps on the ServiceTitan API.
What you can do
Draft the follow-up after an emergency call is closed — a written recap of what was done and what was recommended, never a live triage decision.
Summarize service history on a property before a repeat visit, from the job data the trigger supplies.
Chase estimates that have not converted with a draft built from the estimate record.
Flag job and invoice exceptions, and write results back through documented Zapier actions such as creating a task, job note, or attachment.
Access / caveat
The Zapier integration is in open beta and provided as is; it requires a Client ID and Secret and the Works or a legacy package per current documentation.
Customer-built apps require Works or Enterprise Plus.
ServiceTitan prohibits tunnelled apps where a third party holds the customer's app key — keep custom integrations customer-owned or certified.
Included because its plumbing page documents commercial workflows — emergency service, recurring maintenance and backflow tracking, projects and job financials — that residential platforms do not model.
API/custom implementation (technical review)
Best fit
Commercial plumbing contractors running emergency service, recurring maintenance, and project work in one system.
AI connection path
Customer-built integration on the BuildOps public API, which supports REST endpoints and webhook callbacks. The developer center states public API access is invite-required through your implementation manager or customer success manager.
What you can do
Turn selected service and project events into internal handoff summaries between the call desk, the field, and project management.
Build a pre-visit recap from service history your integration already reads.
Summarize recurring service, backflow, or inspection records into reminder and exception lists where those records are available through your implemented API or reporting path.
Produce variance or exception notes from job and project financial events your access covers.
Access / caveat
Public API access is invite-required; request it through your BuildOps implementation or customer success contact.
Expect engineering work for authentication, permission scoping, and monitoring; do not assume every field is exposed.
OpsAI is built into BuildOps. It is a vendor AI feature, not an external ChatGPT, Claude, or Gemini connector.
Backflow and inspection compliance decisions stay with a licensed person — an LLM may summarize records, never certify them.
Residential service: your platform's official Zapier integration is the fastest route, and it carries only documented triggers and actions.
Commercial plumbing: plan a customer-built API integration with an invite or approval step, and treat it as an engineering project.
Never route an emergency call through an automated decision. Structure and summarize; a dispatcher decides priority and safety response.
Already running a system? Start with its supported path rather than changing field-service software for AI.
Manual export remains the guaranteed fallback for aging, backlog, and accounting analysis.
Workflow categories
The operational areas where a documented connection or a manual path can carry real work.
Emergency intake
Mapping inbound requests onto your intake checklist and listing what the caller still has to be asked.
Service history
Cited, chronological recaps of prior work with unresolved items and gaps stated explicitly.
Customer explanation
Explaining estimate line items with every figure copied exactly, from text a person supplies.
Internal standards
Cited answers from your own standards folder, escalating code questions to the licensed lead.
Shift coordination
Handover briefs built from operational channels and calendars, traceable to the original messages.
Backlog review
Grouping exported aging data against thresholds you set, with no financial interpretation.
Opportunity matrix
What each workflow needs, what the assistant can safely contribute, and what stays a human decision.
Workflow
Inputs it needs
What AI can safely contribute
What a human must decide
Connection path
Emergency intake structuring
Shared service mailbox, intake checklist
Maps the request onto your checklist and lists gaps
Confirms shutoff and hazards, then dispatches
Verified connection
Service history recap
CRM records, prior job summaries
Cited chronology plus unresolved items
Verifies conditions on site
Verified connection
Estimate explanation
Line items supplied by a person
Per-line explanation, figures unchanged
Estimator approves the wording
Human-reviewed copy/paste
Internal standards lookup
Connected standards folder
Cited answer or explicit escalation
Licensed plumber owns code interpretation
Verified connection
On-call handover
Operational channel, dispatch calendar
Open items and promises with message references
Outgoing lead confirms the brief
Verified connection
Aging and backlog review
Exported aging report
Threshold grouping only
Office manager verifies before contact
Manual export/import
Emergency intake structuring
Inputs it needs
Shared service mailbox, intake checklist
What AI can safely contribute
Maps the request onto your checklist and lists gaps
What a human must decide
Confirms shutoff and hazards, then dispatches
Verified connection
Service history recap
Inputs it needs
CRM records, prior job summaries
What AI can safely contribute
Cited chronology plus unresolved items
What a human must decide
Verifies conditions on site
Verified connection
Estimate explanation
Inputs it needs
Line items supplied by a person
What AI can safely contribute
Per-line explanation, figures unchanged
What a human must decide
Estimator approves the wording
Human-reviewed copy/paste
Internal standards lookup
Inputs it needs
Connected standards folder
What AI can safely contribute
Cited answer or explicit escalation
What a human must decide
Licensed plumber owns code interpretation
Verified connection
On-call handover
Inputs it needs
Operational channel, dispatch calendar
What AI can safely contribute
Open items and promises with message references
What a human must decide
Outgoing lead confirms the brief
Verified connection
Aging and backlog review
Inputs it needs
Exported aging report
What AI can safely contribute
Threshold grouping only
What a human must decide
Office manager verifies before contact
Manual export/import
Verified connection
A published, documentation-verified connection record exists between the AI platform and the application, and the page links to it.
Human-reviewed copy/paste
A person copies the source text into the assistant and reviews the output before it is used. No connector is claimed.
Manual export/import
A person exports a file or report from the source system and supplies it to the assistant. No connector is claimed.
Documented workflows
Every workflow states its connection path. A verified connection links to the record it relies on; every other path names the manual step instead of implying a connector.
Workflow 01
Summarize an emergency intake into a consistent handover
Verified connection
Emergency intake is taken under pressure. Details are captured inconsistently, and the technician arrives without knowing whether the water was shut off.
Email intake is read through a published, documentation-verified mail connection. Phone and SMS intake is not covered by any verified connection in this dataset and must be typed in.
The inbound request in the connected mailbox, or intake notes supplied by a person
Your intake checklist
Data the assistant reads
Messages in the mailbox the connection is scoped to, or pasted intake notes
Steps
1.Write the intake checklist first: shutoff status, water source, access, occupancy, hazards.
2.Ask the assistant to map each request onto that checklist.
3.Require missing items to be listed as questions for the caller, never assumed.
4.The dispatcher completes the missing items before dispatch.
5.Store the completed handover with the job record.
Prompt template
Read this service request and map it onto my intake checklist: [paste checklist]. Fill each item only from what the message actually says. List every unanswered item under 'ask the customer'. Do not judge severity beyond what is written and do not suggest a repair.
Expected output
A checklist-structured handover with an explicit list of unanswered questions.
Human review required
A dispatcher confirms shutoff status and hazards with the customer before a technician is sent.
Limitations
Calls, SMS, and voicemail are not reachable through any verified connection here.
The assistant cannot assess flooding risk or structural hazard.
Response prioritization stays with the dispatcher.
Sensitive data
Emergency intake includes occupancy and access details. Keep the mail connection scoped to the shared service inbox.
Workflow 02
Recap service history before a repeat visit
Verified connection
Repeat visits start cold. The technician rediscovers what the last two visits already established, and the customer notices.
CRM and document retrieval run through published, documentation-verified connections. If your history lives only in field-service software, this becomes a manual export.
Prior job summaries in the connected document folder
Data the assistant reads
CRM records the connection is scoped to
Prior job summaries in connected folders
Steps
1.Confirm which system is the record of truth for service history.
2.Ask for a chronological recap of prior interactions for the property.
3.Require each item to cite the record or file it came from.
4.Ask what the history does not show — unresolved items are the point.
5.The technician reads the recap before travelling and confirms on site.
Prompt template
Summarize the service history for [customer/property] using the connected CRM and document folder. Give a dated chronological list, each item citing its source record or file name. End with 'open or unresolved from the history' and 'not recorded anywhere I can see'. Do not infer what was likely done.
Expected output
A cited, chronological history plus explicit gaps and unresolved items.
Human review required
The technician verifies on site. History informs the visit; it does not replace inspection.
Limitations
Coverage is limited to what your team recorded.
Parts and warranty data in supplier systems is not visible.
Duplicate records fragment history — deduplicate before relying on this.
Sensitive data
Service history combines property, access, and payment details. Scope the CRM connection to the service pipeline.
Workflow 03
Explain estimate line items without changing the numbers
Human-reviewed copy/paste
Customers challenge estimates they do not understand, and the office rewrites the same explanations repeatedly.
Estimates typically live in job-management software that no verified connection in this dataset reaches. A person supplies the line items and reviews the draft.
Inputs
The estimate line items, supplied by a person
Your approved explanations for common line items
Data the assistant reads
Only the text a person supplies
Steps
1.Maintain a short internal library of approved line-item explanations.
2.Paste the estimate and the library into the assistant.
3.Ask for a customer-facing explanation with every figure copied exactly.
4.Reject any output that adds, removes, or recalculates a line.
5.The estimator approves before it goes out.
Prompt template
Explain these estimate line items to a customer: [paste line items]. Copy every figure exactly as given. Use the approved explanations below where they apply: [paste library]. Do not total, discount, compare to market rates, or suggest alternatives.
Expected output
A per-line explanation with unchanged figures.
Human review required
The estimator confirms the explanation matches the scope actually quoted.
Limitations
The assistant cannot access the estimate system, so figures depend on accurate pasting.
It must not be used to justify pricing it cannot see the basis for.
Regulatory or code-driven cost items need a licensed explanation.
Sensitive data
Avoid pasting internal cost or margin columns; supply only the customer-facing lines.
Workflow 04
Find the internal standard that governs a job
Verified connection
Internal standards, approved fixture lists, and supplier terms are written down but effectively unsearchable in the field.
Retrieval runs through a published, documentation-verified document connection. Published plumbing codes are not part of this dataset and must be consulted at source.
Internal standards and approved-product documents in a connected folder or site
Data the assistant reads
Files in the connected standards folder
Steps
1.Keep one authoritative folder for current internal standards.
2.Ask questions that demand a citation and a quote.
3.Treat 'not documented' as a valid and useful answer.
4.Escalate any code question to the licensed plumber or the published code itself.
5.Review the folder after every standards change.
Prompt template
Using only the connected internal-standards folder, answer: [question]. Name the file, quote the governing sentence, and give the document date. If the folder does not cover it, reply 'not documented internally — check the published code or ask the licensed lead'.
Expected output
A cited internal answer or an explicit escalation.
Human review required
A licensed plumber owns any code, permit, or safety interpretation.
Limitations
Jurisdictional plumbing code is not included and changes locally.
This is not a substitute for licensed judgement or inspection.
Outdated files in the folder produce outdated answers.
Sensitive data
Standards folders often include supplier pricing agreements. Scope narrowly.
Workflow 05
Produce the on-call handover brief
Verified connection
The on-call handover is a chat message someone scrolls back to find. Open jobs and promised callbacks get lost between shifts.
Channel history and calendar retrieval run through published, documentation-verified connections, limited to the channels and calendars each connection is scoped to.
The shift's coordination channel in the connected workspace
Tomorrow's entries in the connected calendar
Data the assistant reads
Message history in the channels the connection is scoped to
Entries in the connected calendar
Steps
1.Use one channel for operational coordination so history is meaningful.
2.Ask for open items, promised callbacks, and unresolved escalations from the shift.
3.Require each item to reference the message it came from.
4.Add tomorrow's scheduled commitments from the calendar.
5.The outgoing lead confirms the brief before handover.
Prompt template
Summarize the last 12 hours in this channel as an on-call handover: open jobs, promised callbacks with the promise as stated, and unresolved escalations. Reference the message behind each item. Then list tomorrow's calendar commitments. Do not resolve anything or infer status that was not stated.
Expected output
A handover brief of open items, promises, and escalations, each traceable to a message.
Human review required
The outgoing shift lead confirms and corrects the brief; it is not published unreviewed.
Limitations
Only channels within the connection's scope are visible.
Coordination that happened by phone or in person is invisible.
Chat is not a job record; the brief supplements the system of record.
Sensitive data
Operational channels contain customer details and sometimes complaints. Scope the connection to operational channels, not HR or leadership channels.
Workflow 06
Review an aging or backlog report from an export
Manual export/import
Unfinished jobs and unpaid invoices age quietly. The report exists but nobody reads it in a form that prompts action.
No AI platform has a native connection to plumbing job-management or accounting software. Job-management platforms listed on this page publish official Zapier integrations and plan-gated APIs that can supply this data automatically; accounting systems remain export-only here, and a person produces that export.
Inputs
An aging or open-jobs export from your job-management or accounting system
Your escalation thresholds
Data the assistant reads
Only the exported file a person supplies
Steps
1.Export the report with a consistent column set each cycle.
2.Define the thresholds that make an item actionable.
3.Ask for a grouped list against those thresholds, with no financial interpretation.
4.Ask what the export cannot show.
5.The office manager verifies before any customer contact.
Prompt template
Group this aging export by my thresholds: [paste thresholds]. For each group, list the records and the single field that triggered the grouping. Do not calculate collectability, do not rank customers, and do not draft collection messages.
Expected output
A threshold-grouped action list drawn strictly from the export.
Human review required
The office manager verifies every record against the accounting system before contact.
Limitations
Exports lag reality; payments in flight will look overdue.
Collections messaging is regulated in many jurisdictions and is out of scope.
No verified connection reads accounting systems in this dataset.
Sensitive data
Aging reports are financial records. Remove bank or payment identifiers before uploading.
Verified connections used here
Availability, capability, plan and permission detail lives on each connection record and is never restated on this page.
Yes. Gmail is an official ChatGPT app that can search and read connected mail and draft reply content in the conversation. OpenAI does not document ChatGPT saving a draft inside Gmail or sending mail, so those remain unconfirmed here.
Yes, on a paid Anthropic plan. HubSpot documents a HubSpot connector for Claude that reads CRM context, creates and updates supported records such as contacts, companies, deals and tickets, logs activities, tasks and notes, and works from engagement history including emails, calls, meetings, tasks and notes. HubSpot documents no delete capability, caps bulk create or update at 10 records at a time, and recommends setting write tools to Needs Approval so every change is confirmed first.
Yes. ChatGPT has a Google Drive app that provides live access to permitted Drive content for search and reference, and — where the actions are available and enabled — can also create, update, move, share, upload, copy or delete Drive-family files. Individual connections do not build a personal synced index; eligible workspace administrators can separately configure administrator-managed Drive indexing.
Yes. Claude’s Slack connector searches channels, direct messages and shared files for context, and Anthropic’s current interactive-connectors documentation lists Slack as able to draft and send messages, with the user confirming the action. Both are distinct from the Claude app installed inside Slack.
Yes. Google Calendar is an official ChatGPT app that brings connected calendar context into conversations and deep research, and — where write actions are enabled by an administrator — can set up meetings and create events. Updating and deleting existing events is not documented here.
Yes. Claude accesses SharePoint through its Microsoft 365 connector. It can search and read SharePoint content the user can access; optional write tools can create and update files after Microsoft Entra admin consent.
Yes. Claude’s Gmail connector can search and read email, draft messages with formatting and context, and send, reply to and forward email from Gmail. Anthropic’s current documentation states Claude asks for your approval before each of those send actions by default.
Yes. Claude can search Drive, read several file types, upload files, create folders, inspect permissions and recent changes, save generated files to Drive when file creation is enabled, and share, move or trash files with approval.
Yes. HubSpot documents a HubSpot connector for ChatGPT that reads CRM context, creates and updates records such as contacts, companies, deals and tickets, and logs engagements including emails, calls, meetings, tasks and notes. HubSpot documents no delete capability for any object, and bulk create or update is capped at 10 records at a time.
Yes. The ChatGPT Slack app can search and answer questions across Slack messages, threads, channels and direct messages. Where available and enabled by a workspace administrator, it can also perform supported Slack actions.
Implementation path
A staged rollout, from a single low-risk workflow to a documented operating routine.
Setup difficulty: moderateModerate. Mail and document retrieval are quick; useful service-history recaps depend on record deduplication that takes real effort first. A residential Zapier path is a configuration task once the required plan and credentials are available; a BuildOps or FieldEdge integration needs engineering time and vendor approval.
Stage 1
Stage 1 — Standardize intake
Write the intake checklist before connecting anything; the checklist is what makes the output useful.
Define shutoff status, water source, access, occupancy, and hazards as required fields.
Scope the mail connection to the shared service inbox.
Run structured intake for two weeks and measure how often fields are missing.
Stage 2
Stage 2 — Make history readable
Service history only helps if one system is the record of truth and records are deduplicated.
Pick the record of truth and deduplicate customer and property records.
Enable cited history recaps before repeat visits.
Feed unresolved items back into the job record rather than leaving them in chat.
Stage 3
Stage 3 — Coordinate shifts and backlog
Add channel-based handovers and exported backlog review once the first two stages are habitual.
Consolidate operational coordination into one channel and scope the connection there.
Produce the on-call brief at every handover.
Set aging thresholds and review the grouped export on a fixed cycle.
Limitations and boundaries
What this cannot do
Phone, SMS, and voicemail intake is not reachable by any verified connection in this dataset.
Job-management platforms are reached through vendor Zapier or API paths, or through an export — never through a native AI connector.
Accounting systems are not covered by any verified connection here.
Published plumbing code is jurisdictional and is not part of this dataset.
Backflow, gas, sewer, contamination, and code compliance decisions require a licensed person, never an assistant.
Collections messaging is regulated and is out of scope for these workflows.
Security and privacy considerations
Scope every connection to the shared operational mailbox, folder, calendar, or channel — never to a personal account or an entire drive.
Customer records held by a home-services business are personal data. Confirm how your AI provider handles the content you send before connecting anything customer-facing.
Keep one named owner for each connection, and review who is connected when staff change roles or leave.
Assume any prompt containing a customer address, access code, or payment detail is a disclosure event. Remove identifiers you do not need.
Documented workflows beat ad-hoc use: write down what may be connected, what may be pasted, and who reviews output before it reaches a customer.
Data the assistant reads
Shared service mailboxes
CRM customer and property records
Internal standards and approved-product documents
Operational chat channels and dispatch calendars
Human review that stays mandatory
Dispatchers own urgency, licensed plumbers own code and safety interpretation, and estimators own pricing explanations.
Frequently asked questions
Primary sources
Every connection claim on this page resolves to a published record backed by official vendor documentation.