Salesforce Field Service – formerly called Field Service Lightning (FSL) – is Salesforce’s field service management platform for organisations that dispatch technicians, service agents, or field workers to customer sites. It extends Service Cloud with Work Order management, technician scheduling and dispatch, a mobile app for on-site execution, and operational analytics. Field Service fits organisations managing equipment installation and maintenance, HVAC and facilities service, IT infrastructure and hardware support, medical device servicing, and any operation where work happens at customer locations. This guide covers the core Field Service objects, the scheduling and dispatch system, mobile app capabilities, and the setup sequence for a standard Field Service deployment.
The best guide is the one that makes field service feel more manageable.
A useful explanation should help the reader see where the tool helps day-to-day work.
That means the guide should focus on practical service delivery rather than generic platform terms.
For many organisations, the value is in keeping the field operation tied to the customer record.
It should also show how scheduling and work assignment fit into the broader service process.
A good guide should explain what the product is designed to support and why field visibility matters.
That makes it an important tool for businesses with field operations.
Salesforce Field Service Lightning is useful because field teams need a CRM that can support scheduling, dispatch, and service work outside the office. It helps organise work that happens on-site rather than only in a sales desk environment.
Field Service Core Objects
Work Orders
The Work Order is the central Field Service record – the task that needs to be completed at a customer site. Work Orders are typically created from Service Cloud Cases (a customer reports a problem ? a Case is created ? a technician is dispatched via a Work Order) or directly from Account and Asset records for planned maintenance.
Work Order fields:
- Account and Contact: the customer site and contact person
- Service Territory: the geographic area where the work is performed
- Work Type: the type of service task – Installation, Preventive Maintenance, Repair, Inspection
- Priority: determines scheduling urgency
- Service Appointment: the scheduled date/time and assigned technician
- Status: New ? Scheduled ? Dispatched ? In Progress ? Completed ? Closed
- Duration: estimated time to complete the work
- Required Skills: skills the assigned technician must have to complete this Work Order
Work Order Line Items are sub-tasks within a Work Order. For a complex installation, each component is a separate Line Item with its own completion status. Work Order Line Items allow granular tracking when a single site visit involves multiple discrete tasks.
Service Resources
Service Resources represent field technicians – they are Salesforce User records linked to a Service Resource record with field service-specific attributes:
- Skills: the technical skills this technician possesses (Electrical, HVAC, Networking, Certified Crane Operator) – used in skills-based scheduling to match the right technician to each Work Order
- Service Territories: the geographic areas this technician serves
- Resource Type: Technician (individual worker), Crew (a group working together), or Asset (equipment or vehicle, for tracking equipment alongside workers)
- Availability: working hours, vacation, capacity for simultaneous appointments
Service Territories
Service Territories define the geographic coverage areas for field service operations – states, cities, postal code ranges, or custom regions. Territories serve two purposes:
- They define which Service Resources operate in which areas
- They are assigned to Work Orders to indicate where the work is needed – enabling scheduling systems to match Work Orders with Service Resources in the correct territory
Territories have Operating Hours – the hours during which Service Resources in the territory are available and appointments can be scheduled. Both the automated scheduling engine and the Dispatcher Console respect these Operating Hours.
Service Appointments
A Service Appointment is the scheduled instance of a Work Order. It records which Service Resource is assigned, the scheduled start and end date/time, the appointment status (Scheduled, Dispatched, In Progress, Completed), and the actual arrival and departure times logged by the technician.
A Work Order can have multiple Service Appointments – a repair visit, a parts delivery visit, then a completion visit – each tracked separately with its own scheduling and status.
Scheduling and Dispatch
The Dispatcher Console
The Dispatcher Console is the field service operations interface – a map-based dashboard that dispatchers use to view technician locations, current appointments, unscheduled Work Orders, and the team’s daily schedule.
Console panels:
- Map: shows real-time technician locations (from mobile app GPS), appointment locations, and travel routes. Dispatchers drag-and-drop appointments from the unscheduled queue onto technician timelines on the map.
- Gantt chart: a timeline view of each technician’s day – appointments shown as blocks, travel time shown between appointments, available slots visible as gaps
- Appointments panel: unscheduled appointments waiting for dispatch, filtered by territory, work type, or priority
- Team panel: all Service Resources in the selected territory, their current status (en route, on-site, available), and appointment count for the day
Automated Scheduling (Einstein Field Service)
Automated scheduling (Setup ? Field Service ? Global Actions ? Scheduling Policies) uses Einstein AI to suggest the best technician for each appointment. The scheduling engine considers:
- Skill matching: only suggest technicians with the required skills
- Territory: only technicians in the Work Order’s territory
- Travel time minimisation: reduce total travel time across the day’s appointments using route optimisation
- Resource availability: respects Operating Hours, existing appointments, and resource capacity
- SLA compliance: prioritise scheduling so appointments finish before SLA deadlines
Dispatchers can invoke automated scheduling two ways:
- Book Appointment button on a Service Appointment: presents the best available timeslots with recommended technicians for dispatcher selection
- Optimise action on the Dispatcher Console: re-optimises all unscheduled and future appointments for the selected day and territory, reorganising the schedule to reduce total travel time across all technicians
Work Types and Scheduling Policies
Work Types (Setup ? Field Service ? Work Types) are templates that pre-populate Work Orders with standard configurations – estimated duration, required skills, and scheduling policy. Set up a Work Type for “Annual HVAC Inspection” with Duration = 2 hours, Required Skills = HVAC Certified, and a Scheduling Policy that requires appointment within 14 days, and any Work Order of that type automatically inherits those parameters. Dispatchers don’t need to specify them manually for every order.
Scheduling Policies define the criteria used when automated scheduling selects a technician. Policies are configurable priority weightings:
- Primary: match skills, then reduce travel time
- Alternative: if no skilled technician is available in the territory within SLA, escalate to the nearest technician in an adjacent territory
- Customer-preferred technician: always attempt to schedule the technician who last served this account (relationship continuity)
Salesforce Field Service Mobile App
The Field Service mobile app (iOS and Android) is the technician’s operational tool on-site:
- Appointment list: the technician’s daily schedule in order, with addresses and estimated travel time for each appointment
- Navigation: one-tap launch of mapping directions to each appointment from the technician’s current location
- Status updates: technicians update appointment status (En Route, On Site, Work Complete) from the app – these update the Service Appointment record in real time, giving dispatchers and customers live status visibility
- Work Order execution: complete Work Order Line Items, capture photos (attached to the Work Order), log parts used (inventory management), capture customer signature on completion, and generate a service report PDF emailed to the customer
- Offline mode: the mobile app works without internet connectivity – field workers in areas with poor connectivity can work offline and sync when connectivity returns
- GPS location tracking: with technician consent, the app shares location data with the Dispatcher Console, enabling the real-time map view
Asset and Inventory Management
Field Service integrates with Salesforce’s Asset object and inventory management capabilities:
- Assets: physical equipment installed at customer sites – tracked with serial numbers, installation dates, warranty information, and service history. Work Orders can be linked to specific Assets (this repair is for Asset #SN-12345 at Acme Corporation, a Model X HVAC unit installed in 2022).
- Products consumed: technicians log parts used during a visit from the mobile app, selecting from a product catalog. The consumed products are recorded on the Work Order for cost tracking and billing.
- Return merchandise authorisation (RMA): when defective parts need to be returned, Field Service generates RMA records and tracks return logistics.
Preventive Maintenance
Beyond reactive break-fix work orders, Salesforce Field Service supports preventive maintenance – automatically generating scheduled Work Orders based on service intervals, asset age, or usage thresholds. This is the foundation for service contracts and managed service agreements where customers pay for regular maintenance rather than per-incident visits.
To configure preventive maintenance, navigate to the Maintenance Plan object (available from any Asset or Service Contract record). Define the maintenance frequency (every 90 days, every 6 months, annually), the Work Type to use, and the Service Territory. Salesforce will automatically generate Work Orders at the correct intervals, populating the Service Appointment calendar without dispatcher intervention. For IoT-connected equipment – where Salesforce IoT or MuleSoft receives real-time usage data – you can trigger maintenance Work Orders based on usage thresholds (generate a maintenance Work Order when a printer reaches 50,000 pages or a compressor logs 2,000 hours of runtime) rather than calendar intervals alone.
The Asset object in Salesforce Field Service tracks every piece of equipment at every customer site, including installation date, warranty expiry, service history, and firmware or software version. Assets link to Work Orders, so a technician can review the full service history for the specific unit they are visiting before they arrive. Asset hierarchy also supports multi-component equipment – a complex machine with multiple sub-components can be modelled as a parent Asset with child Assets, each with their own maintenance schedule and service history.
Customer Portal Integration
Connect Field Service to a Salesforce Experience Cloud customer portal to give customers self-service visibility:
- Customers log in to track their appointment status (Scheduled, Technician En Route, On Site)
- Real-time estimated arrival time (ETA) based on technician GPS location and traffic
- Appointment rescheduling self-service – customers can reschedule to available slots without calling support
- Post-visit satisfaction survey triggered automatically when appointment is marked Complete
Key Field Service KPIs
Configure a Field Service Operations Dashboard tracking:
- First-Time Fix Rate (FTFR): percentage of Work Orders completed successfully on the first visit, without a return visit for the same issue – the primary efficiency metric for field service quality
- Technician Utilisation: percentage of available working hours spent on billable or productive appointments (vs. travel, admin, or idle time)
- SLA Compliance: percentage of appointments completed within the contracted response or resolution time
- Mean Time to Resolution (MTTR): average time from Work Order creation to closure
- Travel Time Ratio: travel time as a percentage of total technician time – a measure of scheduling efficiency (lower is better)
- Customer Satisfaction (CSAT): average satisfaction score from post-visit surveys by territory, work type, and technician
What is the difference between Field Service and Service Cloud?
Service Cloud is Salesforce’s core customer service platform – it manages Cases, email and chat support, knowledge articles, and the agent desktop. Field Service is an add-on to Service Cloud that extends it with field operations capabilities: Work Orders, technician scheduling, dispatch, mobile execution, and parts inventory management. Service Cloud handles support that happens remotely (via phone, email, chat); Field Service handles support that requires a technician to travel to the customer site. Most Field Service organisations use both: Service Cloud for initial case handling and customer communication, and Field Service for dispatching and managing the site visit. The Service Cloud Case can link to a Field Service Work Order, creating a complete service record from first customer contact through resolution.
How does the Intelligent Scheduling Engine work?
The Salesforce Field Service Intelligent Scheduling Engine (also called the Optimisation Engine) evaluates multiple constraints and objectives simultaneously when assigning a Work Order to a technician: technician skill match, geographic distance and travel time, current workload and capacity, service territory, appointment priority, and time window preferences. It uses a Scheduling Policy to weight these constraints – a policy might prioritise reducing travel time for emergency work orders but prioritise skill matching for specialist installations. The engine runs as a Salesforce-hosted service (not within your org’s compute limits) and can process hundreds of scheduling assignments per minute. For bulk optimisation – where the engine re-optimises an entire day’s schedule for a territory – the process runs in the background and updates the Gantt chart when complete.
Can Field Service be used without the mobile app?
Technically yes, but it defeats the purpose. Without the mobile app, technicians must be dispatched via phone or SMS and update Work Orders from a laptop. The Field Service mobile app – available on iOS and Android – is how technicians receive real-time job updates, access Work Order details and customer history, log parts usage, capture photos and signatures, and update job status. It supports offline operation for technicians in areas without mobile connectivity. The mobile app is included in the Field Service licence at no additional cost. Some organisations use the Salesforce standard mobile app as a minimal alternative, but it lacks the Field Service-specific components (the map view, barcode scanner for parts, signature capture) that make the dedicated app useful.
How is Field Service pricing structured?
Salesforce Field Service is licensed per user per month, with separate licences for dispatcher users (who use the Dispatcher Console to schedule and manage technicians) and technician users (who use the mobile app). As of 2026, pricing starts at approximately $165 per user per month for technician licences and $300 per user per month for dispatcher licences, though enterprise agreements typically involve negotiated rates. The licence includes the core Field Service platform, the mobile app, Work Orders, scheduling, and the Dispatcher Console. Advanced features – including the Intelligent Scheduling optimisation engine for bulk schedule optimisation, asset management, and preventive maintenance automation – require the higher Field Service Plus tier. Salesforce does not publicly list current pricing; request a quote through your account executive or the Salesforce website.
The best field-service setup is the one that keeps mobile work connected to the CRM. If the process is not clear, scheduling becomes harder to control.
Common Problems and Fixes
Problem: Technicians Are Being Scheduled Outside Their Service Territory
A common Field Service configuration issue is the Intelligent Scheduling Engine assigning technicians to Work Orders outside their designated service territory – generating unnecessary travel time and violating geographic contracts with customers. To fix it, verify Service Territory Member records for each technician: navigate to the Service Resource record, then the Service Territory Members related list, and confirm the technician is listed only for the territories where they should operate. Also check the Work Order’s Service Territory field – if it is blank or incorrectly set, the scheduler may ignore territory boundaries. Create a Validation Rule on the Work Order object requiring Service Territory to be populated before a record can be saved (IsBlank(Service_Territory__c) generates an error). In the Scheduling Policy (Setup ? Field Service ? Scheduling Policies), confirm that Territory Matching is set to Soft or Hard constraint – Hard constraint prevents cross-territory assignments entirely; Soft constraint allows them only when no in-territory technician is available.
Problem: Mobile App Not Syncing Work Orders to Technician Devices
Field technicians frequently report that Work Orders assigned to them don’t appear in the Field Service mobile app, or that updates made offline don’t sync when they reconnect. This is almost always a mobile configuration or permissions problem. First, confirm the technician’s user profile includes the Field Service Mobile licence and the Field Service Mobile user permission set. Second, check the Flexipage configuration for the mobile app: in Setup ? Field Service ? Mobile Settings, verify the correct pages are assigned to the technician’s profile. Third, if technicians work in low-connectivity environments, confirm that Offline Priming is enabled (Setup ? Field Service ? Mobile Settings ? Offline Priming) – this pre-loads Work Orders and related records to the device when connected, enabling full offline functionality. If sync conflicts occur, check the Sync Log in the mobile app settings (three dots ? Settings ? Sync Log) for specific error messages identifying which records failed to sync and why.
Problem: Dispatcher Console Not Showing Available Technicians
Dispatchers report that the Gantt chart in the Dispatcher Console shows no available technicians, or shows technicians as unavailable even during their working hours. The most common cause is missing or incorrectly configured Resource Absences and Operating Hours. Check the following: navigate to each Service Resource and confirm that Operating Hours are assigned – the technician’s working schedule must be defined on the Operating Hours record linked to their Service Resource. Then verify that no Resource Absence records are incorrectly covering the dispatch date. In the Dispatcher Console, confirm the date range and Service Territory filter are set correctly – if the console is filtered to a different territory or date, technicians in the correct territory appear to be missing. Finally, confirm that Service Resources are set to Active status – inactive resources don’t appear in the Dispatcher Console even if they have valid operating hours and territory assignments.