DOCSEARCHbyAlgolia
Submit Docs

Q-net Pro V7 Documentation

website·Indexed 31 days ago

https://docs.q-net.com/pro7/

Documentation for the Q-net Pro V7 queue management and customer calling system. Includes guides on system architecture, user authentication, network requirements, and the configuration of hardware devices such as ticket dispensers, calling units, sound players, and feedback devices. Covers administrative features including statistics reports, live monitoring maps, smart ticket reservations, and CRM integrations.

Tokens
91.6K
Snippets
40
Records
828
Agent score
47%

What's inside Q-net

  1. Overview of Q-net v7 Central Server Architecture

    The Q-net v7 central server architecture is designed for simplicity in installation and maintenance. It uses a single installer that includes a built-in web server and an internal ElasticSearch database, running on Windows or Linux. All user interfaces are web-based and accessible via WebSocket. Non-network devices (printers, displays) are managed by a 'Device controller' service running locally at branches, which also communicates with the central server via WebSocket.

  2. Overview of the Workflow Editor

    The Workflow Editor allows developers and administrators to build operational processes and the user interface for ticket dispensers visually. It replaces traditional structures with pages and dialogs (e.g., service selection, information, forms, and confirmation pages). The editor supports variables to store user input from form pages and reuse them on subsequent pages or during ticket printing. To use this feature, the SH87 Workflow editor module must be purchased.

  3. Overview of the Smart Ticket feature

    The Smart Ticket feature provides a customer-facing page (accessible via QR code or URL) that enables users to:

    • Request a ticket
    • Track ticket status
    • Provide feedback
    • Perform reservation and appointment booking (if enabled)

    Administrators can manage the public URLs used to access this page. There are two primary types of URLs:

    • Dynamic URL: Valid for a limited time.
    • Static URL: Intended for permanent use, such as printing on physical materials.
    • Reservation URL: A separate URL provided specifically when reservation features are enabled.

  4. Overview of Advertisement features for ticket and feedback devices

    Advertisements can be displayed on ticket dispensers, feedback devices, and smart tickets (acting as billboards during idle time) or printed on tickets. Advertisements support text, pictures, videos, or live content from external feeds/web services. They are organized into advertisement groups, which are then associated with dispenser profiles, feedback profiles, or ticket layouts. To activate ads, they must be enabled in the profile and the corresponding advertisement group must be selected.

  5. Overview of Q-net 7 Web-based Display Solutions

    The Q-net 7 system supports several web-based display types for different operational needs:

    • SH76 Media Player: A digital signage solution for waiting areas that displays summarized calling information and media content/ads. Content is customized via the Media Storage and Media Profile Editor.
    • SH79 Counter Display: A digital signage solution specifically for counter displays, showing calls for a dedicated counter only.
    • SH69 HTML Waiting Area Display: A simplified waiting area display that does not support video, RSS, or webpage content.
    • SH62 3rd Party Digital Signage: Integration of 3rd party software that receives calling information from the Q-net server while streaming its own signage content.

  6. Overview of Q-net 7 Web-based Display Solutions

    Q-net 7 supports several web-based display types depending on the use case:

    • SH76 Media Player: A digital signage solution for waiting areas. Displays summarized calling information and media/ads. Content is customized via 'Media storage' and 'Media profile Editor'.
    • SH79 Counter Display: A digital signage solution specifically for counter displays, showing calls for a dedicated counter only.
    • SH69 HTML Waiting Area Display: A simplified waiting area display that does not support video, RSS, or webpage content.
    • SH62 3rd Party Digital Signage: Integration of 3rd party software that receives calling information from the Q-net server while streaming its own signage content.

  7. Overview of Q-net Pro 7 Device Pairing

    Pairing is a feature in Q-net Pro 7 used to add devices to a server's management. Supported devices include ticket dispensers, feedback devices, hardware counters (GD08), and media players (including Android devices). When a device starts up, it displays a pairing code on the loading screen. The pairing process automatically creates a server-side entry and configures the device with the necessary address and port communication settings.

  8. Overview of the Workflow Editor

    The Workflow Editor allows the creation of ticket dispenser operational processes and user interfaces visually without programming. It replaces traditional structures with pages (e.g., service selection, information, forms, confirmation) and dialogs. Key capabilities include defining navigation between pages, using variables to store and reuse input field values (even during ticket printing), and full customization of the dispenser interface. Note: This feature requires the SH87 Workflow editor module.

  10. Understand the Q-net Pro v7 Admin welcome screen

    The welcome screen (accessible via the 'Overview' menu item) displays high-level system information, including the number of configured branches, services, users, and devices, as well as a list of connected but unconfigured devices and a log of recent configuration changes.

  11. Configure automated appointment cancellation notifications

    When an administrator deletes a reservation via the Call Center page, or a clerk deletes one via a calling unit, the system automatically sends an email and/or SMS notification to the customer including the reason for the deletion.

  12. Understand Device Controller roles and functions

    Device controllers manage communications for all configurable and non-configurable devices within a system. Every installed system includes one internal device controller by default.

    Key functions provided by the Device Controller include:

    • Ping: Verifies if a device is online and reachable on the network.
    • Start scan: Discovers applicable devices, SD20 communication boxes, and printers on the network.
    • Stop scan: Cancels an active network scan.