Fixed quote after a free call

Maintenance agreement and service reminder automation for HVAC and heating firms

Maintenance agreements and annual services are the steadiest revenue a trades business has, and they leak when reminders are manual. We build a workflow that reads agreement and service due dates from your field service software, sends reminders with booking links in good time, renews agreements before they lapse, books landlord gas safety checks with tenants and hands anyone who does not respond to the office for a call. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why maintenance agreements and annual services slip

Spring and autumn tune-ups, annual boiler services and maintenance agreement visits should fill the quiet weeks. In practice, reminders go out late or not at all, agreements lapse without anyone asking the customer to renew and the schedule gets crowded when everyone calls in the first cold snap.

Landlord work adds legal dates. In Great Britain landlords must have a gas safety check on each appliance and flue every year, and the check can be done from 10 to 12 months after the last one while keeping the original deadline. Missing that window costs the landlord and the engineer the work.

What we build

What our maintenance agreement automation includes

Due list from your FSM

Agreement visits, tune-ups, boiler services and gas safety checks due, read from your field service software.

Reminders with booking

Reminders by text and email with a booking link or preferred times, sent weeks ahead.

Agreement renewals

Renewal notices before an agreement ends, with a payment link where your system supports it.

Landlord and tenant flow

For landlord gas safety checks, the landlord is reminded and the tenant is contacted to arrange access.

Seasonal load balancing

Reminders spread across weeks so tune-ups do not all land in the busy season.

Non-responder list

Customers who do not respond after two reminders go to the office to call.

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

    Due list built

    Each night the workflow reads agreement and service due dates.

  2. 02 Automated

    Reminder sent

    Customers and landlords get reminders with booking options well ahead.

  3. 03 Automated

    Renewal or booking

    Renewals and bookings update the field service software automatically where possible.

  4. 04 Office or dispatcher review

    Office follows up

    The office calls non-responders and confirms tenant access.

  5. 05 Technician or owner decides

    Safety findings

    Safety readings and whether an appliance is safe are recorded and signed by the registered engineer.

How it behaves

How service reminders behave

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

What the customer or landlord sees

  • A reminder weeks before a visit or check is due
  • A booking or renewal link
  • At most two follow-ups, then a friendly call

What the office sees

  • A daily list of non-responders to call
  • Bookings and renewals in the field service software
  • Tenant access arrangements for landlord jobs

What the automation does

  • Reads due dates every night
  • Spreads reminders to balance the season
  • Stops reminders as soon as a booking appears

Edge cases and fallbacks

Customer books by phone mid-sequence
The nightly check sees the booking and stops reminders.
Tenant does not reply about access
The landlord and office are told so they can arrange it.
Due date missing in the FSM
Flagged for the office; no reminder is guessed.
FSM unavailable overnight
The run is skipped and retried, never sent from stale data.

Architecture

Maintenance agreements and service reminders at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Field service app Agreements, dates n8n schedule Nightly check Contact rules Channel, spread Reminders Book or renew Office Calls non-replies Bookings Back into FSM
  • Input
  • Logic and services
  • Output
  • People
  • Data

How it flows

  1. 1 Each night the workflow reads agreement visits, services and gas safety checks coming due.
  2. 2 Contact rules choose the channel, include tenants where needed and spread reminders across weeks.
  3. 3 Reminders go out with booking or renewal links, and bookings flow back into the field service software.
  4. 4 Customers who do not respond go to the office to call, and every step is logged.

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.

Maintenance agreements & service reminders project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Agreement types, service intervals, landlord customers, FSM data and current reminder habits.

  2. 02

    Design

    2 to 3 days

    Reminder timing, wording, renewal flow, tenant access flow and load spreading.

  3. 03

    Build

    1 to 2 weeks

    Due list, reminders, booking and renewal links, tenant flow and the call list.

  4. 04

    Shadow run

    About 1 week

    The list is built daily but reminders go to a test inbox for the office to check.

  5. 05

    Launch

    1 to 2 days

    Start with one agreement type, then add the rest.

  6. 06

    Support

    Ongoing

    New plans, wording changes and monitoring.

What it runs on

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

n8n ServiceTitan, Housecall Pro, Jobber, ServiceM8, simPRO or Commusoft API Twilio SMS Gmail, Microsoft 365 or your email provider Stripe or your FSM's payments for renewals Google Sheets or the FSM for the call list

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

    Agreement types, timing, wording and tenant flow.

    $200 – $400

  • Build

    Due list, reminders, renewals and call list.

    $500 – $1,300

  • Integrations

    Field service platform, payments and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a test-inbox shadow run.

    $100 – $250

  • Launch and training

    Phased switch-on and office walkthrough.

    $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. Payment links use your existing payment provider. 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.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
  • 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.

UK: annual landlord gas safety checks

Landlords must ensure a gas safety check on each gas appliance and flue every year and give tenants the record within 28 days; reminders support the landlord, who keeps the legal duty.

Source: www.hse.gov.uk

UK: service reminders vs marketing

Reminders about a service the customer has agreed to are service messages; promotions such as upgrade offers need consent or the soft opt-in under PECR.

Source: www.legislation.gov.uk

US: marketing texts need written consent

Texts that promote offers need prior express written consent under the TCPA rules, so offers live in a separate flow for customers who agreed.

Source: www.law.cornell.edu

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

Maintenance agreement and service reminder questions questions, answered.

It tracks maintenance plans, visit schedules and renewals. Most field service platforms include agreements; our workflow adds the reminders, renewals, load spreading and follow-up calls they often leave to the office.

Yes. Annual boiler service reminders go out weeks before the due date with a booking link, and customers who do not respond go to the office.

Landlords get reminders before the check falls due, tenants are contacted to arrange access, and the engineer records the check and issues the record in your system. The legal duty stays with the landlord.

Yes, where your field service platform or payment provider supports payment links. Renewals then update the agreement automatically.

No. A reminder and up to two follow-ups, then a call from the office instead of more messages, with opt-outs respected.

Agreements renewed, visits booked from reminders, non-responders called and how evenly tune-ups spread across the season.

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