ServiceNow Field Service Management

ServiceNow Field Service Management puts field work on the same platform as ITSM and CSM. The documented flow is clean: a customer submits a request with a preferred time through a self-service portal, a work order with one or more tasks is generated, tasks are auto-assigned by location, skills, parts and availability, and completion records tasks, parts, expenses and time with a PDF summary attached for audit. The customer gets a text with a link to a map showing the agent current location and an estimated arrival time.

The assignment engine is the standout and it is unusually transparent. Dynamic Scheduling scores candidate agents with configurable weights, default 10 per criterion, across matching skills, matching mandatory skills, skill level gap, matching mandatory parts, agents with the most parts, timezone overlap and several distance variants. You get one configuration per task table, preferred and excluded technicians, and toggles for Auto Assignment and Immediate Assignment; with both off, a dispatcher triggers assignment manually. SLA is a first-class scheduling input rather than a report: an unassignment constraint keeps a task assigned if unassigning would breach SLA in the next five hours, and ordering rules can sort tasks by SLA due date.

Offline is the best-documented of any product in this category, and the honesty is what makes it credible. Offline you can work field service tasks, record time, track asset usage, create part requirements, accept and reject tasks, record travel and work start times, pause and complete tasks, view My Inventory, log incidental expenses, view attached knowledge articles and complete questionnaires. ServiceNow then states the limits: you must pre-download field service data to the app cache and enable offline mode first, you need the wm_agent or wm_dispatcher role, changes queue in an outbox and must sync, refreshing the cache requires going online then offline again, My Schedule is unavailable offline because the underlying remote table is not supported, and SLAs closed offline record the device timestamp and need an administrator to repair the SLA afterwards. That is what a real offline specification looks like.

• Route optimisation needs scoping carefully. Agents can find optimal routes for multiple locations on the mobile task map. Dispatcher-side routing, however, is estimate-based: distance and travel criteria using the Google Maps API or straight-line estimates, falling back to a static Estimated Travel Duration field. There is no documented full route-optimisation engine on the office side.
• No pricing is obtainable. ServiceNow own pricing page returned 403 to automated access, as did its marketing pages. Review aggregators carry conflicting figures which this profile deliberately excludes.

Good fit: enterprises already standardised on ServiceNow for ITSM or CSM who want field work on the same platform, the same CMDB and the same workflow engine rather than integrating a separate FSM product. It is the strongest choice in this category where SLA compliance is contractual and must drive assignment decisions, not just appear in a report afterwards. It is also the right answer when crews genuinely lose connectivity for long stretches and you need a written specification of what works offline before you commit, because ServiceNow publishes exactly that, limitations included.

Poor fit: any small or mid-size contractor. This is platform software with release families, plugins such as Field Service Crew Operations implying modular licensing, and quote-based enterprise pricing that could not even be read. It is also a poor fit if you need quoting, invoicing or customer service-contract management inside the field service product, because none of those could be verified on any ServiceNow page opened during research. And if dispatcher-side route optimisation is a hard requirement, test it: the documented behaviour is travel estimation, not optimisation.

Typical use cases: enterprise IT and facilities field support dispatched from the same platform as the service desk, telecoms and utility field operations with contractual SLA exposure, and crew-based work where the Field Service Crew Operations plugin applies. Budget for sales contact: nothing commercial about this product is publicly readable.