Salesforce Field Service Capability Reference

Validated functions and scope

• Offline-capable mobile work: supported, but not every object, flow, validation, or LWC behaves the same offline.
• Data Capture and mobile flows: accurate for supported Field Service mobile flow types and supported objects.
• Photos, barcode/QR scanning, geolocation, navigation, signatures, notifications: accurate as mobile app/use-case capabilities, subject to device permissions and app configuration.
• Agentforce field assistance, pre-work briefs, voice/Siri shortcut, troubleshooting, post-work summary: Agentforce/Einstein scope, not base mobile-only functionality.
• On-site cross-sell / next best offer: cross-cloud/custom pattern using Sales/Revenue Cloud, Next Best Action, Flow, or custom UX.

Best practices

• Use Field Service mobile as the field execution surface, but design for the actual connectivity profile of technicians. Prime/sync records before travel, test offline create/edit flows, and define conflict-handling and exception queues.
• Use supported Data Capture and mobile flow patterns to replace paper checklists. Keep forms short, role-specific, and tested on real devices.
• Use camera, barcode/QR scanning, geolocation, signatures, and photos where they reduce manual entry. Treat AI guidance as assistive unless the process has explicit human approval and audit controls.

Prerequisites and licensing badges

• Field Service core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer editions; mobile users need a Field Service Mobile user license.
• Offline requires online priming/sync strategy, Briefcase or Performance Priming setup, permissions, and supported mobile configuration.
• Agentforce features require Agentforce/Einstein setup, data grounding, permissions, and current availability validation.

Operational constraints to add

• Offline-created records can be incomplete until sync; date/time values, search, lookups, validation rules, and flows can behave differently offline.
• Performance Priming has documented record and parent-object support limits.
• Validation rule errors may surface during sync rather than at local save.
• Do not imply native on-device AI. Safer wording: AI-assisted mobile workflows grounded in Salesforce data where supported.

KPIs

Validated functions and scope

• Service territories, operating hours, service resources, shifts: accurate Field Service setup concepts.
• Skills and certifications: accurate as resource qualification data used by scheduling rules.
• Crew management: native Field Service resource modeling pattern.
• Contractor workforce management: accurate as a model, but license, identity, and sharing design must be validated. Avoid unverified SKU names like Contractor+ unless confirmed in the order form.
• Timesheets: not universally base Field Service. In current docs, timesheet tooling appears tied to Field Service Plus for Energy & Utilities and Asset Service Lifecycle Management contexts.

Best practices

• Maintain skills, certifications, expiration dates, operating hours, absences, territories, home bases, and crew membership as governed master data rather than dispatcher tribal knowledge.
• Model contractors and partner resources deliberately. Validate licensing, sharing, mobile access, visibility, and data boundaries before exposing work to external users.
• Review resource health regularly: utilization, overtime, travel load, certification coverage, SLA risk, and turnover signals.

Prerequisites and licensing badges

• Field Service add-on/core setup, managed package, permission sets, service resources, territories, operating hours, work types, and scheduling policies.
• Shift usage requires Field Service managed package and scheduling configuration. Contractor access may require Experience Cloud/partner access, Field Service licenses, or industry-specific packaging.

Operational constraints to add

• Resource data quality drives schedule quality. Missing skills, expired certifications, bad geocodes, incorrect home base, or incomplete territory membership can break optimization assumptions.
• Shifts, operating hours, absences, and emergency/on-call models need clear precedence rules.
• Sharing and visibility for contractors requires deliberate external-user security design.

KPIs

Validated functions and scope

• Enhanced Scheduling and Optimization: accurate. Default for new orgs since Summer 23; existing orgs can transition by territory.
• Appointment Assistant / self-service scheduling: accurate, but requires Appointment Assistant managed package and permission set license.
• Bundling, complex work, multiday appointments: accurate managed package capabilities with important limitations.
• Agentforce Scheduling Agent and Schedule Gap Resolution Agent: Agentforce/Einstein scope, not dispatcher console core alone.
• Street-level route optimization: reasonable description, but should be tied to Field Service scheduling/optimization and geocoding/routing setup rather than stated as a standalone SKU.

Best practices

• Design schedule policies and objectives around business priorities, such as SLA protection, travel minimization, utilization, customer windows, parts readiness, and technician skills.
• Run scheduling pilots with real historical appointments before broad rollout. Tune geocoding, skills, operating hours, travel settings, pinned jobs, emergency work, and bundling rules.
• Use customer self-scheduling and Agentforce scheduling only for appointment types that have reliable capacity, entitlement, location, work type, and routing data.

Prerequisites and licensing badges

