Waitlist is one type of the guest confirmation status and it indicates that a guest has not yet been confirmed to the event.

Generally, there are two primary use cases of waitlists:

  1. Enables prospect guests to apply for an event, if you want to qualify people before confirming them to attend.

  2. Your event reaches capacity

This article covers the following topics:

Note: Waiting Lists require a Corporate Subscription plan. To learn more about our subscription plans, see: https://home.d.io/pricing/


The guest experience during the waitlist registration process

When the guest lands on your event website, they will see an action button which brings up the waiting list registration form.

After the prospect guest successfully completes this form, they will receive an email confirming that they have been added to the waiting list.

You (the event organizer) will also receive a similar email notification. Then, you can decide whether to confirm or decline them at anytime before the event. Learn how to confirm waitlisted guests, below.


Enable waiting list registrations

First, go to the Website tab and change the Action button to "Apply to Attend."

Then, publish your Diobox Website. This will always show your registration form through your Diobox Website URL.

Alternatively, you can embed the waitlist button on any external website. Refer to your Event Settings: Embed Code.


Find all waitlisted guests

To find all existing guests with the Waitlisted status, go to the Guests page and select the Guest List dropdown.

Then, select Waitlisted under the Segments section.


Confirm waitlisted guests

After a new person is waitlisted, they will show up in the Guests page with a yellow color tag. Click on that dropdown to change their confirmation status.

A prompt will confirm this action and will also give you the option to send the guest a confirmation email about their updated status.

You can also confirm multiple guests at one time by selecting them and changing their status in bulk.

To learn more, see Perform Bulk Actions.

Did this answer your question?