Magidoc

RoutingGroup
Object

Thanks to the routing groups, you can organise your teams in a flexible way by grouping your agents according to their role (agent, supervisor or administrator), group (i.e: contact centre) or skills (i.e: mobile, photography). A routing group is given a name and a set of segments defining which agents to include in the group.

Fields

#

id

UUID !
Non-null

The identifier of the group.

name

String !
Non-null

The name given to the group.

segments

[ RoutingSegment !]!
Non-null

The list of segments defining which agents are included in the group.

createdAt

DateTime !
Non-null

The date and time when the group was created.

updatedAt

DateTime !
Non-null

The date and time when the group was last updated.

websiteId

LegacyId !
Non-null

Identifies the website to which the routing group is attached. The routing group may only be used by routing rules attached to the same website and appears in report charts of this website only.

This field is now deprecated. This means that iAdvize now considers that this field should not be used and you should migrate any usage of that field. iAdvize will only maintain this field up until the 2025-04-07.

userCount

Int

Number of agents assigned to the routing group.

project

Project

Project of the routing group.

userIds

[ Int !]

The identifiers of the agents currently matching all segments of the group.

users

UserConnection

Agents assigned to the routing group.

Usages

#

References

#

  • Field routingGroup from Query