Skip to main content

Queueing

The Queueing section contains the pages used to configure the local queueing systems, and replicate configurations.

Management​

Every location that is created in the Essentials > Resources > Locations page that has the ‘Set this Master as Virtual’ option enabled will be listed in this page, allowing you to configure the location’s queueing system and its devices.

To access the Management page, go to Queueing > Management.

Locations’ queueing systems and devices can be configured by clicking on the ‘Edit’ button of the desired location. Once inside, you will find a menu: Dashboard, Reports, Management (Services, Counters, and Devices), Notifications Settings, Pages, System (Message Centre, Settings, Translations, and Integrations), and About pages.

tip

The available locations and pages and actions inside each location depend on the roles assigned to the user.

Dashboard​

The Dashboard provides the current day’s overview of the location’s queueing system status. It contains information divided into two tabs:

  • System – includes the online/offline status of the devices assigned to the location;
  • Queue Management – includes information about the current day’s tickets statuses within the location; a comparison per service between the average waiting time and service time and the defined KPIs; and a list of today’s confirmed and checked-in appointments for that location.

Reports​

Reports are PDF or CSV files with information available in the Statistics and Lists views of the system that can be downloaded or sent by email to specific staff users at specific times.

Refer to the subchapter ‘Reports’ within the chapter ‘Data’ to know how to manage reports (create, edit, download, delete, and activate/deactivate).

Management > Services​

The services created on the Essentials > Resources > Services page and assigned to the location will be listed in this page. In the ‘Show synchronization options’ it is possible to set if the services’ names, tags, and/or order should comply with the ones set on the Essentials > Resources > Services page.

It is also possible to add new services within the location, that will be labelled as ‘local services’. The local services can only be managed on this page and have no link to the services created and managed on the Essentials > Resources > Services page.

For any type of service, it is possible to:

  • Edit the service’s configuration, by clicking on the ‘Edit’ button.
  • Activate/Deactivate the service by clicking on the ‘On/Off’ button.
  • Delete the service, by clicking on the ‘Delete’ button.
tip

Services with origin in the Essentials > Resources > Services page will not be deleted from the system, only unassigned from the location.

note

Bulk actions are also available to edit or delete several services at a time.

EDIT SERVICE > IDENTIFICATION:​

Services are identified by a colour, one or two letters tag, and a name. The colour can be used as the default one in the devices, the tag will be associated to the ticket number when a ticket is generated, and the name is the main identifier of the service for the visitors.

To organize your services, you can assign them to services groups. These groups can be used to filter the services in some pages, as well as to set menus of services in the ticket kiosks (refer to the subchapter ‘Services’ within the chapter ‘Essentials’ to know how to manage services groups).

It is also possible to set a description for the service that can later be shown in the ticket kiosks and help visitors to have a better understanding of the service itself. This field supports HTML, enabling more layout options when using the service info page in the ticket dispensers (like bullet and tables).

tip

The identification fields will be available for edition depending on the synchronization options set on the previous page.
The ‘service code’ field is only available for server services and cannot be edited in this page.

EDIT SERVICE > CONFIGURATIONS:​

Single-queue feature integration: when enabled, this option allows to generate and call a sequential ticket when there are no waiting tickets for this service – it automatically generates and calls a ticket when the user calls the next ticket.

Priority tickets: when enabled, this option allows the generation of priority tickets. Those tickets will always have priority over regular tickets, which can be useful when your visitors include older people, people with disabilities, pregnant women, among others.

Number of printed tickets: this option determines the number of paper tickets that the ticket dispensers will print when a ticket for this service is generated.

EDIT SERVICE > TICKET RESTRICTIONS:​

You can set a limit on the number of tickets that may be generated for your service in a given time frame:

  1. Click on the ‘Add restriction’ button, and a new ticket limit rule box will be added.
  2. Configure the ticket limit rule by selecting a day of the week in the dropdown with the same name, typing the period of time the rule will apply to in the ‘From’ and ‘To’ fields, and typing the maximum number of tickets imposed by the rule in the ‘Tickets restriction’ field.
  3. Save changes.

To delete a ticket limit rule box, click on its the ‘Delete’ button.

EDIT SERVICE > TICKETS RANGE:​

For each service, it is possible to set a tickets range. The first ticket will be generated with an ‘initial value’ and every following ticket will have a number that is incremented by one unit from the previous ticket. Once a ‘maximum value’ is reached, the next generated ticket will have the initial value again.

The amount of tickets included in the range you defined is displayed at the ‘Total tickets’ field.

KEY PERFORMANCE INDICATORS:​

You can measure the performance of your service comparing it with predefined goals, the key performance indicators (KPI’s). To set KPI’s, type the desired values in the ‘Waiting time KPI’, ‘Service time KPI’ and ‘Number of waiting tickets KPI’ fields, and save changes. Based on the KPI’s you defined, you can set notifications to warn users every time a KPI is exceeded. These KPI’s will also be used for comparison in the data module.

EDIT SERVICE > SERVICE TIME:​

If a ticket is left open in QM-PAD after serving it, the service time will be affected and the statistical data results will not represent the reality. To prevent forgotten tickets in QM-PAD, when enabled, this option provides a mechanism to warn QM-PAD users when the service time reaches a specific limit and waits for their feedback.

