A Salesforce business card scanner should reduce retyping without bypassing data review, duplicate checks, ownership, or the team’s qualification process.
Why connect a business card scanner to Salesforce?
A printed business card identifies a person, but it rarely captures why the meeting mattered. A useful scanner workflow structures the visible fields, lets the user correct them, attaches the conversation context, and then moves the approved record to the sales system.
ExpoSnap lets a user connect their Salesforce account through OAuth and send a reviewed card as a Lead. Salesforce describes lead records as a way to track prospects separately before qualified records are converted into contacts, accounts, and potentially opportunities. Your Salesforce configuration and sales process determine what happens after the handoff.
How to scan a business card into Salesforce with ExpoSnap
- Connect Salesforce
Authorize your Salesforce account from the ExpoSnap CRM connection area.
- Capture the card
Photograph the printed card in good light so the visible contact fields can be extracted.
- Review the details
Verify the name, company, title, email address, phone number, and website against the card.
- Add meeting context
Record the event, relevant problem, requested material, timing, and agreed next step without inventing intent.
- Send the reviewed record
Choose Salesforce and sync the approved contact as a Lead.
- Continue in Salesforce
Confirm the record, check ownership and duplicates, and apply the team’s normal qualification and follow-up rules.
Keep event leads usable in Salesforce
Before the Salesforce handoff, review the event lead data cleanup checklist with your CRM administrator so existing contacts and new leads follow the right process.
- Agree on the event source, campaign, or naming convention before scanning begins.
- Review uncertain fields before syncing instead of treating text extraction as final data.
- Check for existing leads, contacts, and accounts according to your Salesforce process.
- Keep factual conversation notes separate from the representative’s qualification assessment.
- Confirm who owns the next step and when it is due after the record reaches Salesforce.
- Use Salesforce reporting for pipeline and revenue outcomes rather than treating scan volume as ROI.
Direct Salesforce sync or spreadsheet import?
Direct sync is useful when individual representatives can review and send records under an established Salesforce process. An Excel or CSV handoff can be better when operations must deduplicate, map fields, approve data, or combine lists before import.
ExpoSnap supports both routes. Choose the route that matches your Salesforce governance, required fields, assignment rules, and event volume rather than assuming every collected card should immediately become a new lead.
Compare the available destinations on the ExpoSnap CRM integrations page, then keep campaign attribution and opportunity reporting in the CRM.
Business card scanner for Salesforce: which Lead fields are sent?
Check the destination as well as the scan. ExpoSnap’s current Salesforce integration writes to the Lead object, not directly to a Contact, Account, Opportunity, or Campaign Member. The mapping below reflects the current integration code; it is not a promise that every extracted card field or every Salesforce custom field transfers.
Review missing names and company information before syncing. The integration includes fallback values to construct a Lead request, but a fallback is not evidence that the original card contained that information. Salesforce organization settings can still reject a request.
| Reviewed card information | Salesforce destination | Current behavior |
|---|---|---|
| Last name | LastName | Uses lastName, otherwise fullName, otherwise Unknown. Check the name split rather than relying on the fallback. |
| Company | Company | Uses company, otherwise fullName, otherwise Unknown. Confirm the actual organization before handoff. |
| First name and job title | FirstName and Title | Included when firstName and designation are present. |
| Email and telephone | Email and Phone | Sends the first saved email and first saved phone number when available. Additional values are not included in this standard payload. |
| Website | Website | Included when the saved card has a website. |
| Capture attribution | Description | The request includes integration attribution. Conversation notes use a separate handoff; verify the resulting record and notes. |
| Street address, custom fields, campaign membership, or assignment settings | Not in this standard Lead payload | Do not assume these are set automatically. Use the organization’s reviewed CRM or import process for additional requirements. |
Required fields and duplicate checks: what to verify with your administrator
Before a busy event, review the Lead field requirements and test the intended handoff with an authorized Salesforce administrator. Salesforce provides an sObject Describe endpoint for examining object metadata. This is an administrator verification option, not a feature that ExpoSnap automatically runs to configure every customer’s field mapping.
The current sync first reuses a CRM record ID already associated with the card. Without that ID, it searches the Lead object using the first saved email and takes the first matching record. This is not a cross-object duplicate check against Contacts and Accounts, nor a fuzzy match across names, phone numbers, or all addresses. Review possible existing relationships before sending.
When operations needs to review identifiers or additional fields first, use the event lead cleanup checklist and a controlled export/import workflow rather than assuming direct sync handles every exception.
- Confirm that the connected user has the access needed to create or update the intended Lead fields.
- Check organization-specific required custom fields, validation rules, and duplicate rules. The current standard payload cannot satisfy every custom process.
- For a card with no email, manually check for an existing record: the email-based fallback cannot identify it.
- Verify campaign attribution, owner, status, and the next activity in Salesforce. Their presence should not be inferred from successful contact capture.
- If Salesforce rejects a request, review the displayed error and destination record before retrying. Do not repeatedly send the same card or weaken governance just to complete an import.
Frequently asked questions
Does ExpoSnap connect to Salesforce?
Yes. A user can connect Salesforce through OAuth and send a reviewed business card record as a Lead.
Does ExpoSnap automatically qualify Salesforce leads?
No. ExpoSnap captures and reviews the contact and supports the handoff. Qualification, ownership, duplicate handling, and conversion follow your Salesforce process.
Can I export business cards before importing them into Salesforce?
Yes. ExpoSnap can export reviewed contacts to Excel or CSV when a controlled import is more appropriate than direct sync.
Does the Salesforce business card scanner check existing Contacts and Accounts?
The current direct sync writes Leads. It reuses a saved Lead record ID or searches Leads by the first saved email; this is not a comprehensive search across Contacts and Accounts. Review existing relationships and your organization’s duplicate rules before syncing.
Sources and further reading
Further reading from event-industry and sales resources. Sample scripts and hypothetical calculations in this guide are illustrations, not customer results.
Put the workflow into practice.
Capture business cards, review contact data, add conversation context, and prepare the next step with ExpoSnap.