Smart Virtual Queue (Waiting Room)

High demand events? Users are queued automatically to ensure a smooth, stable experience.

 LIVE DEMO  GET QUOTE

Why need a Waiting Room?

Fair queuing — Users exceeding the limit are queued in order of arrival (FIFO).)
  • The waiting room acts as a gateway between users and your website.

  • Control concurrent users — Limit the number of users who can access the registration page at the same time (e.g., 500 users).
  • Prevent system crashes — During high-demand registrations, excess users are placed in a virtual waiting room to maintain site stability.

  • Fair queuing — Users exceeding the limit are queued in order of arrival (FIFO).

Automatic Admission — When a user completes registration or their session times out, the system automatically admits the next user.



  • Automatic Admission — When a user completes registration or their session times out, the system automatically admits the next user.
When an event reaches full capacity, the system automatically closes the queue for that event. The waiting room will display a message to users: Event full — thank you for your support!


  • When an event reaches full capacity, the system automatically closes the queue for that event. The waiting room will display a message to users: “Quota is full — thank you for your support!

Admin Dashboard

Get a clear, real-time overview of ticket demand. Statistics update in real time.

All visitors are segmented into distinct statuses:
“Waiting”, “Pending Confirmation”,  “Admitted”,  “Completed”,  “Expired”

[Waiting Room] Dashboard – Ticket demand status at a glance

Waiting Room FAQ

1. Is there an extra charge for using the waiting room?
No. The waiting room is disabled by default. You can enable it in the backend. The default limit for Max Concurrent Users is 300. For support with more concurrent users, please contact iEvent technical staff.
2. What settings are available for the waiting room?
  • Max Concurrent Users
    Description: The number of users allowed on the registration or booking page at the same time. Users exceeding this number are redirected to the waiting room.

  • Session Timeout (minutes)
    Description: The time a user can spend on the website after leaving the waiting room. After timeout, the spot is released to the next user in the queue.
    Range: 1–30 minutes
    Recommended: 10 minutes (enough to complete one registration)

  • Require Manual Confirmation
    Disabled (default): Users are automatically admitted when it’s their turn.
    Enabled: Users must click “Enter” to access the website.
    Benefit: Prevents idle users from occupying multiple spots (e.g., same user opening multiple browsers to queue).

  • Auto-Close on Full Capacity
    Enabled: When the event is full, the system automatically closes the queue. The waiting room will display: “Event full — thank you for your support!”
    Disabled: The queue remains open even if the event is full (requires manual closure by admin).
3. Can the queue automatically close when the event is full?
Yes. If an event has limited capacity and many users are waiting, the system can immediately notify waiting users when the event is full, saving them from unnecessary waiting.
4. Can the waiting room page “crash” under heavy load?
No. The waiting room is built on Amazon Web Services’ serverless architecture and can handle hundreds of thousands of requests simultaneously.

Scroll to top