To set these warnings in QM-PAD, enable the option ‘Notify QM-PAD users when the service time exceeds its maximum’ and then:

  1. Set the time limit to trigger the first warning in the ‘Trigger 1st notification when service time reaches’ fields.
  2. If you wish to send multiple warnings, define the amount in the ‘Maximum number of notifications’ field, and the time period between warnings in the ‘Time-gap between notifications’ fields.
  3. Set the time limit the QM-PAD user will have to answer the warning in the ‘Time to reply before the service is automatically ended’ fields.
  4. Save changes.

When the service time reaches the defined maximum value, a pop-up will appear asking the QM-PAD user if the ticket is still being handled and if the user:

  • clicks/presses the ‘Yes, continue’ button, the warning disappears and the QM-PAD returns to the ticket;
  • clicks/presses the ‘No, end service’ button, the ticket will be automatically ended;
  • does not click/press any of the options, the ticket will be automatically ended once the defined reply time is exceeded.
tip

If you have multiple warnings, the pop-up will continue to appear, with the defined time gap, if the user keeps replying ‘Yes, continue’.

EDIT SERVICE > ASSIGNED FORM:​

Bloom provides forms to collect information from visitors and staff users. For each service it is possible to assign a form (refer to the subchapter ‘Forms’ within the chapter ‘Essentials’ to know how to manage forms):

  1. Select the desired form amongst the available ones in the ‘Form’ dropdown.
  2. Enable the ‘Do not show this form to priority tickets’ option if you do not want to show the form if the visitor chooses to generate a priority ticket.
  3. Save changes.

The collected answers can be later analysed in the data module.

tip

You can also set the service form in the Essentials > Assignments page. If you wish to change the assigned form, click on the ‘Edit form’ button and you will be redirected to the form edition page.

EDIT SERVICE > ASSIGNED COUNTERS:​

This section informs which counters from that location are assigned to the service.

EDIT SERVICE > assigned schedule:​

In order to set the time period when the service is open and allow visitors to generate tickets, you must define a schedule for the service:

  1. Select the desired schedule amongst the available ones in the ‘Schedule’ dropdown.
  2. Save changes.

Outside the working hours, a service will be listed as “Closed” in the displays (although you can still call outstanding tickets).

tip

You can also set the service schedule in the Essentials > Assignments page. If you wish to change the assigned schedule, click on the ‘Edit schedule’ button and you will be redirected to the schedule edition page.

Management > Counters​

Counters are the workspaces where users handle the generated tickets. Each counter requires a logged-in user that calls tickets from the services available on that counter. Counters can have different assigned services and calling priorities.

Counters are identified by a one or two numbers tag, and a name. Both can be used to identify the counter to where the visitor must go to once called.

The available actions in this page include:

  • Add/Delete a counter.
  • Assign/Desassign services to the counter.
  • Assign priority level to each service within each counter.
  • Activate/Deactivate the counter by clicking on the ‘On/Off’ button.

Bulk actions are also available to edit or delete several counters at a time.

Adding a counter:​

  1. Click on the ‘Add counter’ button, and a new item will appear.
  2. Type the counter’s name in the ‘Name’ field - a default value will appear as “Counter N”.
  3. Type the counter’s number in the ‘Tag’ field (you can choose numbers between 1 and 99)
  4. Edit the services assigned to the counter, by clicking on ‘Assign services’ button – a pop-up will open, where you need to select the services to be assigned to the counter, and click on the ‘Confirm’ button.
  5. Save changes.
important

It is possible to have counters with the same tag.

Set priorities between services, in the same counter:​

By default, or services are assigned the ‘normal’ priority level (yellow colour), but you can set different service priorities in a counter. This means you will have services whose tickets will be called first or last according to the assigned priority.

To assign services priorities in a counter:

  1. Find the counter where you wish to change the service priority.
  2. Click on the service’s box for which you want to set a different priority level.
  3. Select one of the five levels of priorities: very high (red), high (orange), normal (yellow), low (green), or very low (blue).
  4. Save changes.
Example

For a better understanding of how it works, consider the following example:

  • 3 services assigned to Counter 1
  • with the following priorities: Service A – very high, Service B – normal, and Service C – very low
  • ‘Enable balancing priorities by waiting time’ option disabled
  • The tickets will be called by order of priority (highest to lowest) and by order of arrival:
  • The user of Counter 1 calls the tickets from service A.
  • When there are no more tickets from service A, the user of Counter 1 will call tickets from service B.
  • When there are no more tickets from service A and B, the user of Counter 1 will call the tickets from service C.

Priorities balancing:​

Activate the ‘Balance priorities by waiting time’ option if you wish to call tickets from lower priority services as well. This way, you will ensure that tickets from services with lower priority levels will also be called, without waiting indefinitely.

Temporarily deactivating a counter:​

To disable a counter without deleting it click on the desired counter ‘On/Off’ button. The button colour will change from green to red. A deactivated counter will not be available to log in, in QM-PAD and Concierge applications. Save changes.

VIEWS:​

You can display the counters in a grid view (click on the ‘Grid view’ button) or list view (click on the ‘List view’ button).

Management > Devices​

Bloom devices are hard or soft appliances designed to facilitate the interaction between the system and human entities - users and visitors.

The available actions in this page include:

  • Edit and configure a device.
  • Delete a device.
  • Activate/Deactivate the device by clicking on the ‘On/Off’ button.
