Waiting Room Name

The default waiting room title displays the name of the waiting room to users, so you should pick a name that will make sense to your users. E.g. 'Black Friday Waiting Room'. In this example, we are looking at a match-all room, set to protect the entire domain, so the generic name 'Waiting Room' makes sense. This name will also be used as the label for the waiting line on the  graph on your dashboard.


URL

This is the URL of your waiting room. If you use the DNS implementation, then the first portion of the URL will be your own domain name. If you use another integration method, the waiting room address will start wait.crowdhandler.com the second portion of the URL is editable. When adding a waiting room this portion will be pre-filled with a string of random characters. You can change this to any unique string that is unclaimed. The widget in the field, will let you click to go and view the waiting room at that URL.


Redirect users to

This is the URL on your site that you want to redirect users to when they leave the waiting room. It will default to the home page on your domain.

If you send users directly to the waiting room, they will be forwarded to the redirect URL when leaving the queue. But if the user is redirected from your website to a waiting room, the user will be sent back to the url that they were trying to access on your website. 


Message

The message is for communicating with your users in the waiting room. You can change this at any time, and the new message will reach end users within one to three minutes.  


Room Capacity

This is the capacity of your waiting room. Why would we want to limit the capacity of our waiting room? Well - for one, it's the key metric for CrowdHandler's billing plans. Your total waiting room capacity is split across all the rooms on your domain, so you can give higher capacity to rooms where you expect more users.


Template

Here you select which HTML template this waiting room should use. Standard templates will be available if you're on a plan without custom templates. If you're on a plan that allows custom templates, your custom templates will also appear here.


Countdown Starts

The date time in this field dictates when your waiting room activates. If you hit a protected URL on the website before this date, you will be allowed through. If you visit the CrowdHandler Waiting Room URL before this date you will get a 404. After this date, if you hit a protected URL you will be sent to the waiting room. If the queue is not yet active, your users will be shown a countdown to when the queue activates. This means that if the Countdown has started, but the queue has not yet activated, users will be held in the waiting room, without a position, even if the number of users visiting is not exceeding your domain's ingress rate. 


Queue Activates

This date dictates when your users start being allowed through the queue. After this date, users visiting the waiting room will be shown their queue position, and the queue positions will start ticking down inline with the rate set on your domain. In this mode, if there is no queue, and the number of users visiting your protected URLs is within the ingress rate for your domain, users will be allowed in without even necessarily seeing the waiting room.


Protect URLs

Protect URLs has five modes:



1. All of

This means that a user trying to access any URL on this domain will be checked against the domain rate and the activation dates, for whether they should be in a waiting room. In other words, this pattern creates a waiting room that protects the entire domain. Catch-all rooms have some special properties, which can you can read more about here.


2. URL Contains

This mode means that all URLs containing a particular string will be checked against domain rates and activation dates for this room. In other words, this waiting room protects all URLs on your site that contain a certain string. For example, you might be able to protect the 'store' area of your site by setting the pattern contains and the string '/store'.


3. URL matches regular expression

If you're an advanced user, you can use regular expressions to define the pattern of URLs that are protected.


4. URL does NOT match regular expression

Use a regular expression to apply to all urls that do not match the pattern.


5. Disabled

Disable the room. Any users that are currently in the waiting room will be allowed onto your site.