Case Study

Case Study: HVAC & Plumbing Field Service Automation

We built a connected set of automations for a residential HVAC and plumbing company: every enquiry captured in the field service software, missed callers texted back with emergencies routed to the on-call technician, dispatch changes proposed for approval with customer updates, maintenance agreements renewed on time and install quotes drafted from surveys and followed up. The office now works from clear lists, and technicians and the owner keep every safety and pricing decision.

Company type
Residential HVAC, heating and plumbing service and installation
Team involved
Owner, office manager, dispatcher, estimator, service and install technicians
Systems connected
Field service platform, phone system, Twilio, Google Business Profile, accounting, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Calls rang out whenever the office was busy, and evening calls went to voicemail. Web and Google leads sat in an inbox until someone had time.

The dispatcher re-planned the day by hand and phoned every affected customer, so late-running days meant an afternoon on the phone and frustrated customers.

Maintenance agreements were renewed only when customers asked, and seasonal tune-up reminders went out late, so the busy season was overloaded.

Installation quotes took days to type up after a survey and were rarely followed up.

Goals

What the project had to change

  • Every enquiry lands in the field service software with a fast reply.
  • Every missed caller hears back within minutes, and danger reaches a person at once.
  • Schedule changes are proposed for approval, and customers hear about delays before they ask.
  • Agreements renew before they lapse, and tune-ups spread across the season.
  • Install quotes go out the same day as the survey and are followed up until decided.

What we built

What we built, as one connected system.

01

Enquiries into the field service software

We connected web forms, Google and Facebook leads and texts to the field service platform, with a fast approved reply, separate service and install tracks and a weekly source report.

Service details
02

Missed-call text-back

Missed calls from mobiles get a text from the business number within seconds; replies are sorted by urgency, and any danger words trigger the company's safety instructions and an on-call alert.

Service details
03

Dispatch updates

Overruns and emergencies produce a proposed re-plan respecting skills and certifications; once the dispatcher approves, affected customers get new times and on-the-way texts.

Service details
04

Maintenance agreements

A nightly due list, reminders spread across weeks, renewal links before agreements end and a call list for customers who do not respond.

Service details
05

Quotes and follow-up

Survey notes and photos become a draft quote from the price book, the estimator approves it, and follow-ups run until the customer decides.

Service details

Architecture

How the company's workflows connect

Phone system Missed calls Web and Google Enquiries Field service app Jobs, agreements n8n Five workflows AI steps Sorting, drafts Texts and emails Twilio, email Office, dispatch Lists, approvals Technicians On-call, estimates Log and reports Weekly summary
  • Input
  • Logic and services
  • AI step
  • Output
  • People
  • Data

How it flows

  1. 1 Missed calls, web and Google enquiries, and jobs and agreements from the field service software feed one n8n instance.
  2. 2 Five workflows send texts and emails and use AI steps to sort replies, propose re-plans and draft quotes.
  3. 3 The office and dispatcher approve changes and call back; technicians handle emergencies and approve estimates.
  4. 4 Every step is logged, and a weekly summary shows the measures the company agreed to track.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What customers see

  • A text back within about a minute when their call is missed
  • Safety instructions at once if they mention danger
  • A text when their technician is running late or on the way
  • Reminders before their tune-up or renewal
  • A clear quote soon after the survey

What staff see

  • One call-back list and one lead list
  • Proposed schedule changes to approve
  • Non-responders to call and draft quotes to approve

What the automation does

  • Captures, texts, sorts, proposes, reminds and chases
  • Applies opt-outs, quiet hours and consent across every workflow
  • Logs every step and alerts the owner if anything fails

Edge cases and fallbacks

A caller reports a gas smell
Safety instructions and the on-call alert go out at once; nothing is queued.
No certified technician is free for a refrigerant job
The proposal says so and the dispatcher decides.
A customer opts out in one workflow
One shared opt-out list stops texts from every workflow.
An item is missing from the price book
The draft quote flags it for the estimator.
The field service API or Twilio is down
Calls reach voicemail, the dispatcher works the board by hand and the owner is alerted.

Integrations

What we connected

All integrations

ServiceTitan

Field service management

Customers, jobs, bookings, dispatch, estimates and memberships.

ServiceTitan API through its developer portal (OAuth 2.0 plus app key), confirmed per account.

Housecall Pro

Field service management

Customers, jobs, estimates, invoices and leads.

Housecall Pro public API and webhooks (MAX plan).

Jobber

Field service management

Clients, requests, quotes, jobs and invoices.

Jobber GraphQL API with OAuth 2.0.

QuickBooks Online

Accounting

Invoices, payments and customer records.

QuickBooks Online Accounting API.

Twilio

