Managing guest records.

Guest records change: people get married, mistype their email, buy the wrong tier, or need flagging for the door. This page covers editing, flagging, archiving and deleting, and what each one does to the rest of the system.

Editing a guest

From the guest list, choose Edit Guest on a row, or open the guest and use the same option.

The edit page has two halves. Attendee details is the person attending, their name, email, and their answers to the tier's registration questions. Billing information is the contact who paid, along with the ticket and payment details on file, shown for reference.

Corrections here take effect immediately. Because tickets are rendered when they are opened rather than frozen at purchase, a corrected name shows up on the existing ticket without reissuing anything.

Flagging a guest

Flag guest marks someone for attention at the door.

A flagged guest still scans normally, but the terminal shows an alert when their code is read. That is the point: the scan is not blocked, the person working the door is told to look up.

Use it for the cases where somebody needs to talk to the guest rather than wave them through: an unpaid balance, a sponsor who needs escorting, a guest with an access requirement, a ticket that was disputed.

Unflagging is the same action in reverse.

Archiving a guest

Archive guest takes someone off the working list without deleting them.

Archived guests are hidden from the default guest list, and turning on Show archived brings them back into view. At a terminal, an archived guest's code produces an attention warning rather than a clean check-in.

Archive is the right tool for a cancelled registration, a duplicate you do not want to erase, or a no-show you want out of the way while keeping the record. The person and their history survive, which matters if the situation is ever queried later.

Unarchiving puts them straight back.

Deleting a guest

Delete guest removes the record.

Deleting is deliberately narrower than archiving: it is for a genuine mistake, like a test registration or a row imported twice. If anything real happened, a payment, a check-in, a conversation, archive instead. A deleted guest takes their history with them.

On a completed or cancelled event, deleting is unavailable along with the rest of guest management.

Undoing a check-in

Check-ins are editable from the door desk, not from the guest record. Removing a check-in deletes the attendance record for that guest and that schedule.

Resending a ticket

Send PDF on the guest row emails that guest their ticket again. It is the answer to almost every "I did not get my ticket" message.

For everyone at once, use Broadcast Tickets in the Tools menu, covered in tickets and badges.

What guests can do themselves

An attendee who has lost their ticket can request it again from your public event page without contacting you, using the resend option there. It emails the ticket to the address already on the registration, so it cannot be used to send someone else's ticket anywhere new.