Stack map for field service ops (Oct 2026): inventory AI seats across FSM, CMMS, fleet, construction, and chat

What this how-to covers

Field service companies rarely buy one AI tool on purpose. The FSM adds an AI receptionist, a business-questions assistant, and an agent that drafts quotes; the CMMS adds AI work orders and preventive-maintenance drafts; the telematics platform adds AI coaching and route suggestions; the construction tool adds agents for RFIs and daily logs; someone signs up for a separate after-hours answering service; and every coordinator already has a chat assistant. A year later, three tools can text the same customer about the same visit and nobody knows which one booked it. This how-to builds one table — Job | Tool | Owner | Cost/mo | Overlap | Decision — for the six jobs where that overlap is most common.

It is an inventory, not a ranking. Fill Cost/mo from your own invoices, write overlaps in plain sentences, and add a column for who approves: every AI-booked job, every reschedule and cancellation, every quote a customer sees, every work order created or closed, and every coaching note about a driver or CSR. AI drafts and suggests; a named person approves. An AI-drafted quote or work order isn’t accurate until its owner has checked it, an AI receptionist is not a licensed technician, and no customer PII goes into a general chat tool.

How to inventory field-ops AI seats

Examples at a glance: each feature has a concrete example from a real job plus a short Try this you can run this week.

1. Build the blank table (primary)

What it is: Start with six rows and six columns, and leave cells blank until you have a source: an admin seat list, an invoice, or the person who uses the tool. The six jobs: FSM (ServiceTitan, Jobber, Housecall Pro, Workiz, Service Fusion, Salesforce Field Service, Dynamics 365 Field Service), CMMS or EAM (MaintainX, UpKeep, Limble, Fiix, IBM Maximo, Facilio), fleet telematics (Samsara, Motive, Geotab), construction project tool (Procore, Buildertrend), answering AI (the FSM’s own — ServiceTitan Virtual Agent, Jobber Receptionist, Housecall Pro CSR AI, Workiz Genius — or a separate service), and the chat assistant (ChatGPT, Claude, or Gemini seats used for quotes, notes, SOPs, and customer emails — see ChatGPT for field service ops and Gemini for field service ops).

Concrete example (operations manager at a 70-person HVAC, plumbing, and electrical company) Illustrative: an operations manager fills the table over two afternoons. Phone answering shows up in three rows — the FSM’s AI receptionist, an after-hours answering service on a card, and a chat assistant one CSR uses to draft text replies — and route planning appears twice, once in the FSM and once in the telematics platform.

Try this

Primary workflow:

Build Job | Tool | Owner | Cost/mo | Overlap | Decision blank for: FSM, CMMS, fleet, construction, answering AI, chat assistant.

2. Owners and Cost/mo from invoices

What it is: For each tool, write one owner — the person who can cancel it — and the monthly cost from the invoice, contract, or card statement. If you can’t find it, write "Unknown — check bill". Don’t fill costs from list prices. Field-service tools price in units that don’t compare: per technician, per office user, per asset or site, per vehicle or device, per AI conversation or minute, per credit, or a quote. Several vendors reviewed today publish no prices at all — ServiceTitan, Samsara, Motive, Procore, and Buildertrend among them — and others publish a starting price that says little about a negotiated contract. Our dated reviews note what each vendor showed on 12 October 2026, but your bill is the only number that belongs in this column.

Concrete example (office manager gathering costs) Illustrative: an office manager finds the FSM on an annual per-technician contract, the AI receptionist billed as an add-on per conversation, telematics on a three-year hardware-plus-subscription agreement, and the CMMS on monthly seats. She writes "bundled — ask account manager" for the receptionist line inside the FSM renewal instead of guessing.

Try this

Costs from invoices only:

For each of the six jobs, name the owner and Cost/mo from invoices only. If missing, write Unknown — check bill. Do not invent prices, technician counts, or conversation volumes.

3. Mark overlaps in plain language

What it is: For each job with two or more tools, write one sentence about what both do — for example, "The FSM’s AI receptionist and the answering service both book after-hours calls into the same calendar." Common field-service overlaps: phone answering and booking in the FSM and a separate service; route planning in the FSM and the telematics platform; work orders for your own equipment in both the FSM and a CMMS; AI answers about the business in the FSM assistant (ServiceTitan’s Atlas, Jobber’s Custom Report Builder) and in a chat assistant fed exported Sheets; multi-stage jobs in a construction tool and in the FSM’s project features; and call review in the FSM alongside driver coaching in telematics, both producing notes about people.

Concrete example (service manager reviewing the table) Illustrative: a service manager finds the same remodel tracked in the construction tool and in the FSM’s new project view, each updated by a different coordinator. She flags it for a decision first, because a crew went to the wrong address last month when the two schedules disagreed.

Try this

One sentence per overlap:

Wherever two tools share a job, write what both do in one sentence — for example, both book after-hours calls. Ask each tool’s owner to confirm it before anyone suggests dropping a seat.

4. Add who approves and the data rules

What it is: Add two columns: Who approves and Data rules. Many field-service tools can now act, not just draft — book a job, reschedule or cancel an appointment, text a customer about an estimate, create or close a work order, flag a driver or CSR for coaching — and some can do it on a schedule. For every tool, name the person who approves each action it can take, and write what data may go in: sanitized exports and approved procedures, yes; customer names, phone numbers, addresses, gate codes, payment details, or a tech’s notes about a household in a general chat tool, no. September’s FSM changes show why this matters — see What’s new in ServiceTitan (Sep 2026) for separate reschedule and cancel permissions on the Voice Agent and What’s new in Jobber (Sep 2026) for Teammate routines that can reschedule a day.

