Contents
Home services businesses have a structural problem that most industries do not: a large share of your highest-intent demand arrives outside business hours. A water heater fails at 11pm. A furnace quits on the coldest Saturday of the year. The customer is not shopping carefully at that moment - they are calling down a list until someone picks up. Whoever answers gets a job that would have cost hundreds in ad spend to generate.
The second structural problem is quotes. In HVAC particularly, a system replacement quote is a considered purchase with a multi-week decision cycle, and the standard industry follow-up is one call two days later and then silence. The customer is not saying no. They are talking to their spouse, checking their savings, and getting two more quotes. The company that stays politely present through that window wins a disproportionate share of that work.
Both problems are timing problems, which is what makes them good automation targets. Neither requires software to make a technical judgment. They require something to reliably do the obvious thing at 11pm on a Saturday and on day nine of a quote that everyone in the office has forgotten about.
One thing that separates this page from most of what ranks for these queries: we will tell you specifically which field service platforms this connects to and what that connection can and cannot do. The micro-sites competing for this keyword never do, which is usually a sign that the answer is 'we have not built one'.
The four builds that earn their keep
After-hours call capture
- Trigger
- An inbound call rings out, hits voicemail, or comes in outside your dispatch hours.
- What it does
- The caller gets an immediate text from your business number: acknowledging the call, asking whether this is an emergency, and giving a clear next step for each answer. Emergencies route straight to your on-call technician's phone with the caller's number and their description, and can escalate to a second contact if unanswered inside a few minutes. Non-emergencies get a booking link for the next available slot and a promise of a callback when the office opens. Everything logs as a lead in your FSM so nothing lives only in a voicemail box nobody checks until Monday.
- Why it matters
- This is the highest-value automation in the trades and it is not close. Emergency calls convert at rates normal leads do not, the customer's alternative is the next number on their search results, and the cost of catching them is a text message.
Quote and estimate follow-up cadence
- Trigger
- An estimate is created in your FSM and its status has not moved to accepted or lost.
- What it does
- A structured sequence over two to three weeks rather than one forgotten phone call. Early touches confirm the quote arrived and offer to walk through it. Mid-window touches address what customers actually hesitate on - financing options, warranty terms, what happens to the old equipment, whether the rebate applies. Later touches are short and direct: is this still something you are considering, or should we close it out? High-value quotes raise a task for a human call rather than only sending a message. Any reply pauses the sequence.
- Why it matters
- Most quoted work is lost to silence, not to a competitor's price. The cadence costs nothing per quote and recovers deals that were never actually decided against you.
Maintenance agreement renewal chasing
- Trigger
- A service agreement approaches its renewal date, or a covered tune-up visit comes due and is unscheduled.
- What it does
- A sequence that starts well before expiry: a reminder of what the agreement includes, what they used it for this year, and a direct link to book the tune-up or renew. Non-responders escalate to a call task. Lapsed members get a separate win-back sequence with a different message, because someone who let an agreement expire eighteen months ago is a different conversation from someone who is thirty days late. Renewals and bookings write back so people drop out of the sequence the moment they act.
- Why it matters
- Agreement revenue is the most valuable revenue in the business - recurring, high-margin, and it produces the diagnostic visits that generate replacement work. It also erodes silently, because nobody's job is chasing renewals when the board is full of emergency calls.
Review request on job completion
- Trigger
- A job is marked complete in the FSM, with a delay of a few hours.
- What it does
- A short message thanking the customer, naming the technician who attended, and linking directly to your primary review destination. Naming the tech matters: reviews that mention a technician by name read as authentic and give you something to recognise internally. The sequence suppresses repeat asks, excludes jobs with open complaints or warranty disputes, and can be scoped to specific job types.
- Why it matters
- Local search visibility for emergency trades is heavily review-driven, and the customer is never happier than the hour after their heat comes back on. Manual asking is inconsistent by nature; this is not.
Unsold recommendation follow-up
- Trigger
- A technician logs a recommendation on a visit that the customer declined or deferred.
- What it does
- A follow-up at a sensible interval - often seasonal, so a deferred AC recommendation surfaces before the first hot week rather than in November. It references the specific recommendation from the specific visit, which is the only reason it works. Generic reactivation blasts get ignored; 'when Marcus was out in April he noted your capacitor was reading low' does not.
- Why it matters
- Deferred recommendations are pre-qualified demand sitting in your database that almost nobody works systematically.
Done for you
Not sure which of these to build first?
That is what the free audit is for. We look at how enquiries, bookings, and follow-up actually move through your business today, and tell you which single workflow is worth building first - including if the answer is none of them yet.
What after-hours capture actually involves
Owners often assume this is a phone system feature they can toggle on. It is not, and the parts that make it work or fail are mostly decisions rather than code. Here is the build.
1. Decide what counts as an emergency - precisely
This is the whole design, and it has to be your call, not a vendor's. No heat below a temperature threshold, no water, active leak, sewage backup, gas smell, no cooling above a threshold for a vulnerable occupant. Everything else waits until morning. Write the list down. Then write down the second list: what your on-call tech is authorised to attend without waking you, and what needs your approval first. Automation without those two lists produces either technicians dragged out for a dripping tap or genuine emergencies sitting in a queue.
2. Get the phone plumbing right
You need call events - missed, voicemail, after-hours - reaching the automation layer, and a business number capable of two-way text. Most modern VoIP providers expose this; some legacy setups do not, and that is a hard blocker worth discovering in week one. The messages must come from the number the customer dialled, or they will not trust them.
3. Write the triage exchange, short
Two questions maximum. Is this an emergency, described in plain terms with examples from your list. And what is the address or general area, because a job outside your service radius should be told so immediately rather than raising an on-call escalation. Anything beyond two questions and people stop replying and call the next company.
4. Build the escalation ladder with a timeout
Emergency confirmed, message the on-call tech with the caller's number, location, and description. If no acknowledgement in a set number of minutes, escalate to the second on-call. If still nothing, escalate to the owner. The timeout is the part people forget, and it is the part that stops a system from silently swallowing the exact call it exists to catch. Every escalation logs.
5. Write it into the FSM as a real record
Whatever happens overnight has to exist as a lead or job in ServiceTitan, Housecall Pro, or Jobber by the time the office opens, with the conversation attached. Otherwise Monday morning is a person reading text threads and re-keying them, which is the manual work you were trying to remove.
6. Test it on a real weekend before trusting it
We run live tests at genuinely awkward hours - including deliberately failing to answer the first escalation - before this goes into production. An after-hours system that fails silently is worse than no system, because the office stops checking voicemail once they believe the automation has it.
Two to three weeks is typical for this build, and most of it is testing and tuning the triage wording, not the integration.
Which field service software this connects to
This is the question competing pages never answer, so here is a straight one. The answer determines what is possible, so it is the first thing we check in scoping.
ServiceTitan exposes a documented API covering customers, jobs, estimates, memberships, and more, and it supports webhooks for event-driven work. It is the richest integration surface in the category, which makes it the platform where the full set of workflows - including membership renewals and estimate-status-driven follow-up - is most straightforwardly buildable. Access depends on your account and API entitlements, which is worth confirming with your account team early.
Housecall Pro offers an API for core objects - customers, jobs, estimates, schedule - sufficient for after-hours capture, review requests, and quote follow-up. Some workflows need polling rather than events, meaning near-real-time rather than instant, which is fine for follow-up cadences and marginal for emergency routing.
Jobber has a GraphQL API with webhooks covering clients, quotes, jobs, and invoices. Quote follow-up and review-on-completion map cleanly onto it. Capabilities and rate limits vary by plan tier, so we verify against your actual account rather than the docs alone.
Other platforms in this space - FieldEdge, Service Fusion, Workiz, ServiceM8 and others - range from well-documented APIs to export-only. We tell you which category yours falls into before quoting the work, and if the integration path is genuinely bad, the honest answer is sometimes that a workflow is not worth building until you move platforms.
API capabilities and plan entitlements change. Everything above is a starting point for a scoping conversation, verified against your account before any design is committed.
Company size and fit
The natural range is roughly three to forty technicians. Below that, the owner is usually still answering the phone personally and the after-hours problem is real but the quote-follow-up problem is not yet at volume. Above that, you likely have dedicated dispatch and a marketing function, and the conversation shifts from building missing systems to integrating existing ones - still useful work, but a different engagement.
The strongest fit is a company running a real FSM with reasonably clean data, doing a mix of service and replacement work, where someone in the office can name the frustration precisely: 'we lose calls at night' or 'we quote thirty replacements a month and never follow up past the first call'.
The weakest fit is a company where the schedule and customer history live in a mix of paper, texts, and one person's memory. Automation on top of that produces confident-sounding messages to the wrong people. Fix the record system first.
Working out whether it pays
Rather than quote you a number we cannot support, here is the calculation to run on your own figures.
Take your average ticket for an emergency service call and, separately, for a system replacement. Ask your office how many after-hours calls went to voicemail last month and never converted - most owners have never counted this and the exercise alone is worth doing. Then look at your quote log: how many estimates from three months ago are still sitting in an ambiguous status, neither won nor formally lost.
If after-hours capture converts a handful of otherwise-lost emergency calls per month, and the quote cadence recovers a small share of estimates that were drifting, you can weigh that against a build cost and a monthly running cost. Replacement-quote arithmetic in particular tends to be decisive because of ticket size - a single recovered system replacement is a large number relative to automation cost. That is an illustrative structure for you to fill in with real figures, not a projection of your results.
Do factor in the operational cost too. After-hours capture means your on-call rotation actually gets called. That is the point, but it is a real change to how your team works and it should be agreed with them, not sprung on them.
Questions owners ask
Does this replace an answering service?
It can, for many companies, and it can also sit alongside one. The trade-off is straightforward: an answering service has a human who can handle anything but costs per call and adds a delay; automated capture responds in seconds, at effectively no marginal cost, but only handles the paths you designed. A common arrangement is automation as the immediate first response with a human service or on-call tech as the escalation for confirmed emergencies.
Will it wake my technicians up for non-emergencies?
Only if the triage rules say to, and those rules are yours. The escalation criteria are written down explicitly during scoping - what qualifies, who is on call, how long before escalating, and who is last in the chain. We test the ladder including deliberate non-responses before it goes live.
Does it integrate with ServiceTitan?
Yes. ServiceTitan's API covers customers, jobs, estimates, and memberships and supports webhooks, which makes it the platform where the widest range of these workflows is buildable. What your specific account can access depends on your entitlements, so that is verified in scoping before design.
What about Housecall Pro or Jobber?
Both are workable. Housecall Pro's API supports the core objects, with some workflows running on a polling interval rather than instant events. Jobber's GraphQL API with webhooks maps well onto quote follow-up and review-on-completion. In both cases the exact capability depends on plan tier, which we confirm against your account rather than assuming from documentation.
Can the system quote jobs?
No, and you should be suspicious of anyone offering that in the trades. Diagnosis and pricing in HVAC and plumbing depend on what a technician sees on site. What automation does is make sure the quote your technician produced gets followed up properly, and that the customer who needs one gets booked in fast.
How does the maintenance agreement workflow know who is due?
It reads membership or agreement records from your FSM - renewal dates, covered visit entitlements, and whether those visits have been scheduled. Platforms with proper membership objects make this clean. If your agreements live in a spreadsheet, the first phase of the work is getting them into a system that can be read reliably, and we will say so rather than building on the spreadsheet.
What is the sensible first build?
After-hours capture, almost always. It is self-contained, the value is immediate and easy to see, and it does not depend on historical data quality. Quote follow-up is the usual second build because it uses the same messaging infrastructure and has the largest ticket size behind it.
Do we own the system afterwards?
Yes. It is built in accounts belonging to your company, documented, and handed over. If you want to maintain it internally or move providers later, you can. This is worth asking every vendor you talk to, because some of them are selling access rather than ownership.
Start with a free consult
Tell us how hvac & plumbing enquiries and bookings move through your business today. We will tell you which workflow to build first, roughly what it involves, and whether it is worth doing at all. No cost, and no obligation to hire us.