• Field Service managed package, scheduling policies, work rules, service objectives, geocoded addresses, resource skills, operating hours, territories, and travel settings.
• Appointment Assistant managed package and permission set license for customer-facing appointment tracking and self-service scheduling.
• Agentforce scheduling/gap features require Agentforce/Einstein configuration and release-status verification.

Operational constraints to add

• Complex work across territories requires optimization requests that include all relevant territories.
• Multiday appointments cannot span more than eight calendar weeks, are not supported for capacity-based resources, and have limitations with complex work.
• Bundling can have limits around pinned appointments, complex work chains, and same-day/multiday configuration.
• Bad geocoding, incomplete skill data, parts availability gaps, and loose scheduling policies can produce poor schedules even with ESO.

KPIs

Validated functions and scope

• Work order, sub-task, related case/asset/entitlement, closure, and status management: accurate Field Service/Service Cloud objects and processes.
• Milestone SLA tracking: accurate when using Entitlements and Milestones; not automatic without entitlement process design.
• Flow Orchestration, Data Capture, Work Plans: accurate as platform/Field Service process tooling, subject to mobile/offline support.
• Service Process Manager: verify org/package availability before using as a named feature; safer wording is work templates, work plans, flows, and guided service processes.
• AI post-work summaries and daily SLA risk highlighting: Agentforce/Einstein or custom analytics/automation scope.
• Outcome-based contract tracking: valid solution pattern, but usually cross-cloud/contract integration, not a simple Field Service toggle.

Best practices

• Use Work Orders for the work scope and Service Appointments for the scheduled visit. Keep status values, ownership, entitlement logic, and closure rules explicit.
• Standardize work templates, required fields, parts, labor capture, knowledge prompts, photos, signatures, and closeout steps by work type.
• Use AI summaries or wrap-up automation only after validating source fields, technician notes, attachments, knowledge, and customer-facing wording controls.

Prerequisites and licensing badges

• Work Orders enabled through Field Service setup, managed package where needed, permission sets, page layouts, object security, entitlement processes, products/assets, and mobile configuration.
• AI summaries require Agentforce/Einstein capabilities and data permissions. Contract/outcome tracking may require Service Contracts, Revenue Cloud/ERP integration, or custom objects.

Operational constraints to add

• Clearly separate Work Order from Service Appointment. Work Order defines work; Service Appointment defines when/where/who for visits.
• Do not promise automatic SLA risk prediction without confirming entitlement data, operating hours, milestones, escalation rules, analytics, and AI configuration.
• Mobile closure flows should be tested offline, including validation rules, required fields, file uploads, signatures, and sync conflicts.

KPIs

Validated functions and scope

• Product Items, Product Requests, Product Transfers, Product Item Transactions, Shipments, Return Orders: accurate Field Service inventory objects/processes.
• Trunk stock and inventory location visibility: accurate using locations and product items.
• Parts replenishment / auto-order: accurate as configured process automation; often requires ERP/WMS integration for purchasing and fulfillment.
• Barcode/QR scanning: accurate mobile capability, but scanning UX may require supported LWC/mobile setup.
• Tableau parts dashboards: analytics/cross-cloud pattern, not a native Field Service dashboard promise unless built or licensed.

Best practices

• Define inventory source of truth before implementing trunk stock, product transfers, returns, replenishment, or consumption. Many organizations still need ERP/WMS integration.
• Use barcode/QR scanning, serialized asset tracking, and mobile parts consumption to reduce manual inventory errors, but test offline consumption and later sync reconciliation.
• Set minimum stock, replenishment, return, defective, and obsolete-parts processes with exception queues for mismatches between Salesforce and warehouse systems.

Prerequisites and licensing badges

• Field Service inventory objects, Locations, Products, Product Items, object permissions, page layouts, and mobile access.
• Shipments and product transfers require create/edit permissions on relevant objects. ERP/WMS integration may be needed for procurement, ATP, shipping labels, and financial reconciliation.

Operational constraints to add

• Salesforce inventory should not be treated as system of record unless intentionally designed that way.
• Define source of truth for on-hand, reserved, in-transit, consumed, returned, serialized, and defective stock.
• Offline parts consumption can create sync and availability timing issues; design reconciliation and exception queues.

KPIs

Validated functions and scope

• Operational reports and dashboards: accurate using Salesforce reports, Field Service objects, and custom analytics.
• Operations Home: accurate Field Service command center for operational health.
• Demand forecasting and capacity planning: valid planning patterns, but often custom analytics unless using packaged industry functionality.
• Tableau Next and agentic analytics: Data 360/Tableau/Agentforce scope, not Field Service core.
• Asset service prediction: predictive/AI capability requiring sufficient asset/service history and data readiness.

