When you add Queue-it’s virtual waiting room to your website or app, visitors exceeding capacity limits of your website or app are offloaded to an online queue on Queue-it’s infrastructure.
An online queue in Queue-it's virtual waiting room is simply a waiting page that is inserted between two web pages.
At the throughput rate you configure, Queue-it then redirects the visitors who waited in line back to your website in the correct, sequential order.
You can implement the virtual waiting room at the site level and/or on specific pages.
Implementing at the site level gives visitors a seamless customer experience. They start on the queue page that is customized to match your brand, and once they are redirected they browse your website and check out like normal. Site-level implementation also gives you full control over precisely how many visitors are on your infrastructure.
Implementing at the page level can, for example, allow visitors to browse a ticketing website and not be placed into an online queue unless they select tickets to a particular concert. Or, it can allow online shoppers to browse products and not be placed in the online queue until they proceed to checkout.
There are two principal implementation patterns for covering your site or page(s):
Concert onsales, shopping holiday sales, conference registrations, and similar situations have a fixed start time by which visitors will already have accumulated on your website and exceed your website’s capacity.
To manage pre-event build-up, you offload early visitors from your infrastructure to Queue-it’s pre-queue waiting room. Early visitors will see a page with a countdown timer. At sale or registration start, visitors are randomized and assigned a place in line. This has the added benefit of neutralizing any advantage to arriving early.
Visitors who arrive after the sale starts get a first-come, first-served place in the queue.
When the online queue is empty, Queue-it will switch off the virtual waiting room unless traffic inflow exceeds your configured thresholds.
Enterprises use this implementation pattern as a safety net to mitigate unexpected traffic surges and for protection during high traffic peaks all year round.
With the 24/7 protection implementation, traffic levels on the covered site or page(s) are constantly monitored. If traffic inflow exceeds the thresholds you configure, only then will the online queue activate.
The visitors would be placed in a standard first-in, first-out queue. When the online queue is empty, Queue-it will switch off the virtual waiting room and no visitors will notice a queue page until traffic inflow again exceeds your configured thresholds.
When your web page is covered by Queue-it's virtual waiting room, the visitor flow is changed to the following:
- A visitor navigates to your website.
- The Queue-it Connector determines if the visitor needs to go to the queue (based on your configuration).
- The visitor is offloaded to the Queue-it infrastructure using a standard HTTP 302 redirect.
- The visitor enters Queue-it’s virtual waiting room and is shown a personalized queue page with information about queue number, estimated waiting time, and more.
- After waiting in the queue, the visitor is automatically redirected if the queue page is open. If not, the visitor gets a sound notification and popup the next time the queue page is viewed.
- The visitor is given a signed token and is redirected to a page on your website using a standard HTTP 302 redirect.
- The Queue-it Connector verifies the signed token to ensure that the visitor is allowed access to the web page and creates a session for the visitor.
- The visitor continues the user journey on your website.
Queue-it does not operate as a DNS / reverse proxy. Therefore, no sensitive personal data between the visitor and your website goes through Queue-it's service.
Queue-it offers four integration options:
By linking to the queue directly, visitors are taken directly to the Queue-it infrastructure and no load is put on the target server until they have completed their waiting period in the queue.
This integration involves including a simple script on the web pages to be covered. The majority of our customers integrate with this approach. Although tech-savvy users can skip the queue, it is easier and quicker to integrate than the server-side Known User method.
This integration removes the possibility of end-user manipulation, ensuring an unskippable queue. Queue-it offers Connectors to easily plug in to existing CDNs, proxies, and ecommerce and ticketing platforms.
Similar to the Proxy / CDN / Load Balancer Connector, this method creates an unskippable queue. It can be completed by a skilled developer in under a day. We offer Connectors for several programming languages.
For more information on all Queue-it Connectors, visit our Connectors Page.
Once the technical integration is complete, you will be able to configure when and where Queue-it's virtual waiting room covers your website or app.
Queue-it offers two methods to administer your account.
GO Queue-it, our web-based admin platform, gives you a powerful overview of everything you need to manage your account successfully, including real-time communication and queue traffic analytics.
Alternatively, you can use our REST-based Admin API to programmatically manage the entire lifecycle of virtual waiting rooms, from creation to sunsetting.
You can integrate Queue-it’s virtual waiting room to flexibly protect your entire website or select pages. There are two options for configuring this.
Alternatively, you can trigger the queue on the relevant page(s) programmatically using our Connector SDKs.
For a comprehensive overview of Queue-it’s technical setup, get your Technical Integration white paper.