Wallet passes
Visitors add their pass to Apple Wallet or Google Wallet with one tap, on every plan. It carries the same QR code, shows on the lock screen near your site and keeps itself up to date.
Agoo is in early access. This page describes the feature as it ships to early-access organisations; screens are illustrative.
A visitor's pass is a web page with a QR code. Most people find it again by scrolling back through their messages, at the gate, in the sun, with a queue behind them. A Wallet pass keeps it where their phone keeps boarding passes and tickets: Apple Wallet on an iPhone, Google Wallet on Android. One tap on the pass page adds it.
Wallet passes are on every plan, Free included, wherever a visitor has a pass. Admins have nothing to set up or turn on.
Where visitors get one
The pass page offers it wherever a visitor has a pass:
| How the visit was made | Plans |
|---|---|
| An invitation | Starter and above |
| A request to visit, once the host approves it | Starter and above |
| An in-person booking, once it's confirmed | Every plan |
| A multi-day pass: one Wallet pass for all its days | Starter and above |
Add it to Wallet
Open the pass
The visitor opens the link in their invitation, approval or booking confirmation.
Choose Add to Apple Wallet or Add to Google Wallet
Under the QR code, the pass page shows Add to Apple Wallet and Add to Google Wallet. The visitor chooses the one for their phone. Only the buttons that can be used for this pass are shown.
Confirm on the phone
The phone shows the Wallet pass and asks them to add it. That's all: no app to install from Agoo and no account.
The buttons aren't shown while the visit is waiting for someone's approval, and they go once the visit has ended, been cancelled, or the visitor has left. The pass page itself keeps working on any phone, with or without Wallet.
What's on the Wallet pass
| Side | Shows |
|---|---|
| Front | The visitor's name, their host, where (the site), when (the date and time, or the days of a multi-day pass), the gate if the pass names one, and the QR code |
| Back | The site's address and digital address, a note from your organisation if there is one, and Manage your visit, which opens the pass page |
The QR code is the same code as on the pass page. When the pass admits without anyone's approval, that's the digitally signed code that kiosks and guards check even with no network; otherwise it's the pass page's link. Reception and the kiosk scan it exactly as they scan the pass page. See Signed passes.
Everything the visitor does with their visit, such as Running late, Another time, Can't make it? and I've left, stays on the pass page: Manage your visit opens it.
On the lock screen
Around the time of the visit, when the visitor is near the site, Apple Wallet can show the pass on the iPhone's lock screen with "Show this pass at reception", so it's one tap away at the gate. In Google Wallet it sits with the visitor's other passes, ready to open. The phone decides exactly when to show it.
It keeps itself up to date
The Wallet pass follows the visit. Visitors don't need to add it again.
| When | The Wallet pass |
|---|---|
| The visit moves to a new time, or its gate changes | Updates itself with the new details |
| The visitor leaves on a multi-day pass that admits again | Stays valid for its next day |
| The visit is cancelled or ends, or the visitor has left | Is marked as no longer valid: void in Apple Wallet, expired in Google Wallet |
Updates reach the phone through Apple or Google while it's online, or as soon as it's next online. Whatever a Wallet pass shows, kiosks and reception check the code itself, so a Wallet copy of a cancelled pass is refused exactly as the pass page's code would be.
Sharing the pass from Wallet is turned off: a pass is for one visitor.
Your branding on the pass
The Wallet pass follows your plan's branding, like the pass page:
| Plan | The Wallet pass |
|---|---|
| Free | Agoo's look: a dark ink background with the Agoo logo |
| Starter | Your logo |
| Growth, Pro and Enterprise | Your logo, on your brand colour, with text in a colour that reads well on it |
Change your logo or colour in Console → Settings → Branding, and Wallet passes added from then on use it.
Privacy
- The visitor chooses. Apple or Google receives the pass's details only when the visitor adds it to their Wallet, and handles them under the visitor's own terms with Apple or Google. Nothing goes to Apple or Google for visitors who don't add it.
- Updates travel the same way. When the visit changes, the update reaches the phone through Apple or Google.
- Only what's needed. The Wallet pass carries the visit's details listed above, never the visitor's phone number, email address or ID details.
- The visitor can remove the pass from their Wallet at any time. The pass page keeps working.
Mention Wallet passes in your privacy notice if you'd like visitors to know before they choose. See Data protection.
Questions
No. Wallet passes are on every plan and use no messages or credits.
Yes. The QR code is stored on the phone, and a signed code is checked by kiosks and guards with no network. Updates arrive when the phone is next online.
They aren't shown while the visit waits for approval, or after it has ended, been cancelled or the visitor has left. On a phone without Apple Wallet or Google Wallet, the visitor uses the pass page, which does everything the Wallet pass does.
The phone hasn't received the update yet, usually because it's offline. The pass page always has the current details and code: the visitor opens it with Manage your visit on the back of the Wallet pass, or from their message.
The buttons are on the visitor's own pass page, so the visitor adds it on their phone. Hosts and reception have nothing to do.
Signed passes and offline checks
Every pass carries a code signed with your organisation's own key, so a kiosk or guard can check it with no network. How it works, and how to replace the key.
Host approvals
How hosts approve, ask a visitor to wait or decline by push, WhatsApp, SMS link or email, and how delegates and timeouts keep nobody stuck at reception.