Service Call Intake to Dispatch: A Workflow for HVAC, Plumbing and Electrical Firms

A service call intake to dispatch workflow takes every request, whether a phone call, web form or after-hours message, and turns it into a complete job: the right questions asked, safety risks escalated to a person at once, a qualified technician proposed, the customer kept updated. Automation does the capture and messaging. Your dispatcher still approves the schedule and handles every emergency.

Most trade firms don't lose jobs because their technicians are slow. They lose them between "the phone rang" and "someone is on the way": retyping, call-backs for missing details and decisions made from a note that says "no heat".

For the broader picture, from quotes to invoicing, see our automation guide for tradespeople.

AI Automation for HVAC, Plumbing and Electrical Firms, Explained Step by Step · 3:03 Subscribe

Why intake and dispatch break down

Planned maintenance and breakdowns arrive through the same front door, often while the owner is on a roof. The common failure points:

• No single queue. Calls, web forms and texts to a technician's personal phone all land in different places.
• Thin details. "AC not working" says nothing about the equipment, error code, access or whether anyone smells burning.
• After-hours requests wait. A form sent at 10pm may not be read until 8am, by which time the customer has called someone else.
• Dispatch by memory. Who holds which credentials, who is near which zip or postcode, and how long the job takes all live in one person's head.
• Silence. Many customers get no update until a van turns up, or doesn't.

These need a consistent process, which automation is good at, as long as people keep the decisions.

The service call intake workflow, stage by stage

Here is the workflow Make It Flow uses as a starting point. Each stage has a trigger, an action and a reviewer.

1. Capture from every channel

Trigger: a call, missed call, web form, email or business messaging enquiry. Action: every request is logged in one queue with channel, time and contact details. Forms and messages get an instant acknowledgement saying what happens next. Missed calls are logged where the phone system shares call records. Who reviews: the office checks the queue throughout the day.

Print a QR code to your request form on invoices, vans and service stickers with our free QR code generator, and tag each link with the UTM builder to see which channel brings in requests.

2. Safety screening comes first

Trigger: any request, on any channel, before anything else happens. Action: the system checks for words and answers suggesting danger: a gas smell, carbon monoxide alarm, symptoms such as headaches or dizziness, burning, sparking, scorch marks, water near electrics. If any appear, it stops the normal flow, shows or sends the approved safety message with the local emergency number, and alerts a named person by call or text. Who reviews: a person, every time, straight away.

The wording should come from official guidance where the property is, and the system should never talk someone through a hazard. For example:

• US: the federal pipeline regulator PHMSA advises leaving the area and calling 911 from a safe distance, avoiding anything that could spark. Many utilities ask to be called too.
• Canada: Enbridge Gas tells customers to leave and then call its emergency line or 911, and not to use phones or switches near the leak.
• Great Britain: gas networks direct people to the free 24-hour National Gas Emergency Service on 0800 111 999, called from outside the property, as SGN explains. The HSE's carbon monoxide guidance uses the same number for suspected CO and lists symptoms.
• Northern Ireland: the gas emergency number is 0800 002 001, as HSENI notes.
• Australia: Energy Safe Victoria advises calling Triple Zero (000) where life or property is at risk, and otherwise the gas distributor's emergency line, which varies by area.
• EU: 112 is the single European emergency number, and national gas networks run their own lines.

3. Guided triage questions

Trigger: the request passes safety screening. Action: the system asks questions matched to the job type. For a no-cooling or no-heat call: equipment type, make and model, error code, when it stopped, thermostat display, anyone vulnerable in the home. For a leak: where, how fast, whether the stopcock or shut-off valve is off. For electrical: what tripped, whether it resets, any smell or heat. It also asks for property type, access notes, parking and pets. Who reviews: the dispatcher reads the summary before booking.

Ask for photos of the data plate and error display. iPhone photos often arrive as HEIC, which some systems handle badly: convert them with the HEIC to JPG converter and shrink them with the image compressor.

4. Classify and set priority

Trigger: triage answers are complete. Action: the job is classified (repair, maintenance, survey, warranty) and given a suggested priority from rules you write: no heat with an elderly occupant in freezing weather ranks above a noisy outdoor unit. Unclear requests are flagged, not guessed. Who reviews: the dispatcher confirms or changes the priority.

5. Match a technician and propose slots

Trigger: the job is classified. Action: the system filters technicians by the licence or certification the job needs where it is located, such as gas, electrical or refrigerant credentials, then by area, skills and existing bookings. It estimates duration from similar past jobs and proposes two or three slots. Who reviews: the dispatcher approves the booking and can override any proposal.

The owner must keep credential records current, so add an alert for expiring certifications.

6. Confirm with the customer

Trigger: the dispatcher approves. Action: the customer receives a confirmation with the arrival window, technician name, what to prepare, how to rearrange and any cancellation information you must give. A draft job is created in your field service software where it offers an API or import. Who reviews: automatic, once the template is approved.

7. Updates on the day

Trigger: schedule changes or technician status. Action: day-before reminder, on-the-way message and, if a job overruns, a proposed new window for affected customers. Many field service tools include this: Jobber, for example, has an on-my-way text in its app. Who reviews: the dispatcher approves rescheduling proposals before customers are contacted, and calls vulnerable customers personally.

