A public page with one-tap RSVP
Set the date, the location, ticket tiers and recurring dates. Guests browse and answer your questions before anyone asks them to sign up, because asking a stranger to register before they can say yes loses them.
Events and the people who come to them
Host the event. Keep the people.
Publish the page, sell the tickets, send the invites, scan guests in at the door, and still have everyone who came in your contacts a month later, without wiring four products together first.
- Publish the page
- Sell tickets
- Invite and remind
- Check in at the door
- Keep the guest list
Six jobs one event puts on your desk.
Ticketing that collects the money
Paid tickets check out through embedded Stripe payments, and payouts release on their own schedule once the event has run. Hosting the event itself costs nothing.
Invites, reminders and the follow-up
Email and SMS go out from the event. A reminder fires before doors open and a follow-up after it ends, on timers the event arms when you publish and moves if you reschedule.
Door check-in on any screen
Kiosk check-in runs in a browser, so there is no scanner to buy for one night. Guests scan in and the guest list updates while the room fills.
Every attendee becomes a contact
The guest list does not end when the event does. Everyone who came stays in your contacts with the event attached, so the next invitation goes to people you have actually met.
Sponsors and memberships
Send a sponsor a Stripe-backed invoice link from your sponsor list, or sell a recurring membership from the event page or the check-in kiosk when the night becomes a series.
A ticketing tool sold to an email address. It has nothing else when the night ends.
| Capability | Connections | Ticketing tool plus a separate CRM |
|---|---|---|
| Public event page with RSVP | Yes | Yes |
| Paid ticket tiers and payouts | Yes | Yes |
| Email and SMS invites sent from the event | Yes | Limited |
| Kiosk check-in with a live guest list | Yes | Limited |
| Attendees kept as contacts with the event attached | Yes | No |
| Booking pages and intake forms on the same account | Yes | No |
| Sponsor invoices and host memberships | Yes | No |
| One sign-in across all of it | Yes | No |
Frequently asked questions
Can I host an event and keep the attendees as contacts in the same place?
Yes, and that is the reason this page exists. On Connections the guest list is not a separate export at the end of the night. Everyone who RSVPs, buys a ticket, or scans in at the door lands in your contacts with the event attached to them, so the next invitation goes to a real list of people you have actually met rather than to a spreadsheet somebody has to rebuild. The event page, the ticketing, the check-in kiosk, and the address book are one account rather than four.
Does it sell tickets, or only collect RSVPs?
Both. A free event takes RSVPs in a few taps: guests answer your questions first and make a free account as they send it. A paid event gets ticket tiers and recurring dates, and the money is collected through embedded checkout on Stripe. Connections takes a three percent cut on top of Stripe's own processing fee for payments it handles, and ticket payouts release on their own schedule after the event has run. Hosting the event itself is free, so there is no plan to buy before you can publish a page.
How do people get invited and reminded?
From the event itself, by email and SMS, using the account-wide sending allowance rather than a separate mail tool you connect. Attendees get a reminder before the doors open and a follow-up after the event ends, both on timers the event arms for you when you publish and re-arms if you move the date. A secret-location event releases its address to attendees on whatever lead time you chose, rather than requiring you to remember to send it.
How does check-in work at the door?
Kiosk check-in runs in a browser on whatever screen you have at the entrance, so there is no scanner to buy or app to install for a one-night event. Guests scan in, the guest list updates while the room fills, and the host console shows arrivals live. Because check-in writes to the same contact record as everything else, the person who walked through the door is already the person your follow-up will reach next week.
What happens to the guest list after the event?
It becomes your network rather than an archive. Each attendee stays as a contact carrying the event you met them at, and the follow-up digest surfaces the ones you have not spoken to since. If two of your contacts both came, the relationship map records that. This is the part a ticketing tool structurally cannot do: it sold a ticket to an email address, and the email address is all it has when the event is over.
Can I take sponsor money or sell a membership through the same event?
Yes. From the sponsor list on your host console you can send a sponsor a Stripe-backed invoice link, so sponsorship money arrives through the same rail as ticket money instead of a separate invoice tool. You can also sell a recurring membership to attendees from the event page or the check-in kiosk, which is the natural move for a series, a night that repeats, or a room that keeps drawing the same people back.
Do guests need a Connections account to come?
Yes, a free one, and they meet it last. Anyone can browse a public event and answer your questions without signing in; the free account comes when they send the RSVP or buy the ticket, so nobody is asked to sign up before they have said yes.
What else is on the same account if I need it later?
Booking pages and forms for the intake around an event, a shared calendar that pulls in every date across the account, payments and a seller console if you sell more than tickets, bookkeeping with receipt scanning if the event has costs, community pages with their own registration questions if the event becomes a group, site analytics, and an AI support bot for the questions attendees ask before they arrive. None of it needs to be switched on in advance.
How much event history and analytics do I get?
Every host sees visits, RSVPs, and check-ins for their own events. The free base keeps a two-week analytics lookback, and paid plans widen that window so a recurring series can be compared against itself over a longer run. The underlying capture is not sampled or reduced on the free base; the plan sets how far back you can look, not how much is recorded.