Support
Communications

Email and push notifications to your ticket list, traced to delivery per person.

The confirmation, the reminders, the room on the morning, a schedule change, your own broadcasts. Designed once in your brand, sent to the same list the door checks, and every send answers sent, delivered, opened or bounced, name by name.

One list for the ticket, the email and the door. Every send leaves a row.

2
Channels
Email, and a push notification to the app. Both from the same list.
48 h
The reminder, before doors
Then one a day out, then one an hour out. Anchored to the date, not to your memory.
1
List
Whoever holds a ticket at that moment. The door scans the same one.
4
Answers per person
Sent, delivered, opened or bounced, for every name on every send.
On the phone

A push notification for what cannot wait. An email for what should be kept.

The room, a change, a message from you: a push notification on the phone they carry. The ticket, the programme, the receipt: an email in the inbox. Written once, sent to the same list, and the app is already updated when either arrives.
The push, on the phone
The programme, already changed
Your brand

Design the email once, in your colours. Every confirmation and reminder wears it.

Blocks, not a template: your logo, the cover, the ticket with its QR code, the buttons, your footer line. Set the brand on the Style tab and every message the event sends resolves to it, so the reader sees you, not the mail tool.
MessagesStyleDelivery

Brand

  • Colour#0F2A5C
  • LogoA Players Club
Founders blue

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
A PLAYERS CLUBAmsterdam Founders Summit

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

Open your ticket
Add to Apple Wallet

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.

A

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
Open your ticket
Add to 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.

Delivery

See per person whether a message was sent, delivered, opened or bounced.

Every send is a list of names with an answer beside each one. A quiet week is a fact you can act on, and a bounce is a person you can call before the day, not a percentage in a report.

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
Audience

Send to everyone with a ticket, or to one ticket tier only.

The audience is the ticket list, picked by tier. A message about the VIP dinner reaches the 22 people it concerns and nobody else, and the list is never a week old because it is not a copy.

To

Who gets this message

  • Everyone with a ticket146
  • Early bird41
  • Standard83
  • VIP22
Send to 22 people

The VIP dinner reaches VIP holders and nobody else. The list is the ticket list, so it is never stale.

The record

Every notify-or-not is a decision the event records, with who made it.

A moved session, a corrected address, a cancelled clinic: each one asks whether to tell the room, and each answer is a row in History. Choosing silence is recorded too, so nobody has to wonder later whether the room was told.

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.

The usual way

What changes when the email list is the ticket list.

The listA mail tool fed by an exported spreadsheetThe ticket list the door checks, always current
DeliveryA reply asking whether the email arrivedSent, delivered, opened or bounced, per person
The reminderOne you remember to sendThree, scheduled off the event date
A schedule changeAn email nobody sees in timeA push notification, and the app already updated
The VIP dinnerA filtered export, hopefully rightOne tier, picked from the ticket list
The designA template that looks like the mail toolBlocks, your colours, your name

The left column is your own experience of a mail tool fed by a spreadsheet. Nobody else’s product is named, on purpose.

The numbers

Every send shows what happened to it: delivered, opened or bounced, per person.

Sent is not delivered. The Delivery tab says which one it was, for every message and every name.

Five sends, and what each one did.

Delivered, opened and bounced, per message, from the Delivery tab.

Confirmation
131 opened
Reminder · 48 h
98 opened
Get ready · 1 day
104 opened
Doors open · 1 h
121 opened
Dinner tonight · VIP
21 opened
OpenedDeliveredBounced

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.

On your desk

Every message the event sends, on the Comms tab, in the order a guest lives them.

Messages, Style and Delivery in one hub: what goes out and when, in your brand, and what happened to each one. The rows are the product’s own defaults, on from the day you publish.

The list you email is the list the door scans.

The people who bought are the people you write to are the people the scanner admits. There is no export between the three, so a reminder cannot go to last year’s list and the door cannot disagree with the inbox.
Straight answers

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.

Also in the product

Check-in, the event page and the app run on the same ticket list.

The app

A real app on the App Store, for them and for you.

See the app
Ticketing & payments

You are the merchant. The money goes to you as you sell.

See ticketing & payments
Who's going

People arrive already knowing who to meet.

See who's going
Get started

Reach your next event’s room, not a spreadsheet.

© Confexio