Salesforce mobile app for field sales: setup that reps will use

Outside reps use the Salesforce mobile app when logging a visit takes a few taps from the parking lot. That means a phone-specific record page, a short compact layout, and quick actions that ask for three or four fields with sensible defaults. Add email and calendar sync so meetings log themselves, then test the setup with real reps on their own phones before rollout. Measure success by mobile logins and records updated from the app, not by installs.

What does the Salesforce mobile app do without any setup?

Out of the box, the app shows your Lightning record pages, list views, reports, dashboards, tasks and notifications on iOS and Android. It works, but it shows the desktop design squeezed onto a small screen.

• Record pages: if no page is activated for the phone form factor, users get a default page built from your existing layout.
• Actions: quick actions on the page layout appear in the mobile action bar, including standard ones like Log a Call and New Task.
• Notifications: push notifications for approvals, mentions and custom notifications sent from Flow.
• Limited offline: recently viewed records are cached, and admins can allow offline edits to them. Briefcase-based offline needs Salesforce Mobile App Plus.

Salesforce has also announced Agentforce features in the mobile app, including voice summaries and dictated updates. Availability and licensing change by release, so confirm what your org holds with your Salesforce account team.

Why do field reps stop opening the mobile app?

Reps quit when one update takes longer on the phone than it would at a desk tonight. The usual causes are layouts built for a wide monitor, too many required fields and slow pages.

• The record page scrolls through every section the desktop shows, so the field a rep needs sits nine swipes down.
• Validation rules and required fields designed for sales ops demand data a rep cannot know from a car.
• Picklists with dozens of values are painful to scroll on a phone keyboard.
• Heavy pages with many related lists, custom components and report charts load slowly on a weak signal.
• Nobody showed reps the app. They installed it once, saw a cluttered page and went back to texting their manager.

If the wider problem is that reps distrust Salesforce at any screen size, fix that first.

How should you design record pages for a phone?

Build a separate Lightning record page for the phone form factor, or use device-based component visibility on one page. Then trim the compact layout so the header shows what a rep checks before walking in.

In Lightning App Builder, you can activate a page for desktop, phone or both, and set component visibility by form factor. A phone page for the account might carry only the highlights panel, open opportunities, recent activity and contacts. Leave the full field detail on a tab further down for the rare case someone needs it.

The compact layout drives the record header in the app. Pick the handful of fields a rep glances at before a meeting: account status, owner, phone, last activity and the open opportunity value. Salesforce allows up to ten fields there, but four or five reads better on a small screen.

Which quick actions should a field rep have?

Give reps a small set of object-specific quick actions that each finish one job in under a minute. Prefill everything you can and require only what you will act on.

Object-specific actions sit on a record and inherit context, so a Log a Visit action on an account fills in the account automatically. Global actions live outside a record and suit tasks like creating a new lead met at a trade show. Both appear in the mobile action bar in the order set on the layout, so put the three most-used actions first.

Rebuild the action layouts specifically. A quick action has its own layout, separate from the page layout, and that is where most of the trimming happens.

How do you cut typing for activity capture?

The biggest win is not typing at all. Sync email and calendar so meetings and messages log from the rep's inbox, and keep mobile actions for what sync cannot catch.

If reps already book meetings in Outlook or Gmail, calendar sync creates the event record, and the visit action only needs to add the outcome.

Phone dictation through the keyboard microphone already works in any text field, including Next Step and description fields. It is free and reps already know it. Salesforce's own voice features in the mobile app go further by turning a spoken summary into record updates. Treat them as a pilot, check the licensing, and have reps confirm what the agent wrote before it saves.

Do reps need offline access, and what is Briefcase?

Most outside sales teams need little offline access, because cell coverage is usually adequate. Rural territories, plant floors and basements change that answer.

