AI for field service management: what to automate in your support inbox

Why is a field service inbox full of "when will the tech get here?"

Because the answer lives on the technician's phone and the customer can't see it. A homeowner who booked a "between 1 and 5" window has taken the afternoon off work, and every hour without news turns into a call or a text. The office then has to find the job, check which tech has it, see if they've left the last job, and reply. Multiply that by every open job on a busy July afternoon and you've got a support desk that spends its day relaying status. A dispatcher on Reddit put the stakes plainly when asking techs to check in:

"just check in so the customer isn't chewing us out because they were scheduled for 10-12 arrival and it's 2:30 and they haven't heard anything because we haven't been able to get ahold of you"

u/Nggt88, Reddit

I work a support queue every day, so before writing this I asked ChatGPT the question a field service support lead would ask: we send technicians out for HVAC, plumbing and electrical jobs, our inbox and phones are full of ETA, rescheduling, quote, invoice and warranty questions, can AI help and how should we set it up? It read the Jobber, Housecall Pro, ServiceTitan, Microsoft and Salesforce sites plus a stack of software roundups, and came back with a sensible six-bucket plan. Its best line was that AI should never invent an ETA. What it didn't say is where the ETA actually comes from in those tools, which AI features cost what, or what the AI is allowed to do when someone writes "I smell gas". That's what this guide covers.

The questions are simple. The answers are scattered. Service areas and hours sit on your website. Open slots sit in the schedule. Arrival status sits in the job record, updated when the tech taps a button. Quotes and invoices sit in your field service software (the FSM, the system that runs your jobs, dispatch and billing). Warranty terms sit in a PDF, and the install date sits in an old job. An AI can only answer from the one it's connected to.

That last point is the one I see trip teams up most. On a real-traffic trial of eesel on an ecommerce inbox, the support team rewrote most drafts before sending, and when we dug into why, only about 5% of rewrites were the AI being factually wrong. Around 20% were drafts that needed data the AI couldn't see, like order and logistics records. Field service is the same problem with a van in it: connect the AI to the job record, or keep it out of the questions that need one.

What can AI answer, what should it draft, and what stays with a person?

Sort every message by one question: can the AI read the exact answer somewhere you trust, and does it involve danger, money or a decision? If the answer is on a page you wrote, AI answers. If it's in a job record that changes by the hour, AI drafts from that record and the office sends (or answers, once you've connected it and trust it). If someone could get hurt or lose money, a person owns it.

Here's how that plays out across the six topics ChatGPT and every FSM vendor agree fill the queue:

The right-hand column isn't there because AI writes badly. It's there because those are the messages where a wrong reply costs someone money or puts them in danger. The FSM vendors draw the same line in their own tools: Jobber's Receptionist escalates on keywords you set, with the product page using "burst pipe, no heat, or a commercial account" as examples, and Housecall Pro says emergency handling in its CSR AI is "always on". My piece on AI escalation management has more phrases worth routing.

Two lanes hide inside friendly messages. "Quick question about my invoice" can be a billing dispute, which a person should own from the first reply. And "the same noise is back" is a callback, which usually means a warranty conversation and an unhappy customer at once. Route on the words, not the topic, and send angry messages to a person too, as my guide to AI for complaints explains.

Try it on a few real-sounding messages:

Can AI tell customers when the technician will arrive?

Yes, but only by repeating what the job record already says, and that record is only as fresh as the technician's last tap. This is the part of field service AI I'd want every support lead to understand before buying anything.

Here's how the main tools produce an arrival update today:

• Jobber: the technician taps a visit, taps On My Way, picks how far away they are (5 to 60 minutes) and taps Send Text, per Jobber's help center. It's one tap, not automatic.
• Housecall Pro: "A text message will be sent when you click the 'On my way' button," according to its customer notifications guide. The tech can also untick "Notify customer" on a job.
• ServiceTitan: sends reminder texts with a technician bio and can show customers the truck on a map, per its customer experience page.
• Salesforce Field Service: its Appointment Assistant add-on gives customers "real-time updates" about the visit, per the product page.

