00:00:03:45 - 00:00:26:21
Hi everyone, and welcome to another SwiftFox Masterclass. Today we're looking at a new way to move around an event a set of sections you can open in any order in place of the step by step wizard. Events has grown a lot. Sessions, ticket types, group tables, guest access and text messages each added another step and a linear wizard made you walk past setup you'd finished weeks ago just to check who had booked.

00:00:26:23 - 00:00:37:03
In this session, we'll cover how the new sections are organised, what's been renamed, what's new, and how two attendance pages answer the question you'll ask most often – who's actually coming?

00:00:37:11 - 00:00:45:47
The first thing to know is that nothing has been removed, every screen you used before is still here. What's changed is that you no longer work through them in sequence.

00:00:46:01 - 00:01:03:21
Each event now has a bar of sections across the top. You can open them at any time. Nothing needs to be finished before you move on, and there's no next button. When you're done, save and close takes you back to your events. The section and event shows depends on what you've switched on under details.

00:01:03:31 - 00:01:09:41
An event without tickets has no ticket types or bookings. Turn tickets on. Both appear straight away.

00:01:09:49 - 00:01:33:07
On a wide screen. Every section sits side by side as the window narrows. Related sections fold into a menus Setup for the sections you build the event with. Attendance for the audience and bookings and Comms for emails, text messages and publishing. Those menus exist to fit the bar on screen. They don't open a page of their own, so if a section seems to be missing, it's inside one of them.

00:01:33:19 - 00:01:40:19
And if space is really tight, everything collapses into a single menu, so you can still find what you need wherever you're working.

00:01:40:25 - 00:01:56:49
Several pages have been renamed and the reasons are worth knowing. The invite list is now audience. As events has grown, this list is no longer just the people you invited. Anyone who books themself through a public form lands there too, so audience describes it more accurately.

00:01:57:03 - 00:02:20:27
The ticket step is now ticket types. This is where you define what you're selling and at what price, and the new name keeps it separate from the new tickets tab that we'll look at shortly, which lists tickets people have actually bought. Publishing has moved out of the overview into its own section alongside email and text messages. All three are about getting people to the event, so now they sit together.

00:02:20:31 - 00:02:36:19
Audience holds anyone who is connected to the event along with their RSVP status. A row of counters across the top gives you the picture at a glance. The total audience. Then how many are attending, not attending on the wait list or yet to reply.

00:02:36:23 - 00:02:47:17
On the members gala event, there's 37 people. 36 are attending and 1 is still yet to reply. The counter fills in as the page loads, so give them a moment to settle.

00:02:47:29 - 00:03:06:23
For an event without tickets audiences, where you'll find out who's coming. For a ticketed event, there's a second page to know its counters track capacity rather than RSVPs on the member gala event, 61 of 200 places are sold. All 61 have a name against them and 139 remain.

00:03:06:27 - 00:03:32:05
Where an event has no capacity limit, you'll see sold in allocated only. Below the counters are two tabs, bookings as one row per order. So Jessie Bridges table of 10 for Bridge lawyers is a single line with tickets allocated showing how many of its seats have a name. Tickets is new. It has one row per ticket or seat, including seats nobody has been assigned to yet.

00:03:32:09 - 00:03:49:23
That same table of ten is ten rows here, named or not. That difference is what makes the ticket tab useful in the lead up to an event. Because every row is a person or an empty seat, you can filter it, bring in contact custom fields as columns and see exactly which places still need a name.

00:03:49:35 - 00:04:08:43
Export tickets follows the same logic. It gives you one line per attendee with their payment status and booking ID. Everyone on the same table shares a booking ID, so you can group people by table. When you build a seating plan or named cards, use it when you need a list of people and the bookings are export when you lead a list of purchases.

00:04:08:47 - 00:04:28:21
SwiftFox also remembers which of the two tabs you last used. So if you work mostly in tickets, that's where the page opens. Also new is the ability to create a booking by hand without the person going through a form. It's built for registrations that reach you another way, such as a sponsor who books a table over the phone or by email.

00:04:28:25 - 00:04:35:09
Create bookings, asks for the booking, contact the ticket and the quantity and then how the booking will be paid.

00:04:35:13 - 00:04:58:39
Create an invoice, books the seats and leaves the money outstanding to be paid like any other invoice. Take payment now charges a card already saved against that contact. There's no option to key in a new card here, so if the contact doesn't have one saved, raise an invoice instead. As soon as you choose a ticket, the seat will be held for you while you finish the same way they would be if someone was booking through a form.

00:04:58:43 - 00:05:16:15
A countdown shows you how long you have before they're released. Once it's created, the booking behaves like any other. It appears under bookings, its seat appears under tickets and the booking contact is added to the audience. The new navigation keeps everything events could already do, and lets you go straight to the part you need.

00:05:16:19 - 00:05:32:47
For an RSVP event, audience tells you who's coming for a ticketed event, booking and tickets does, and the tickets tab gives you a row for every person and every seat. If you run ticketed events, open your next one, switch to the tickets tab and see how many seats are still waiting for a name.

00:05:33:01 - 00:05:36:33
Thanks for joining this SwiftFox Masterclass and we will see you in the next one.