GenAction54

AddQueueMember

Description (v1.2)

This action adds a device to a specific queue.

The queue [Queue] will accept calls

for device [Device] (if the device is unspecified, it is the calling device which will be added in the queue).

The device is added with a penalty of [Penalty] in the queue.

Release notes

Show release notes

Version 1.2 - General deployment

Improvement: Compatibility with the Communication Server module.

Version 1.01 - General deployment

Improvement: penalty parameter is now a dropdown & custom value field

Version 1.00 - General deployment

Initial version

Action parameters

When this action is played inside a callflow, either the calling device or the specified device is added to the specific queue.

Queue: The queue to which the device will be added.
Device: The device which will be added to the queue. If the device is unspecified, the calling device will be added in the queue, which is the most commonly used option.
Penalty: The device is added in the queue with a specific penalty.

Example of use

Queue members can be defined as having a penalty, example:

SDC20001; penalty 1
SDC20002; penalty 2
SDC20003; penalty 3
SDC20004; penalty 2

If the strategy is defined as 'ringall' (which is defined in the queue resource), then only those available members with the lowest penalties will ring. In the example above, if SDC20001 is not busy, then only SDC20001 will ring. If SDC20001 is busy, then only SDC20002 and SDC20004 will ring. If SDC20001, SDC20002 and SDC20004 are busy, then SDC20003 will ring.

Note: If extension SDC20001 does not pick up it will not automatically go to device SDC20002 and SDC20004. It will keep ringing SDC20001 until they pick up. It will only go to the next queue member if the current queue member is either busy or unavailable.