Here is the practical path to set up the Field Service mobile experience for a team. You enable notifications, optionally add a flow as an app extension, and decide on geolocation, all inside a Field Service Mobile Settings configuration.
- Open Field Service Mobile Settings
In Setup, enter "field service mobile" in Quick Find and click Field Service Mobile Settings. You can also reach it from Field Service Settings. Confirm the Default row exists.
- Expand a configuration
Click Show Details on the Default row, or add a new configuration and assign it to the user profiles it should serve. Edit the Default first since it covers anyone without a profile-specific row.
- Set appointment notifications
Turn on Send Appointment Notifications on Dispatch or Send Appointment Notifications on Assignment, or both, to match when your dispatch process should ping technicians.
- Add an app extension (optional)
Create an app extension that launches a flow. Give it a type, launch value, label, name, and the scoped object types where it should appear, for example a parts-capture flow scoped to Work Order.
- Decide on geolocation
Under additional settings, choose whether to enable Collect Service Resource Geolocation History, then set Geolocation Update Frequency in Minutes and Geolocation Accuracy to balance live visibility against battery and data.
Pushes a notification when a service appointment is dispatched to the technician.
Pushes a notification when the appointment is assigned to the service resource.
A custom action defined by type, launch value, label, name, and scoped object types that launches a flow in context.
Enables the app to upload technician geolocation to Salesforce at regular intervals while running.
Sets the app's brand color so the mobile experience matches your company styling.
- Notifications ride on the Salesforce Field Service connected app. If the connected app or device push permissions are not set up, the dispatch and assignment toggles do nothing.
- A profile with no matching configuration falls back to the Default. If a technician sees the wrong flows or notifications, check which configuration their profile actually maps to.
- Geolocation tracking is a privacy decision, not just a toggle. Communicate what is collected, and tighter accuracy with shorter intervals costs battery and data.
- An app extension flow that needs related records the device never primed will fail in the field. Align offline priming with the extensions you enable.