How to Choose a Virtual Waiting Room
This guide is best for teams evaluating virtual waiting room software for the first time, whether for ticket on-sales, product drops, enrolment windows or public-sector registrations. It sets out eight criteria to judge any provider against, a checklist of questions to ask, and CrowdHandler's own plans as a worked example.
A waiting room earns its place wherever demand can outrun what a site, a system or a limited supply of something can handle at once. That covers the obvious cases, ticket on-sales, product drops and flash sales, but also enrolment and registration windows, appointment and exam bookings, grant and benefit openings, membership renewals, and any announcement that draws more attention than planned. It is also insurance: a catch-all waiting room stays invisible under normal traffic and engages only when a spike arrives, which protects against the day you did not forecast. The alternative is infrastructure sized for the busiest hour of the year and idle the rest of it, or letting the site fail when it matters most. Load test vs queue and Queue theory vs reality explain why scaling alone rarely settles it.
1. Integration method
Why it matters. Where the queue check runs decides how hard it is to bypass, how much load reaches your servers, and how much developer time you need. A check in the visitor's browser is quick to deploy but can be skipped by a determined visitor. A check at the edge or on your server cannot.
What good looks like. A choice of methods, so you can start simply and harden later without changing provider: a JavaScript tag, edge integrations for the CDN you already use, a server-side API with SDKs, and apps for platforms such as Shopify and WordPress.
How CrowdHandler handles it. All of the above: a JavaScript tag that is live in about 15 minutes, edge integrations for Cloudflare, AWS CloudFront and Akamai, a DNS-based proxy, a server-side API with SDKs, a Shopify app and a WordPress plugin. How a virtual waiting room works explains where each fits, and the Cloudflare comparison covers the one platform that bundles a basic waiting room of its own.
2. Fairness of the queue
Why it matters. How positions are allocated decides who gets the tickets, the stock or the places. First come, first served rewards bots and visitors who camp on the page before the start. A randomised pre-queue gives everyone present at the start an equal chance. A ballot is a third option for the most oversubscribed releases.
What good looks like. Both modes, chosen per waiting room, with a countdown that withholds positions until the advertised start, random allocation that is documented rather than asserted, and later arrivals ordered fairly behind the initial group.
How CrowdHandler handles it. In countdown mode, nobody holds a position until the queue activates; everyone present at that moment is given a random position, and later arrivals join behind them in the order they arrived. Always-on catch-all rooms are first in, first out. Pre-registration ballots can be run through the same waiting room, as described in Online ballots vs queues. The product launches and drops page shows how this works on the day of a release.
3. Capacity and outflow control
Why it matters. The waiting room only protects your site if the admission rate matches what the site can take, and that figure changes with the type of sale: a basket of fifteen concerts puts a different load on a checkout than a single pair of tickets.
What good looks like. A per-minute admission rate, automatic tuning from measured page performance rather than a number guessed in advance, and several waiting rooms sharing one domain's capacity.
How CrowdHandler handles it. Rate limiting is on every plan; autotune, on Plus and above, samples live page performance and targets 98 per cent of page loads under five seconds by default. Several rooms share the domain rate and rebalance as queues clear. The Royal Albert Hall runs pre-scheduled rooms for each Friday on-sale so that someone booking a tour never queues behind 20,000 concert-goers; the case study describes the setup, and One In, One Out explains why a per-minute rate is not the same thing as capacity.
4. Bot and abuse protection
Why it matters. For anything scarce, whether tickets, stock or places, automated traffic is the main threat, and the queue is where it is easiest to identify: before it holds anything, and while every session is in one place.
What good looks like. CAPTCHA at queue entry with a choice of providers; device fingerprinting that ties each position to one device; IP rules you control plus curated threat lists for data centres, proxies and known attackers; behavioural anomaly scoring; and reporting that shows you what was blocked and why.
How CrowdHandler handles it. CAPTCHA at entry with ALTCHA included, or Google reCAPTCHA or hCaptcha; device fingerprinting from the Standard plan; a firewall with manual rules and automatic blocking of IPs that open too many sessions from Plus; known-threat categories and a global block database of around 3 million IP addresses from Professional; and anomaly scoring across more than 20 metrics. At the Nike x Wu-Tang Clan Dunk relaunch, all 3,600 pairs reached genuine fans despite 11 million bot attempts. The bot mitigation page lists each layer.
5. Branding and templates
Why it matters. The waiting room is your page in the customer's eyes, at the moment they are paying most attention. A generic holding page undermines trust; a branded one carries the event.
What good looks like. Your logo and colours as a minimum; full control of markup, styling and behaviour for teams that want it; multi-language support; a different template for each waiting room; and room for video, music or embedded content.
How CrowdHandler handles it. Upload a logo and go, or take full control of fonts, colours, layout and behaviour with Vue.js, in more than 60 languages, with a different template for each waiting room and embedded video, music and polls. Custom templates are on the Standard plan and above; see the templates guide.
6. Pricing model and contract terms
Why it matters. Waiting room demand is spiky by nature. A model that charges per queued session or splits visitors into metered tiers can cost more than the event is worth, and you will not know the bill until the peak has passed. Whether you want cover for one on-sale or for the whole year depends on your calendar, so the terms should fit it either way.
What good looks like. Published prices; terms that match your calendar, whether that is a month around an event or a year of always-on protection; a free tier to keep on standby; no per-session metering or overage charges; and clear limits on concurrent waiting and outflow so you can size the plan to the event.
How CrowdHandler handles it. Flat monthly pricing with no overages or add-ons. Lite is free; Starter is $290 a month, Standard $900, Plus $1,680 and Professional $4,500, and you can move between these listed plans instantly from the dashboard. Enterprise is agreed by quote on its own terms. The full comparison is on the pricing page.
7. Setup time
Why it matters. Launch and opening dates do not move. If the integration takes six weeks you will run the event without protection, or postpone it.
What good looks like. A basic waiting room in under an hour, a hardened edge or server-side integration in days, documentation good enough to self-serve, and nothing to install.
How CrowdHandler handles it. A basic waiting room takes 15 minutes or less with no software to install, and most other integrations can be set up within a few hours. See how long it takes to implement CrowdHandler.
8. Support and procurement routes
Why it matters. Your busiest hour of the year is when support response time matters, and public bodies often cannot buy outside an approved framework at all.
What good looks like. Published response times and an uptime SLA; onboarding that scales with the plan; help with security questionnaires at the top tier; and listings on the procurement frameworks your organisation already uses.
How CrowdHandler handles it. A 99.9 per cent uptime SLA from the Starter plan up, with support response times of 48 hours on Starter, 24 on Standard, 8 on Plus, 2 on Professional and 1 on Enterprise, which also includes screenshare onboarding and help with security assessments. For UK public bodies, CrowdHandler is listed on the Digital Marketplace under G-Cloud 15; French public bodies can buy through UGAP, the French central purchasing body; and the service is also available through the AWS Marketplace. See government and utilities.
Ten questions to put to any vendor
- Where does the queue check run: in the browser, at the edge or on my server, and what happens if a visitor bypasses it?
- When the queue activates, how are positions allocated, and can I choose between first come, first served and random allocation for each waiting room?
- Can I set the admission rate per minute, and can several waiting rooms share one domain's capacity?
- Does the admission rate tune itself from live page performance, and what does it measure: page load times, response codes, or both?
- Which CAPTCHA providers are supported, and is one included without a third-party account?
- Can I control the look, markup and language of the waiting room myself, and can each waiting room have its own template?
- How is pricing calculated: per session, per event or flat monthly, and what happens if I exceed a limit during a peak?
- What are the contract terms, and can I move between tiers or drop to a free tier around my event calendar?
- How long does a basic setup take, and how long should I allow before a major on-sale?
- What are the support response times at my tier, and is the service listed on the procurement frameworks my organisation uses?
CrowdHandler plans at a glance
Figures from the pricing page on 3 November 2026, in US dollars.
| Plan | Price per month | Max. concurrent waiting | Max. outflow per minute | Waiting rooms | Domains | Support response |
|---|---|---|---|---|---|---|
| Lite | Free | 100 | 10 | 1 | 1 | No SLA |
| Starter | $290 | 2,000 | 100 | 2 | 1 | 48 hours |
| Standard | $900 | 7,500 | 250 | 3 | 2 | 24 hours |
| Plus | $1,680 | 20,000 | 500 | 5 | 3 | 8 hours |
| Professional | $4,500 | 100,000 | 1,000 | 10 | 5 | 2 hours |
| Enterprise | By quote | 1M+ | Custom | Custom | Custom | 1 hour |
Choosing a waiting room FAQ
Do I need a virtual waiting room?
If demand for anything on your site can outrun what it can handle at once, whether that is tickets, stock, appointment slots, places on a course or simply server capacity, then yes. If your traffic has always been steady, a catch-all waiting room is still worth having as insurance: it stays invisible until the day that changes.
Should the queue be first come, first served or random?
First come, first served suits always-on crash protection, where there is no advertised start time. Random allocation after a countdown suits scheduled on-sales and openings, where bots and early arrivals would otherwise take every position at the front.
Is a waiting room an alternative to load testing or scaling?
No, it complements them. Load testing tells you the rate your site can sustain, scaling raises that rate, and a waiting room holds demand to it on the day while also handling fairness and scarcity. Read Load test vs queue.
How much does a virtual waiting room cost?
CrowdHandler's listed plans are flat monthly prices with no overages or add-ons: Lite is free, Starter $290, Standard $900, Plus $1,680 and Professional $4,500 a month, and Enterprise is agreed by quote. Other vendors may price per session or per event, so ask how your busiest day is billed before you compare.
Can public bodies buy a waiting room through a procurement framework or marketplace?
Yes. UK public bodies can buy CrowdHandler through G-Cloud 15 on the Digital Marketplace. French public bodies can buy through UGAP, the French central purchasing body. Organisations that buy through AWS can use the AWS Marketplace.
Try the criteria against CrowdHandler
The Lite plan is free and takes about 15 minutes to set up.