Mobile Builder for the Seller-Focused Experience
Mobile Builder for the Seller-Focused Experience is a point-and-click admin tool in Salesforce that customizes how the Seller-Focused Mobile Experience looks and behaves.
Definition
Mobile Builder for the Seller-Focused Experience is a point-and-click admin tool in Salesforce that customizes how the Seller-Focused Mobile Experience looks and behaves. It lets you add native pages for custom objects and reshape the record home page layouts that sellers see inside the Salesforce mobile app on iPhone and Android.
The Seller-Focused Mobile Experience itself is the native interface that Sales Cloud reps use to track accounts, contacts, leads, opportunities, events, and tasks while away from a desk. That experience is enabled by default and works without admin setup. Mobile Builder is the layer on top: it gives admins control over which components appear, how they are ordered, and which quick actions a seller can tap. The builder is enabled by default too, and admins publish a configuration to push their changes to mobile users.
How the builder shapes the seller's mobile screen
The product behind the builder
The Seller-Focused Mobile Experience is a native experience inside the Salesforce mobile app, built for reps who work from their phone. Out of the box it surfaces accounts, contacts, leads, opportunities, events, and tasks, with an activity timeline that lets reps respond to upcoming work. Sellers can call or email a contact directly from a record, view enhanced contact details, and manage events and to-do items in a layout tuned for a small screen. The experience is available on iOS and Android phones and tablets, in every edition except Database.com. It is enabled by default, and any user with Sales Cloud access can open it without an admin turning anything on. Mobile Builder for the Seller-Focused Experience is the configuration surface that sits over this product. The product gives sellers a working mobile workspace; the builder lets an admin decide what that workspace contains. Knowing the split matters: when a rep asks why a field or button is missing on mobile, the answer usually lives in a Mobile Builder configuration, not in a page layout or Lightning record page on desktop.
Native pages for custom objects
By default the Seller-Focused Mobile Experience shows a fixed set of standard objects natively, and other objects are reachable only from the Menu. The single biggest job of Mobile Builder is to change that. The builder lets an admin add a native page for a custom object, so a rep can open that object the same way they open an account or opportunity, rather than digging through the Menu. This is what makes the mobile experience fit a real sales process instead of a generic one. If a team tracks site visits, demo requests, or a custom deal object, those records can now have first-class mobile pages. The builder is a point-and-click tool, so adding a native page does not require code. You pick the object, then arrange its mobile record home page. The result is a mobile app where the records that matter to your sellers behave like native records, with the layout you chose, instead of being buried one level down. This single capability is often the reason an org adopts the builder at all.
App configurations and object configurations
Mobile Builder uses a two-tier model. The top tier is the app configuration, a container you create first and give a name. Inside it you create object configurations, one for each object whose mobile pages you want to control. You can add as many object configurations as you need within a single app configuration. The flow is short. From Setup, search Mobile Builder for the Seller-Focused Experience in Quick Find and open it. Click New Configuration, name the app, and save; the object configuration page opens automatically. Click Create Object Configuration, type an object name, pick it, and save. The builder canvas then opens for that object. You manage existing object configurations from a dropdown next to the selected one, where you can edit or delete them. One naming rule is easy to trip over: an app configuration name has to be unique across every mobile builder in the org. You cannot reuse a name already taken by Field Service Mobile Builder or the standard Mobile Builder, so plan a clear naming convention before you start.
Customizing the record home page
Inside an object configuration, the builder edits the record home page that a seller sees when they open a record on mobile. You add components, reorder them, and delete the ones a seller does not need, so the most useful information sits at the top of the screen. You can also create quick actions, which are the tap targets a rep uses to log a call, create a follow-up task, or update a field without opening the full record editor. When the layout is ready, you publish the configuration, and the change reaches mobile users. Two display behaviors are worth knowing because they shape what your layout can do. A record opens in a compact view that shows about ten fields, and the rep taps View Full Record to see everything else, so the fields you place high in the layout carry the most weight. The Path component on mobile is view only, which means a rep can see the stage but changes the stage in standard Lightning Experience rather than in the app. Designing around these limits keeps the mobile screen fast and focused instead of trying to replicate the desktop record page.
Agentforce inside the seller experience
The Seller-Focused Mobile Experience includes an Ask Agentforce button, which brings the AI assistant into the rep's pocket. Through voice or text, a rep can ask Agentforce to find and summarize records, and to draft emails on their behalf. For a seller between meetings, this means summarizing an account before walking in, or generating a follow-up email without typing it out on a phone keyboard. Access depends on licensing and permissions, not just on having the app. A user needs the Use Einstein Copilot for Salesforce permission in addition to the Salesforce Mobile App Native Seller Experience permission, and Agentforce availability also depends on the org's licensing. So the AI layer is opt-in by entitlement rather than on for everyone the way the base experience is. Mobile Builder and Agentforce work on different parts of the same screen. The builder decides the static layout and the quick actions; Agentforce handles the conversational, on-demand requests. Together they cover both the predictable taps a rep makes and the ad hoc questions that come up in the field.
Where it fits among Salesforce mobile options
Salesforce ships more than one way to deliver a mobile experience, and it helps to place this one. The standard Salesforce mobile app is the general container that works for every persona. The Seller-Focused Mobile Experience is a native, sales-tuned experience that runs inside that app for Sales Cloud users. Mobile Builder for the Seller-Focused Experience is the admin tool that configures that experience. Separately, Salesforce offers other builders for other personas; the limitations note that app configuration names must stay unique across Field Service Mobile Builder and the standard Mobile Builder, which tells you these tools are siblings rather than the same product. For deeper or fully branded mobile needs, Mobile Publisher produces white-label apps, and the Mobile SDK supports custom-built apps. The Seller-Focused path is the lowest-effort option for a sales team: no code, no separate app to distribute, and a configuration model an admin can learn in an afternoon. Choosing it is usually right when the goal is a better mobile experience for existing Sales Cloud reps rather than a standalone product for external users.
Build and publish a seller configuration
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.
Prefer this walkthrough as its own page? How to Mobile Builder for the Seller-Focused Experience in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Mobile Builder for the Seller-Focused Experience.
Hands-on resources to go deeper on Mobile Builder for the Seller-Focused Experience.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Who is the Mobile Builder for the Seller-Focused Experience optimized for?
Q2. What does the home screen of the Seller-Focused Experience surface for a rep?
Q3. Which capability helps a rep capture data hands-free between meetings in the Seller-Focused Experience?
Discussion
Loading discussion…