Best practices

• Build dashboards around agreed operational definitions: appointment completion, first-time fix, utilization, travel, repeat visit, no-show, SLA compliance, backlog, and cost to serve.
• Plan capacity by skill, territory, shift, seasonality, asset population, maintenance commitments, install base growth, and service contract demand.
• Use Tableau Next/Data 360 or agentic analytics only after establishing canonical data IDs, semantic definitions, permissions, refresh frequency, and metric ownership.

Prerequisites and licensing badges

• Reports/dashboards require object model completeness and report access. Tableau Next requires Data 360/Data 360 semantic layer and Tableau Next setup; AI/agent features require additional configuration and possibly credit consumption.
• Data quality, asset hierarchy, service history, product/inventory data, entitlements, and external system integration drive analytics usefulness.

Operational constraints to add

• Do not promise predictive accuracy without training data volume, data quality, and historical consistency.
• Define metric grain: Work Order, Service Appointment, Resource, Asset, Product Item, Territory, or Customer.
• Normalize time zones, appointment status lifecycle, cancellation/no-show logic, and travel/labor cost definitions.

KPIs

Validated functions and scope

• Installed assets, asset location mapping, service contracts, entitlement-aware service: accurate Salesforce data model and service process concepts.
• Preventive maintenance scheduling: accurate Field Service capability.
• Usage-based maintenance: documented GA capability using maintenance work rules.
• Condition-based / IoT-triggered maintenance: accurate as a solution pattern; requires telemetry ingestion and integration design.
• Predictive maintenance / Asset Service Prediction: AI/predictive scope, dependent on data readiness and licensing.
• Service campaigns: valid proactive service pattern, but confirm exact packaged feature availability for the target org/industry.

Best practices

• Keep asset hierarchy, serial numbers, installed location, warranty, service contract, covered asset, and maintenance plan relationships clean before relying on automated PM generation.
• Use time-based preventive maintenance first when asset history is limited. Add usage-based or condition-based maintenance only when telemetry identity matching and data quality are reliable.
• Balance preventive maintenance generation with workforce capacity so proactive work does not create avoidable backlog or SLA pressure.

Prerequisites and licensing badges

• Assets, accounts/locations, maintenance plans, covered assets, maintenance work rules, work types, products, entitlements, and Field Service scheduling setup.
• Usage/condition-based maintenance needs reliable source telemetry, asset identity matching, thresholds, data ingestion, and exception handling.

Operational constraints to add

• Asset identity is the hidden risk: serial numbers, parent/child hierarchy, installed location, warranty, and service contract relationships must be clean.
• Preventive maintenance can overload capacity if demand forecasting is not tied to resource planning.
• For outcome-based contracts, define measurable uptime/service outcomes, exclusions, penalties, and source-of-truth telemetry.

KPIs

Validated functions and scope

• Return Orders and Return Order Line Items: accurate for tracking returns and repairs of products/inventory.
• Shipments: accurate for product items in transit and links to product transfers.
• RMA eligibility checks: automation pattern using entitlement/warranty/asset/contract data.
• Swap-outs / loaners, depot assignment, shipping label management, billing reconciliation, compliance tracking: custom/integration scope unless the org has industry/package-specific functionality.
• SPM depot repair templates: verify feature naming and availability before using. Safer wording: configured depot repair templates/workflows.

Best practices

• Separate return authorization, shipment, receipt, triage, repair, refurbishment, replacement, loaner, scrap, billing, and inventory disposition as distinct process states.
• Use native Return Orders, Shipments, Product Items, and inventory transactions where applicable, but validate whether depot WIP, carrier labels, loaners, warranty adjudication, or billing need ERP/WMS/carrier integration.
• Track chain of custody, serial numbers, customer-owned versus company-owned inventory, expected arrival, repair status, and financial outcome.

Prerequisites and licensing badges

• Return Orders, Shipments, Product Requests/Transfers, Locations, Product Items, Cases/Work Orders, Assets, Entitlements, and object permissions.
• Carrier labels, depot WIP, loaner pools, refurbishment status, warranty financials, and invoicing typically require ERP/WMS/carrier/billing integration.

Operational constraints to add

• Define whether the RMA is customer-owned inventory, company-owned inventory, loaner, defective stock, refurbishable stock, or scrap.
• Track chain of custody, serial numbers, warranty status, expected arrival date, receipt, triage, repair status, and financial disposition.
• Do not promise end-to-end depot repair as native unless validated against the exact Salesforce SKU/package.

KPIs