Salesforce Field Service: When Is It Worth It?

Salesforce Field Service is worth it for manufacturers whose technicians handle many short jobs per day. There, scheduling and route optimisation clearly improve the numbers: more jobs per day, less travel time, more appointments kept. With few long jobs, such as commissioning over days or weeks, the benefit is much smaller, and licence costs of $175 per technician and month are harder to justify. Before a quote is signed, it should therefore be clear what kind of field service the company actually runs.

What does Salesforce Field Service do?

Salesforce Field Service is the field service product built on Service Cloud. Salesforce now calls it Field Service and Operations. It covers three parts:

• Scheduling and optimisation. A scheduling engine picks a suitable technician and time slot for every job.
• Mobile app. Technicians see their jobs, assets and history, also offline, and record working time, parts, photos and signatures.
• Documentation. Service reports are created directly from the app. What the standard can do and where it stops is covered in Service Documents: is Document Builder enough?.

Scheduling is the core. According to Trailhead (opens in a new tab), it works with two kinds of rules. Work rules filter out technicians who cannot take a job, for example because a skill is missing. Service objectives rate the remaining candidates, for example by least travel time, earliest slot or preferred technician. Together they form a scheduling policy.

When is Field Service worth it?

Optimisation helps most where there is a lot to optimise. In my experience that depends on the type of work, the locations and the duration of jobs. I see the biggest benefit with:

• Many short jobs per day, such as maintenance, repairs or inspections. A typical example is telecommunications companies whose technicians have up to 16 appointments a day.
• A high share of travel time, because customers are spread across a region.
• Many skills and spare parts that have to match, so the right technician arrives with the right part.
• Committed response times from service contracts that have to be met and proven.

Salesforce backs this direction with its own research. In an article on scheduling (opens in a new tab), Salesforce calls scheduling the biggest efficiency blocker for technicians and writes that 47 percent of appointments do not go as planned. Whoever reschedules dozens of jobs a day saves the most.

When is Field Service not worth it?

With few long jobs the benefit is much smaller. A technician who commissions a plant over two weeks does not need route optimisation. He or she needs a project plan, access to drawings and clean documentation at the end.

Typical cases are commissioning, conversions or overhauls where a team works at one site for days. The difference from 16 appointments a day is big: access to documents, coordination with the customer and a complete acceptance matter more than which technician is where in the afternoon.

For such cases there are alternatives I check before a Field Service licence:

• Service Cloud with work orders and the Salesforce mobile app, if documentation is what is mainly missing.
• A portal with Experience Cloud, if subcontractors or partners report work and exchange documents.
• Planning in the ERP or a project tool, if jobs are more like projects than appointments.

This is the same make-or-buy question as with any other Salesforce product. I describe the approach under make-or-buy and licence forecasts.

How much does Salesforce Field Service cost?

The pricing page (opens in a new tab) lists these prices in October 2026, per user and month, billed annually on Enterprise Edition:

Licence	For whom	List price
Dispatcher	Dispatchers who plan jobs	$175
Technician	Technicians using the mobile app	$175
Field Service Plus	Users who also handle cases	$230
Contractor Plus	Subcontractors	$80 or $32 per login

On Unlimited Edition, Dispatcher and Technician cost $330 according to the footnote, Field Service Plus $380. Add-ons such as Appointment Assistant, which keeps customers informed about arrival times, cost extra.

An example with list prices: 40 technicians and 4 dispatchers on Enterprise Edition are 44 licences at $175, so $7,700 per month or $92,400 per year. Implementation, ERP integration and maintenance come on top.

Two conditions from the small print matter for licence planning. Field Service requires at least one Service Cloud licence, and technicians need at least one dispatcher for scheduling to work. Dispatcher and Technician licences may also not be used for a contact centre or case management. Anyone in the back office who handles cases and plans jobs needs Field Service Plus.

How do I decide?

I start with four numbers from your own field service, before the product even comes up:

1. Jobs per technician and day. If the average is clearly above one, there is something to optimise.
2. Share of travel time in working time. The higher it is, the more route optimisation helps.
3. Number of skills and parts that have to match. The more there are, the harder manual planning gets.
4. First-time fix rate, meaning how often a job is done on the first visit. If it is low because parts or skills are missing, better scheduling helps directly.

These numbers can usually be pulled from the ERP or the existing scheduling tool. If nobody knows them, that is a finding in itself: the basis for any business case is missing, whatever the product.

Then comes the data question. Field Service only schedules as well as assets, locations, skills and availability are maintained. A technician whose skills are recorded nowhere will be scheduled wrongly by the engine.

Where should you start?

Collect the four numbers for one month and one region. If they show many short jobs with a lot of travel, build the business case for Field Service with licences, implementation and maintenance over several years. If they show few long jobs, first check whether Service Cloud, a portal or the ERP can close the gap. What the mobile app can do for technicians today is covered in Field Service mobile: guidance and voice.

Field Service is worth it when your field team runs many short appointments, and rarely when it handles long projects. If you are facing this decision and want an independent assessment, send me a message.