For the person running the event
Publish a page people can register on, ask the questions you actually need answered, sell tickets straight into your own Stripe account, scan the room in at the door, and walk away with the guest list. One account, from the invitation to the follow-up.
A real URL with a link-preview card, so the event looks like itself when somebody pastes it into a group chat. Guests browse and register without making an account, because asking a stranger to sign up before they can say yes loses them.
Ask what you need to run the night - dietary requirements, a company name, which session, whether they are bringing someone - alongside the standard fields. The answers arrive attached to that attendee instead of in a separate form tool you reconcile at midnight.
Set the number the room holds. Registration stops there, and anyone who arrives after it joins a waitlist rather than bouncing off a sold-out page, so a cancellation has somebody to give the place to.
Paid tiers check out on the host's own connected Stripe account, so payouts follow your schedule and refunds and disputes stay with you. Connections takes three percent of what you collect, on top of Stripe's own processing fee. Publishing, registrations and check-in cost nothing.
Email and SMS go out from the event itself, in waves rather than one blast. A reminder fires before doors open and a follow-up after it ends, on timers the event arms when you publish and re-arms if you move the date.
Kiosk check-in runs in a browser, so there is nothing to buy for one night. Guests scan in, walk-ins get matched against the roster on the spot, parties arriving together are grouped, badges print from the same flow, and the list updates while the room fills.
Who registered and who actually walked in, exportable as a CSV the moment the event ends - which is exactly when a host needs it, not one upgrade later. Everyone who came stays in your contacts with the event attached.
An event repeats on a real recurrence rule, and every date is addressable on its own. Your calendar publishes as a subscribable feed, so somebody who follows it gets each new date in the calendar app they already use.
Publishing an event, taking RSVPs, sending the invites and running check-in at the door cost nothing, and there is no plan to buy before your page is live. When you sell tickets, Connections takes three percent of what you collect, on top of Stripe's own processing fee, because the money moves through your own connected Stripe account rather than ours. That rate is fixed; the amount it comes to scales with what you sell.
Yours. Ticket payments are charged directly on the host's own connected Stripe account, so payouts follow your Stripe schedule and the customer relationship, the refunds and the disputes stay with you. Connections is not a middleman holding your ticket revenue until some threshold clears.
Yes. A registration form takes your own fields alongside the standard ones, so you can ask what you actually need to run the night - dietary requirements, a company name, which session someone wants, whether they are bringing a guest - and the answers arrive attached to that attendee rather than in a separate form tool you have to reconcile afterwards.
Set a capacity and the page stops taking registrations at it. Anyone who arrives after that joins a waitlist rather than bouncing off a sold-out page, so a cancellation has somebody to give the place to and you keep the demand signal instead of losing it.
Kiosk check-in runs in a browser on whatever screen is at the entrance, so there is nothing to buy or install for one night. Guests scan in, walk-ins can be matched against the roster on the spot, parties arriving together are grouped, and the guest list updates while the room fills. Badges print from the same flow.
Yes, as a CSV export of who registered and who actually arrived, and it stays yours. The list is not locked behind an upgrade at the moment the event ends, which is when a host most needs it.
From the event itself, by email and SMS, in waves you control rather than one blast. A reminder fires before doors open and a follow-up after it ends, on timers the event arms when you publish and re-arms if you move the date.
Yes. An event can repeat on a real recurrence rule rather than as copies you maintain by hand, and every date is addressable on its own. Your calendar publishes as a subscribable feed, so somebody who follows it gets each new date in whatever calendar app they already use.