Fixed quote after a free call

Missed-call text-back for HVAC, plumbing and electrical contractors

When the office is on another call or the owner is under a sink, the next caller goes to voicemail and then to a competitor. We build a workflow that texts every missed caller back within seconds from your business number, asks for the problem and address, offers booking options, puts no-heat, no-cooling and active leak replies at the top of the list and sends any mention of gas, carbon monoxide or sparks straight to a person with your safety instructions. A typical build costs $1,000 to $2,500 and goes live in about three to four weeks.

The problem

Why missed calls cost trades businesses jobs

Small trades businesses miss calls all day: the owner is on a job, the office is booking another customer, and calls after 5pm go to voicemail. A homeowner with no heat or a burst pipe will not wait for a call back; they ring the next company on Google.

Not every missed call is equal. A routine service booking can wait an hour; a reported gas smell cannot wait at all and must never be handled by a booking bot. The workflow has to sort urgency without ever giving technical or safety advice.

What we build

What our missed-call text-back for contractors includes

Instant text-back

A short text from your business number to any missed caller, during or after hours, with a reply option and booking link.

Problem and address capture

A couple of quick questions so the office knows the job type and location before calling back.

Urgency sorting

No heat, no cooling, active leak and no power go to the top of the list using your own wording.

Danger goes to a person

Gas smell, carbon monoxide alarm, sparks or burning trigger your safety instructions and an immediate on-call alert.

Call-back list

One list in your field service software, Slack or a shared sheet, cleared as the office works through it.

After-hours rules

Different wording for evenings and weekends, and an on-call rota for emergencies if you offer them.

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

    Call missed

    Your phone system or Twilio reports a missed call from a mobile number.

  2. 02 Automated

    Text sent

    The caller gets an approved text with a reply option and booking link within seconds.

  3. 03 Automated

    Reply sorted

    The reply is sorted by urgency; danger words trigger safety instructions and an alert.

  4. 04 Office or dispatcher review

    Office calls back

    The office or on-call tech calls back and books in the field service software.

  5. 05 Technician or owner decides

    Safety and diagnosis

    Whether anything is safe and what is wrong are decided by a qualified technician on site.

How it behaves

How the missed-call system behaves

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

What the customer sees

  • A text from your business number within about a minute
  • A couple of quick questions and a booking link
  • Safety instructions straight away if they mention danger
  • A call back from the office or on-call tech

What the office sees

  • One call-back list, most urgent first
  • Problem and address already captured
  • Danger alerts routed to the on-call person

What the automation does

  • Detects missed calls and checks hours and opt-outs
  • Sends approved texts and sorts replies by urgency
  • Logs everything and clears the list when a job is booked

Edge cases and fallbacks

Caller is on a landline
No text is possible, so the number goes straight onto the call-back list.
Caller has opted out
No text is sent; the call goes on the list for a person.
Same person calls repeatedly
One text only, with repeat calls noted as a sign of urgency.
Twilio or n8n is down
Calls still reach voicemail as before and the owner gets an alert.
Reply is unclear
It goes to the office unsorted rather than being guessed at.

Architecture

Missed-call text-back for a trades business at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Missed call Business number n8n workflow Hours and rota Text-back Twilio SMS Reply sorting Urgency, danger Office or on-call Calls back Field service app Job created
  • Input
  • Logic and services
  • Output
  • AI step
  • People
  • Data

How it flows

  1. 1 A call to the business number goes unanswered and the phone system reports it to the workflow.
  2. 2 n8n checks hours and the on-call rota, then sends an approved text with a reply option.
  3. 3 Replies are sorted by urgency; any danger words trigger safety instructions and an immediate alert.
  4. 4 The office or on-call technician calls back and books the job in the field service software.

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.

Missed-call text-back for contractors project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Phone system, field service platform, hours, emergency policy and the wording your team uses.

  2. 02

    Design

    2 to 3 days

    Text wording, urgency and danger words, safety instructions, call-back list and opt-outs.

  3. 03

    Build

    About 1 week

    Twilio number or phone-system hook, n8n workflow, sorting and the call-back list.

  4. 04

    Shadow run

    About 1 week

    Texts go to a test phone while the office compares every reply with what they would have done.

  5. 05

    Launch

    1 to 2 days

    Switch on for real callers and walk the team through the list and rota.

  6. 06

    Support

    Ongoing

    Wording changes, rota updates and monitoring.

What it runs on

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

n8n Twilio Programmable Messaging Your phone system (missed-call webhook) ServiceTitan, Housecall Pro or Jobber API Slack or SMS for on-call alerts Claude or OpenAI for reply sorting

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

    Wording, urgency rules, safety instructions and specification.

    $200 – $400

  • Build

    The n8n workflow, sorting step and error handling.

    $500 – $1,300

  • Integrations

    Phone system, field service platform and alerts.

    $150 – $400

  • Testing and shadow run

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

    $100 – $250

  • Launch and training

    Switch-on, walkthrough and run book.

    $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. Twilio (number, messages and A2P 10DLC registration) and n8n are billed to you directly, not marked up.

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). A2P 10DLC registration fees also apply.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually) or €50 (Pro).
  • AI model usage: Billed by the provider per use; sorting short replies is usually a small monthly amount.

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: keep the text-back to the caller's request

The TCPA rules restrict automated texts to mobiles, and marketing texts need prior express written consent. The text-back only responds to the call and carries no promotions.

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.

Source: www.twilio.com

UK: gas work by registered engineers only

In Great Britain, work on gas fittings in homes and workplaces must be done by a Gas Safe registered engineer. The workflow never suggests a customer fixes anything themselves.

Source: www.hse.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

Missed call text back questions questions, answered.

When a call to your business number is not answered, the phone system tells the workflow, which sends a text from the same number within seconds. The caller can reply with their problem and address or use your booking link, and the office sees everything on one call-back list.

They immediately get your approved safety instructions, such as leaving the property and calling the gas emergency line, and the on-call person is alerted. The system never tells anyone a situation is safe.

Most VoIP systems can report missed calls by webhook or email, and Twilio can sit in front of your existing number with call forwarding. We confirm the route on the free call.

It can send your online booking link or create a job request in the field service software. Many firms prefer the office to confirm, so the schedule stays realistic.

You pay Twilio for the number and messages and your n8n plan directly. For a small trades business that is usually a small monthly amount, and we estimate it from your call volume before launch.

We log every missed call, text, reply and booking. Watch the share of missed callers who reply and book, and how fast urgent replies get a call back.

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