Parameter | Description |
Default name | Default name of the Unit. |
Description | Description of the Unit. |
Unit Identifiers | The two columns of the table are: • Name - Name of the unit, by default the name of the unit plus a sequential number, for example WebReception 5 or WebServicePoint 2. Can be changed to anything, so long as the name is unique, within the Branch. • Logic Id - An ID used in the connectors. The Logic Id continues with the next number in the sequence of the auto generated ID's within the Unit Type (e.g. Service Points, Entry Points, or Presentation Points). The number can be changed to anything, in the range of 1-9999, as long as it is unique within the Service Point, Entry Point, Presentation Point, or Device Controller. |
Unit id | Unique id of the unit |
Phone number field | Default is CUSTOMER:phoneMobile. The phone number will then be placed in the property phoneNumber which can be used in the SMS / Email message. |
Visit Call | If enabled, an SMS should be sent out when the Customer is called. Default disabled. |
Position A to be notified | Enter position A in the Queue when an SMS should be sent. Used together with Visit Call events and in combination with Position B to be notified, below. If you, for example, enter 10 here, and 5 in the field Position B to be notified (below), and a Visit enters the Queue at position 15, it will get the first SMS (A) when it reaches position 10 and the second SMS (B) when it reaches position 5, in the Queue.  Notifications will only be received when moving to lower positions in the Queue. In other words, if a Visit starts at position 8 and moves up to position 5, due to Visits in front being called, it will get a notification. However, if it is moved down to position 6 again, due to other Visits being transferred into the Queue, in front of the Visit, it will not get another notification. |
Position B to be notified. | Enter position B in the Queue when an SMS should be sent. Used together with Visit Call events and in combination with Position A to be notified, above. If you, for example, enter 5 here, and 10 in the field Position A to be notified (above), and a Visit enters the Queue at position 15, it will get the first SMS (A) when it reaches position 10 and the second SMS (B) when it reaches position 5, in the Queue. Notifications will only be received when moving to lower positions in the Queue. In other words, if a Visit starts at position 8 and moves up to position 5, due to Visits in front being called, it will get a notification. However, if it is moved down to position 6 again, due to other Visits being transferred into the Queue, in front of the Visit, it will not get another notification. |
Enable Visit Call Events for position A | Enable/disable events for when a Visit is called. Depending on Position A to be notified, above. |
Enable Visit Call Events for position B | Enable/disable events for when a Visit is called. Depending on Position B to be notified, above. |
Enable Visit Create Events | Enable/disable events for when a Visit is created. Enabled by default. |
Enable Visit End Events | Enable/disable events for when a Visit is ended. Enabled by default. |
Enable Arrival Events | Enable/disable events for when a customer arrives to a specified Queue or Service. |
Enable SLA Alerts | Enable/disable alerts for when the Service Level Agreement (SLA) is reached. |
SLA Alerts Time Interval | Time interval, in seconds, for checking for SLA Alerts |
Multiservice Notifications | Enable to send out a notification for each Service in a Multiservice Visit. Default disabled. |
Write data in QAgent log (debug) | Note that this may make the log file grow, use with caution! |