Mobile Builder for the Seller-Focused Experience is configured in Setup with no code. You create one app configuration, then add an object configuration for each object whose mobile record home page you want to control, customize the layout, and publish it to your sellers.
- Open Mobile Builder in Setup
From Setup, type Mobile Builder for the Seller-Focused Experience in the Quick Find box and select it. The builder is enabled by default, so the page is available without turning a feature on first.
- Create an app configuration
Click New Configuration, enter an app name, and save. Pick a name that is not already used by Field Service Mobile Builder or the standard Mobile Builder, because names must be unique across all builders. The object configuration page opens automatically.
- Add an object configuration
Click Create Object Configuration, start typing the object name, select it, and save. Repeat for each object you want to give a native mobile page, including custom objects. The Mobile Builder canvas opens for the object you selected.
- Customize the record home page
On the canvas, add, reorder, and delete components, and create quick actions for the taps your reps make most. Put the highest-value fields near the top, since the compact view shows about ten fields before a rep taps View Full Record.
- Publish to sellers
Publish the configuration so the layout reaches mobile users. Open the app on a phone or tablet to confirm the components, quick actions, and any custom object pages appear as intended.
The top-level container, created first, that holds a unique name and groups all object configurations for the seller experience.
A per-object setup inside the app configuration that defines the native mobile record home page for a standard or custom object.
An object configuration on a custom object, which gives that object a first-class mobile page instead of access only from the Menu.
Tap targets you add in the builder so reps can log a call, create a task, or update fields without opening the full record editor.
- App configuration names must be unique across Field Service Mobile Builder and the standard Mobile Builder, not just within the seller experience.
- The compact view shows about ten fields; anything below that needs a tap on View Full Record, so order the layout with that in mind.
- The Path component is view only on mobile. Reps change the stage in standard Lightning Experience, so do not rely on the mobile screen for stage updates.
- Agentforce in the app is not automatic. A seller needs the Use Einstein Copilot for Salesforce permission plus the Native Seller Experience permission, and the org needs the licensing.