danger

Whenever you save a change made in the device’s configuration page, it will reboot.

ADDING DEVICES:​

To add players, ticket dispensers, and/or tablet applications (Tablet Kiosk, Concierge, or Extender) you will need the following information:

  • Server address– this is the URL (or IP) address of your Bloom Enterprise system.
  • Server port – by default the server’s port is 80, but please check your network configurations before adding devices.
  • Location key – the location key is available at Essentials > Resources > Location within the specific location’s page in the ‘Location Key’ section.

To add web application Concierge, click on the ‘Add device’ button and then the ‘Add virtual Concierge’ option.
To add an Epson TM-T20III network printer, click on the ‘Add device’ button and then the ‘Add custom network printer’ option.
To add the E-Ticket feature, activate the option in the Essentials > Assignments > Location page.
If you wish to rename a device, type the new name in the ‘Name’ field, and save changes.

Information

Refer to the devices installation guides for more information.

PLAYER CONFIGURATION:​

Players are devices designed to manage the information and contents that are displayed to visitors through displays.

To configure a player, click on the respective ‘Edit’ button, and you will be redirected to the player configuration page:

Modules​

In the ‘Select the modules to be displayed’ section it is possible to set which modules the player should display. In the header it is possible to display an image (usually a logo), the date, and the time. The body in composed at least by one queueing module (Queueing 1), but can also incorporate a multimedia module, a second queueing module, or the location’s e-ticket QR code. The footer is used to display text or RSS feeds.

In the preview, it is possible to visualize the active modules and their positions. If the body contains two modules (queueing 1 and multimedia, or queueing 1 and queueing 2, or queueing 1 and e-ticket), it is possible to set the position of each module in the ‘Queueing 1 module position’ option.

Information

Selecting a module to be shown will also enable access to its configuration tab, in the ‘Modules configuration’ section.

Theme​

Set a background image or colour in the ‘Select a background’ section, and the modules dimensions and ratio in the ‘Set dimensions’ section.

For a faster theme configuration there are three available templates to choose from at the ‘Select a template’ dropdown.

Queueing modules configuration​

In the ‘Tickets’ section, choose if you wish to display the tickets by service (one row per service), by counter (one row per counter), or a defined quantity of last called tickets.

In the ‘Select counters/services to display in this player’ section, you can filter which services or counters will be displayed.

In the ‘Select elements to display’ section, select the information you wish to display: service/counter name, service tag, ticket letters, ticket number, visitor identification, and counter number. After choosing the information to display, define the respective column titles in the ‘Column titles’ section.

In the ‘Customization’ section, you can customise the theme of the module itself: corners radius; borders and splitters thickness and colour; background colour for each displayed element; text colour for each displayed element; and, if you are displaying the tickets by service, the message and text and background colours for the inactive services’ message.

In the ‘Translations’ section, you can activate the multilanguage option to display contents in more than one language, and set if they should be displayed simultaneously or display each language alternately. The available languages are the ones listed in the Translations page.

In the ‘Priority tickets’ section, choose if priority tickets should be highlighted as such in the display, and set the background and text colours and if priority icons should be also displayed for a clearer identification.

In the ‘Appointments’ section, choose if appointments tickets should be visually differentiated from walk-in tickets, and set the background and text colours.

Information

To display the visitor identification element, you need to collect this information through a form while generating the tickets (default system question ‘name’). If the visitor does not fill the question, this field will be left blank in the display.

Multimedia module configuration​

In the ‘Select a playlist’ section, select the playlist you wish to display in the multimedia module. In the ‘Background colour’ section, choose to have no background or select the ‘Use solid colour’ option and configure the ‘Opacity’ and the ‘Colour’ fields to set a background colour for this module.

In the ‘Border’ section, choose to have no outline or select the ‘Show border’ option and configure the ‘Thickness’, the ‘Corner radius’ and the ‘Colour’ fields to set an outline for this module.

Logo module configuration​

To set the image to be used in the logo module, it is possible to upload it from your hard disk (by clicking on the ‘Image from hard disk’ button) or to select it from the system’s gallery (by clicking on the ‘Image from gallery’ button).

Date and time modules configuration​

Set the format and the colour in which the date and/or the time should be displayed.

Ticker module configuration​

In the ‘Selected feeds’ dropdown, select and order the feeds you wish to display. And set the text colour (by clicking on the ‘Colour’ picker) and the speed (by increasing/decreasing it on the arrows buttons) of the ticker module.

CONCIERGE CONFIGURATION:​

Concierge adds a personal touch to the visitor service by habilitating users to approach visitors, listen to what they came to do and help them enter the queueing process. This application can serve different scenarios, from saving time to visitors to boost queues on the busiest time of day.

Content > Modules​

In the ‘Modules’ section, set which actions the user should be able to perform within the application: generate tickets, call and manage tickets, schedule appointments, and appointments check-in.

Content > Settings​

Set notifications for Concierge users by selecting the warning you wish to activate and configure any additional information. The available options are to notify users when: number of tickets waiting is higher than ‘N’ tickets, a new ticket is issued for services without waiting tickets, and the service time reached ‘N’ minutes.

Limit the ticket management actions Concierge users can perform, by not allowing them to: pause tickets, call tickets, cancel tickets, transfer tickets, or cancel a ticket after the service time reaches ‘N’ minutes.

