What is Salesforce Field Service? Modules, integrations and alternatives
Salesforce Field Service is the field service management product on the Salesforce platform, formerly known as Field Service Lightning. It covers work orders, service appointments, scheduling and optimisation, inventory and a mobile app for technicians. It is usually chosen by companies that already run Salesforce for sales or service.
Also known as: Field Service Lightning, FSL, Salesforce FSL
Salesforce Field Service extends the Salesforce service data model with objects such as work orders, work order line items, service appointments, service territories, service resources and skills. Because these live on the same platform as accounts, cases and assets, a customer's cases, assets and field visits share one record set.
It is used by manufacturers that service installed equipment, by distributors with installation or repair teams, and by businesses delivering planned maintenance. Dispatchers use a console to see schedules on a Gantt view and a map, while technicians use the Field Service mobile app, which is designed to work offline and sync when connectivity returns.
In a manufacturing stack, the ERP remains the system of record for items, pricing, inventory valuation and invoicing, while Salesforce holds the customer-facing service process. Most implementations integrate the two through middleware so that assets, entitlements, parts usage and billable work stay consistent. Scheduling quality depends heavily on how territories, skills, working hours and travel are modelled.
Modules and capabilities
Work orders and line items
Defines the job, its steps and the parts and labour used, linked to the customer and asset.
Service appointments and scheduling
Books visits against resources using territories, skills, working hours and scheduling policies.
Optimisation
Automates and re-optimises schedules against configurable policies, with options for emergency insertions.
Dispatcher console
Provides Gantt, map and list views for dispatchers to monitor and change the schedule.
Field Service mobile app
Gives technicians schedules, job details, forms and offline support.
Inventory management
Tracks product items across locations and vehicles, with transfers and consumption linked to work orders.
Maintenance plans and assets
Generates recurring work from plans tied to customer assets.
Digital engagement
Offers customer appointment booking and notifications through portals and messaging channels.
Integrations and data access
ERP
Items, price books, customers, orders, inventory and invoices typically sync with the ERP through middleware such as Boomi, MuleSoft or Celigo, or custom integrations.
Platform APIs
REST and SOAP APIs, bulk APIs and platform events let external systems create and update work orders and assets, subject to API limits.
Assets and IoT
Connected product data can create cases or work orders through an integration layer or event-driven flows.
Maps and routing
Scheduling uses geocoding and travel estimates; the mapping service and its configuration should be reviewed for your regions.
Documents and knowledge
Manuals and knowledge articles can be linked to work types so technicians see relevant guidance on the job.
Strengths
- Single platform for CRM, cases, assets and field work
- Flexible low-code customisation with flows and custom objects
- Mature scheduling model with territories, skills and policies
- Large ecosystem of integration partners and consultants
- Offline-capable mobile app for technicians
Limitations
- Not available on premises, which rules it out for some secure environments
- Scheduling optimisation and mobile features depend on licence and configuration
- Asset-heavy manufacturing service often needs extra design for installed base structures
- Platform limits on APIs and data volumes need planning
- Costs and complexity can grow with customisation
Where AI helps Salesforce Field Service users
- - Summarising case, asset and visit history into a pre-visit brief for the technician
- - Suggesting repair steps from manuals and knowledge articles based on the work order description
- - Predicting parts and job duration to improve schedule quality
- - Drafting customer updates and close-out notes from technician input
- - Detecting repeat visits and recurring faults across an installed base
Evaluating Salesforce Field Service? Check these
- Model territories, skills and working hours before judging the scheduler
- Decide which system owns inventory, parts and pricing, and design sync accordingly
- Test the mobile app offline with real job types and forms
- Check API limits and data volumes against your asset and work order counts
- Confirm which AI and optimisation features are included in your edition
- Plan a clean asset and product load from ERP before go-live
Common alternatives: ServiceMax, Dynamics 365 Field Service, IFS Field Service Management, Oracle Field Service, ServiceNow Field Service Management, SAP Service and Asset Manager.
Frequently asked questions
What is Salesforce Field Service?
It is the field service management product on the Salesforce platform. It handles work orders, appointment scheduling, dispatch, inventory and a mobile app for technicians, and it connects to Salesforce cases, accounts and assets. It was previously called Field Service Lightning, and many people still use the abbreviation FSL.
Is Salesforce Field Service the same as Field Service Lightning?
Field Service Lightning was the earlier name for the product that Salesforce now calls Salesforce Field Service. The core objects and concepts carried over, such as work orders, service appointments and scheduling policies, although packaging and features have continued to change. Check current documentation rather than older posts.
Can it integrate with my ERP?
Yes, typically through middleware or custom integration, because Salesforce is not an ERP. Common flows include customers, items, price books, sales orders, parts movements and invoices. Decide which system is the source of truth for each object before building, because duplicate ownership causes most integration problems.
Does it work offline?
The Field Service mobile app is designed to let technicians work offline and sync later, but behaviour depends on configuration, the size of data you pre-load and the forms in use. Test with your real work types, attachments and device types before committing to an offline-heavy process.
How does it differ from ServiceMax?
Salesforce Field Service is a native Salesforce product that suits teams using Salesforce CRM and cases. ServiceMax is built around asset-centric service for equipment-heavy companies. Which is better depends on your installed base complexity, contract logic and parts processes, so compare them against your own scenarios.
Running Salesforce Field Service?
We add AI, chat, automation and integrations to the systems manufacturers already run, on-prem if needed.
Get a free assessment