Salesforce Mobile App Business Card Scanner Guide

January 2, 2026

Your Salesforce Mobile App is where your reps live when they’re away from the desk. Your business card scanner runs inside the same app, no new login, no extra install.

Why inside Salesforce Mobile matters

Your reps have learned one login, one interface, one navigation pattern. Asking them to switch to a separate scanner app breaks the flow and often breaks adoption too.

Your scanner appears as a tile in the Salesforce Mobile App. Your reps tap it, scan, and the result lands in Salesforce without leaving the session.

Authentication and Permission Sets

Your scanner uses the Salesforce Mobile App’s existing session. Your rep is already authenticated; no second login. Your Permission Sets, field-level security and sharing rules all apply automatically.

Your security team doesn’t need to whitelist a separate app or manage a second set of credentials. Your Salesforce audit log captures every scan under the rep’s normal user ID.

What the scan creates

Your scan inside Salesforce Mobile can create:

  • A Lead (with standard lead source, ownership rules, assignment)
  • A Contact with a linked Account
  • An Opportunity at a specified stage and amount
  • A CampaignMember if your rep’s attending an event
  • An Activity (Task or Event) recording the meeting

Your record creation respects every validation rule, required field and workflow rule in your org.

iOS and Android parity

Your reps use a mix of iPhones and Android phones. Your scanner works identically on both. Same tile, same scan flow, same result.

Your training materials are the same. Your rollout is a single Permission Set assignment.

iPhone setup

Your iPhone users install the Salesforce Mobile app and the scanner becomes available once the admin enables it.

Android setup

Your Android users follow the same flow. No platform-specific differences in behaviour.

Offline inside the app

Your Salesforce Mobile App supports offline briefcase mode. Your scanner works within that, captures offline, queues locally, syncs when the Salesforce Mobile session syncs.

Your field reps in coverage-poor areas don’t lose scans. Your pipeline gets the capture whenever connection returns.