So in two of the most popular tools for small and mid-sized trades businesses, the ETA starts as a human estimate typed on a phone. That's fine. Techs know how long the last job will run better than any model does. It just means the AI's job is to relay, not to predict. Read "On my way, 20 minutes, sent at 2:10" and say exactly that. Read "scheduled 1-5pm, not started" and say the visit is still booked for that window and a text will come when the tech leaves. Never take "scheduled 1-5pm" and reply "should be there around 3", which is a guess dressed as a fact.

Notice what the vendor AI agents list, too. ServiceTitan's AI Virtual Agent books, confirms and reschedules appointments, but "where is my technician" isn't on its feature list. The best ETA answer in most shops is still the automatic text, sent the moment the tech leaves. If your techs skip the tap, no AI will fix that, and the cheapest win you have is a habit, not software.

If you want a written-inbox AI to read that status itself, check two things. Does your FSM expose the job status through an API a third party can call? And can it send a webhook when the tech taps On My Way? eesel has no built-in Jobber, Housecall Pro or ServiceTitan integration, but its Network Access setting lets the agent look up live data from any API you allow, and a webhook can wake it with the job details when the status changes. Without either, keep ETA replies in draft mode, with the job number attached so the office can answer in one click.

HVAC operators know the data problem better than anyone. On a thread about ServiceTitan's AI dispatching, one commenter summed it up:

"It's only gonna be as good as the data you feed it. I think most AI products out there are too early to be fully useful. Augmentation, sure."

u/LionNotSheep94, Reddit

The same lookup-first rule runs in production at Swiftreg, a UK number plate seller whose instructions tell eesel to report the status a lookup confirmed, never the next step along. A field service desk needs the same line in its instructions: "booked" is not "on the way", and "on the way" is not "arriving at 3". I go deeper on this pattern in my guide to AI for order tracking and in the one on delay notifications.

Which messages should never go to an AI?

Anything where someone could be in danger right now. In HVAC, plumbing and electrical work that list is short and specific, and the official guidance is clear enough that your AI can follow it word for word.

• Gas smell. The US pipeline safety regulator, PHMSA, tells people who suspect a leak to "Leave the area by foot immediately" and to call 911 from a safe location, and warns against using a phone or flipping a switch nearby, per its leak guidance. A customer texting you about a gas smell needs that instruction first and a booking second.
• Carbon monoxide. CPSC's CO guidance says "Never ignore an alarming CO alarm!", to move outside to fresh air, and to call 911. It names furnaces, water heaters and room heaters among the appliances that can produce CO, so this lands in an HVAC inbox more often than people expect. The CDC adds that CO symptoms are often described as "flu-like", which is why "the furnace is on and we all have headaches" belongs on the trigger list too.
• Electrical danger. Sparks, buzzing, a burning smell, a breaker that won't stay on, or water near the panel. Ready.gov warns people not to touch electrical equipment that's wet or while standing in water. Your AI shouldn't troubleshoot any of it. Plenty of HVAC offices already hold their human staff to the same line, as one r/HVAC commenter explained:

"Anything else is qualified personnel only because of injury/damage/death liability."

u/mechanical_marten, Reddit

• No heat in a freeze, no water, active flooding. Not always life-threatening, but always urgent, and usually after hours. These go to your on-call tech, not a queue.

The setup that works is a short list of trigger words, a pre-approved safety reply your owner or safety lead signs off, and an instant alert to a person. Jobber lets you set escalation keywords like "emergency" or "urgent" so the call transfers or you get a text, per its Receptionist help article. Housecall Pro's CSR AI forwards emergency calls or sends a text alert after hours. Do the same on the written side: email and web forms arrive at 2am too.

Luxedo, which sells projection systems to home customers and runs eesel on Gorgias, wrote this rule into its setup. A list of things always go to the team: possible hardware failure, replacement equipment, warranty decisions, refunds or billing, anything about electrical safety, and any customer who asks for a person. Different product, same instinct a field service desk needs.

Where does AI save the most time in field service support?

