Guests and their states

Updated on 2026-10-19

An event's page is the list of its guests. It is the screen you will spend the most time on: it is where you add, filter, fix, and on the night, let people in.

Adding guests

Three routes, all legitimate.

Search multiple guests — you pick from the address book, filtering as you would on contacts, select and add in bulk. The normal route once the address book has something in it.

Add single new guest — one person at a time. If the email is not in the address book, the contact is created and stays there after the event: you are not making a throwaway duplicate.

Import guests — you upload a file straight onto this event. The right route when the list comes from the client and is not in the address book yet: see Importing and exporting contacts.

Anyone already invited is not duplicated. When you add people who are already there, you can choose not to touch their confirmation status: that is for re-running the add on a wider selection without wiping the answers already in.

The states

Every guest carries three independent pieces of information. Confusing them causes half the questions we get.

StateWho changes itWhat it says
InvitedThe system, when a campaign goes outAt least one campaign was sent to them
Confirmed / Not confirmed / No answerThe guest, answering on the landing page — or you, by handWhether they said they are coming
Checked inWhoever is on the door, on the nightWhether they actually walked in

They really are independent: you can have someone confirmed who was never invited (you added them after a phone call) and someone checked in who never confirmed (they turned up anyway). The application does not reconcile them for you, and that is deliberate: they are different facts, and overwriting one with another would destroy information.

Every confirmation also keeps its moment: the Confirmed on column, which you switch on among the columns of the list and of check-in, and which is in the export, tells when the guest said yes. If they change their mind the date is cleared; a second confirmation does not overwrite the first. Confirmations given before this feature have no date.

For campaigns, confirmation is not enough: only guests who accept your invitations receive them, including those who signed up for the event — on the landing page, by answering yes to the invitation, or because you confirmed them. The others only receive the automatic confirmation and denial emails. See Who receives a campaign.

Companions

If you enabled them on the event, each guest declares how many people they are bringing, up to the limit you set. At the door you record how many actually came in, which rarely matches how many were announced.

Hence the distinction between the two numbers on the event:

  • Guests — how many rows are in the list.
  • People — guests plus companions: the number that matters for capacity, catering and safety.

The people count is the right one for every practical question about the night.

Turn on Require companion names in the event settings and a companion stops being a bare number: the guest is asked for each companion's first name, last name and email, and every one of them is added as its own row in this same list (and to your address book) — a real guest, not just a count. Opening a companion's row tells you who added them; opening the original guest's row lists their companions too. If the guest later lowers the count, the companions no longer needed are kept as "not attending", never deleted, so nothing about emails already sent gets lost. A companion without a name (left empty by you on the guest's card, or given with the guest's own email or twice) stays a number on the guest's row and counts among people and confirmed ones; someone already invited to the event is never added a second time. If they have not answered yet, they are confirmed and become the companion of whoever named them (they get the confirmation email); if they have already answered or checked in, they stay as they are, because their own answer beats someone else's. If whoever named them removes them, or then does not attend, they go back to being a guest of their own with no answer; if they answer themselves, their answer wins and they are no longer a companion. A companion who was not already in the address book enters it without invitations to your later events; the emails of this event reach them anyway.

Editing a guest

Opening a row edits what belongs to this event: confirmation, companions, slot, list, notes, and the privacy consents they gave.

First name, surname and email belong to the contact, not to the guest: correcting them here corrects them in the address book and therefore everywhere. That is the right behaviour — a wrong email is wrong everywhere — but it is worth knowing before you discover it. At the bottom there is also the read-only box with the contact's consents, as in the contact card.

Guest notes are the other underrated field: allergies, access needs, "arriving late", "friend of the director". They are visible at the door too.

When you change a confirmation by hand, you can choose whether to fire the automatic confirmation or refusal email. If you are tidying up the list after a round of phone calls, you almost always want it off. Until the account has a verified sending domain the option stays disabled, with the reason underneath: emails to guests only go out with a domain. The same goes during a free trial with no card: the option stays disabled until you add a card from the Billing page (details).

Filtering and working in bulk

The list filters by confirmation state, attendance, list, slot and receives emails, that is whether the contact accepts your invitations and therefore receives campaigns; the same information is also available as a column. With a selection active you can confirm, cancel, delete or edit in bulk: that is how you tidy up a list that arrived in a mess.

As with contacts, when results run past one page you can select everybody matching the filters, not just what you can see. And as with contacts, it is worth reading the counter before pressing anything.

Exporting

The export button produces the guests as Excel, CSV or PDF, respecting your active filters. It is the file reception, security and catering need — and the backup copy to have on the night anyway, for when the network will not cooperate.

The Excel and CSV export also carries the read-only columns about open and click measurement: see Importing and exporting contacts.

Removing a guest

It takes the person off this event and nothing more: the contact stays in the address book, and other events notice nothing.

The whole guide