Virtual waiting room: keep your site up when everyone arrives at once
On the day of a sale or a ticket release, more visitors turn up than your server can handle: everything slows down, then payments start failing, on the very day you should be selling the most. Klacos lets in as many visitors as your server can serve and holds the rest, in order, on a page that tells them where they stand. Bots don’t get a place in the line.
Why sites go down on the day everyone shows up
A server can only serve so many visitors at once. Beyond that, everything slows down for everyone, then the errors start: baskets empty, payments fail, and the day you’d been waiting for becomes the day nobody buys. Adding servers is expensive, hard to plan and often arrives after the peak.
Bots make it worse. Faster than any person, they arrive first and take the places your customers were waiting for. Your customers, meanwhile, remember an error page and a lost basket.
What you should expect from a waiting room: it holds the surge at the door instead of letting your server collapse, it respects the order people arrived in, and it doesn’t let bots jump the queue.
What waiting looks like
The surge arrives
A threshold is crossed, or the time of your sale has come. The queue opens on the whole site or on the paths you picked.
The visitor waits
They see their place in the queue and an estimate of the time left. The page updates on its own, so there’s nothing to reload.
They get in when it’s their turn
In order of arrival, or as the draw decides. Their entry stays valid for as long as you allow to complete a purchase.
You follow it all
The console shows, live, how many people are waiting, how many got in and how many left before their turn.
A queue with no room for bots
An ordinary queue counts sessions; it has no idea who opens them. The Klacos waiting room sits where every visit is already analysed for bot management, and on a sale day that makes all the difference. A bot that has been turned away never joins the queue, so it takes nobody’s place. One that opens session after session to hold several places is treated like any other bot. Whatever throughput your server can handle goes to real customers.
Search engines never see the waiting page. They get a temporary unavailability response telling them to come back later, so the queue leaves no trace in your search results. The waiting room builds on what performance and availability already do for your site: caching, a copy served if your server goes down, and failover to a standby server.
Hold the surge without losing your customers
An entry rate
Opens on its own
Scheduled or manual
Whole site or one path
In order, or by draw
No bots in the queue
A page that keeps people informed
Live figures
Questions about the waiting room
Do I need to change my site?
No. The queue is set up in the console, for the whole site or one path: a threshold, an entry rate and a waiting page.
Can I open it at a set time?
Yes, for an announced sale or ticket release. It can also open by itself when a threshold is crossed, or with one click from the console.
Do search engines see the waiting page?
No. They get a temporary unavailability response and come back later. The waiting page isn’t indexed.
How long can an admitted visitor stay?
That’s up to you: you set how long an entry stays valid.
Plan your next sale with a queue kept for real customers
Request early access, or tell us about the sale, ticket release or campaign you’re planning.