Loading…
Every enrollment ends up in the same place: an application row, a customer record in DK, and a wallet pass. How the application is created is up to you.
Open Enroll a member, pick a program, and fill in the customer's name, kennitala, email, and phone. If the program is open, the pass is issued immediately and the email goes out within seconds. If it requires approval, the application sits in the queue.
Enrolling an existing customer? Open their customer profile and click Enroll in a program. The form is pre-filled from their record and the pass attaches to that customer — no duplicate. Anything you add (a missing email or phone) saves back to the customer.
Programs with the public form enabled have a URL of the form /enroll/{tenant-slug}/{program-slug}. Open that URL on a kiosk iPad or share it with the customer to fill out themselves. The form is tenant-branded, requires no Stokk login, and runs the same enrollment pipeline.
Most enrollees aren't in DK yet. Stokk creates the DK customer first, mirrors it locally, then issues the pass. Returning customers (kennitala already in DK) are reused — no duplicate records.
To remove someone, open them in CRM → the Loyalty box → Revokenext to their card. The pass stops working immediately and is pushed off their phone (cleared from Apple Wallet, greyed out in Google Wallet). It can't be undone — they can re-enroll for a fresh card.