You don't pre-generate a pass for every contact in your CRM. PocketPass uses lazy enrollment: each customer gets a personal install link, and the pass is created the instant they click it and add it to their wallet. Nobody who ignores the link ever becomes a pass you have to manage.
How lazy enrollment works
When you connect a CRM and Refresh customers, PocketPass writes a personal install link onto each contact. Send that link, and the customer's pass is created the moment they open it and add it to their wallet - not before. This keeps your pass list to the people who actually carry one.
PocketPass then writes back onto the same contact:
- the Apple Wallet and Google Wallet links for the pass, and
- an "installed" Yes/No flag.
So your CRM record shows, per contact, whether they hold a pass and where to send them to get it. You can see the same view per customer at /dashboard/customers.
Add install buttons to your emails
Drop the merge tag for the install page (or the direct Apple/Google links) into an email and it renders as that contact's personal link. Use the block type that lets you paste raw markup.
Klaviyo - into a Text block (raw HTML):
{{ person.PocketPassInstallPageURL }}- the install page (Apple or Google auto-detected){{ person.PocketPassAppleWalletURL }}- Apple Wallet direct{{ person.PocketPassGoogleWalletURL }}- Google Wallet direct
Mailchimp - into a Code block:
*|PPURL|*- the install page*|PPAPPLE|*- Apple Wallet direct*|PPGOOG|*- Google Wallet direct
Me&u Connect - into an HTML block:
{{contact.pocketpassInstallUrl}}- the install page{{contact.pocketpassAppleUrl}}- Apple Wallet direct{{contact.pocketpassGoogleUrl}}- Google Wallet direct
The install page link is the safe default - it detects the device and offers the right wallet. Use the direct Apple/Google links only when you're building separate "Add to Apple Wallet" and "Add to Google Wallet" buttons.
Which template a customer gets
Two things decide the template, and one always wins.
Template rules (automatic). Map a CRM list or segment to a template. When a customer enrolls, PocketPass walks the rules and uses the first match, so order your rules from most specific to most general. Rules read the same audiences covered in Lists, tags & segments from your CRM.
Per-customer override (manual). On a customer's page under /dashboard/customers you can set the template for that one person. The per-customer choice always wins - it overrides whatever the rules would have picked.
An override sticks to that customer even if their CRM audiences change later. Use it for one-off exceptions; use template rules for anything you'd want to apply to a whole group.
Where to go next
- Connect your CRM: Klaviyo, Mailchimp, or Me&u Connect.
- Lists, tags & segments from your CRM - the audiences template rules read.
- Choosing an audience - targeting the passes you've created.