Field Service Lightning Licensing Costs Explained

Field Service Lightning (now often marketed as Salesforce Field Service) layers three separate license types on top of a standard Salesforce org — dispatcher, mobile technician, and contractor — each priced differently, with scheduling optimization sold as a further add-on. Teams that scoped a pilot for a handful of technicians often find the per-technician math doesn’t stay flat as the crew grows.

Where the field service bill comes from

• Dispatcher licenses. The console users who assign and manage work orders carry a full Service Cloud-tier cost, separate from the technicians they’re scheduling.
• Mobile technician licenses. Each field technician using the mobile app to view work orders, capture signatures, and update job status needs their own license — a cost that scales linearly with crew size, including seasonal and contract technicians.
• Scheduling optimization add-on. The automated, rules-based scheduling engine that actually optimizes routes and technician assignment is typically priced as an additional per-user add-on on top of the base Field Service license.
• Contractor/partner technician access. Subcontracted technicians who need work-order visibility but aren’t full employees often require a separate, still-billed license tier rather than free guest access.

Why growing field teams feel this first

A field service org that starts with five technicians and scales to fifty hasn’t changed its workflow — it’s just added headcount, much of it seasonal or contractor-based. Because every one of those additions is a licensed seat, field service cost tends to scale in lockstep with crew size in a way that back-office CRM seat growth usually doesn’t, since back-office headcount grows more slowly than field crews during a busy season.

Salesforce Field Service vs. a custom dispatch tool

	Salesforce Field Service Lightning	Custom-built dispatch & technician app
Cost driver	Per dispatcher + per technician + scheduling add-on	Flat monthly fee, no per-technician billing
Best fit	Deep native integration with existing Salesforce Service Cloud case data	Standalone dispatch, mobile work-order, and technician workflows
Seasonal scaling	Cost rises with every seasonal technician added	No per-technician penalty for seasonal crew growth

Where the fix actually lives

Field Service Lightning is a strong fit when work orders need to stay tightly wired to existing Salesforce Service Cloud case history and account data. It’s a weaker fit when the core need is simply getting technicians a mobile app for job status, signatures, and routing — work a custom-built application can deliver on a flat fee regardless of crew size, still syncing back to Salesforce where that record matters. See how to reduce CRM licensing costs for the seat-based version of this pattern, and field service dispatch software per-seat costs for how this compares to standalone (non-Salesforce) dispatch platforms.

Frequently asked questions

Can seasonal technicians be added and removed to control cost?

Yes, most editions support adding and deactivating licenses as crew size changes seasonally — but that requires someone actively managing the roster every season, which many teams don’t do consistently.

Is the scheduling optimization add-on required?

No — teams can run Field Service with manual dispatch and skip the optimization engine, though that shifts scheduling effort back onto the dispatcher rather than automating it.

Does moving technician workflows off Salesforce lose the case history link?

Not necessarily — a custom-built technician app can still read and write work-order status back into Salesforce as the system of record, so case history stays intact even though the day-to-day technician app lives outside the platform.