Fixed quote after a free call

HVAC and plumbing CRM automation that turns every enquiry into a booked job

Service requests arrive by phone, web form, Google Business Profile, Local Services Ads, Facebook and text, and many never make it into the field service software. We connect every source to your HVAC or plumbing CRM, create the lead or job with the right details, send a fast reply with booking options, follow up the ones who go quiet and report weekly on which sources bring booked and paid work. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why trades businesses lose leads in busy weeks

A heating, plumbing or electrical company is busiest when the weather turns, and that is exactly when leads slip. A web form sits in an inbox, a Facebook message goes unread and a call is noted on a scrap of paper while the office handles three others.

Even when leads are captured, they often live outside the field service software, so nobody can see which marketing brings jobs that are actually completed and paid. Replacement and installation leads, which need a survey and a quote, are the most valuable and the easiest to lose.

What we build

What our HVAC and plumbing CRM automation includes

Every source into your FSM

Web forms, Google and Facebook leads, texts, chat and calls create a customer and lead or job in ServiceTitan, Housecall Pro, Jobber or your platform.

Fast first reply

An approved text or email within minutes with booking options or a call-back time, day or night.

Service and install tracks

Repairs go towards booking; replacement and installation leads go to a survey and quote pipeline.

Follow-ups with stop rules

A short sequence for leads who have not booked, ending as soon as they book or reply.

Customer history

Repeat customers recognised by phone or address, with equipment and past jobs shown to the office.

Source and revenue report

A weekly report of leads, bookings, completed jobs and invoiced value by source.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Enquiry arrives

    A form, call, text, Google or Facebook lead reaches the workflow.

  2. 02 Automated

    Lead or job created

    The customer and lead or job are created or matched in the field service software.

  3. 03 Automated

    First reply sent

    The customer gets an approved reply with booking options within minutes.

  4. 04 Office or dispatcher review

    Office books

    The office or dispatcher books the job and records the outcome.

  5. 05 Technician or owner decides

    Diagnosis and pricing

    What is wrong and what it costs to fix are decided by the technician or estimator.

How it behaves

How the field service CRM pipeline behaves

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

What the customer sees

  • A reply within minutes with booking options
  • A call from the office when they asked for one
  • A couple of follow-ups at most, then nothing

What the office sees

  • Every lead in the field service software with source and history
  • Install leads in a survey and quote pipeline
  • A weekly report by source

What the automation does

  • Matches repeat customers and removes duplicates
  • Creates leads or jobs through the platform API
  • Stops follow-ups when a booking appears

Edge cases and fallbacks

Customer mentions a gas smell or sparks
Safety instructions go out at once and the on-call person is alerted; no booking flow.
Same customer enquires on two channels
Merged into one lead with both messages noted.
Address outside your service area
Polite approved reply and a flag for the office to decide.
FSM API limit or outage
Leads are queued and retried, and the office gets an alert.

Architecture

An HVAC and plumbing CRM pipeline at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Web and chat Forms, live chat Google and social GBP, LSA, Facebook Calls and texts Main number n8n Match and dedupe Field service CRM Lead or job First reply Text and email Office Books the job Source report Weekly
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Enquiries arrive from the website, Google, Facebook, calls and texts.
  2. 2 n8n matches repeat customers, removes duplicates and creates the lead or job in the field service software.
  3. 3 The customer gets a fast reply, and the office books the job or schedules a survey.
  4. 4 A weekly report shows leads, bookings, completed jobs and invoiced value by source.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

HVAC & plumbing CRM automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lead sources, field service platform and plan, booking rules and reporting needs.

  2. 02

    Design

    2 to 3 days

    Field mapping, service and install tracks, reply wording, consent and duplicate rules.

  3. 03

    Build

    1 to 2 weeks

    Source connections, FSM integration, replies, follow-ups and the weekly report.

  4. 04

    Shadow run

    About 1 week

    Leads flow into the FSM while replies go to a test phone, and the office compares.

  5. 05

    Launch

    1 to 2 days

    Switch on replies and train the office team.

  6. 06

    Support

    Ongoing

    New sources, rule changes and report tweaks.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n ServiceTitan API, Housecall Pro API or Jobber GraphQL API ServiceM8, simPRO or Commusoft APIs Google Business Profile and Facebook lead ads Twilio SMS Your email provider

Cost estimate

What it costs, line by line.

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

    Sources, field mapping, tracks and reporting.

    $200 – $400

  • Build

    Matching, replies, follow-ups and report.

    $500 – $1,300

  • Integrations

    Field service platform, lead sources and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with the office.

    $100 – $250

  • Launch and training

    Switch-on and office training.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Your field service plan must include API access (some platforms limit it to higher tiers). Messaging and n8n are billed to you directly.

Monthly running costs you pay directly

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

  • Field service platform: Your vendor's own plan; API access may need a higher tier.
  • 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). A2P 10DLC registration fees also apply.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

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

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: marketing texts need written consent

Automated marketing texts to mobiles need prior express written consent under the TCPA rules, so follow-ups that promote offers only go to customers who agreed.

Source: www.law.cornell.edu

US: A2P 10DLC registration

Anyone sending application texts to US numbers from a 10-digit long code must register for A2P 10DLC, so registration is part of the plan.

Source: www.twilio.com

UK: marketing by text and email

PECR requires consent, or the soft opt-in conditions, for marketing by electronic mail, with a simple way to refuse in every message.

Source: www.legislation.gov.uk

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.

FAQ

HVAC and plumbing CRM questions questions, answered.

An HVAC CRM tracks customers, leads, equipment and jobs from first call to paid invoice. Most HVAC, plumbing and electrical firms use the CRM inside their field service software, such as ServiceTitan, Housecall Pro or Jobber, and we automate around it.

The best one is usually the field service platform your team already uses well. ServiceTitan suits larger firms, Housecall Pro, Jobber and ServiceM8 suit smaller teams, and simPRO and Commusoft are common in the UK. We automate whichever you run, as long as your plan includes API access.

Yes. Electrical contractors use the same field service platforms, and the workflow handles their mix of service calls, installs, EV chargers and inspections.

Yes, through each platform's API where your plan allows. Some firms prefer leads to land in a booking queue for the office to confirm, which we can do too.

No. A first reply and a couple of follow-ups at most, stopping as soon as they book or reply, with opt-outs honoured across every workflow.

Time to first reply, share of leads booked, completed jobs and invoiced value by source, and how many installation leads reach a quote.

Free 20-minute call

Want this 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