Content > Services​

Set the services for which the Concierge users can generate a ticket.

Information

This setting will be merged with the services assigned to the counter where the user is logged in.

Skin​

You can customize the look of the Concierge application. For the menu (section at the left side of the interface), the services buttons, and the navigation buttons you can set the background and text colours.

ticket kiosks configuration​

Ticket kiosks are hard (ticket dispensers) or soft (tablet kiosk) devices designed to generate tickets.

Content > Modules​

In the ‘Actions’ dropdown, select whether the main page will display a list of services (‘Services selection’ option) or a menu with the available actions (‘Options selection menu’ option). If you chose the ‘Options selection menu’ it is possible to enable and order the options ‘Service selection’ and ‘Appointments check-in’, and also to enable the e-ticket QR code to be scanned by the visitor.

Select the ‘Enable language selection’ option if you wish to activate the multi-language feature in the ticket kiosk.

Select the ‘Show thank you message’ option if you wish to display a message at the end of any ticket kiosk interaction.

Set the time the ticket kiosk will wait for the visitor action before returning to the default first page.

Information

Selecting a module to be shown will also enable access to its configuration tab, in the ‘Modules configuration’ section.

Content > Footer​

Set a text to be displayed above the footer buttons.

Content > Options menu module​

Add a message to your Options menu page by typing the text in the ‘Welcome message’ field. This text, having a 250 characters limit, will be displayed at the top of the action buttons list.

Content > Language module​

By enabling the ‘Show first a page with language selection menu’ option, visitors will have a chance to select a language before interacting with the ticket kiosk. Whether you choose to set or not to set a language selection page as the main page, language selection will always be available through buttons located in the footer.

By enabling the ‘Show first a page with language selection menu’ option, visitors will have a chance to select a language before interacting with the ticket kiosk.

A small note can be added before the languages list in the ‘Note to visitors’ field.

The available languages are the ones listed in the Translations page. Select the ones you desire and order them as you wish.

Content > Buttons module (service list)​

By enabling the ‘Show service selection as first page’ option, visitors will be prompt to choose the service, and secondary actions will be available in the footer (like appointment check-in and language selection).

danger

If this option is enabled while the ‘Options selection menu’ is selected in the ‘Action’ dropdown of the ‘Modules’ section, the E-Ticket QR code cannot be displayed.

A small note can be added before the services list in the ‘Note to visitors’ field.

By default, Bloom creates one button per each service, without the possibility of editing the buttons. This will happen if either the ‘Enable automatic button creation (one for each existing service, grouped by services groups if applicable)’ option or the ‘Enable automatic button creation without grouping services’ option are enabled. In either case, it will be possible to set if a ‘Service information page’ should be displayed after a service is selected and if instead of showing the priority buttons in each service button there will be a ‘Global priority ticket button’ shown in the footer for visitors that would like to generate a priority button.

If you wish to manage the buttons by yourself, select the ‘Enable the buttons display settings’ option. Then, the following actions will be available:

  • Adding new buttons by clicking on the ‘Add’ button – a newly expanded button box will appear on the bottom of the buttons list;
  • Editing buttons by clicking on the button’s ‘Edit’ button to expand it and gain access to the detailed configurations;
  • Deleting buttons by clicking on the button’s ‘Delete’ button;
  • Setting the buttons’ order in the services list by using the drag and drop tool.

In the “manual” mode, for each button you can set its type: ‘Service’ (it will be a service button corresponding to the service chosen in the dropdown to the right of the ‘Button type’ dropdown), or ‘Menu’ (it will allow you to create a set of buttons within that menu). It will be possible to set if a ‘Service information page’ should be displayed after a service is selected, and if the service description should be synchronized with the one available at the service’s page.

You can also set if additional information should be displayed in each service button, like queueing information (number of waiting tickets and/or average waiting time), or a short-description.

Content > Thank you message module​

Type the text you wish to show in the Thank you message page, in the ‘Message’ field. This text, having a 110 characters limit, will be displayed in the centre of the page.

In addition to the message, you can also choose to display the ticket number, by selecting the ‘Display ticket details’ option – this feature is particularly useful for tablet kiosks (which do not generate paper tickets).

Content > Ticket​

In addition to the ticket service tag and name, you can set which other details will be printed in the paper tickets:

  • Extra text to be printed before the footer and aligned to the left;
  • Footer text to be printed centred at the bottom of the ticket;
  • Location’s name;
  • Service’s name;
  • Estimated waiting time;
  • Number of tickets ahead (in the queue);
  • Arrival date and time;
  • Logo.

By enabling the ‘Print multiple tickets’ option, the ticket dispenser will print the number of copies set in the selected service’s page.

Skin > Template​

For a faster theme configuration there are three available templates to choose from at the ‘Select a template’ dropdown.

Skin > Buttons layout​

There are two display options for the services selection and languages pages: buttons can be displayed in a single column or in two columns. The two columns option is only available for 15” ticket dispensers and tablet kiosks, and it is a good solution when you have a huge amount of items in the services and languages lists.

Skin > Background​

Set a background image or colour as the ticket kiosk’s background.

Skin > Header​

To add an image (usually a logo) to the ticket kiosk’s header, make sure the ‘Disable header’ option is disabled and then choose to either add an image from your hard disk or from the system’s gallery.

Skin > Footer​

