...
Example: You want to collect phone numbers/email
Name: The internal name of the field. Used for analytics and integration purposes. Shouldn’t be changed after the queue is created. Should be the same within the tenant so later we will provide the analytics on the tenant level. Example: “phone-number” / “email”
Label: Customer visible name. Example: “Please provide your phone number” / “Please provide your email”
Placeholder: Customer visible placeholder if no value is specified by customer “+46999999999” / “test@email.com“
Value: Value that is used before customers specify any information. If customers do not change the value, the value will be used. For example, if value is omitted, there is no predefined value for all customers. Usually, you do not want to provide it
Validation rules: Applied for checking if the information is valid. Example: Regular expression (Regexp) pattern is specified (please reach technical team to support here). Default validations always will be applied to check that provided value is the phone/email address
Required field: The customer has to provide information before the ticket is created
Will be used for user notification: The Queue system will automatically use collected phone/email for sending notifications if SMS / email notifications are enabled
...
...
Note: please specify Categories first. add link to categories
Example: You want the customer to select under which Category ticket should be created, for example which type of questions the customer has
Name: The internal name of the field. Already fixed. Used for analytics and integration purposes. Shouldn’t be changed after the queue is created
Label: Customer visible name. Example: “Please choose service the service”
Placeholder: Not applied
Options: Will be taken from the Categories section (add link to categories).
Validation rules: Applied for checking if the information is valid. Example: Regular expression (Regexp) pattern is specified (please reach technical team to support here). Default validations always will be applied to check that provided value is the phone/email address
Required field: The customer has to provide information before the ticket is created
...
Enable Admin UI ticket printing: To use printed tickets in addition to the mobile-only solution.
Enable check-in by scanning QR code from ticket: This lets the staff manager use the camera on their personal device to check people in, by scanning a QR code on the visitor’s phone ticket or printed ticket. If you have a steady flow of people coming in, you can use this feature to speed up the process.
Customers can cancel ticket: Enable cancellation
Automatically check out tickets when calling in a new ticket (Serving mode and Email login are required): When the Queue manager calls the next ticket in and still has another ticket under the Serving (Serving column) which is assigned to the Queue Manager, the ticket from the Serving will be checked out automatically.
Notify X pending positions*: Notify someone waiting that it will soon be their turn to approach the entrance, based on the number of tickets in front of them in the queue. For example, if only one person is in front of you, you will be called to approach the entrance.
A maximum number of people per general (A-type) ticket*: Set a limit on how many people can register on a single ticket.
Walk-in ticket prefix: You can set a custom prefix label for general (walk-in) tickets. By default, these tickets get the A prefix (eg. ticket number “A23”). If Categories are specified, labels from Categories will be used instead
Admin UI ticket prefix: You can set a custom prefix label for manually issued tickets. By default, these tickets get the M prefix.
Stations (Queue can have multiple stations. Define them here): Enabling stations means that one queue can hold multiple endpoints, for instance, multiple cash registers in a single store.
Custom information for tickets: You can add a custom information text field to your tickets, for examples safety instructions or information to your email, etc.
Auto checks out after minutes (only when the Show serving tab is enabled): if the Queue manager doesn’t Check the ticket out manually, the system will check it out automatically after a specified amount of minutes.
...
Categories
Enable the categories to registration flow for the customer information.
...