Field Service and Field Service Lightning refer to the same product. Setting up the product follows the Field Service Lightning configuration workflow described in that term. The steps below cover navigating the naming gap when reading documentation, communicating with various audiences, and pursuing certifications.
- Treat Field Service and FSL as equivalent
When you see Field Service or Field Service Lightning in documentation, integrations, or conversation, treat them as the same product. The technical configuration, APIs, and capabilities are identical.
- Use Field Service in formal communication
For Salesforce-facing communication (sales calls, support cases, formal proposals), use the current Field Service branding. It signals current product knowledge.
- Use FSL or Field Service Lightning for practitioner shorthand
Among practitioners, FSL is the everyday shorthand. Using it matches how most training, certifications, and community resources describe the product.
- Search documentation under both names
Older Trailhead and Help articles use Field Service Lightning. Newer content uses Field Service. Cover both when researching specific features to find the complete answer.
- Reference the Field Service Lightning term for detailed setup
The dictionary entry for Field Service Lightning covers detailed configuration steps. Follow those steps; the product is identical regardless of which name appears in the dictionary.
- Pursue the Field Service Consultant certification
The certification credential is now Field Service Consultant. New candidates pursue this credential. Holders of older Field Service Lightning Consultant credentials hold equivalent expertise.
- Match terminology to audience expectations
Internal documentation can use either name. Customer-facing assets and current proposals use Field Service. Match the audience expectation rather than enforcing one name consistently across all contexts.
- Update documentation gradually
Update internal documentation to current Field Service branding during routine maintenance. Forced rapid rename of all documentation produces churn without clear benefit; gradual updates align with the broader community transition.
Current Salesforce branding for sales, proposals, and official documentation. Signals current product knowledge.
Community standard for everyday conversation. Matches certifications, books, and tutorials.
Telecommunications, Utilities, Healthcare. Industry-specific editions extend the base Field Service product.
- Field Service and Field Service Lightning refer to the same product. Treating them as different products produces confusion in documentation searches and conversations.
- The Field Service Lightning name persists across the community. Documentation, certifications, AppExchange listings, and practitioner speech use both names interchangeably.
- Industry editions are paid add-ons. The base Field Service does not include the industry-specific extensions; pricing scales with the edition selected.
- Field Service is one of the most actively developed Salesforce products. Capability changes per release; stay current with release notes for new features and behavior changes.
- The Field Service Mobile App branding lags behind the Field Service rebrand. Some installations and App Store listings may still show the FSL Mobile name.