Guest registration page

The registration page is the public page your guests open to register themselves for your event. Guests don’t need an account and don’t need to install an app — they just need a link, fill in a few details, and their QR ticket arrives by email. This page explains what your guests see so you know how to share the link and guide them.

Your event can use one of two registration layouts. The individual form is the default, where each guest signs themselves up one at a time. The organization form lets one person sign up a whole team or company in a single submit. Most of this page describes the individual form; the organization form has its own section, Organization registration (sign up a whole team), further down.

What guests see when they open the registration page

When a guest opens the registration link, they see a simple page with:

• Event information at the top — name, description, time, venue, and a banner image (if you uploaded one).
• The registration form below — where guests enter their details.
• A language toggle — guests can switch between English and Vietnamese depending on your setup.

The page is designed to be clean on a phone, since most guests will open the link from a message or email on their mobile.

What guests need to fill in

The form has two parts: the always-required details and any extra questions you configure.

Part 1: Personal details (always present)

Every registration form asks for two basic fields:

• Full name — required, so organizers can match guests and print tickets.
• Email — required, since this is the address the system uses to send the guest their QR ticket.

A third field may appear depending on your configuration:

• Phone number — you can choose to hide it entirely, show it as optional, or require it. This setting is configured per ticket tier.

Tip

If you don’t need a phone number, hide the field so guests can register faster. The shorter the form, the higher the share of guests who finish registering.

Part 2: Custom questions (added by you)

Beyond name and email, you can add your own questions for your event — for example “Which showtime do you prefer?”, “Do you need a vegetarian meal?”, or “Which company do you work for?”.

There are four question types you can create:

Question type	What the guest does
Short text	Guest types a short answer (e.g. company name).
Number	Guest enters a number (e.g. number of companions).
Choose one	Guest picks one option from a drop-down list.
Choose multiple	Guest ticks checkboxes to select one or more options.

You can set limits per question: minimum/maximum length for text answers, or smallest/largest value for number answers. Each question can be marked required or optional.

Note

You configure all of the custom questions and the phone field in the event’s registration form settings. See

Registration form configurationCustomize the questions and fields guests must fill in.

for details.

Organization registration (sign up a whole team)

Some events let one person register a whole company, team, or group in a single form. This is the organization registration form, a separate layout from the individual form. The organizer turns it on per event, so guests only see it when they’ve enabled it and shared the organization link.

On this form, one person (for example a team lead or admin) fills in two sections:

• Organization — a few questions about the organization itself, answered once. These usually include the organization name and a contact email. If the organizer added no organization questions, this section does not appear.
• Employees — a list of the people attending. Each row is one employee.

How guests reach the organization form

The organizer shares a specific link for the organization form. It is either:

• A short, custom link like /r/summer-festival that the organizer chose, or
• The default organization link based on the event id.

Opening that link always opens the organization form (it never switches to the individual form). If the organizer has not enabled the organization form, or registration is closed, the link shows a Registration closed notice. If the event has already ended, it shows an Event ended notice instead.

Filling in the employees

For each employee, the person registering enters:

• Full name (required).
• Email (required, and checked for the right format).
• Phone — only if the organizer chose to collect it; required only if they marked it so.
• Tier — a free-text box, pre-filled with the tier from the share link (for example “General”). The organization form is single-tier, so the tier is fixed by the link.

If the organizer added per-employee questions, they appear under each row.

Click Add employee to add another blank row. Click the remove button on a row to delete it (the last remaining row cannot be removed). The section header shows a live count of how many employees have been added.

Note

At least one employee is required. If the list is empty when someone tries to submit, the form asks them to add at least one employee first.

Import employees from CSV

If there’s a list of employees in a spreadsheet, the person registering can import them instead of typing each one. Click Import CSV to open a four-step dialog:

1. Download a template — review the columns the file expects (Name, Email, Phone, TicketTier, plus one column per per-employee question), then click Download sample template to get a starter file with the correct headers.
2. Upload — drag and drop a .csv file (up to 5 MB), or browse to pick one.
3. Review — see how many rows are valid and how many have issues, with a row-by-row preview. Rows beyond the 200-employee limit are dropped and a truncation notice appears.
4. Confirm — check the first few employees and click Add N to form to append them.

Imported employees are added to whatever rows were already typed in. They do not replace them.

Tip

The template and the upload accept English headers (Name, Email, Phone, TicketTier) and common Vietnamese headers (Họ tên, Email, Số điện thoại, Hạng vé). Vietnamese diacritics are fine.

