Product tour

The event ends.
The guest list doesn’t.

Associations, clubs, businesses and venues host the same people again and again. What they’re building isn’t an event. It’s a relationship with a few hundred people, and the software ought to treat it that way.

So the guest list is an asset you keep, not a spreadsheet you rebuild every March. Events, contacts, invitations, attendance and the team who runs them, in one place. Here are five pieces of it.

See pricing
01
Through to the door

Who turned up, and who didn’t

Invited, delivered, viewed, responded, checked in. The chain runs all the way to the entrance, which means it ends on the number you actually plan against: how many of the yeses came. Eighty-six per cent, on the event beside this. That figure sets next year’s catering order, tells you how far to oversubscribe a room, and names the people worth a phone call rather than another email.

  • Bounces and complaints come back from the receiving mail providers, so a guest who never replied reads as “never arrived” rather than “not interested”, and the address gets fixed before you send again.
  • Every guest gets their own link, so page views and replies attribute themselves. You can see who still hasn’t replied and chase exactly those people, rather than mailing all four hundred a second time.
  • Six signals make up that chain, and five of them are recorded events rather than inferences: an SMTP response, a feedback-loop report, a hit on a unique link, a form submission, a scan at the door.
  • The sixth, opens, is the only estimate. Apple Mail Privacy Protection, Gmail’s image cache and automated scanners inflate open rates across the whole market; ours is corrected for them, which moves the number down rather than up.
  • No proprietary engagement score. Counts you can check, not a number you have to trust.

Most platforms stop at the RSVP, because they never see the door. Response and attendance are two different numbers, and only one of them is the one you needed.

Starter and up

Summer Gala 2026 · funnel
Business plan
  1. Invited420 · 100%
  2. Delivered412 · 98%
  3. Opened296 · 70%
  4. Page viewed271 · 65%
  5. Responded238 · 57%
  6. Checked in204 · 49%
8 never reached an inbox, addresses flagged86% of yeses turned up
02
A link and a code

RSVP and check in from a QR code

Everyone does QR check-in. The part worth choosing on is what your guest has to do to use it: open a link, answer in the browser that’s already in front of them, keep the code that arrives. No app, no account, no password. An invitation should ask for a reply, not a download. Your team scans at the entrance and the count moves against the RSVPs while the queue is still going.

  • A code identifies one guest on one event, so the scanner can answer the question that matters at the door: let them in, or not.
  • It also tells a genuine duplicate apart from two of your staff scanning the same person at once, and says which of the two it was.
  • Kiosk mode lets walk-ins register themselves on a tablet you leave on the table: the same check-in, minus a queue at the desk.

RSVP on every plan · door check-in from Starter · scanning from Standard

Door scanner · main entrance
Scanning
199/238
checked in against RSVPs
Any phone with a camera will do.

Waiting for the first scan…

Illustrative: press to step through it
03
The second event

Build the guest list once. Keep it.

This is where the promise at the top of the page either holds or doesn’t. Rosters belong to your organisation, not to an event: save the guest list from something you already ran, or build one out of your contacts, then invite the whole roster to the next event in one action. Somebody on five of your rosters is one contact, not five copies of a name, so the second event costs a click instead of an afternoon of re-importing.

  • Duplicate protection at four layers, so nobody lands on an event twice and people already invited are skipped rather than mailed again.
  • Rosters point at contacts rather than copying them: correct an address once and every list that person is on is correct too.
  • CSV in, CSV out. Duplicate a roster before you edit it, archive one you’re finished with instead of deleting the history.

Every plan. 5 lists on Starter, 25 on Standard, uncapped on Business

Guest lists · Acme Events
3 of 25 used
One action, one event, 42 people.
Illustrative: pick a roster, then invite it
04
Consent, done properly

Decline one invitation, not every invitation

When a guest unsubscribes, they unsubscribe from you, or from that one event. There is deliberately no platform-wide switch, because whether your guests hear from you isn’t our decision to make on your behalf.

  • They can undo it themselves: the confirmation email carries the link back, so re-consent isn’t a support ticket.
  • One-click unsubscribe (RFC 8058) is live, which is what keeps inbox providers trusting the mail everyone here sends.
  • Every guest email names you as the sender and us as the delivery agent, so the opt-out points at whoever the guest actually meant.
  • A spam complaint stops your mail, not their password resets and not another organiser’s invitation.

Platforms that send for thousands of organisers from one shared domain tend to offer one blunt unsubscribe, and it takes every other organiser down with it.

Every plan, always on

Unsubscribe · guest’s own choice
Reversible
What the guest is choosing to stop
Everything on QRSVPnot offered
  • Summer Gala reminders stopped
  • Acme’s next event invitation still delivered
  • A different organiser’s invitation still delivered
  • Their own password reset still delivered
The guest can undo this themselves, from the same page
05
Mail out, people in

Send from your own server. Switch passwords off.

Point guest mail at your own SMTP server and invitations leave from your infrastructure, your domain and your sending reputation. The message body never transits ours. On the way in, your team signs in with passkeys, and an organisation can turn password login off entirely.

  • Passkeys and TOTP 2FA on every plan; organisation-wide enforcement, session revocation and step-up checks on sensitive actions from Business.
  • Audit logs that still remember who did it after that person leaves the team.
  • Every request re-checks a live session record, so a revoked login stops working immediately, because a valid token on its own isn’t enough.
  • Stored credentials are encrypted with AES-256-GCM and never shown back to you.

Guest mail today. Transactional mail, such as password resets, still leaves through our own sending.

Passkeys & 2FA on every plan · own SMTP and org-wide enforcement from Business

Organisation settings
Business plan
Guest mail leaves through
Your event mail.acme.comGuest inbox

Your domain, your reputation. The message body never transits our provider.

Password login for the team
Passkeys only. 6 devices enrolled, nothing to phish.
Illustrative: both switches are real settings

Want the other fifty rows?

Capacity, comms, security, branding and support: every feature against every plan, with the two entry prices published.

Compare every feature by plan

Don’t see something you need? Tell us. What customers ask for is how the roadmap gets ordered.

Run one event on it

Fourteen days, no card. Build a guest list, send the invitations, scan people in at the door.

Talk to us first