Skip to main content

Integrations

The integration compatibilities make possible to extend the capabilities of the queue management and customer calling system, or connecting to external systems (CRM, databases, authentication, etc.)

CRM​

  • Useful in case of identifying the customers via an external CRM system (examples: raising priority, providing VIP services, displaying customer data to the clerks, etc.)
  • The process is being called upon ticket printing, based on the unique ID provided by the customer (customer number, quotation number, card number, phone number, etc.)
  • Ten different customer data field (can be named)

CRM ID

REST​

  • Used to call HTTP REST API
  • The result of the JSON query can be mapped

RestCRM

SQL​

  • Used to query an SQL database
  • The result of the query can be mapped to custom values

SQLCRM

Rules Call REST​

  • Certain ticket events can trigger custom external REST API calls (i.e: upon ticket printing, calling, closing, too much waiting time, etc.) Read more about the rules here:
  • The parameters can be passed from the ticket events and data

RulesCRM

Rules JS​

  • Certain ticket events can trigger custom JavaScript codes to be executed (i.e: after ticket printing, redirecting tickets to clerks, putting tickets to waiting list, etc.)
  • The system's internal objects are accessible
  • Not documented, the custom JS scripts are developed by Q-net