Updated: 5 January 2026 for Release 224
The Peppered Waiting List is active when an event has the status "waiting list". This status can be set manually in the Dashboard. It can also be the default status when an event is Sold out.
For these settings, please check our article Event Availability, Event Status Changes and Buffers.
For the Peppered Waiting list, there are two processing options available:
- Manual processing: requests are emailed to a designated email address.
- Automatic processing: adds the request directly to the ticketing system (supported systems only). Settings in the Control Panel allow customization of email recipients, API usage, and pop-up options for ticket requests.
Once the Waiting list status is active, the tickets button will change into a “Waiting list" button on the event page and in the overview.
Option 1: Manual processing of Waiting list requests
This option uses an in-page popup that is active when the Visitor is logged in (if not logged in, a login prompt will be given). The Visitor only needs to select the amount of tickets. The correct event is automatically selected and together with the Visitor information is sent in an email to the box office.
The requests have to be processed by the Box office staff. This option works for all ticketing connections, as there is no direct communication with the ticketing system.
Option 2: Automatic processing of Waiting list requests in a ticketing system
This option also uses the in-page popup that is active when the Visitor is logged in (if not logged in, a login prompt will be given).
The Visitor needs to select the amount of tickets then require.
The correct event is automatically selected and together with the visitor information is directly added to the ticketing system waiting list for that event.
Waiting List Settings
In System > Control Panel > Waiting List you can find the following settings:
- Set activated to Yes to switch on the Peppered Waiting list function
- Automatic status offset (hours): Minimum number of hours before an event starts, where it will automatically switch to the "waiting list" status once sold out. When zero or empty, the status must be set manually. For example, if you only want there to be a Waiting list for Sold out events from 1 day before the event starts, you would set it to 24 hours. Visitors can only join the Waiting list if the events is in the next 24 hours and not before.
- Use pop-up: This should always be set to Yes when using the integrated option via API. When switched to No, the pop-up is disabled and any other custom or third party URL to redirect to from the "Waiting list" button can be used.
- Custom form URL: When Use pop-up is set to No, use any external URL here to send the waiting list request to. Please note that this is a single URL that will be used to redirect Visitors from any Waiting list event. There is no event specific data, just a general form. So if you use this, make sure to ask the visitor for which event he is requesting tickets.
- API integration: When the ticketing system supports the connection, switch this option on to sync the waiting list request web form straight to the ticketing system .
- Mail request to: When Use pop-up is set to Yes and API integration is set to No, this is the email address the manual requests will be sent to.
- Mail confirmation to visitors: Send a confirmation email of the request to the visitor. Text can be changed in the Template text module. Search for “FE3_waitlist_mail”.
- Require phone number: When set to Yes, the in-page popup includes a field for a phone number. If a phone number already exists on the account, it displays and can be updated. If the field is empty, visitors can add their number, which will be saved to their account.
- Enable price type selection: Only for Ticketmatic users. This activates a detailed price type selection form.
- Enable price type selection and options: Only for Ovatic users. This activates a detailed price type selection form.
Follow up with Visitors on the Waiting List
For integrated Waiting lists (via ticketing API) Waiting List requests are now automatically stored on Visitor accounts and can be used in a Query Builder filter. This lets you target everyone on the Waiting list for specific events.
Related articles