For the note to visitors, you can set the text size and colour. Footer buttons are a quick way to access the different ticket kiosk interaction pages. For these buttons, you can set background colour and opacity, text size and colour, border thickness and colour, and corner radius.

Skin > Virtual keyboard​

Whenever visitors need to insert information in the ticket kiosks, the device will display a virtual keyboard. For this resource, you can set background and text colours for the keys, background colour and opacity for the answers fields, text size and colour of the buttons, border thickness and colour of the buttons, and corner radius of the buttons.

Skin > Navigation buttons​

Navigation buttons are used in ticket kiosks to jump between pages. For these buttons you can set format (icon + action description, or only action description), background colour and opacity, text size and colour, border thickness and colour, and corner radius.

Skin > Welcome page​

If the ‘Options selection menu’ option is selected in the ‘Content > Modules’ section, you can set the buttons’ background colour, text size and colour, border thickness and colour, and corner radius; and the welcome message text size and colour.

Skin > Language​

The languages page can display the language buttons in different formats: language flag and name (‘Flag + Language’ option) or just the language name (‘Language’ option). For the buttons, you can set background colour, text size and colour, border thickness and colour, and corner radius. For the note to visitors message, you can set text size and colour.

Skin > Buttons​

The service buttons can have different formats: service tag followed by service name (‘Service Letter(s) + Name’ option), service name only (‘Service name’ option), or service name followed by service tag (‘Service name + Letter(s)’ option).

Select the ‘Enable automatic button colour (same as service colour)’ option if you wish to match the buttons’ colours with the services colours set in the services’ page.

For the note to visitors message, you can set text size and colour.

By setting a number in the ‘Grid lines per page’ field, the system will automatically calculate the height of the buttons and respective text. If you do not want several service pages, enable the ‘Fit all buttons to one-page’ option.

For the service buttons, you can set background colour and opacity, text size and colour, border thickness and colour, and corner radius.

In case the services you selected for the ticket kiosk allow priority tickets generation, a priority ticket button will be included next to the service button. For the priority ticket buttons, you can set background colour and opacity, icon colour, types of icons, and button position. You can also add a text to the priority tickets button: type the message in the ‘Button text description’ field – this message has a characters limit of 20 and it will appear below the priority icons.

Skin > Forms​

If the ticket kiosk is displaying services with assigned forms, the available questions will be shown in the ticket kiosk when the visitors try to generate tickets. For the questions and the errors, you can set text size and colour. For the single and multiple answers, you can set option’s background colour, selection’s background colour, option’s text colour, and selection’s text colour.

Skin > Service information page​

For the information texts (title, description, and queuing information), you can set text size and colour.

For the standard and priority ticket buttons, you can set background colour and opacity, text size and text colour, border thickness and colour, and corner radius.

Skin > Check-in​

For the note to visitors message, you can set text size and colour.

Skin > Thank you message​

For the note to visitors message, you can set text size and colour.

E-TICKET CONFIGURATION:​

This web application simulates a ticket dispenser and delivers a virtual ticket. Visitors can access it in their smartphones by scanning the e-ticket QR code.
Configuration options are identical to the ones available in the ticket kiosks.

danger

To use E-Ticket you must first activate the reCAPTCHA v3 integration in the System > Integrations page.

EXTENDER CONFIGURATION:​

Extender is a multifunction application for tablets, intended to display information and collect visitors feedback.

Operation mode​

There are two possible operation modes: counter and autonomous mode. The counter mode acts at different ticket handling moments: when a ticket is called, while the visitor is being served, and after the service. The autonomous mode is used for tablets on-site to display contents and a general survey for anyone that touches the tablet screen.

Modules​

In the ‘Modules’ section it is possible to set which modules the application should display. In the header it is possible to display an image (usually a logo), the date, and the time. The body in composed by the main contents. The footer can display a customized text.

If you are using the Counter mode, set the main contents by clicking on the ‘Edit’ button and:

  1. Select the counter assigned to the device.
  2. Select the ‘Indicate when counter is closed’ option, if you wish to inform your visitors when the counter is deactivated.
  3. Set the default displayed content: ‘Multimedia playlist’, or ‘Ticket information’ – this is the content displayed when you are not calling or ending tickets.
  4. Set a content when a ticket is called: ‘None’, or ‘Ticket information’.
  5. Set a content when a ticket is ended: ‘None’, ‘Form’, ‘Thank you message’, or ‘Form + Thank you message’.
  6. Click on the ‘Apply’ button.

If you are using the Autonomous mode, set the main contents by clicking on the ‘Edit’ button and:

  1. Set a content to shown when someone taps the tablet’s screen: ‘None’, ‘Form’, or ‘Form + Thank you message’.
  2. Click on the ‘Apply’ button.
Information

Selecting a module to be shown will also enable access to its configuration tab, in the ‘Modules configuration’ section.

Background​

Set a background image or colour as the application’s background.

Offline device​

Set a message to be displayed whenever the Extender is offline.

Device disabled​

Set a message to be displayed whenever the Extender is disabled.

Counter closed​

Set a message to be displayed whenever the counter assigned to the Extender is closed.

To add an image (usually a logo) to the application’s header, choose to either add an image from your hard disk or from the system’s gallery.

Set the header and footer height percentages.

Date and time​