Concrete example (operations manager) Illustrative: an operations manager fills the two columns and finds the AI receptionist can cancel two job types without a person, and that a dispatcher pastes whole tickets, addresses included, into a chat assistant to draft notes. She makes the CSR manager the approver for cancellations, turns those off, and moves note cleanup to sanitized exports only.

Try this

Who approves, what goes in:

For each tool, write who approves bookings, reschedules, cancellations, quotes, and work orders, and one line on what data may go in. Have the operations manager sign off on the two columns.

5. Write one-sentence decisions

What it is: Start with the two rows that overlap most — answering AI and the chat assistant — and write a decision for each in one sentence: keep both with a clear split, consolidate on one, or pause one for 30 days. Name the person who owns the follow-up and the renewal date. If anyone built a custom GPT for quotes or dispatch notes, include it here: OpenAI retires custom GPTs on December 11, 2026, and our ChatGPT for field service ops guide covers moving that work into a project. A decision is not a cut; it is a statement of which tool owns which job.

Concrete example (owner before a renewal) Illustrative: an owner writes, "The FSM’s receptionist owns after-hours booking for three job types; the answering service owns emergency calls only; chat assistants draft internal notes from sanitized exports." He pauses the answering service’s overflow line for 30 days and sets a reminder two months before its renewal.

Try this

One sentence, one owner:

For the answering AI and chat assistant rows only, write a Decision in one sentence each (keep both, consolidate, or pause). Name who owns the follow-up date and note any renewal date.

Pricing context (October 2026)

This how-to is dated 12 October 2026 and is not a price sheet. Field-service tools price per technician, office user, asset, vehicle, AI conversation, credit, or quote, and many publish no prices at all. Our dated reviews record what each vendor listed when we checked today: ServiceTitan, Jobber, Housecall Pro, Workiz, Service Fusion, MaintainX, UpKeep, Limble, Fiix, IBM Maximo, Facilio, Samsara, Motive, Geotab, Procore, Buildertrend, Salesforce Field Service, and Dynamics 365 Field Service. Fill Cost/mo from your invoices.

Optional structured help: $9 toolkit spreadsheet or $19 toolkit audit.

Uncertainty: Plan names, AI add-ons, conversation and credit pricing, and bundles change often, and several field-service vendors moved AI features between packages or into Private Preview, Early Access, or beta in September 2026 (our dated notes explain each one). Which features count as AI, which can act without a person, and which are on by default differs by vendor and contract. Always verify on the vendor’s live page and your bill before budgeting. This is product education, not legal, safety, or licensing advice.

When it’s useful (honest take)

Useful when field ops pays for more than one AI surface and you suspect several tools answer the same calls, plan the same routes, or draft the same quotes.

Useful when you need to show an owner, insurer, or auditor who approves every AI booking, cancellation, quote, and work order.

Less useful when you have one FSM, one phone process, and one chat seat with clear jobs. Soft $19/$9 only if overlaps are real.

Related options (educational)

FAQ

What is a field-ops stack map?

One table that lists each field service job (FSM, CMMS or EAM, fleet telematics, construction project tool, answering AI, chat assistant), the tool that does it, its owner, its monthly cost from your invoices, overlaps with other tools, and a one-sentence decision.

Which jobs should we inventory first?

Answering AI and the chat assistant, then route planning. They overlap most often, because the FSM, a separate answering service, and chat assistants can all answer or draft replies to the same customer, and the FSM and telematics can both plan the same day.

Should we use list prices for Cost/mo?

No. Use invoices, contracts, or card statements. Field-service tools price per technician, user, asset, vehicle, conversation, or credit, and many are quote-only or bundled. Write Unknown — check bill when you can’t find it.

Why add who approves?

Because several tools can now book, reschedule, cancel, text customers, or close work orders, some on a schedule. A named person should approve each of those actions, and an AI-drafted quote or work order isn’t accurate until its owner has checked it.

When do the $9 / $19 toolkit offers help?

Only after your own table shows real overlap between field-ops tools. The $9 spreadsheet gives you the columns ready to fill; the $19 audit is a second look at a table you have already filled. Neither is needed if each job has one tool and one owner.

Optional next step (if seats overlap)

If field ops already pays for overlapping AI across the FSM, CMMS, telematics, construction tool, answering service, and chat, map that before you buy another assistant. Map the overlap with the $19 AI toolkit audit or the $9 AI toolkit spreadsheet. Email Audit $19 or Toolkit spreadsheet $9.

Checkout is live via Stripe. After you pay, we email delivery (spreadsheet) or intake next steps (audit).

Related: ServiceTitan AI · Jobber AI · Housecall Pro AI · MaintainX AI · Samsara AI · Procore AI · Gemini for field service ops · What’s new in ServiceTitan (Sep 2026) · What’s new in Jobber (Sep 2026) · Workiz AI · Service Fusion AI · UpKeep AI · Limble AI · Fiix AI · IBM Maximo AI · Facilio AI · Motive AI · Geotab AI · Buildertrend AI · Salesforce Field Service AI · Dynamics 365 Field Service AI · ChatGPT for field service ops · Stack map for IT ops · Stack map for support ops · Three checks before another AI seat · ops hub