Email and push notifications to your ticket list, traced to delivery per person.
One list for the ticket, the email and the door. Every send leaves a row.
A push notification for what cannot wait. An email for what should be kept.
Design the email once, in your colours. Every confirmation and reminder wears it.
Brand
- Colour#0F2A5C
- LogoA Players Club
Blocks · Confirmation
- HeaderYour logo, the event’s name
- CoverThe event cover, full width
- TextHi {first name}, you are in.
- TicketThe QR code, the tier, the seat
- ButtonOpen your ticket · Add to Wallet
- FooterYour name, your contact line
Sofia, you are in.
Your VIP ticket for Thursday 22 April is below. Show the code at the door, or add it to your Wallet.
VIP · #8811
Doors 08:30 · Concertzaal
Thursday 22 April
A Players Club · Questions? Reply to hello@aplayersclub.com
The run of messages
From the confirmation to the morning of, every message is scheduled off the event date.
Set up when you publish. Sent without you. Asked about when it should be.
Step 1 of 4
The confirmation goes out the moment they buy, with the ticket in it.
Amsterdam Founders Summit
Just now · sent on the order
Your ticket to Amsterdam Founders Summit
Hi Sofia, you are in. Your VIP ticket and its QR code are below. Open it in the app, or add it to your Wallet.
- TicketVIP · #8811
- Thursday 22 AprilDoors 08:30 · Concertzaal
- WalletApple Wallet · Google Wallet
Sent on every order and every RSVP, designed once in your brand.
Every order and every RSVP sends one: their ticket and its QR code, the link that opens it in the app or the browser, and the Wallet pass. Designed once in your brand, sent every time without you.
See per person whether a message was sent, delivered, opened or bounced.
Reminder
Sent Tue 20 April, 09:15
146 people
- Sofia MarinVIPOpened · 09:21
- Jonas BergStandardDelivered · 09:15
- Priya RamanStandardOpened · 10:04
- Marc DeleonEarly birdBounced
- Delivered141 of 146
- Opened98
- Bounced2 · names, not a rate
Send to everyone with a ticket, or to one ticket tier only.
To
Who gets this message
- Everyone with a ticket146
- Early bird41
- Standard83
- VIP22
The VIP dinner reaches VIP holders and nobody else. The list is the ticket list, so it is never stale.
Every notify-or-not is a decision the event records, with who made it.
History
This week
- Investor roundtable moved to 11:30Notified · push + emailNadia · 10:52
- Venue address correctedNot notifiedNadia · Mon
- Pricing clinic cancelledNotified · push + emailSaved default
- Dinner tonight: De Kas, 19:30Sent to VIP · 22 peopleNadia · 16:40
What changed, whether the room was told, on which channels, and who decided. Choosing not to notify is a row too.
What changes when the email list is the ticket list.
The left column is your own experience of a mail tool fed by a spreadsheet. Nobody else’s product is named, on purpose.
Every send shows what happened to it: delivered, opened or bounced, per person.
Five sends, and what each one did.
Delivered, opened and bounced, per message, from the Delivery tab.
Opened, not just sent.
The reminder, person by person.
98
opened of 141 delivered
The reminder, two days out.
Bounces are names.
Two people to call, not a percentage to worry about.
- Marc DeleonAddress does not existHard bounce · suppressed from future sends
- Lena AaltoMailbox fullSoft bounce · tried again
The run, anchored to the date.
Set up when you publish. Each send goes to whoever holds a ticket at that moment.
Move the event a week and every stop moves with it.
Every message the event sends, on the Comms tab, in the order a guest lives them.
The list you email is the list the door scans.
Your own domain, replies, SMS, and what it does not do yet.
Yes, we set that up for you. Every email is designed in your brand with your event's name on it, and sending from your own domain is part of the brand set-up our team does with you.



