The category of software that coordinates scheduling, dispatch, routing, mobile execution, and analytics for technicians who work outside of a fixed office or store.
FSM is the operational system of record for field work. It assumes that the unit of work is a job that happens at a specific place and time, performed by a technician with specific skills and parts. It is distinct from CRM (which centers the customer record) and ERP (which centers the financial and inventory record). Modern FSM platforms add AI to scheduling, dispatch, and customer communications.
The act of assigning a specific job to a specific technician and sending the job to that technician in real time.
Dispatch is the difference between an assignment plan and a working day. A dispatcher (or an automated dispatch engine) handles arrivals, no-shows, traffic, cancellations, and emergencies in real time. Manual dispatch breaks down past ~20 technicians a day; AI-driven dispatch evaluates thousands of reassignment options per minute and keeps the day on track.
The process of matching jobs to time windows and technicians ahead of the day they happen.
Scheduling is the planning layer above dispatch. It answers 'who, when, and for how long?' based on skills, location, parts availability, customer SLAs, and time-zone constraints. Sophisticated FSM platforms score thousands of assignment combinations per minute and optimize across the whole day, not job by job.
The computation of drive sequences that minimize windshield time and maximize jobs per technician per day.
Route optimization factors in traffic, time windows, vehicle constraints, technician skills, and parts pickups. Done well, it lifts jobs-per-day by 15-30% without adding headcount. Done badly (or skipped entirely), it leaves capacity stranded in traffic.
The structured record of a single job to be performed in the field, including customer, location, scope, parts, and SLA.
The work order is the unit of work in FSM. It originates from a sales order, a service ticket, a warranty claim, or a recurring maintenance contract. A complete work order carries every piece of information the technician needs to complete the job in one visit, including photos of the install location, customer instructions, and any safety requirements.
A contractual commitment to a measurable level of service, typically expressed as an arrival or resolution time.
Common FSM SLAs include arrival within 4 hours of dispatch, resolution within 24 hours of FNOL, or a guaranteed appointment window of 2 hours. SLA breaches usually carry financial penalties, so dispatchers monitor at-risk SLAs in real time and re-route to protect them.
In insurance, the moment a policyholder reports a claim for the first time — the trigger event for assistance and inspection workflows.
FNOL is the start of the SLA clock for insurance assistance and claims. FSM platforms used in insurance route FNOLs to the right inspector or assistance technician, dispatch the visit, and capture evidence on a mobile app. Time-to-resolution from FNOL is a top operational KPI for insurance carriers.
The percentage of jobs resolved completely on the first visit, without a return trip.
First-time fix rate (FTFR) is one of the most important FSM KPIs because every return visit costs travel, parts, and customer satisfaction. Top operators run FTFR above 85% by combining skill-based dispatch, parts forecasting, and structured pre-job checklists. FSM platforms surface FTFR by technician, job type, and customer for targeted improvement.
The percentage of a technician's paid hours that are spent on billable, customer-facing work.
Utilization is the operational health metric for any field workforce. Idle time, excessive travel, no-shows, and rework all erode utilization. Healthy enterprise field operations run 65-80% utilization for employed teams; pure contractor models can run higher because pay is per-job rather than per-hour.
The hours a technician spends driving between jobs rather than performing work.
Windshield time is unavoidable but minimizable. It is the single biggest lever for utilization in geographically dispersed operations. Route optimization, density planning, and zoning are the main tools to reduce it. A 10-percentage-point reduction in windshield time typically translates to one additional job per technician per day.
A field operation that uses both employed (W-2) technicians and contracted (1099) technicians on the same platform.
Blended workforces are the dominant model in LATAM service operations. They combine the SLA control of employees with the elastic capacity of contractors. An FSM platform that supports blended operations gives each technician the same dispatch UX while differentiating on onboarding, payment, and compliance workflows.
The workflow that calculates how much an external contractor is paid for completed jobs and pays them on a defined schedule.
Contractor reimbursement in FSM combines job pricing, completion validation (photos, signatures, GPS), deductions for SLA misses, parts cost recovery, and disbursement to the contractor's payment account. Done well, it pays contractors within days of job completion and is a competitive advantage for keeping good contractors loyal.
Using a technician's GPS location to automatically trigger workflow events when they enter or leave a defined area.
Common geofencing events: clock in when arriving at the customer site, start the SLA clock on visit start, push the customer an 'on the way' message when leaving the previous job. Geofencing is especially valuable in compliance-heavy workflows where proof of presence matters.
The technician-facing mobile application used to receive jobs, navigate, capture work, and close out completion evidence.
A real FSM mobile app is offline-capable, optimized for one-handed use, and built around the technician's day — not for office users. Core capabilities include work order details, navigation, parts lookup, photos, customer signatures, payments, forms, and chat with dispatch. Adoption breaks if the app feels like a CRM screen.
The single source of truth for a given dataset — typically the CRM for customers and the ERP for finance.
In a healthy enterprise stack, the system of record holds the canonical version of the data, and downstream systems sync from it via APIs. CRMs are systems of record for accounts and contacts; ERPs are systems of record for invoices and inventory. FSM platforms operate as systems of execution that integrate with these systems of record.
A specialized operational platform that performs work and writes outcomes back to upstream systems of record.
FSM platforms are systems of execution: they take a work order from a CRM or ERP, dispatch and execute it, then write back the outcome. The model decouples the heavy operational logic from the CRM/ERP, reducing customization risk and accelerating deployment. Most enterprise field operations need both kinds of system, integrated.
Assigning jobs only to technicians who hold the certifications, training, and equipment required to complete that specific job.
Skill-based dispatch is essential for regulated work (gas, electrical, refrigerant), brand-certified installs, and warranty work. The FSM platform maintains a skill matrix per technician and excludes incompatible matches from dispatch automatically.
A customer-facing time window for booking a service visit, computed from live technician capacity.
Availability slots are how an FSM platform turns operational capacity into customer-friendly booking choices. A real-time slot engine guarantees that the slot offered will actually be honored. Bad slot engines overbook the day, generate no-shows, and erode trust.
Forecasting future demand for field jobs and proactively allocating workforce capacity before the demand arrives.
Predictive capacity planning combines historical patterns, seasonality, weather, marketing pipeline signals, and contracted SLAs into a forward demand curve. Operations leaders use it to hire, train, redistribute geographic coverage, and onboard contractors before a capacity crunch hits. AI-native FSM platforms automate the heavy lifting.
The capture, qualification, deduplication, and routing of service-demand leads from multiple channels into a unified pipeline.
Lead management in FSM is different from sales-pipeline lead management. The lifecycle is shorter, the conversion rate is higher, and the next step is a scheduled visit rather than a sales meeting. FSM lead management spans web forms, WhatsApp, contact centers, and partner APIs, and feeds directly into scheduling.