Guide · Updated October 2026

Field service CRM features: a practical checklist for 2026

Feature lists from vendors are long and look the same. This checklist separates what a service company uses every day from what looks good in a demo, and gives you the questions that reveal whether a product — or a custom build — fits your work.

Guide

Must-have features

  1. One customer and property record with every job, call, estimate, invoice and photo at that address.
  2. Request intake from phone, web forms and marketplaces without retyping.
  3. Dispatch board by technician and day, with drag-to-reschedule and live updates.
  4. Technician mobile app with job details, notes, checklists, photos and signatures.
  5. Offline mode for basements, rural sites and poor coverage.
  6. Estimates on site with options the customer can approve.
  7. Invoicing and payments by card or link, right after the job.
  8. Accounting sync with QuickBooks or your accounting system, both directions where needed.
  9. Recurring service — maintenance agreements that create visits and reminders automatically.
  10. Customer notifications — confirmations, on-the-way texts, reminders.
  11. Roles and permissions for owners, office, technicians and subcontractors.
  12. Reports you actually use: jobs, revenue per technician, unpaid invoices, callbacks.

Nice-to-have features

  • Route optimization (valuable with many daily stops, less so for long jobs).
  • Inventory per truck and parts ordering.
  • Customer portal with history and invoices.
  • Call tracking and recordings on the customer record.
  • Marketing campaigns and review requests.
  • GPS fleet tracking.

Nice-to-haves are where subscription tiers and add-ons grow. Decide which you will really use before comparing prices.

Questions to ask in every demo

  • Show me a job that needs two visits and a second technician. How is it scheduled and invoiced?
  • What does the technician see offline, and what syncs when they reconnect?
  • Show the QuickBooks sync for an invoice that is edited after it was sent.
  • How do I get all my data out, in what format, and at what cost?
  • Which of the features you showed are in my tier, and which are add-ons?
  • What did the price do at renewal for customers like us?

Features that signal you need custom

If your must-have list includes things no platform does the way you work — commercial contracts with progress billing, construction-style job costing, multi-trade jobs, special dispatch rules, an integration with a niche system, or a workflow unique to your trade such as fireplace installs and annual sweeps or glass orders with long lead times — a custom system may fit better. We cover that path on custom field service CRM.

Mistakes we see most often

  • Buying for the demo, not the dispatcher. Polished marketing modules impress owners; the dispatch board decides whether the office is happy.
  • Ignoring data migration. Ask early how customers, equipment history and open invoices will move.
  • Skipping the technician test. Give the app to one technician for a week before signing.
  • Underestimating accounting sync. Edited invoices, partial payments and credits are where most sync problems appear.

How to run the evaluation

  1. Write down your top three daily workflows step by step.
  2. Make every vendor (and any custom developer) walk through those workflows, not their standard demo.
  3. Ask a dispatcher and a technician to join the demos — they will spot problems in minutes.
  4. Compare five-year total cost, not monthly price: TCO worksheet.

Related: ServiceTitan vs custom software, HVAC & plumbing CRM, field service CRM case study.

FAQ

Questions we are asked most

What features should a field service CRM have?

At minimum: a customer and property record, request intake, a dispatch board, a technician mobile app with offline mode, on-site estimates, invoicing and payments, accounting sync, recurring service, customer notifications, roles and reports.

Do I need route optimization?

Only if technicians make many short stops a day. For long jobs or small service areas, a good dispatch board matters more.

What is the difference between field service CRM and field service management software?

In practice the terms overlap. FSM emphasizes scheduling, dispatch and mobile work; CRM emphasizes customers and sales. A good system for a service company does both on one record.

How do I compare a platform with custom software?

Walk both through your own top workflows and compare five-year total cost, including add-ons, workarounds, hosting and support.

Contact

Talk to the people who will build it

Planning a project like this? Describe the system in two minutes — we reply within one business day and send a written scope after a short call.

Get a quote