Caution

A row is skipped if the name is missing or too long, the email is malformed, the phone is too long, or an answer to a per-employee question does not match its type (a number that is not numeric, a choice that is not in the list). Invalid rows never block the valid ones, only valid rows are added. Note: a phone that is too long currently shows as “Invalid email” because of a shared error message, a known cosmetic quirk.

What happens when the form is submitted

Click Register all to register every employee. Each employee is registered one at a time, and each row shows its own live status:

• Registered — this employee is on the list and will receive their ticket.
• Added to waitlist (with a position number) — the event is full, so this employee is queued and gets their ticket only when a seat opens.
• Failed — something went wrong for this employee (for example, they were already registered, or the system asked the sender to slow down). The reason is shown on the row.

Submission keeps going even if some rows fail, so one duplicate never blocks the rest of the team. When it finishes, a summary shows how many were registered, waitlisted, and failed, and lists each employee under their outcome.

Every successfully registered employee becomes a regular guest, receives the same confirmation email with their QR ticket (see The confirmation email guests receive), and has the organization answers saved on their record. There is no separate “organization contact” recipient. If the organizer wants a contact, they add it as an organization-level question.

Click Register another organization to clear the form and sign up another team.

The links you can share

The links below are for the individual form. An event with the organization form enabled also has a separate organization form link (covered in Organization registration). It helps to understand the difference between these individual-form links.

Short link (clean, memorable)

This is a compact link where you pick a short name for the event — for example a link like /e/summer-festival. This link:

• Is short, readable, and easy to paste into a message or print on a poster.
• Takes guests straight to the event’s main registration page (guests see the default form).
• You choose the short name yourself when creating the event, as long as no other event is already using it.

Tip

Use the short link on posters, event graphics, and social posts — anywhere a long link would look cluttered and be hard to read.

Per-tier link

If your event has several ticket tiers (for example General, VIP, Student), you can send guests a link specific to each tier. When a guest opens a particular tier’s link:

• A colored badge at the top of the form shows that tier’s name (e.g. “VIP”) so the guest knows which tier they are registering for.
• The form shows the exact set of questions you configured for that tier.
• The guest doesn’t need to pick a tier themselves — the link has already fixed it.

Per-tier links are the best approach when you invite different groups of guests (for example sending the VIP link to loyal customers and the Student link to students).

Note

Configuring a separate set of questions and the phone field per tier is done in the registration form settings. See

Registration form configurationHow to set a different form per ticket tier.

.

What happens after a guest submits

When a guest finishes filling in the form and taps submit, one of the following outcomes occurs:

1. Success — the guest sees a confirmation screen. The system immediately creates a QR e-ticket and sends a confirmation email with the ticket to the address the guest entered.
2. Added to the waitlist — if the event has reached capacity and you have not allowed overselling, the guest sees a notice that they are on the waitlist along with their position. When a seat frees up, the system automatically promotes them to the main list and only then sends their ticket.
3. Duplicate — if the guest has already registered before with the same email and name, the system tells them they are already on the list to avoid duplicates.
4. Closed — if you have turned registration off (or the event has ended), the guest sees a polite notice that registration is not currently open.

Tip

Guests should check their spam folder if they don’t see the ticket email. You can also track ticket status in the CMS and resend if needed — see

Issue e-tickets to guestsHow to issue and resend QR tickets to guests.

.

The confirmation email guests receive

After registering successfully, the guest receives an email containing:

• The QR e-ticket — either as an attachment or shown directly in the email.
• An “Add to calendar” button — guests can save the event date to their phone calendar with one tap.
• A link to view the ticket — guests can reopen their ticket at any time.

The email follows the design you configured for the event. To customize the email content, see

Event email templatesHow to edit the look and content of emails sent to guests.

.

Things to remember when sharing the link

• Test the link before you send it — open it on your own phone to see what guests will see, and confirm the form looks right and your custom questions are present.
• Share the right link with the right group — when using per-tier links, make sure each group gets the correct tier link.
• Turn registration on before sending the link — if registration is off, guests who open the link will see a closed notice instead of the form.
• Don’t worry about duplicates — the system automatically prevents guests from registering twice with the same email and name, so you don’t need to check manually.

Next steps

Registration form configuration

Customize the questions and fields guests must fill in, and set a different form per ticket tier.

Issue e-tickets to guests

Understand the full ticket lifecycle — from creation to check-in at the door.