SMS and voice

Text-back, ETAs, reminders, follow-ups and the AI voice line.

Twilio Messaging and Voice APIs, with A2P 10DLC registration.

Google Business Profile

Local search and reviews

Booking link, leads and review requests.

Google Business Profile settings and APIs.

Slack and Microsoft Teams

Staff alerts

Emergency alerts, dispatch approvals and failure alerts.

Incoming webhooks and APIs.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We sat with the office, dispatcher and estimator, rode along on a service day, mapped calls, dispatch, agreements and quotes and agreed the safety wording with the owner.

  2. 02

    Design and access

    Week 2

    Message templates approved by the owner, urgency and danger words, re-plan rules, API access to the field service platform, Twilio number and A2P 10DLC registration.

  3. 03

    Sprint 1: missed calls

    Week 3

    Built and shadow-ran the missed-call workflow with texts going to a test phone; demo and sign-off.

  4. 04

    Sprint 2: enquiries

    Week 4

    Missed calls went live. Connected web, Google and Facebook leads to the field service software with fast replies.

  5. 05

    Sprint 3: dispatch

    Week 5

    Enquiries went live. Built change detection, re-plan proposals and customer updates, shown to the dispatcher first.

  6. 06

    Sprint 4: agreements

    Week 6

    Dispatch updates went live. Built the due list, reminders, renewals and call list.

  7. 07

    Sprint 5: quotes

    Week 7

    Agreements went live for one plan type. Built survey capture, draft quotes and follow-ups.

  8. 08

    UAT and handover

    Week 8

    The team ran acceptance testing on every workflow, then we switched everything on, handed over the run book and trained staff.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures enquiries and sends fast replies
  • Texts missed callers and sorts replies by urgency
  • Proposes re-plans and updates customers after approval
  • Sends maintenance and renewal reminders
  • Drafts quotes from surveys and follows them up

The team does

  • Call back customers and book jobs
  • Approve schedule changes and call vulnerable customers
  • Call agreement customers who do not respond
  • Answer customer questions about quotes

Technician or owner decides

  • Handles every emergency and safety concern
  • Diagnoses faults and decides repairs on site
  • Approves equipment sizing, scope and price on every quote
  • Records and signs safety readings and findings

Compliance handled

Privacy, consent and safety, built in.

Safety concerns always go to a person

Danger words trigger the company's safety instructions and an on-call alert; nothing tells a customer a situation is safe.

Texting rules in the US

Text-backs and updates stay informational; promotions need prior express written consent.

Source: www.law.cornell.edu

A2P 10DLC registration

The business number was registered for A2P 10DLC before any texts went out.

Source: www.twilio.com

Certified technicians for refrigerant work

Dispatch proposals only offer refrigerant jobs to technicians recorded as Section 608 certified.

Source: www.epa.gov

Data minimisation

Each workflow uses only the customer data it needs.

Source: gdpr-info.eu

Outcomes

What changed for the practice

  • Missed calls from mobiles now get a text back within about a minute, day or night.
  • Danger reports reach the on-call technician straight away with the company's safety instructions.
  • Customers hear about delays and arrival times before they need to call the office.
  • Maintenance agreements are renewed before they lapse, and tune-ups are spread more evenly across the season.
  • Install quotes go out soon after the survey and are followed up until the customer decides.
  • The office works from one set of lists instead of an inbox, voicemail and sticky notes.

What we track

The measures the practice watches.

Missed-call response

Share of missed callers who reply and book.

Lead response

Minutes from enquiry to first reply, and bookings by source.

Customer updates

Share of delayed jobs where the customer was told before their window.

Agreements

Renewals before lapse and visits booked from reminders.

Quotes

Hours from survey to quote sent and acceptance rate by job type.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, safety wording, data flows and the backlog for all five workflows.

    $1,000 – $2,000

  • Enquiry and missed-call modules

    Lead capture, fast replies, text-back and urgency sorting.

    $800 – $2,000

  • Dispatch module

    Change detection, re-plan proposals and customer updates.

    $800 – $2,000

  • Maintenance agreement module

    Due list, reminders, renewals and call list.

    $700 – $1,700

  • Quote module

    Survey capture, draft quotes and follow-ups.

    $700 – $1,600

  • Integrations

    Field service platform, phone system, Twilio and accounting connections.

    $300 – $700

  • Testing, UAT and launch

    QA, user acceptance testing, launch and training.

    $700 – $2,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every company gets its own fixed quote after a free call.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing), plus A2P 10DLC registration fees.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • Field service platform: The vendor's own plan, including the tier that provides API access.
  • AI usage: Pay-per-use model fees, usually small at a single company's volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built for your heating, plumbing & electrical?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call