Before the truck rolls. Answering "when will the tech arrive?" saves the office a minute. Getting the right details before the visit saves a second trip. A tech who shows up to a "my AC is blowing warm air" job without the model number, a photo of the unit or any idea whether the breaker was checked is guessing which part to bring.

This is the job written-channel AI is best at, and the one the phone tools spend least time on. When a customer emails or fills in a web form, AI can reply in seconds with the three or four questions your techs always ask: a photo of the unit and the model and serial plate, when the problem started, whether the breaker and thermostat have been checked, and anything about access, like a gate code, pets or parking. Then it puts all of that in the job notes so the dispatcher and the tech see it before they leave.

Luxedo's setup is the closest example I know in production. Before escalating a ticket, eesel gathers error messages, when it started, what has been tried, and photos, and puts that summary in an internal note so the specialist doesn't have to ask again. It also troubleshoots one step at a time instead of sending a checklist of everything that might be wrong, which matters for trades too. "Have you checked the breaker?" is a fine first question. A twelve-step troubleshooting guide sent to someone with no heat is not.

There's a second, quieter win here: your own technical knowledge. An industrial automation company put its manuals, guides, training material and past support answers behind eesel, with a strict rule that answers come only from those documents and say plainly when they have nothing. Well over twice as many questions now reach the chat as reach the support desk. For a trades business, that's your install guides, your maintenance checklists and the answers your best CSR gives every week, turned into something the AI can quote. My guide to building an AI knowledge base covers what to put in first, and the one on AI for first contact resolution shows how to measure it.

What are field service platforms' own AI tools doing today?

Mostly answering the phone and booking jobs, the job an AI appointment setter does in any industry. I went through the product pages, pricing pages and help centers of the five platforms ChatGPT recommended. Every one leads with booking, and only two publish a price for their customer-facing AI.

A few things stand out. Jobber is the most transparent: the Receptionist help article spells out that a text conversation stays open for 24 hours and counts once, and that at your limit you can pay overages or pause it. Housecall Pro's CSR AI help pages are refreshingly honest that "Even with the best setup, AI can occasionally make mistakes", and they tell you to name price book items specifically ("Repair - Dishwasher", not "Service Call") because that's how the AI matches a request to a price. That tip alone is worth reading if you run Housecall Pro.

ServiceTitan publishes the strongest customer results, all vendor-reported. On its Contact Center Pro page, Bonney Plumbing, Electrical, Heating and Air reports 60% fewer missed calls and a 17% higher booking rate, and one customer on the Virtual Agent page puts its AI booking rate at 80% to 85%. Contact Center Pro is still marked early access, and its omni-channel inbox is "coming soon". Microsoft and Salesforce are enterprise tools with enterprise pricing: Salesforce's Agentforce charges per customer conversation, and its AI add-on at $125 per user covers employee use only. My Agentforce pricing breakdown has the full picture.

Phone AI also carries a risk the vendor pages don't mention: a caller who can't get past it may just leave. One homeowner on Hacker News described exactly that:

"I recently fired a plumber I was trying to contract for a five figure remodel job because his AI receptionist couldn't understand my address and therefore could not schedule the appointment."

CodingJeebus, Hacker News

That's the case for a clear "press 4 for a person" path during business hours, which Jobber supports with its per-time-slot phone menu, and for testing the AI on your own customers' accents and addresses before switching it on.

The gap is the same in all five. These tools are built for the phone and the booking. The written queue, meaning the support email, the web contact form, the warranty thread with photos, the property manager who emails about six units at once, usually lands in a helpdesk or a shared inbox that the trades-focused phone tools from Jobber, Housecall Pro and ServiceTitan don't answer. Texts are their own channel too, covered in my SMS support guide, and WhatsApp in my WhatsApp guide. That's where a helpdesk AI layer earns its place: it works on the tickets you already have, in the tool your office already uses. If missed calls are your biggest leak, buy the phone AI in your FSM first, and use my voice agent guide to check it. If you run Freshdesk alongside your FSM, my post on Freshdesk field service management covers that pairing.

How do you set up AI on a field service support inbox?

Start with the written queue, one service line, and a short list of things the AI must never do. Here's the setup I'd run, in order.

