Field Service Lightning
Field Service Lightning (often called Field Service, formerly Field Service Lightning or FSL) is Salesforce's product for managing field operations: dispatching mobile workers to on-site jobs, scheduling appointments, tracking work orders, and handling the mobile workflow technicians use in the field.
Definition
Field Service Lightning (often called Field Service, formerly Field Service Lightning or FSL) is Salesforce's product for managing field operations: dispatching mobile workers to on-site jobs, scheduling appointments, tracking work orders, and handling the mobile workflow technicians use in the field. It extends Service Cloud with the data model, scheduling engine, and dedicated mobile app needed to run a service organization with truck rolls, installations, repairs, or any other on-site work.
A Field Service deployment uses several specialized objects: Work Order (the job to be performed), Service Appointment (the scheduled time slot for the work), Service Resource (the technician or team performing the work), Service Territory (the geographic area), and Asset (the customer equipment being serviced). The scheduling engine uses optimization algorithms to dispatch work optimally across resources considering skills, geography, working hours, and customer preferences. The dedicated Field Service Mobile App runs on iOS and Android, supports offline workflows, includes scanning, photo capture, and customer signatures. Field Service is one of Salesforce's more complex products to implement.
How Field Service runs mobile and dispatch operations
The data model: Work Order, Service Appointment, Service Resource
The Work Order is the central object: a discrete piece of work to be performed (install a router, repair an HVAC unit, inspect equipment). Each Work Order has one or more Service Appointments representing scheduled time slots; complex jobs may need multiple appointments across days. Service Resources are the technicians or crews who can perform appointments. Service Territories group resources by geography. Each appointment binds a Work Order to a Resource at a specific time within a Territory.
Skills, work types, and the matching engine
Service Resources have skills (Plumbing, Electrical, Network Installation) at proficiency levels (Beginner, Intermediate, Expert). Work Types categorize Work Orders by type and define required skills. The scheduling engine matches Work Orders to Resources by required skill versus available skill. This skill-based matching is the foundation of intelligent dispatch; it prevents scheduling a beginner electrician for a complex commercial installation.
The Dispatcher Console and scheduling optimization
The Dispatcher Console is the workspace dispatchers use to assign and schedule appointments. It shows a Gantt-style schedule view per resource, a map view per territory, and lists of unscheduled appointments. Drag and drop appointments onto resources. The Optimization Engine runs schedule optimization automatically based on configurable goals (minimize travel time, maximize same-day completion, balance workload). Optimization can run nightly for next-day planning and on-demand for re-optimization after disruptions.
The Field Service Mobile App
Technicians use the dedicated Field Service Mobile App on iOS and Android. It shows assigned appointments, navigation to the work site, the work order details, the customer info, and any required forms or checklists. Offline support is robust because field workers often operate in areas without reliable connectivity. Photos, signatures, scanned barcodes, and entered data sync when connectivity returns. The mobile app is specifically tuned for technicians, not a generic Salesforce app.
Appointment booking and customer-facing scheduling
Many Field Service deployments offer customer-facing appointment booking. The customer selects a service window through the Experience Cloud portal or an embedded widget; Field Service confirms the slot, books the appointment, and triggers any customer notifications. Real-time appointment booking integrates with the scheduling engine to show only valid time slots based on resource availability, travel time, and territory rules.
Inventory, parts, and product consumption
Field Service tracks the parts and products consumed during work. Each Service Resource has a Van Stock (parts carried in the truck). Work Orders consume parts during execution. Inventory transfers between warehouses and trucks. Parts requests flow when stock runs low. The inventory model is essential for service organizations where parts management drives operational cost and customer satisfaction.
Field Service versus standalone field-service platforms
Several specialized field-service platforms compete with Field Service Lightning: ServiceMax, ServiceTitan, FieldEdge, and others. Each has industry-specific strengths. Field Service Lightning''s advantage is deep integration with Salesforce: the same customer record drives sales, service, and field operations. The disadvantage is that Field Service Lightning is broader and less industry-specific than vertical-focused platforms. The choice depends on whether Salesforce integration or industry depth matters more.
How to set up Field Service
Setting up Field Service is a multi-month exercise. Plan the data model, configure scheduling rules, deploy the mobile app, integrate with inventory systems, and roll out by territory. Most successful implementations engage a specialized Field Service consulting partner because the depth and complexity exceeds typical Service Cloud admin work.
- Document the field service operation and workflow
Map every job type, every resource skill, every territory, every customer-facing process. The document drives the entire Field Service configuration. Trying to configure without it produces unmaintainable spaghetti.
- Provision Field Service and install the managed package
Setup > Field Service > Enable. The product installs custom objects, page layouts, and Setup pages. Configure permissions for dispatchers, technicians, and field service admins.
- Configure Service Territories and Operating Hours
Setup > Field Service > Territories. Define geographic regions matched to the business operation. Setup > Operating Hours. Define when each territory operates including holidays and special hours.
- Set up Service Resources and skills
For each technician or crew, create a Service Resource record. Define skills at the right proficiency levels. Define resource availability and working hours. Bulk-load technician data from HR systems where possible.
- Configure Work Types and Work Orders
Define Work Types for each kind of job: New Installation, Repair Call, Preventive Maintenance. Each type specifies required skills, estimated duration, and parts. Work Orders inherit the type configuration.
- Set up the scheduling engine and optimization rules
Setup > Scheduling Policies. Configure optimization goals (minimize travel time, maximize completion rate). Schedule nightly optimization runs. Test the scheduling engine with realistic appointment loads.
- Deploy the Field Service Mobile App
Distribute the mobile app to technicians via App Store, Google Play, or Mobile Device Management. Configure the mobile experience: which fields appear, which forms launch, what offline data syncs.
- Roll out by territory and refine
Start with one territory. Train dispatchers and technicians. Iterate based on operational feedback. Expand to additional territories once the first one stabilizes. Big-bang rollouts produce significant adoption friction.
Optimization rules: minimize travel, maximize same-day completion, balance workload. Drives how the engine assigns appointments to resources.
Geographic regions matched to operations. Each Resource belongs to one or more territories.
Service Resources have skills at proficiency levels; Work Types specify required skills. The engine matches accordingly.
- Field Service depth exceeds Service Cloud significantly. Most successful implementations engage a specialized partner; DIY produces multi-quarter struggles.
- Scheduling optimization is sensitive to data quality. Wrong skills, wrong working hours, wrong territory assignments produce optimization outputs that look mathematically correct but operationally wrong.
- The Field Service Mobile App is separate from the standard Salesforce Mobile App. Technicians need the dedicated app; deploying the wrong one produces immediate adoption problems.
- Offline support requires careful data priming. Technicians need access to upcoming appointments, customer details, and parts data without connectivity. Configure the offline data set deliberately.
- Inventory integration with ERP systems is often complex. Plan the integration with the IT team because mismatched data produces stockouts or excess inventory.
Trust & references
This term has been renamed to Field Service.
View current pageCross-checked against the following references.
- Field Service DocumentationSalesforce Help
- Field Service Mobile AppSalesforce Help
Straight from the source - Salesforce's reference material on Field Service Lightning.
- Field Service SetupSalesforce Help
- Field Service SchedulingSalesforce Help
- Field Service MobileSalesforce Help
Hands-on resources to go deeper on Field Service Lightning.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Salesforce Field Service?
Q2. What components does Field Service include?
Q3. Why is the mobile app important?
Discussion
Loading discussion…