Run your domain through the email deliverability checker so booking emails don't land in spam.

The workflow at a glance

What stays human

Automation handles the routine flow. These stay with people, consistent with how we describe the boundaries on our page about automation for HVAC, plumbing and electrical firms:

• Any suspected gas leak, carbon monoxide or electrical danger. The system escalates; a person responds.
• Final schedule decisions, especially squeezing in emergencies and moving existing customers.
• Vulnerable customers, such as elderly people or households with no heating or cooling in extreme weather.
• Diagnosis on site, safety readings, unsafe-situation decisions and signing records. The qualified technician owns these entirely.
• Pricing, disputes and complaints.

The aim is a cleaner queue for your dispatcher, not a replacement for them.

Data protection and legal checks

Intake collects addresses, door codes, details about vulnerable occupants and sometimes call recordings. Treat this as a checklist, not legal advice, and check the rules where you operate.

Personal data. In the UK and EU, customer details fall under UK GDPR and the EU GDPR; the ICO's guidance is a practical starting point. In Canada, private-sector businesses generally fall under PIPEDA or a similar provincial law. In the US, state laws such as California's CCPA may apply depending on your size and where customers live. In Australia, the Privacy Act generally exempts businesses with annual turnover of A$3 million or less, with exceptions, according to the OAIC. Collect only what the job needs and set retention periods.

Text messaging. In the US, the Telephone Consumer Protection Act governs automated calls and texts, and the FCC explains its consent rules. Separately, carriers require business texts sent from standard 10-digit numbers to be registered under A2P 10DLC, as Twilio's documentation describes. In the UK, the ICO's direct marketing guidance separates service messages from marketing. Canada's anti-spam law, CASL, has its own rules for commercial electronic messages, set out by the CRTC. Keep booking updates purely about the booking, and don't slip promotions into them.

Call recording. If an AI phone assistant or call system records calls, tell callers. Some US states, such as California under Penal Code section 632, require consent from all parties to a confidential call.

Telling people they're talking to AI. Under the EU AI Act's Article 50 transparency obligations, which apply from 2 August 2026, people must be told when they're interacting with an AI system unless it's obvious, as Cooley summarises. Elsewhere, it's still good practice to say a virtual assistant is taking details.

Vendors. Check each tool's processor agreement, data location and log retention.

How to start small and measure

A sensible order:

1. Map three real jobs, a breakdown, a maintenance visit and an after-hours request, noting where details were lost or retyped.
2. Fix capture and safety screening first, testing the escalation with sample messages before going live.
3. Add triage questions for your two most common job types, refined by what technicians still had to ask on site.
4. Then matching and updates, once credential and duration records are reliable.

Measure qualitatively: ask the dispatcher whether the queue is clearer, ask technicians whether they arrive better informed, and track how many requests still need a call-back for basic details. As our guide to AI agents explains, clear rules and approval points matter more than a clever model.

Make It Flow starts every project by following real jobs before recommending any tool. If you'd like help mapping your own intake, talk to us.

FAQ

What is service call intake?

Service call intake is the process of capturing a customer's request for repair, maintenance or installation and turning it into a job with enough detail to plan the visit. It covers phone, web, email and messaging requests, safety screening, triage questions about the equipment and problem, access notes and contact details. Done well, it means the dispatcher can book from facts rather than calling the customer back.

Can an AI assistant answer after-hours calls for my HVAC or plumbing business?

It can take details, acknowledge the request, ask triage questions and log the job for the morning, which stops requests going unanswered. It should not handle emergencies on its own. Anything suggesting gas, carbon monoxide or electrical danger must trigger approved safety advice, the local emergency number and an alert to your on-call person. Tell callers they're speaking to a virtual assistant.

What questions should intake ask for a no-heat or no-cooling call?

Ask for the equipment type, make and model, any error code, when it stopped, what the thermostat shows and whether breakers or switches have tripped. Ask whether anyone vulnerable is in the home, about property access, parking and pets, and request photos of the data plate and display. Always screen first for gas smells, carbon monoxide alarms, burning or sparking.

Does automated dispatch replace the dispatcher?

No. Automation can filter technicians by credentials, area and availability, estimate durations and propose slots, but the dispatcher approves bookings and handles exceptions. Emergencies, vulnerable customers, schedule clashes and regulated work need human judgement. The benefit is a dispatcher who spends less time chasing basic details and more time on the decisions that genuinely need experience.

Will this work with ServiceTitan, Jobber or Housecall Pro?

It depends on your software and plan. Many field service platforms include request forms, booking confirmations and on-the-way texts, and some offer APIs or imports for connecting other tools. Check what your current system already does before adding anything. Where there's no integration, intake can still feed a structured email or form that the office copies in.

Do I need customer consent to send booking texts?

Rules vary. In the US, the TCPA and carrier registration requirements apply to automated texts. In the UK, service messages are treated differently from marketing under PECR, and Canada's CASL has its own rules for commercial messages. Keep booking texts strictly about the appointment, include your business name and check the rules where you operate before switching texting on.