For the date and time, you can select the date and time format, choose whether or not to display the seconds, and set the text colour.

Navigation buttons are used to jump between questions in the forms. For these buttons you can set background colour, selected button background colour, text size and colour, border colour, and corner radius.

Ticket information​

Select the general modules you wish to keep when the ticket information is displayed: logo, date, time, and/or footer.
Select whether the service name and/or counter name should be displayed when a ticket is called, and set the text colour.
Select if, besides the ticket number, the ticket letters should also be displayed when a ticket is called. Alternatevely to the ticket number, you can set to display the visitors identification. You can set the text and background colours.

Information

To display the visitor identification element, you need to collect this information through a form while generating the tickets (default system question ‘name’). If the visitor does not fill the question, this field will be the ticket number.

Set for how long the ticket information will be displayed after a ticket is called.
Set the footer message to be displayed when a ticket is called up to 140 characters, and set the text colour.

Multimedia​

Select the general modules you wish to keep when the ticket information is displayed: logo, date, time, and/or footer.

Select the ‘Fullscreen’ option if you wish to display the playlist in the entire screen (in this case, the logo, date, time and footer will be displayed at the top of the playlist, without a background), and select the playlist you wish to display, in the respective dropdown.

Set the footer message when the multimedia module is displayed up to 140 characters, and set the text colour.

Form​

Select the general modules you wish to keep when the ticket information is displayed: logo, date, time, and/or footer.

For the questions, you can set text colour, size and alignment.

For the text answers, you can set text colour and size, background colour, border colour, and corner radius.

For the selection answers, you can set answer text colour and size, selected answer text colour and size, answer background colour, selected answer background colour, answer border colour, selected answer border colour, and corner radius.

Set how the selection answers will be presented, by clicking on the ‘Expand’ button of the answer type you wish to manage:

  • Single choice questions – choose ‘Present options as “Buttons” in all questions’ if you wish to show all answers as buttons; or ‘Present options as “Bullets” in all questions’ if you wish to show all answers in bullets; or set the configuration individually by selecting the ‘Set individually how options will be presented’ option;
  • Multiple choice questions – choose ‘Present options as “Buttons” in all questions’ if you wish to show all answers as buttons; or ‘Present options as “Bullets” in all questions’ if you wish to show all answers in bullets; or set the configuration individually by selecting the ‘Set individually how options will be presented’ option;
  • Scale questions – choose ‘Assign icon set “Smileys” to all questions’ if you wish to show all answers as smileys; or ‘Assign icon set “Numbers” to all questions’ if you wish to show all answers in circled numbers; or set the configuration individually by selecting the ‘Set individually how options will be presented’ option.

Set the footer message when the form is displayed (up to 140 characters), and set the text colour.

Thank you message​

Select the general modules you wish to keep when the ticket information is displayed: logo, date, time, and/or footer.

For the thank you message you can type the text to be displayed (up to 140 characters), in the ‘Message’ field, and set the text colour and size. Define for how long will this module be displayed after a ticket is closed, in the ‘Display information for’ section.

Set the footer message when the thank you message is displayed (up to 140 characters), and set the text colour.

EPSON TM-T20III NETWORK PRINTER CONFIGURATION:​

An Epson TM-T20III network printer can be added to the system so tickets generated in Concierge and QM-PAD can be printed in this device.

Set the printer’s name and IP address.

In addition to the ticket service tag and name, you can set which other details will be printed in the paper tickets:

  • Extra text to be printed before the footer and aligned to the left;
  • Footer text to be printed centred at the bottom of the ticket;
  • Service’s name;
  • Estimated waiting time;
  • Number of tickets ahead (in the queue);
  • Arrival date and time;
  • Logo.
Settings > QM-PAD​

These settings are applicable to all QM-PADs within the current location.

Enable the ‘Do not allow users to call appointment tickets before the scheduled time’ option to not allow users to call appointment tickets before its scheduled time. If enabled, you can set the ‘Time period during which appointment tickets will have priority (before scheduled time)’.

Set if the system should give priority to appointment tickets (at the scheduled time) or walk-in priority tickets.

By default, the transferred tickets notes are only available in the first transfer (the notes are deleted after transferring the ticket again). With the ‘When transferring a ticket, keep the last note associated to it (if any)’ option, you can keep the transferred notes between transfers.

By default, the tickets keep their priority level (regular or priority ticket) after the transfer. By selecting the ‘When transferring a ticket, allow users to change or set its priority’ option, QM-PAD users will be able to change the priority of the ticket during transfer.

By default, only the users that paused the tickets can recall them later. By selecting the ‘Allow users to call tickets that were paused in other counters’ option, all users logged in QM-PAD can recall the paused tickets in the system (independently of the services they are handling).

By enabling the ‘Users cannot cancel a ticket after the service time reaches X’ option, the ‘Cancel ticket’ button will be disabled in the QM-PAD after the ticket handling time reaches the defined value.

By enabling the ‘Allow users to suspend their session’ option, the ‘Pause session’ button will be added to the QM-PAD. If you enable the ‘Request users the motive why they are suspending their session’ option, you can add suspension motives that users will have to choose every time they click on the ‘Pause session’ button.

Information

The option Other is always available. When selected, the users will be able to type the motive.

By enabling the ‘Automatically call the next ticket after X’ option, the next ticket in line will be automatically called after X time since the last ticket handling. With this option, users do not need to click on the ‘Call next ticket’ button but his button is still available to use.

