Run the event. Know who came.

A page for it, tickets or a plain RSVP, the reminders, and a door you check people through from your phone. Everyone who came is already in your contacts.

A small cream-and-violet shop building at dusk, string lights across its open door, a small-business owner in the doorway holding up a phone to the glowing ticket on an arriving guest's phone, three more people waiting in a short line behind.

You run a workshop, a class, a talk, an open evening. People come.

It's everything around it that's yours to carry. The ticketing site has the money. The spreadsheet has the names, because you copied them out of the ticketing site. The reminder is an email you send at eleven the night before, from your own inbox, with everyone in BCC. And on the day, it's a printout and a pen.

You've got ideas for the next three. The names from the last one are still in that spreadsheet.

A small-business owner at a folding table beside a lit doorway in the evening, pen over a printed list of blank lines, a laptop with an empty spreadsheet open beside it, a lantern on the table corner.

The event is the easy part. The week on either side isn't.

The event itself usually goes fine. It's the week on either side. Before: who's paid, who's confirmed, and who needs the link again. After: a printout with ticks next to some of the names, which nobody does anything with, because the next thing has already started.

And a free event with a page and an RSVP is a real event. Nothing has to be sold for it to be worth running.

What you get for every event.

  • A page for the event that looks like yours. What it is, when, where, who's speaking, what it costs. It lives on your website, or anywhere else you put it. Where your site comes in

  • Tickets, free or paid, more than one kind. Each with a price, a number available, and a window they're on sale. Or a plain RSVP with no payment step at all. A cap on numbers, or none.

  • In person, with a map. Or online, with the link on the page, shown when you decide.

  • The reminder goes out without you. Confirmations and reminders go out by email on their own, and you're told when somebody registers. Nobody's in your BCC line.

  • At the door, your phone instead of the printout. There's a QR code on every ticket. Scan it, and they're in. You can see who's come in while it's happening.

  • Everyone who registers is a contact in your account. Not a row in an export you copy out later.

Paid tickets go through the same payment setup as everything else you sell. The only fee on a paid ticket is the card processing — there's no platform fee on top. How the money side works

Somebody registering, or checking in, can set a workflow going. What automations do

The people who came to your event are people you keep.

The person who bought the ticket was in your contacts before they walked in, and they're still there after they leave. So whatever comes next — the thank-you, the recording, the next thing you're running — goes to somebody you already know. Not to a list you first have to get out of the ticketing site.

And because they were checked in at the door, you know who came. Not just who paid.

A small-business owner in a cream cardigan waving beside an open doorway, holding a check-in tablet, three contact cards drifting from the door into their open satchel.

Events for your members, or for anyone.

An event just for the people in your community — a live call, a session — can live inside the community itself, where they already are. How communities work

This page is the other kind: public, with a page anyone can find, and a ticket or an RSVP for people who aren't members yet. And a session you run inside a course is a lesson, not an event. Courses are over here

What events and ticketing cost.

Events are part of the software at $127 a month. Set the first one up yourself, or put it in your queue and the team sets it up for you.

See what's in the price How the team works

Questions people ask about events and ticketing.

Can I run a free event, or does it have to sell tickets?

It can be free. An event can take paid tickets, free tickets, or a plain RSVP with no payment step at all, and a free one gets the same page, the same reminders, and the same door.

How do I know who actually turned up?

You check them in. Every ticket carries a QR code, and you scan it from your phone at the door. So you can see who came, and not just who registered.

Is this the same as booking — what's the difference?

Booking is one person taking a slot in your time. An event is a thing that happens once, that many people come to, with a page and a ticket or an RSVP.

If what you run is one-to-one sessions, or a class people book into, booking is the page you want

Can it go on my own website?

Yes. The event page can sit on your site, on a landing page, or on a site somewhere else, and the people who register still land in your account.

Illustration of the FableForge queue-keeper — a halfling with violet braids holding up a long checklist with its top items already ticked off.

Other features that work with events and ticketing.

The day after the event, nobody's typing names off a printout.

At the door, you scanned tickets instead of running a finger down a list. The night before, you weren't the one sending the reminder. And the thank-you goes to the people who were there, from the account they're already in.

See what it costs

Rather ask a person first? Book a call.