Events · Marketing
Fill the room. Keep the people who came.
From the event page to the books, in five steps.
The event page is up, with its tickets
An event is a record: a date, a venue, a quota, one or more ticket types with a price or none. Publish it and it is a page on your site with a registration form on it.
From the event page to the books, in five steps.
An event is a record: a date, a venue, a quota, one or more ticket types with a price or none. Publish it and it is a page on your site with a registration form on it.
Tickets, the form, the waiting list, the sponsor.
What a ticket is, who may register and what the reminder says are yours to set.
Ticket types with a price and a quota
Free, paid, by invitation only, early bird until a date: each with its own quota and its own form.
Your questions on the registration
Dietary needs, the company, how they heard of you: fields on the registration, so they are on the contact afterwards.
A waiting list that fills itself
A cancellation frees the seat; the first on the list gets it, with a deadline, and the next one if they let it lapse.
Sessions, speakers, rooms
A programme when the event has one: sessions on a timeline, each with its room and its speaker, published on the page.
Sponsors on the record
A sponsor is a line on the event with its package and its level, on the page in that order, and an invoice from that line.
The figures while it happens
Registered against quota, sold out, waiting, checked in, from the same records.
The same event, for a brewery that sells tastings and a firm that hosts its clients.
What adapts: what a registration is (a seat, a session, a place at a table), what a ticket costs and includes, the questions on the form, what happens at the door, and what the registration turns into afterwards. Two businesses can run Events and disagree on every one of those.
A microbrewery's open-door tasting
A registration is a seat in a Saturday session, two sessions of 25. The ticket costs €12.00 and includes three tastings, the form confirms the age, and the door hands out a wristband. The ticket is sold in the shop beside the bottles, and the day's revenue is the day's sales.
An accounting firm's client seminar
A registration is by invitation only and free, one seat per client, with a question submitted on the form. The door prints a badge. The next morning each attendee has an attendance certificate for their training hours, generated from the registration, and their contact on the CRM carries the question for the partner's follow-up.
At the door, on a phone.
Sofie holds the phone at the door. The ticket is scanned, the name and the ticket type come up, and the registration is checked in. Someone arrives without one: she types the name, the registration is created on the spot and the badge prints from it. The count at the desk is the same count she sees.
This is the room.
The event record: tickets against their quotas, the registrations and the waiting list, the sponsors and their invoices, the programme, the documents it produces and the rules that run it.
What the event leaves behind.
A ticketing tool ends the evening with a payout and an export. Here the registration returns to the contact it belongs to, and the contact does what a contact should: it carries "Attended", it gets the follow-up, it is in the next segment. The invitation came from your campaigns, the page sits on your site, the paid ticket went through your shop, and the sponsor's package is an invoice in your books.
The invitation and the follow-up. The invitation goes to a segment of your contacts; the reminder, the "sorry we missed you" and the "thank you for coming" are campaigns on the event's own list.
See Email Marketing.
The invitation and the follow-up. The invitation goes to a segment of your contacts; the reminder, the "sorry we missed you" and the "thank you for coming" are campaigns on the event's own list.The contact. Every attendee is on the CRM with the events they came to, the answers they gave and the next activity planned.
See CRM.
The contact. Every attendee is on the CRM with the events they came to, the answers they gave and the next activity planned.The page. The event page is a page on your site, published from the record, with the form and the tickets on it, in your design.
See Website Builder.
The page. The event page is a page on your site, published from the record, with the form and the tickets on it, in your design.The ticket in the shop. A paid ticket is a product; the order carries the registration and the seat, and pays online through a payment provider ⟨to confirm⟩.
See eCommerce.
The ticket in the shop. A paid ticket is a product; the order carries the registration and the seat, and pays online through a payment provider ⟨to confirm⟩.Built for businesses whose events are for people they already know.
Showrooms, breweries, accounting and law firms, associations, training centres, agencies: the businesses that run an open evening, a tasting, a seminar or a members' day a few times a year, for clients, prospects and members who are already in their contacts. The event is not the product. It is a moment in a relationship that exists before the invitation and continues after the door closes.
The ticketing tool you would otherwise buy hands you a payout and an export.
An event page with tickets and quotas
- A spreadsheet
- A form and a link
- A ticketing tool
- Yes
- A suite module
- Yes
- Enobase
- Yes, a page on your own site
Your questions on the registration
- A spreadsheet
- Yes
- A ticketing tool
- Yes
- A suite module
- Yes
- Enobase
- Yes, saved on the contact
Reminder and waiting list
- A spreadsheet
- By hand
- A ticketing tool
- Yes
- A suite module
- Yes
- Enobase
- Yes, rules you can read
Check-in on a phone
- A spreadsheet
- A printed list
- A ticketing tool
- Yes
- A suite module
- Sometimes
- Enobase
- Yes, and the walk-in is registered there
The attendee on your CRM with their history
- A spreadsheet
- Copied
- A ticketing tool
- Exported
- A suite module
- Yes, in their CRM
- Enobase
- Yes, the same contact
Ticket revenue in the ledger with its VAT
- A spreadsheet
- Typed in
- A ticketing tool
- A payout
- A suite module
- Yes, in their accounting
- Enobase
- Yes, per ticket type
The sponsor's invoice
- A spreadsheet
- Typed in
- A ticketing tool
- No
- A suite module
- Yes
- Enobase
- Yes, from the sponsor line on the event
Time to live
- A spreadsheet
- A day
- A ticketing tool
- An hour
- A suite module
- Months
- Enobase
- One week
| What you need | A spreadsheet | A ticketing tool | A suite module | Enobase |
|---|---|---|---|---|
| An event page with tickets and quotas | A form and a link | Yes | Yes | Yes, a page on your own site |
| Your questions on the registration | Yes | Yes | Yes | Yes, saved on the contact |
| Reminder and waiting list | By hand | Yes | Yes | Yes, rules you can read |
| Check-in on a phone | A printed list | Yes | Sometimes | Yes, and the walk-in is registered there |
| The attendee on your CRM with their history | Copied | Exported | Yes, in their CRM | Yes, the same contact |
| Ticket revenue in the ledger with its VAT | Typed in | A payout | Yes, in their accounting | Yes, per ticket type |
| The sponsor's invoice | Typed in | No | Yes | Yes, from the sponsor line on the event |
| Time to live | A day | An hour | Months | One week |
Questions about Events
Yes. On its own it is an event page, tickets, a registration list and a phone at the door. Turn CRM on and the attendees are contacts with a history; turn Email Marketing on and the invitation is a campaign; turn eCommerce on and the paid ticket is an order in your shop.