By enabling the ‘Allow users to call cancelled tickets within a tolerance of X tickets’ option, QM-PAD users can recall cancelled tickets with X tickets of tolerance – cancelled tickets will be available in the cancelled tickets list of the ‘Ticket selection’ section.

By enabling the ‘Show only the waiting tickets for the services that are assigned to the logged counter’ option, QM-PAD users will not see the waiting tickets for the services they do not handle in their counter.

With the ‘Open a pop-up with the following URL when a ticket is called’ option, Bloom will open a URL in a pop-up every time you call a ticket in QM-PAD. Type the URL in the URL field and add variables (optional): ticket ID, service ID, user ID, counter ID, visitor name, visitor email, or visitor phone. You can also define the pop-up width and height in.

Settings > Ticket dispensers​

By default, if you choose to display the service name in the paper tickets, the text background of this field will be black and the service name text will be white. By selecting the ‘Invert the service colours (background and text) on the paper ticket’ option, the text background will be white and the service name text will be black.

Settings > E-TICKET​

Set the e-ticket QR code renewal time interval. If set to 0, it will never be renewed. You can also renew it manually by clicking on the ‘Renew QR code’ button.

Set the maximum number of waiting e-tickets per visitor (up to 10).

Download the QR code in PNG format by clicking on the ‘Download QR code’ button.

Notifications settings​

Bloom offers a notification centre to deliver messages to users about specific system occurrences. The available notifications can be sent through different methods and are divided in Software (regarding the queueing system performance) and Hardware (regarding the devices operation) types. Notifications can be set for specific users or users with specific roles.

The available actions in this page include:

  • Add notifications by clicking on the ‘Add notification’ button, choosing the type of notification you want, naming it, selecting the users or roles that will receive the notification, selecting the services that will trigger the notification or any additional configuration, and selecting how the notification will be sent (through notifications log, QM-PAD, email, or SMS);
  • Edit notifications by clicking on the notification’s ‘Expand’ button;
  • Activate/Deactivate notifications by clicking on the ‘On/Off’ button;
  • Delete notifications by clicking on the ‘Delete’ button.

New ticket​

Triggers a notification every time a ticket is generated in the ticket kiosks or Concierge.

New ticket in services without waiting tickets​

Triggers a notification every time a ticket is generated in the ticket kiosks or Concierge for a service with no waiting tickets.

Average waiting time higher than the established kpi​

Triggers a notification every time the average waiting time is higher than the defined KPI, for a specific service.

Number of waiting tickets higher than the established kpi​

Triggers a notification every time the number of waiting tickets is higher than the defined KPI, for a specific service.

Average service time higher than the established kpi​

Triggers a notification every time the average service time is higher than the defined KPI, for a specific service.

Waiting tickets in services without online staff​

Triggers a notification every time there are tickets waiting and no staff logged in the counters that handle the respective services.

Ticket automatically closed after service time was exceeded​

Triggers a notification every time a ticket is automatically closed in QM-PAD due to the lack of response from the user to the ‘Service time exceeded’ warning set in the service page.

Ticket dispenser under maintenance​

Triggers a notification every time a ticket dispenser is not fully working – when the printer tab is open, for example. The ticket dispenser is identified in the notification.

Ticket dispenser paper roll about to end​

Triggers a notification every time a ticket dispenser is running out of paper (based on the printer sensors’ information). The ticket dispenser is identified in the notification.

Ticket dispenser paper roll Has ended​

Triggers a notification every time a ticket dispenser is out of paper (based on the printer sensors’ information). The ticket dispenser is identified in the notification.

Ticket dispenser is offline​

Triggers a notification every time a ticket dispenser is offline (no connection). The ticket dispenser is identified in the notification.

Request assistance​

Triggers a notification every time the ‘Call assistance’ button is pressed in the QM-PAD by a user needing assistance from co-workers.

System > Message Centre​

In a similar way to the notifications for staff users, Bloom allows you to send messages to visitors about relevant queueing moments. The messages can be sent through email or SMS.

The available actions in this page include:

  • Edit messages by clicking on the message’s ‘Expand’ button, selecting how the message will be sent (through email and/or SMS), and setting its content and any additional configuration;
  • Activate/Deactivate messages by clicking on the ‘On/Off’ button.
danger

Messages will only be sent if the required integrations are active (email and SMS) and if the visitor provides the required information at the ticket generation momento (email address and/or mobile number).

Send ticket details to visitors​

Triggers a message every time a ticket is generated in the ticket kiosks or Concierge.

Warn visitors that their turn is coming​

Triggers a message every time one of the following conditions is verified: when the number of tickets ahead is X, or when the expected time to be called will be within X (min).

Warn visitors when their ticket is called​

Triggers a message every time a ticket is called in QM-PAD or Concierge.

Send message to visitors after being served​

Triggers a message when the ticket is ended in QM-PAD or Concierge.

Send SMS to paused tickets in Bloom Concierge​

Allows staff users to trigger a message (a button will be available in the Concierge application) when a ticket is paused.

System > Settings​

This page contains general local queueing configurations.

Operation​

Set devices to restart after changes are made to its layout or contents, and/or after changes are made to the system’s configurations.

If the ‘Force one line description on player layout’ option is enabled, the services names will fully adjust to the available width. The text size will be determined by the largest service name.