The standard app caches recently viewed records, which reps can read and, if enabled, edit without a signal. For broader offline work, Salesforce Mobile App Plus adds Briefcase so reps can prime the records they need and sync changes later. Admins use Briefcase Builder to define which records download to each device, such as a rep's own accounts and their open opportunities.

Briefcase rules have record and object limits, and Mobile App Plus supports Lightning Web Components rather than every custom component you may have. Check both before you promise offline access, and confirm licensing with your account team. Field Service technicians use a different mobile app with its own offline model, covered in our Field Service guide.

Can reps see nearby accounts on a map?

Not natively in a useful way for planning routes. Mapping, nearby-account search and route planning come from Salesforce Maps, a separately licensed add-on.

Salesforce has retired the standalone Salesforce Maps mobile app in favor of Maps inside the Salesforce mobile app, so check the current setup with your account team. Licensed users now reach maps through a Maps Mobile navigation item inside the Salesforce mobile app. If your reps used the old app, check that the item is in their mobile navigation. Without Maps, address fields still open in the phone's map app for directions, which covers the basic need.

How do approvals and alerts work on a phone?

Approval requests, mentions and custom notifications arrive as push notifications, and approvers can act from the notification. Reps and managers must allow notifications on the device for any of this to work.

Use Flow to send custom notifications for events that need a fast reply. Examples include a large deal reaching negotiation or a quote awaiting approval. Keep the volume low. A rep who gets twenty alerts a day turns them all off, including the ones that matter. Check notification delivery settings in Setup so each type is enabled for mobile.

How do you secure Salesforce on personal phones?

Start with the controls you already have: multi-factor authentication, session timeouts and a PIN or biometric lock on the app. Add device or app management only if your policy requires it.

• Mobile device management: the app works with common MDM suites, which can push configuration and enforce device rules on company phones.
• Enhanced Mobile App Security: a paid app-level add-on that sets policies such as blocking jailbroken devices or restricting copy and paste, without managing the whole device.
• Mobile Publisher: a separate product for publishing a branded version of the app. Most sales teams do not need it.
• Permissions: reps see on the phone exactly what their profile and permission sets allow, so review export and report access before rollout.

Bring IT and security in early when reps use personal phones. Whether you require MDM on a personal device is a policy decision, not a Salesforce setting.

How should you test the mobile setup before launch?

Hand the configured app to three to five working reps, on their own phones, during a normal day. Watch them use it rather than asking what they think.

• Mix iPhone and Android users, and include an older device and a rep with a weak-signal territory.
• Give each rep real tasks: log today's visits, create one opportunity and update next steps on three deals.
• Time each task and note every scroll, error message and abandoned attempt.
• Ask what they still write elsewhere, such as paper notes, texts or a spreadsheet. That list is your backlog.

Fix what the pilot finds, then retest with the same reps. They will become the go-to helpers for their teams.

How do you know whether reps are using the mobile app?

Login History shows which application each sign-in came from, so you can usually separate mobile app sessions from browser sessions. Pair that with records created from the app to see real use.

Report on visits and opportunities created per rep, and add a hidden checkbox or source field that each mobile quick action stamps. That shows which actions earn their place. Our guide to measuring adoption covers the wider metrics and how to coach from them.

What belongs in phase one?

Keep phase one narrow: one phone page each for accounts and opportunities, three to five quick actions, calendar sync and a pilot group. Leave offline, maps and AI for phase two.

• Agree the three rep tasks that matter most and design only for those.
• Build phone record pages and trimmed compact layouts for accounts, contacts and opportunities.
• Create the quick actions with prefilled defaults and short action layouts.
• Turn on email and calendar sync for the pilot group.
• Confirm notification settings and your MFA and security policy for phones.
• Run the pilot, fix what it finds and roll out by team with a short in-app demo.
• Baseline mobile logins and mobile-created records, then review them with sales managers.

If you want help designing the mobile experience or cleaning up the layouts behind it, our optimization team does this work with sales ops leaders.