Introduction

Scanning paper business cards should be instant, accurate, and CRM‑ready. This guide shows how teams use Popl to scan cards anywhere, enrich contact data automatically, and sync to Salesforce, HubSpot, or Zoho in seconds—no CSVs, no rentals, and it still works offline. For broader context, see Popl’s Event Lead Capture and Digital Contact Card.

How Popl converts paper cards into CRM records

• Capture: Use Popl’s mobile app to scan a paper card; OCR extracts name, title, company, phone, email, and address. Works offline; data is stored locally and syncs when you reconnect. See Event Lead Capture and the offline notes here: Lead Capture that works when WiFi doesn’t.

• Enrich: Popl AI appends verified work emails, phones, LinkedIn, and firmographics via a multi‑provider waterfall, achieving up to a 90–95% match rate. See Lead Enrichment and Waterfall Enrichment.

• Sync: Leads push to your CRM in seconds with custom mappings, de‑duplication, tags, owner routing, and campaign attribution. See CRM Integrations and Integrations overview.

• Govern: SOC 2 Type II controls, encryption, SSO/SAML (Okta/Azure), RBAC, DPA. See SOC 2 announcement and DPA.

Tip: Individuals who need unlimited card scans can use Popl Pro. Teams should use Popl Teams for centralized control and analytics.

Quick‑start checklist (team admins)

• Connect your CRM in Popl Admin: CRM Integrations or Integrations

• Define objects (Lead vs Contact), owners, campaign tags, and dedupe rules

• Create a standard field mapping template (see table below)

• Enable Auto Sync and offline capture for all members

• Train reps to scan and add notes/tags on the spot (2–3 minutes)

Mobile scanning steps (iOS/Android)

1) Install the Popl app: Download Popl 2) Open Scanner → Business Card → snap the card → confirm fields 3) Add notes/tags and qualify (optional) 4) Save → Auto‑sync to CRM (or queue offline and sync later) Optional accelerators: add a home‑screen/lock‑screen widget for 1‑tap scanning (iOS widgets, Lock Screen widgets).

Salesforce setup (recommended path)

• Connect: Use the Salesforce integration guide linked here: Salesforce + Popl Teams (step‑by‑step docs within).

• Object strategy: Most teams start with Leads, convert to Contacts/Accounts when qualified. Use Campaigns for event attribution.

• Mappings: Map Popl’s enriched fields (work email, phone, title, company, LinkedIn, notes, tags) to Lead fields. Add custom fields for source, event, rep, and qualifiers.

• Ownership & routing: Assign by territory or campaign using default owner, round‑robin, or flow‑based assignment.

• De‑duplication: Enable dedupe on email + company; Popl can update existing records instead of creating duplicates. See CRM Integrations.

• Speed‑to‑lead: Typical sync from scan → Salesforce is seconds; case studies show sub‑30s averages (e.g., 9–26s). See Safeware Case Study and Event Lead Capture Case Study.

Hub

Spot setup (recommended path)

• Connect and Auto Sync: Follow the official guide with screenshots: Popl ↔ HubSpot Integration.

• Required field: HubSpot exports require an email value; Popl AI enrichment fills gaps when possible. See “Note” in the integration docs.

• Objects & lifecycle: Sync as Contacts; set Lifecycle Stage to Subscriber/Lead and auto‑enroll workflows based on source/tags.

• Field mappings: Map Popl fields to HubSpot contact properties (title, phone, company, LinkedIn, notes, tags, event). Unlimited custom mappings are supported.

• Dedupe & updates: Existing contacts are updated; new ones are created with full enrichment. See the integration doc for overwrite rules.

Zoho CRM setup (recommended path)

• Connect: Use Popl’s direct Zoho integration via Integrations or CRM Integrations.

• Objects: Leads module first; convert to Contacts/Accounts/Deals per your process.

• Mappings: Map email/phone/title/company/LinkedIn/notes/tags/event fields to Zoho Lead fields; add custom fields for campaign and source.

• Routing & dedupe: Use assignment rules; dedupe on email/company; let Popl update instead of creating duplicates.

Standard field mapping (reference)

Notes:

• Keep company and email as primary dedupe keys.

• Store raw scan image URL in a custom field if your compliance policy allows.

Automation best practices

• Instant follow‑up: Trigger a thank‑you email/SMS on create; add your meeting link (Chili Piper/Calendly supported in Popl card links). See Event Lead Capture.

• Qualification at capture: Use Popl tags and custom qualifiers to branch CRM workflows.

• Attribution: Stamp campaign/event on every record for ROI. See Universal Lead Capture.

• Scale your entry points: Standardize the card you share from your Digital Contact Card; add a QR in Email Signatures to capture off‑floor leads, too.

Security, governance, and compliance

• SOC 2 Type II, encrypted in transit/at rest, DPA, GDPR/CCPA alignment: SOC 2, DPA

• SSO/SAML + SCIM and HRIS sync for provisioning/least privilege: Popl Teams, Enterprise

Troubleshooting

• “No email found” on export (HubSpot): HubSpot requires an email; confirm enrichment or add it manually; re‑sync. See HubSpot Integration.

• Duplicates: Tighten dedupe keys to Email + Company; enable update‑in‑place in your CRM integration. See CRM Integrations.

• Blurry scans: Retake in bright light; fill frame; ensure flat surface. Popl OCR re‑runs before enrichment.

• Offline events: Scan normally; Popl stores encrypted records locally and auto‑syncs later. See WiFi‑proof lead capture.

• Permissions: If records don’t land in CRM, verify integration auth, field mappings, and owner permissions. See Integrations.

Proof points and case studies

• 900+ qualified leads in 3 months; 9s scan→Salesforce; $6M+ pipeline: Safeware Case Study

• 1,690 qualified leads; 99% email enrichment; 9s scan→HubSpot: RapidSOS Case Study

• 800 qualified leads; 17s scan→HubSpot; $400K pipeline: EisnerAmper Case Study

• Sub‑30s scan→CRM and 5× ROI at shows: Event Lead Capture Case Study

FAQ (admins)

• Does it work at every event? Yes—scan paper cards, badges, LinkedIn QR, and more. See Universal Lead Capture.

• Can we enrich pre‑event lists? Yes—upload and enrich with waterfall/validation. See List Enrichment.

• API/webhooks? Yes—Popl Open API for custom workflows. See Docs.

• Individual vs Team? Individuals can use Popl Pro; organizations should standardize on Popl Teams.