Verified AI assistant connections for HVAC contractors — maintenance agreement retention, equipment documentation, diagnostic explanation, and replacement quoting — with the unverified paths named.
4 verified-connection workflows9 verified connectionsReviewed 25 Aug 2026
Written for: HVAC contractors and service managers running maintenance agreements, service calls, and replacement installations.
Short answer
HVAC contractors can use documentation-verified connections to CRM, document libraries, calendars, and mail for renewal outreach, equipment documentation retrieval, quote comparison, and install coordination. Field-service data no longer has to be exported by hand everywhere: ServiceTitan, Housecall Pro, Jobber, Workiz, and Service Fusion publish official Zapier and API paths, while commercial mechanical platforms such as ServiceTrade and BuildOps document customer-built API integrations.
Three workflows to start with
Step 1
Retention and renewals
Building the renewal working list from CRM properties your team maintains, with drafts that name real plan inclusions.
Step 2
Equipment documentation
Cited retrieval from your own equipment library, with conflicts surfaced rather than resolved silently.
Step 3
Customer explanation
Translating confirmed technician findings into homeowner language without changing a single measurement.
None of them is a native ChatGPT, Claude, or Gemini connector, and diagnosis stays with a technician.
What this guide covers
This guide covers documented connections between general-purpose AI assistants and the applications an HVAC contractor already uses, plus the vendor-documented automation and API paths published by residential field-service platforms and commercial mechanical service platforms. It does not claim a native ChatGPT, Claude, or Gemini connector for any HVAC product, and vendor-built AI features are named as vendor features rather than as external model connections.
How HVAC 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
HVAC work generates two kinds of information problem. The first is documentation: equipment sheets, warranty registrations, and submittals that exist somewhere but cannot be found while a technician is standing in a mechanical room. The second is retention: maintenance agreements that lapse because nobody built the renewal list. Both are retrieval and drafting problems over systems you already own, which is exactly where a verified connection helps. Diagnosis is not, and this guide keeps that boundary explicit. The third problem is that job data lives in field-service software, and the honest answer there has changed: residential platforms publish official Zapier integrations and plan-gated APIs, and commercial mechanical platforms publish APIs behind a partner or invite process, so an export is now the fallback rather than the only option.
Maintenance agreements lapse because the renewal list is rebuilt by hand each season.
Equipment, warranty, and submittal documents are scattered across drives and sites.
Technicians write accurate findings that homeowners read as upselling.
Replacement options are presented as three prices with no comparable explanation.
Install days fail on permits, access, and equipment that nobody assembled into one brief.
Seasonal staffing and stocking decisions run on memory instead of last year's export.
Residential and commercial mechanical work run on different software, and the route to AI differs with them.
HVAC software you can connect to AI
HVAC contractors split into two software worlds. Residential and light-commercial service runs on field-service platforms with self-serve Zapier integrations and plan-gated APIs. Commercial mechanical service runs on platforms whose route to an LLM is a customer-built integration on a documented API, usually behind a partner or invite process. Neither world has a native ChatGPT, Claude, or Gemini connector; what each vendor documents is the automation or API surface below.
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 HVAC platforms with documented integration paths, covering both residential service and commercial mechanical work. 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 HVAC 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.
Build maintenance-agreement and renewal follow-up drafts from supported customer, membership, and job data instead of rebuilding the season's list by hand.
Classify supported lead and job events — new booking, job completed, membership expiring — before a coordinator sees them.
Draft a homeowner-readable summary from technician notes carried on a supported job event, with the technician approving the wording.
Chase quoted-not-sold replacement work with a follow-up draft built from the quote record.
Raise invoice and job exception alerts, 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.
FieldEdgeIncluded because its route is partner-gated rather than self-serve, which changes how an HVAC contractor should plan the work.
Established multi-truck residential and light-commercial HVAC 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 operational and service-history data into an LLM step inside an approved partner or customer implementation — pre-visit recaps and agreement-status summaries are the usual first candidates.
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.
Housecall ProHousecall Pro states it serves more than 200,000 service pros across 50+ industries.
Small and midsize residential HVAC service and maintenance 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.
Turn new and scheduled job intake into a structured summary for the dispatcher before the truck rolls.
Summarize a completed maintenance visit from the supported job event so the office can act on it the same day.
Draft the follow-up on a tune-up that surfaced recommended work, with a person approving before it is sent.
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 residential HVAC 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 by system type and urgency before a coordinator triages them.
Draft maintenance and quote follow-up from the documented quote created, quote approved, and invoice created triggers.
Produce a job-close summary when a job or visit closes, ready for the customer record.
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.
Growing, call-heavy residential HVAC service 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 — to produce service summaries and exception triage.
Draft follow-up on estimates that have not converted, from 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.
ServiceTradeIncluded because it closes the commercial gap: ServiceTrade publishes an industry page specifically for mechanical and commercial HVAC contractors.
Commercial HVAC and mechanical service contractors running planned maintenance, deficiencies, and service agreements.
API/custom implementation (technical review)Customer-controlled integration built through the ServiceTrade developer program. Its developer page describes a Partner App review that issues an official Partner App Key once approved; Connector Scout has not verified an official Zapier integration.
Assemble a pre-visit summary from selected customer, location, asset, and service-call history that your integration already reads.
Draft an internal or customer-facing recap from completed service and deficiency notes a technician wrote.
Summarize agreement, backlog, or reporting data into renewal and exception lists, using only the API resources you have implemented.
This is engineering work: the developer program routes integrations through Partner App review and access approval.
The current pricing page lists API access for custom integrations in its higher tier — confirm your account's entitlement with ServiceTrade.
ServiceTrade also ships its own ServiceTrade AI features. Those are vendor features inside the product, not a connection to ChatGPT, Claude, or Gemini.
BuildOpsIncluded because its HVAC page positions it for commercial mechanical work and its developer center documents webhook-driven integration.
Commercial HVAC and mechanical contractors running service, projects, and job financials in one system.
API/custom implementation (technical review)Customer-built integration on the BuildOps public API, which supports REST endpoints and webhook callbacks for real-time and near-real-time workflows. The developer center states public API access is invite-required through your implementation manager or customer success manager.
Turn selected service, job, or project webhooks into internal summaries or exception alerts for a dispatcher or project manager.
Build a pre-visit recap from the asset and service history your integration reads.
Summarize project or financial reporting data into variance and exception notes where your API access covers those fields.
Public API access is invite-required; request it through your BuildOps implementation or customer success contact.
Expect engineering work for authentication, permission scoping, retry handling, and monitoring — and do not assume every BuildOps field is exposed.
BuildOps ships OpsAI inside the product. That is a vendor AI feature, not an external ChatGPT, Claude, or Gemini connector.
Major HVAC platforms with documented integration paths, covering both residential service and commercial mechanical work. 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 HVAC 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
Build maintenance-agreement and renewal follow-up drafts from supported customer, membership, and job data instead of rebuilding the season's list by hand.
Classify supported lead and job events — new booking, job completed, membership expiring — before a coordinator sees them.
Draft a homeowner-readable summary from technician notes carried on a supported job event, with the technician approving the wording.
Chase quoted-not-sold replacement work with a follow-up draft built from the quote record.
Raise invoice and job exception alerts, 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 route is partner-gated rather than self-serve, which changes how an HVAC contractor should plan the work.
API/custom implementation (technical review)
Best fit
Established multi-truck residential and light-commercial HVAC contractors.
AI connection path
Partner-gated FieldEdge API and Marketplace integration path. There is no documented self-serve, no-code connection.
What you can do
Pass selected operational and service-history data into an LLM step inside an approved partner or customer implementation — pre-visit recaps and agreement-status summaries are the usual first candidates.
Scope the data set with FieldEdge rather than from public documentation, because endpoint detail is gated.
Access / caveat
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.
Growing HVAC service contractors consolidating scheduling, jobs, and invoicing.
AI connection path
Official Zapier integration plus an Open API.
What you can do
Use the documented triggers — new invoice, job status updated, new job, new customer, new estimate — to produce service summaries and exception triage.
Draft follow-up on estimates that have not converted, from estimate data the trigger supplies.
Read Open API resources including customers, jobs, estimates, invoices, techs, and availability into a workflow you build.
Access / caveat
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.
Included because it closes the commercial gap: ServiceTrade publishes an industry page specifically for mechanical and commercial HVAC contractors.
API/custom implementation (technical review)
Best fit
Commercial HVAC and mechanical service contractors running planned maintenance, deficiencies, and service agreements.
AI connection path
Customer-controlled integration built through the ServiceTrade developer program. Its developer page describes a Partner App review that issues an official Partner App Key once approved; Connector Scout has not verified an official Zapier integration.
What you can do
Assemble a pre-visit summary from selected customer, location, asset, and service-call history that your integration already reads.
Draft an internal or customer-facing recap from completed service and deficiency notes a technician wrote.
Summarize agreement, backlog, or reporting data into renewal and exception lists, using only the API resources you have implemented.
Access / caveat
This is engineering work: the developer program routes integrations through Partner App review and access approval.
The current pricing page lists API access for custom integrations in its higher tier — confirm your account's entitlement with ServiceTrade.
ServiceTrade also ships its own ServiceTrade AI features. Those are vendor features inside the product, not a connection to ChatGPT, Claude, or Gemini.
Included because its HVAC page positions it for commercial mechanical work and its developer center documents webhook-driven integration.
API/custom implementation (technical review)
Best fit
Commercial HVAC and mechanical contractors running service, projects, and job financials in one system.
AI connection path
Customer-built integration on the BuildOps public API, which supports REST endpoints and webhook callbacks for real-time and near-real-time workflows. 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, job, or project webhooks into internal summaries or exception alerts for a dispatcher or project manager.
Build a pre-visit recap from the asset and service history your integration reads.
Summarize project or financial reporting data into variance and exception notes where your API access covers those fields.
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, retry handling, and monitoring — and do not assume every BuildOps field is exposed.
BuildOps ships OpsAI inside the product. That is a vendor AI feature, not an external ChatGPT, Claude, or Gemini connector.
Residential service: start with your existing platform's Zapier integration. It is the fastest no-code route, and it carries only the triggers and actions the vendor documents.
Commercial mechanical: expect a customer-built API integration with a partner or invite step, and budget engineering time rather than a no-code setup.
Already running a system? Keep it. Switching field-service software to reach AI costs more than the workflow is worth.
Vendor AI features such as ServiceTrade AI or BuildOps OpsAI can be genuinely useful, but they are separate from connecting your data to an external assistant.
Manual export stays the guaranteed fallback for seasonal reporting and analysis when neither automation nor API access is available on your plan.
Workflow categories
The operational areas where a documented connection or a manual path can carry real work.
Retention and renewals
Building the renewal working list from CRM properties your team maintains, with drafts that name real plan inclusions.
Equipment documentation
Cited retrieval from your own equipment library, with conflicts surfaced rather than resolved silently.
Customer explanation
Translating confirmed technician findings into homeowner language without changing a single measurement.
Quoting support
Comparing quoted options strictly from quote documents — no savings maths, no payback claims.
Install coordination
Assembling schedule, scope, and open items into one brief; permits and inspections stay manual.
Seasonal reporting
Descriptive summaries of exported job data with your own category definitions.
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
Maintenance renewals
CRM records with tier and renewal date
Builds the list and drafts tier-specific outreach
Approves pricing and sends
Verified connection
Equipment documentation lookup
Connected equipment library
Cited answers, conflicts flagged
Confirms warranty with the manufacturer
Verified connection
Diagnostic explanation
Technician finding supplied by a person
Plain-language rewrite, measurements unchanged
Technician approves; safety findings escalate
Human-reviewed copy/paste
Replacement options comparison
Quote documents in a connected folder
Side-by-side table of quoted facts
Verifies every cell before delivery
Verified connection
Install coordination brief
Calendar entry, signed scope, checklist
Assembles the brief and lists open items
Confirms permits, stock, and access
Verified connection
Seasonal demand summary
Exported completed-jobs report
Counts and directional change only
Interprets and decides staffing
Manual export/import
Maintenance renewals
Inputs it needs
CRM records with tier and renewal date
What AI can safely contribute
Builds the list and drafts tier-specific outreach
What a human must decide
Approves pricing and sends
Verified connection
Equipment documentation lookup
Inputs it needs
Connected equipment library
What AI can safely contribute
Cited answers, conflicts flagged
What a human must decide
Confirms warranty with the manufacturer
Verified connection
Diagnostic explanation
Inputs it needs
Technician finding supplied by a person
What AI can safely contribute
Plain-language rewrite, measurements unchanged
What a human must decide
Technician approves; safety findings escalate
Human-reviewed copy/paste
Replacement options comparison
Inputs it needs
Quote documents in a connected folder
What AI can safely contribute
Side-by-side table of quoted facts
What a human must decide
Verifies every cell before delivery
Verified connection
Install coordination brief
Inputs it needs
Calendar entry, signed scope, checklist
What AI can safely contribute
Assembles the brief and lists open items
What a human must decide
Confirms permits, stock, and access
Verified connection
Seasonal demand summary
Inputs it needs
Exported completed-jobs report
What AI can safely contribute
Counts and directional change only
What a human must decide
Interprets and decides staffing
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
Work the maintenance-agreement renewal list
Verified connection
Maintenance agreements lapse quietly. The renewal list is rebuilt every season and the outreach is generic, so retention depends on whoever remembers.
CRM retrieval runs through a published, documentation-verified connection. Which properties and pipelines are visible is a plan and permission question answered on the connection record.
Contact and deal records for agreement holders in the connected CRM
Your renewal window and the inclusions of each plan tier
Data the assistant reads
CRM contact and deal properties the connection is scoped to
Renewal dates and plan tiers as recorded by your team
Steps
1.Record the plan tier and renewal date as CRM properties so the list can be built at all.
2.Ask the assistant for agreement holders inside your renewal window.
3.Ask for a draft per contact that names the tier's actual inclusions.
4.Never let the draft state a renewal price that is not in the record.
5.A person reviews, sends, and logs the outcome.
Prompt template
From the connected CRM, list agreement holders whose renewal date falls in the next [n] days. For each, draft a renewal email under 130 words that names their plan tier and its inclusions from this list: [paste inclusions]. If the record has no tier, mark it 'tier missing' and skip the draft. Never state a price unless it is present on the record.
Expected output
A renewal working list with per-contact drafts and explicit gaps where records are incomplete.
Human review required
Service management approves pricing and inclusions. Every message is sent by a person.
Limitations
If plan tier and renewal date are not maintained in the CRM, the workflow cannot run.
Equipment age and service history stored only in field-service software are not visible.
The assistant cannot tell you which customers are worth retaining.
Sensitive data
Agreement records combine property details with billing history. Scope the connection to the service pipeline only.
Workflow 02
Retrieve equipment, warranty, and spec details from your own document library
Verified connection
Model numbers, warranty registrations, and installed-equipment sheets are scattered across drives and sites, so the office guesses or calls the manufacturer.
Document retrieval runs through a published, documentation-verified connection to the drive or site where these files already live.
Equipment sheets, warranty registrations, and submittals in a connected folder or site
Data the assistant reads
Files in the site or folder the connection is scoped to
Steps
1.Consolidate equipment documentation into one site or folder, one file per property where possible.
2.Adopt a naming convention that includes the property identifier.
3.Ask questions that force citation: file name plus the quoted line.
4.Treat manufacturer documentation stored outside the folder as out of scope.
5.Confirm warranty status with the manufacturer before making any commitment to a customer.
Prompt template
Using only the connected equipment documentation, answer: [question about a property's installed equipment]. Return the file name, the quoted line, and the document date. If more than one file disagrees, show both and say they conflict. If the answer is not in the folder, say 'not in the document library'.
Expected output
A cited answer with file name and quoted text, or an explicit conflict/not-found result.
Human review required
Warranty coverage and part compatibility are confirmed with the manufacturer or distributor before anything is promised.
Limitations
Documents can be outdated; retrieval does not know an installation changed.
Manufacturer portals and distributor catalogues are not reachable by any verified connection here.
Scanned images without extracted text may not be readable.
Sensitive data
Equipment libraries can include site plans and access details for commercial clients. Restrict the connected site accordingly.
Workflow 03
Explain a diagnostic finding in language the homeowner accepts
Human-reviewed copy/paste
Technicians write accurate findings in trade shorthand. Homeowners hear jargon, assume upselling, and decline work they need.
The finding is supplied by a person rather than read from a diagnostic tool. Connector Scout has not verified any connection between these AI platforms and HVAC diagnostic equipment or field-service apps.
Inputs
The technician's confirmed finding, supplied by a person
Your approved explanation glossary and disclosure policy
Data the assistant reads
Only the text a person supplies
Steps
1.Have the technician state the finding, the measurement, and the recommendation in one paragraph.
2.Paste it in with your glossary and the disclosures you are required to include.
3.Ask for a homeowner-facing explanation that keeps every number unchanged.
4.Reject any output that adds a cause the technician did not state.
5.The technician confirms the explanation before it is delivered.
Prompt template
Rewrite this technician finding for a homeowner with no HVAC knowledge: [paste finding]. Keep every measurement exactly as written. Explain what it means, why it matters, and what happens if it is deferred — but only using what the finding says. Do not add causes, do not estimate cost, and do not imply urgency the finding does not state. Include this disclosure verbatim: [paste disclosure].
Expected output
A plain-language explanation preserving the technician's measurements and conclusions.
Human review required
The technician who took the readings approves the wording. Safety findings such as combustion or gas issues follow your escalation procedure, not a draft.
Limitations
The assistant has no access to readings, photos, or equipment data.
It cannot diagnose, and any output that appears to diagnose should be discarded.
Combustion safety and refrigerant handling are regulated activities outside this workflow.
Sensitive data
Do not paste customer addresses or account numbers into an explanation draft; the property does not need to be identified.
Workflow 04
Draft a replacement options comparison from your own quote data
Verified connection
Replacement quotes are presented as three prices with no comparable explanation, so customers stall on the decision.
Quote documents are read from a published, documentation-verified document connection. Pricing itself is never generated — only restated from your files.
Your quoted options with scope and equipment, stored in a connected folder
The comparison criteria you want every option judged against
Data the assistant reads
Quote documents in the connected folder
Steps
1.Keep each quoted option in a single document with scope, equipment, and price.
2.Define the comparison criteria once — for example scope included, equipment specified, warranty terms as quoted.
3.Ask for a side-by-side table drawn strictly from the documents.
4.Require '[not stated in quote]' wherever a criterion is missing.
5.A salesperson or owner verifies every cell before the customer sees it.
Prompt template
Build a side-by-side comparison of the quoted options in these documents, using these criteria: [paste criteria]. Every cell must come from the document text. Where a document does not state something, write '[not stated in quote]'. Do not calculate savings, efficiency gains, or payback periods.
Expected output
A comparison table restricted to quoted facts, with gaps marked rather than filled.
Human review required
Pricing, equipment models, and warranty wording are verified against the signed quote before delivery.
Limitations
Efficiency, savings, and payback claims require manufacturer data and load calculations that are not in scope.
Rebate and incentive eligibility changes by jurisdiction and is not covered.
The assistant cannot judge which option suits the home.
Sensitive data
Quote folders hold pricing strategy. Scope the connection to the customer-facing quotes, not internal cost sheets.
Workflow 05
Prepare an installation-day coordination brief
Verified connection
Install days fail on logistics: the wrong equipment on the truck, no confirmed access, permits unaccounted for. The information exists but was never assembled in one place.
Calendar and document retrieval each run through published, documentation-verified connections. Permit submission and inspection booking remain manual.
The scheduled installation entry in the connected calendar
The signed scope and any permit or inspection checklist in a connected folder
Data the assistant reads
Calendar entries and documents in the connected scopes
Steps
1.Book installs on one calendar with a consistent entry format.
2.Store the signed scope and checklist where the document connection can reach them.
3.Ask for a brief combining schedule, scope, and outstanding checklist items.
4.Require unconfirmed items to be listed as open questions.
5.The install coordinator resolves every open item before the truck is loaded.
Prompt template
For the installation scheduled on [date], produce a coordination brief: scheduled time and crew from the calendar entry, equipment and scope exactly as written in the signed document, and checklist items that the documents do not show as complete. List anything unconfirmed under 'open before install'. Do not assume permit status.
Expected output
A one-page install brief with an explicit list of unresolved items.
Human review required
The install coordinator confirms permits, equipment availability, and access with the responsible parties.
Limitations
Permit and inspection systems are not reachable by any verified connection in this dataset.
Inventory and truck stock live in systems this workflow cannot read.
Local code requirements are not covered.
Sensitive data
Install briefs contain property access instructions. Share them with the assigned crew only.
Workflow 06
Summarize seasonal demand from exported service data
Manual export/import
Staffing and stocking decisions before peak season run on last year's memory rather than last year's data.
No AI platform has a native connection to HVAC field-service or job-costing software. Most residential platforms — ServiceTitan, Housecall Pro, Jobber, Workiz, Service Fusion — publish official Zapier integrations and plan-gated APIs that can remove the manual step, and commercial platforms such as ServiceTrade and BuildOps support customer-built API integrations. Where none of those is available on your plan, a person produces the export.
Inputs
An export of completed jobs by type and date from your field-service system
Your own definitions of job categories
Data the assistant reads
Only the exported files a person supplies
Steps
1.Export completed jobs for the comparable period in prior years with consistent columns.
2.Supply your category definitions so 'maintenance' means the same thing each year.
3.Ask for volume by category and month, with no interpretation beyond the data.
4.Ask explicitly what the export cannot answer.
5.Management combines the summary with capacity knowledge the data does not contain.
Prompt template
Here are completed-job exports for [periods]. Using only the columns present, report job counts by category and month and the change between periods. Use these category definitions: [paste]. Do not forecast, do not attribute changes to weather or marketing, and list any question the export cannot answer.
Expected output
A descriptive seasonal summary with an explicit list of questions the data cannot answer.
Human review required
Operations validates the counts against the source system before staffing or stocking decisions.
Limitations
Correlation with weather, pricing, or marketing is not established by a job export.
Historical categorisation drift makes year-over-year comparison unreliable unless definitions held constant.
No verified connection reads this data directly.
Sensitive data
Remove customer identifiers from the export before uploading if the analysis is purely volumetric.
Verified connections used here
Availability, capability, plan and permission detail lives on each connection record and is never restated on this page.
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. Microsoft SharePoint is an official ChatGPT app that gives live access to permitted SharePoint and OneDrive for work or school content for search and reference, and — where enabled and approved — can create folders, upload and update files, manage sharing links and work with supported lists and pages. Administrator-managed SharePoint sync is a separate feature for eligible Enterprise and Edu workspaces.
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. 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, 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. 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. 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. 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. Gemini accesses Calendar through the Google Workspace Connected App and can retrieve, create, and manage calendar events.
Implementation path
A staged rollout, from a single low-risk workflow to a documented operating routine.
Setup difficulty: moderateModerate. Document retrieval is quick to enable; renewal workflows depend on CRM properties that most contractors have to backfill. A residential Zapier path is a configuration task once the required plan and credentials are available; a ServiceTrade or BuildOps API integration is engineering work behind a partner or invite step.
Stage 1
Stage 1 — Fix the document library
Equipment documentation is the highest-value, lowest-risk starting point, and citation requirements expose its gaps immediately.
Consolidate equipment sheets and warranty registrations into one connected site or folder.
Adopt a naming convention that includes the property identifier.
Run cited lookups for two weeks and fix every conflict the assistant surfaces.
Stage 2
Stage 2 — Make renewals systematic
Renewal outreach only works if plan tier and renewal date exist as CRM properties.
Backfill plan tier and renewal date on agreement records.
Generate the renewal list and drafts weekly, with management approving pricing.
Log which records were unusable and fix the data, not the prompt.
Stage 3
Stage 3 — Support the sale and the install
Add quoting comparison and install coordination once documentation and CRM hygiene hold.
Standardize quote documents so scope, equipment, and price are always present.
Produce install briefs from the calendar and signed scope, with open items tracked.
Review connection scopes and named owners each quarter.
Limitations and boundaries
What this cannot do
Diagnostic equipment, combustion analysers, and telemetry are not reachable by any verified connection in this dataset.
Manufacturer portals, distributor catalogues, and warranty registries are not covered.
Efficiency, savings, payback, and rebate eligibility claims are outside these workflows.
Field-service and mechanical service platforms are reached through vendor Zapier or API paths, or through an export — never through a native AI connector.
Vendor AI features such as ServiceTrade AI and BuildOps OpsAI run inside those products and are not an external assistant connection.
Equipment sizing, combustion, refrigerant, and code decisions stay with a qualified technician.
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
CRM agreement and deal records
Equipment, warranty, and submittal documents
Customer-facing quote documents
Installation calendars
Human review that stays mandatory
Technicians own findings, service management owns pricing and inclusions, and the install coordinator owns permits and logistics.
Frequently asked questions
Primary sources
Every connection claim on this page resolves to a published record backed by official vendor documentation.