1. Pull your top 20 questions. Export a month of emails, form fills and texts, and count them. My guide to AI for FAQ deflection shows how to sort them. In most trades inboxes, ETA chasers, reschedules, invoice copies and "do you service my area?" fill the top five.
2. Write the safety list first. Gas smell, CO alarm, sparks, burning smell, water near the panel, no heat in a freeze, active flooding. Pair each with the approved reply and the on-call person to alert. Test it before anything else goes live.
3. Write the never list. Never estimate an arrival time the record doesn't show. Never agree to a discount or a price change. Never approve or refuse a warranty callback. Never promise a specific tech. Innr, a smart lighting company on Freshdesk, sends warranty claims, billing, bulk orders and anything the help center doesn't cover to a person with a note explaining why.
4. Give the AI your real knowledge. Service area list, prep instructions per job type, your written warranty, financing terms, membership plan details, and a few hundred solved tickets so it learns how your office actually answers. If you bill through QuickBooks, eesel's QuickBooks integration answers invoice and payment questions from your accounting records and sends the customer a copy. Innr also filters out supplier pitches, courier updates and marketplace notifications before the AI runs, which matters if your inbox gets parts-supplier mail.
5. Verify before you share a record. Invoices, quotes and job details go only to the customer on file. Match the phone number or email on the job before the AI says anything about it.
6. Start with drafts, then let the safe lane answer. Run AI as a copilot for two weeks so your office sees every reply before it goes. Then let it answer service-area, prep and invoice-copy questions on its own, and keep ETA, quotes and warranty in draft mode until it has a lookup you trust. The implementation timeline guide has realistic dates.
7. Test on past tickets before going live. Replay a few hundred real messages and compare the AI's replies with what your team sent. My guide to simulation testing covers how many tickets per topic you need for a fair read.

Measure what changes for the office as well as what the AI handles: the share of messages answered without a person, time to first reply after hours and on weekends, how many "any update?" messages you get per job, and how many jobs needed a second visit for the wrong part. That last one is the number your owner cares about. The pilot scorecard I use has the full list, and the first heat wave or cold snap is a good stress test, as my piece on seasonal support spikes explains.

What does AI for field service management cost?

It depends on which side of the queue you're automating. For the phone, the AI in your FSM is priced per conversation or bundled into a plan, and only two of five vendors publish the number. Jobber's Receptionist is included on Plus or $29 a month for 30 conversations, then $0.79 each. Salesforce charges $2 per conversation. Housecall Pro and ServiceTitan want a sales conversation. Use a vendor checklist to compare quotes on the same terms.

Helpdesk AI for the written inbox is easier to price. eesel publishes its rates on its pricing page: a free plan with 100 credits, then fixed monthly plans where one ticket or chat is one credit however many replies it takes.

A worked example: an HVAC and plumbing company with 15 techs getting 1,000 written messages a month pays $499, or about 50 cents a message, whether the AI answers it or drafts it for the office. Add Jobber's Receptionist at 300 phone conversations and that's $29 plus 270 extra conversations at $0.79, about $242 a month, unless you're on Plus where it's included. Overage on eesel is off by default, and if you turn it on, extra credits are $0.80 each with a cap you set. My breakdown of AI vs human agent cost has the maths for comparing against another CSR hire, and the one on support staffing covers peak season.

Try eesel for your field service inbox

eesel is an AI helpdesk teammate that joins the queue you already run in Zendesk, Freshdesk, HubSpot or Gorgias, or works straight from its own email address and website chat. For an HVAC, plumbing or electrical company, that means it answers service-area, prep and invoice questions from your own pages, collects the photo and model plate before the visit, drafts ETA, quote and warranty replies for your office, and sends gas, CO, sparks and disputes straight to a person. It doesn't plug into Jobber, Housecall Pro or ServiceTitan out of the box, so I'd keep their phone AI for calls and let eesel take the written inbox. It's the pattern Luxedo runs on its home customer queue: one troubleshooting step at a time, diagnostics gathered before escalating, and electrical safety always with the team.

You can try it free with 100 credits and see real drafts on your own tickets before you pay anything. Try eesel.