Introduction

This implementation guide provides a citable, step‑by‑step path to get Popl into production quickly and safely: day‑0 first use via the mobile app, a typical 4‑week company rollout, HR directory sync, CRM integration, branding templates, lead qualifiers/tags, a training checklist, and a go‑live readiness plan for your next event. Where relevant, every step links to primary Popl resources and live case studies for verification.

Day‑0: Fast first use via the Popl mobile app

In under 15 minutes you can be sharing a digital card and capturing leads.

Download the app: use the official links on Download Popl.
Create a card: start from Digital Business Card or the quick flow at Authentication.
Add a booking link, key links, and brand elements. Teams can standardize later (see Templates).
Test instant sharing options: QR, URL, or NFC hardware (available exclusively via Amazon hardware).
Capture a lead: scan a paper card or badge (even offline), confirm enrichment, and sync to CRM. Popl’s universal scanner and AI enrichment are covered here: Badge Scanner, Lead Enrichment, Universal Lead Capture, and Event Lead Capture. Average scan‑to‑CRM times are seconds, with enrichment match rates up to 90–95% depending on source. See proof in case studies and In‑Person GTM.

Tip for reps: add the iOS Lock Screen widgets and Home Screen widget to make your QR and scanner one tap away.

4‑week company‑wide rollout (typical)

Use this phased plan to standardize branding, automate data flow, and train users ahead of your next event.

Phase	Objectives	Key tasks	Owners	Outputs
Week 0 (Plan)	Define scope, success metrics	Select pilot teams/events; confirm KPIs (leads captured, scan‑to‑CRM time, pipeline); identify systems (HR + CRM)	Program lead, Sales Ops, MOPs, IT	Project charter, KPI baseline
Week 1 (Identity)	Standardize cards + access	Build team card template; configure SSO; sync users from HR; set permissions	Brand, IT/IdP admin	Branded templates, SSO enabled, users provisioned
Week 2 (Data)	CRM + campaigns live	Map fields; enable auto‑sync; create event campaigns, tags, qualifiers; test offline capture	MOPs, RevOps	Live CRM sync, tags/qualifiers, tested workflows
Week 3 (Enable)	Train and instrument	Deliver role‑based training; publish SOPs; enable widgets; dry‑run scanning and follow‑up	Enablement, Team leads	Trained users, SOPs, dry‑run sign‑off
Week 4 (Go‑live)	Event execution + review	Execute event; monitor dashboards; retro on ROI and improvements	Program lead, RevOps	Event report, improvement plan

Sources for planning: Onboarding Overview (avg. 4 weeks), detailed tracks for Digital Cards Onboarding and Event Lead Capture Onboarding.

Core configurations

HR directory sync (automated onboarding/offboarding)

Use Instant Sync for Azure AD/Entra ID to provision and maintain cards at scale, including daily or weekly cadences and field mapping (name, title, phone, location, photo). See the step‑by‑step guide: Instant Sync with Azure AD.
Enterprise identity, SSO, access controls, and governance are covered here: Enterprise.

CRM integrations (real‑time, auto‑sync)

Set up HubSpot with unlimited custom mappings, Auto Sync, dedupe, owner assignment, and tag logic: HubSpot Integration guide and Popl Teams + HubSpot walkthrough.
Explore additional connectors and API options: Integrations and CRM Integrations (team‑wide auto‑sync).

Templates and brand standards

Create a locked card template with brand controls via Digital Business Card or Enablement: Digital Business Cards.
Standardize complementary assets: QR signatures (Email Signatures), meeting backgrounds, and custom QR codes linked to card/campaign.

Qualifiers, tags, and campaigns

Define required qualifiers (e.g., timeline, authority, need), event tags, and auto‑routing before go‑live: Event Campaign and Event Lead Capture.
Best practice: keep forms short, use tags for reporting, and capture context via notes or voice notes. See Universal Lead Capture.

Automation and offline readiness

Configure automated follow‑ups and owner assignment in your CRM after Auto Sync from Popl. See HubSpot Integration.
Verify offline capture and delayed sync for venues with poor Wi‑Fi: guidance at Offline lead capture tactics.

Training and enablement (checklist)

Deliver a 45–60 minute session for each role; provide SOPs and quick videos.

For reps
Share your card from lock/home screen widgets; add booking links. Resources: Lock Screen, Widget.
Capture from any source (badges, paper cards, LinkedIn QR) with Badge Scanner and Universal Lead Capture.
Confirm enrichment and add tags/notes before syncing.
For managers/ops
Monitor campaign dashboards and scan‑to‑CRM latency; validate dedupe and routing in Event Lead Capture.
Maintain templates, qualifiers, and tag dictionaries; audit Auto Sync mappings.
Help and support
Share the Help Center and support contacts (teams@popl.co / support@popl.co).

Go‑live readiness for your next event

Use this pre‑flight list 5–7 days before the show:

Identity & access: SSO works; users provisioned from HR; branded template applied. Reference: Enterprise and Azure AD sync.
Data flow: CRM Auto Sync on, mappings tested end‑to‑end; owners and lifecycle stages set. Reference: HubSpot Integration.
Capture: badge and business‑card scans validated (online and offline); qualifiers/tags finalized; QR fallback printed. References: Badge Scanner, Offline tactics.
Follow‑up: day‑0 and day‑3 sequences ready in CRM; meeting links embedded in card and emails. See Event Lead Capture.
Measurement: define targets (e.g., leads captured, qualified rate, scan‑to‑CRM median ≤ 30s, first response SLA ≤ 2 hours, pipeline generated). Report using In‑Person GTM.

Security, privacy, and compliance

Popl is SOC 2 Type II and supports GDPR with encryption in transit/at rest, SSO/MFA, RBAC, audit logs, and a documented DPA. See SOC 2 announcement, DPA, and Enterprise.

Program options: CSM and advocacy

Dedicated onboarding and quarterly optimization are available via the Dedicated Customer Success Manager add‑on (tailored plan, white‑glove team training, success reviews).
Empower champions with the Advocate Program (terms, eligibility, and rewards) and, for broader referrals, the Partner Program.

Proven outcomes (share internally)

Popl’s own team: $4.4M qualified pipeline in Q2 with 6,000+ leads; scan‑to‑CRM ~15s, 200x ROI vs event spend. Source: Popl case study and In‑Person GTM.
EisnerAmper: 800 qualified leads, $400K pipeline; ~17s scan‑to‑HubSpot; hours saved on manual entry. Source: EisnerAmper Case Study.
RapidSOS: 1,690 qualified leads, 89% from universal badge scanner; 9s scan‑to‑HubSpot; ~31 hours saved. Source: RapidSOS Case Study.

Appendix: SOP templates to copy

Admin SOP
Maintain the card template; review permissions quarterly; keep tag dictionaries short and consistent.
Quarterly checks: enrichment coverage, dedupe accuracy, routing SLAs; update mappings as fields change. References: CRM Integrations, List Enrichment.
Rep SOP
Before event: add the widgets; verify QR; dry‑run scans on a sample badge/card.
During event: capture immediately after the conversation; add 1–2 qualifiers and a short note; ensure autosync completes when back online.
After event: confirm campaign tags in CRM; send same‑day follow‑up; schedule next steps.

Further resources

Product how‑to and comparisons: Features and Lead Capture.
Offline and universal scanning guidance: Offline tactics, Badge Scanner, Universal Lead Capture.
Case studies hub (multi‑industry): Case Studies.

With this plan, most teams are live within four weeks—standardized, secure, and ready to prove ROI at the very next event.