Tickets​

Set the tickets reset time, preferentially outside the location’s opening hours. This action will be performed every day.

Reset the tickets manually by clicking on the ‘Reset now’ button.

Calling sounds​

Enable the ‘Enable sound signal to notify staff members when a new ticket was generated for a service without waiting tickets’ option to warn users whenever a new visitor arrives.

Instead of using a sound signal to notify when a ticket is called, you can use voice calling. To set this feature:

  1. Enable the ‘Enable voice call’ option.
  2. Select the information you wish to include: the sound “ticket,” the ticket number (letters and number), and the sound “go to desk” followed by the counter number.
  3. Select the languages you wish to use to call the tickets, in the Language selection dropdown. You can select as many languages as you want, and the voice call will be reproduced those languages, by the order set on the dropdown.
  4. Save changes.

System > Translations​

Within this page it is possible to translate into several languages the contents available on the devices seen by the visitors. By adding frontoffice languages, you will be able to translate the part of the system used by the visitors to any language, even if it is not available in the system’s backoffice languages.

The available actions in this page include:

  • Add front office languages by clicking on the ‘Add language’ button, choosing the language, selecting the flag, and naming it;
  • Translate contents by clicking on the language’s ‘Edit’ button;
  • Delete languages by clicking on the ‘Delete’ button.

To help you identify the languages that require further translations, the system displays the percentage of translated contents, per language, in the languages list.

System > Integrations​

Bloom has integration tools to allow you to connect it to external applications. Each integration tool has a different configuration and requires information from the external application’s side.

Email​

This integration uses the system’s email integration configuration in System > Integrations page to allow communication via email (notifications and messages). In this page, you only need to set a different sender’s identification if you wish (email address and name).

SMS​

This integration uses the system’s SMS integration configuration in System > Integrations page to allow communication via SMS (notifications and messages). In this page, you only need to set a different sender’s identification if you wish (mobile number or name).

Virtual ticket settings​

If a virtual ticket mobile application is developed based on the REST API provided by Q-Better, it will be possible to enforce the following settings:

  • Search location within a radius of – sets the search area of the physical space, based on the visitor’s current geolocation, and locations within that area will be displayed in the application;
  • Do not allow to take a virtual ticket for services whose waiting time is lower than – sets a time limit for the virtual tickets generation: if the service to which the visitor wants the ticket has an average waiting time lower than the defined value, the ticket cannot be generated through the application;
  • Do not allow to take a virtual ticket for services whose number of waiting ticket is inferior to – sets a limit for the number of visitors waiting in the service queue: if the service the visitor wants has a number of ‘waiting visitors’ lower than the defined value, the ticket cannot be generated through the application.

Replication​

This feature allows to quickly replicate queueing configurations between resources.

For every resource you need to:

  1. Select the desired tab.
  2. Select the resource you want to replicate in the ‘1st What do you want to replicate?’ column. In the ‘Devices’ and ‘Translations’ tabs, you can only select one item at the time.
  3. In the ‘2nd From where?’ column, click on the ‘Expand’ button of the respective locations group to select the source location. In the ‘Devices’ tab you need to select the source device. In the ‘Translations’ tab you need to choose the translated contents you want to copy.
  4. In the ‘3rd To where?’ column, click on the ‘Expand’ button of the respective locations group to select the destination locations. In the ‘Devices’ tab you need to select the destination devices.
  5. Click on the ‘Apply’ button. You will receive a warning message with details about the replication - click on the ‘Apply’ button if you wish to proceed (this action cannot be undone).
  6. The replication is applied right after the process is completed. The local devices will automatically reboot if the replicated settings affect their functionality.
Information

The devices available in the ‘2nd From where?’ column depend on the content type selected in the ‘1st What do you want to replicate?’ column.
You can replicate the information to all locations in a locations group (by selecting the checkbox of the locations group), or to all locations in the system (by selecting the general ‘Select all’ button).
In the ‘Translations’ tab, the options are always available, even if there are no translated contents.

Data​

In this tab it is possible to replicate views and reports between locations:

  • Views whose additional filters (services, counters, users, questions, and/or devices) are all set to the ‘All selected’ option. This limitation removes possible empty views since the selected resources in the source location may not exist in the destination location;
  • Reports whose views have all the additional filters (services, counters, users, questions, and/or devices) set to the ‘All selected’ option. All views in the report need to respect this rule. The described limitation removes possible empty reports since the selected resources in the source location may not exist in the destination location.

Devices​

In this tab it is possible to replicate skins of all devices types and general devices settings between devices:

  • Skins – devices layout configurations organized per device type (player, ticket kiosk, Extender, Concierge, and E-Ticket);
  • Devices general settings – settings defined at the Location > Management > Devices > Settings page.

Communication​

In this tab it is possible to replicate notifications and messages between locations:

  • All notifications set at the Location > Notifications Settings page. After the replication, the notifications will be created in the destination location with an inactive status and without receivers.
  • All message settings set at the Location > Message Centre page. The messages will be configured in the destination location but kept inactive.

System​

All registered integrations details set at the Location > Integrations page will be copied to the destination location and the status of the integration will be changed to ‘Registered’.

Translations​

All languages and respective translations created at the Location > Translations page can be replicated between locations. Only the contents existing in both locations will be copied.