For plumbing, electrical, and HVAC field service teams, the phone is the office. These are the moments dispatch, quote follow-up, and the job report still fall to hand work.
On the tools
The visit is the work. The office is the phone, the route sheet, and the report that used to wait until night. AI agents sit on that office work, not on the wrench in the van.
Inputs: chat booking, phone note, voice note after the job.
Outputs: job draft, route change, service report, invoice.
Human step: coordinator or technician sends what the customer reads.
Before the van leaves
Address, symptoms, photos, and building access still get collected one chat at a time. The building office, the parking bay, and the floor number are the details that make a slot real. A missing access rule sends the van to a door that will not open.
Trigger: inbound chat or phone note with a partial address.
Draft: job card with units, symptom, access rule, parking, and a slot suggestion.
Staff sees: coordinator confirms the price range before the customer treats it as a quote.
Through the working day
Traffic, a job that overruns, and rooftop work in the hottest part of the day pull the route apart. A busy season bunches cleaning and repair on the same book. A waitlist only helps if a cancellation can fill itself without a phone call from the office.
Trigger: overrun message from the technician, or a freed slot on the book.
Draft: re-sequenced dispatch list and new arrival times for customers who move.
Staff sees: a person sends the new time. The technician is not blamed by an automatic message.
After the last job
Before-and-after photos sit in a chat group. The service report, the invoice, the instant payment QR, and the warranty end date are still typed that night. The rate card and the job notes have to match before anyone sends the bill.
Trigger: photos and a voice note after the visit.
Draft: service report, invoice from the rate card, instant payment QR, warranty end date.
Staff sees: technician or office sends the invoice after the amount check.
Monthly contract sites
Recurring maintenance contracts need a visit schedule, site access rules, and compliance certificates on file. The monthly note for the site manager is rebuilt from closed jobs by hand. A missed certificate or a wrong unit count stalls the next visit.
Trigger: contract renewal date or a closed visit on the site.
Draft: next visit list, access rules, and a monthly note from closed jobs.
Staff sees: someone at the company sends the report. This is not a building-control system.
What these businesses usually automate first
AI for plumbers usually starts at the booking or the close-out. The same shape fits an electrician and an HVAC desk. A person still sends what the customer reads.
Intake from chat
What gets in the way
The address, the symptom, the photos, and the building access rules arrive as fragments.
What runs
An agent collects them, offers a price range from your rate card, and opens the job.
What stays with a person
The coordinator confirms the range before the customer treats it as a quote.
Slots that respect the day
What gets in the way
A slot that ignores road time, the technician's skill, van stock, or heat is a slot you will break.
What runs
Suggestions weigh zone, travel, job length, skill, what the van is carrying, urgency, and a cap on outdoor work in the hottest hours.
What stays with a person
The coordinator picks the slot. Urgency such as no water, no power, or a leak over furniture is a rule you set.
Busy season and the quiet ones
What gets in the way
A busy season fills the book. The quieter months are when a maintenance visit is easier to place.
What runs
A waitlist offers a freed slot, and a pre-season note goes to customers you already have.
What stays with a person
You choose who is offered the early visit. We do not claim a queue length we have not measured.
The rest of the day moves
What gets in the way
One long job makes every later arrival wrong, and the next customer hears nothing.
What runs
The route is re-sequenced, and a new arrival draft is prepared for the customers who move.
What stays with a person
A person sends the new time. The technician is not blamed by an automatic message.
Photos, report, invoice
What gets in the way
The proof of the visit is a photo in a group chat, and the invoice is a separate chore.
What runs
Photos and a voice note become a service report, an invoice, and an instant payment QR, with the warranty end date logged.
What stays with a person
The technician or the office sends the invoice. Amounts are checked against the rate card, not invented by the draft.
Maintenance contracts
What gets in the way
Buildings, offices, and shops expect a schedule and a monthly note for the person who manages the site.
What runs
The contract generates the visits and a monthly report from the jobs that were closed.
What stays with a person
Someone at the company sends the report. This is not a building-control system.
Van stock
What gets in the way
Refrigerant, capacitors, fittings, and breakers run out on the van, and the warehouse hears about it late.
What runs
A low line on a van or in the warehouse opens a restock task.
What stays with a person
Purchasing approves the refill before an order is placed.
What the coordinator sees
The booking is a draft job. The route change is a draft message. Neither goes out alone.
Chat
Two bedrooms, AC not cold, floor 28. The building office needs names before 10. Parking is level B2.
Agent suggestion · awaiting approval
I have the unit count, the symptom, the floor, the access rule, and the parking. The morning slot is a suggestion until you confirm the technician.
Job draft
Units
Two
Symptom
Not cold
Access
Floor 28, names before 10
Parking
Level B2
Slot
Suggestion only
Phone note
Shop on the main road, no water since morning, they can wait until after lunch if the leak is contained.
Agent suggestion · awaiting approval
I marked it urgent and held a technician who already has a job in that zone. I did not promise an arrival.
Priority held
Issue
No water
Zone
Same area
Urgency
Same day
Promised
No
Technician
This condenser is taking another hour. The 2pm is a building two zones away.
Agent suggestion · awaiting approval
I drafted a later arrival for the 2pm and a nearer job that can move up. Nothing is sent until you approve the new order.
Route change
Delay
About an hour
Next customer
Drafted a new time
Sent
No
Decides
Coordinator
Voice note
Filter washed, gas topped, both rooms cooling. Photo of the gauge is in the group.
Agent suggestion · awaiting approval
I drafted the report and the invoice from the rate card, with an instant payment QR. The warranty date is filled from the contract. You send it.
Close-out draft
Work
Clean and gas
Invoice
From the rate card
QR
Instant payment QR, in the draft
Sent
No
How it fits into existing systems
An agent does not act outside the rules you set. Internal reading can run alone. A customer message or a payment waits for one click. A script, not the model, checks the math.
Level 1
Acts on its own
Internal reading only. The agent can read a document, parse it, and check stock or a record without changing it. Nothing is sent to a customer, and nothing moves money.
Level 2
Waits for a person's approval
A customer-facing message, and anything that moves money, waits for one click in team chat or in the ERP. The agent prepares the draft. A person approves it before it is sent or posted.
Level 3
A script checks the numbers
A deterministic script, not the model, verifies the math. It checks tax calculations, invoice totals, payment slips, and date formats against the rules of the business. If a check fails, a person gets the case.
Personal data stays in the tools you already use. The agent writes a log of what it read and what it changed. We can sign an NDA before reviewing any workflows or data.
Systems we already run
These run at N2o. The lead system is the pattern for finding building managers and repeat customers. A person still takes the conversation.
Lead sourcing, qualifying, and contacting
Finding buyers by hand does not keep up. Someone has to search, judge who is worth a note, and send the first message.
What runs
A system we built for N2o sources leads, qualifies them, and sends the first contact.
What a person still does
A person reviews the outreach messages before pressing send, and reads the replies to take the conversations worth a meeting.
Built to handle 200+ leads a day.
The lead list N2o runs for itself.
LinkedIn posts, drafted from live sources
Posting on a schedule means someone has to watch the field, notice what changed, and write.
What runs
An automation checks a set of sources, studies the trends, and proposes LinkedIn posts that are ready to publish.
What a person still does
A person reviews and edits the draft before posting it. Nobody posts blind, and nothing goes out on its own.
Drafts N2o prepares before anyone posts.
Blog articles, from the same pipeline
A longer article needs the same research, and it stalls when nobody has a free afternoon.
What runs
The same kind of automation checks sources, studies the trends, and proposes article drafts.
What a person still does
A person edits the draft and publishes it. The draft is not the finished article.
The article pipeline for the N2o blog.
Automated order intake
Orders arrive as chat messages, emails, PDFs, and notes that were never meant to look official.
What runs
The intake reads the request, holds anything unclear, and creates a quotation or sales order in the system the team already uses.
What a person still does
A person handles missing quantities, unknown parts, and unusual commercial terms.
More than one way to build it, when both are honest
A written list of what not to automate
Tasks where the return is negative or not measurable
The example fee is credited if you proceed to a build
Questions from plumbing, electrical, and HVAC teams
What happens when a customer calls or sends a chat message while the team is out on a job?
The message can become a booking draft with the address, the symptom, and a proposed slot. The coordinator approves it before anyone is promised a time. The technician on the tools is not pulled off the job to type the reply.
Does this cover electricians and HVAC, or only plumbers?
Yes. Plumbers, electricians, and HVAC teams share the same booking, route, and close-out work. We scope the trade you actually run.
Does this automate office dispatch and maintenance contracts, or building thermostat controls?
Office dispatch and maintenance contracts. We do not install or run building controls, thermostats, or plant equipment. The work is the schedule, the route, the job report, and the monthly note for customers on a contract.
How do routes treat heat and traffic?
Suggestions can cap outdoor and rooftop jobs in the hottest hours, cluster work by zone, and leave room for the drive. You set the cap. We do not publish a minutes-per-job figure before we have seen your diary.
What happens in a busy season?
Cleaning and repair requests bunch up. A waitlist can offer a slot when someone cancels, and an earlier note can offer maintenance to customers you already have, before that rush. We do not quote a wait time we have not measured.
Who sends the invoice?
A person, with one click before it is sent. The draft uses your rate card and can include an instant payment QR. A deterministic script checks that the amount matches the card, including tax where that applies. If the slip or the amount does not match, it waits. The model does not decide that a number is correct.
Where does customer data sit?
In the tools you already use for jobs and invoices. Access and personal-data rules are agreed before the build. We do not start by copying your book into a separate product. We can sign an NDA before reviewing any workflows or data.
Which languages do you work in?
English is preferred. We can also work in French, and we can arrange Thai speakers if really required. A person still checks anything that goes to a customer.
How long until something is running?
Most workflows are running in 2 to 4 weeks. The exact timing depends on the size of the company and the size of the task.
Is the call free, and how is a workflow priced?
The call is a free 30-min Workflow ROI Blueprint for one repeated job. The AI audit and roadmap is a separate paid service. An informational example for one automated workflow is $2,000 to $5,000+ per workflow. It varies by workflow complexity and the systems it touches. Training is $1,000 to $2,500, varying by team size and number of sessions. An AI audit and roadmap is $750 to $1,500, varying by company size and number of teams, and that fee is credited if you proceed to a build. Prices shown on this site are informational examples only and will differ from project to project. At handover you own the code, the prompts, and the accounts, with no vendor lock-in. Optional monthly care covers drift when document layouts, supplier formats, or APIs change.
Book a call for a free 30-min Workflow ROI Blueprint
Bring the repetitive task that costs your team the most hours every week.
Email or call. A person reads every note and says whether that work is worth automating.