Availability-based Routing
| Description |
Allows to route the call based on overall Service availability, considering MS Teams Presence – and in extension the Nimbus User State of all relevant Service Users.  |
||||||
| Required Predecessor | None - can work even without accepting a call (e.g. to check ahead, then Accept, Transfer or Disconnect immediately) | ||||||
| License |
|
||||||
| Modalities | Audio / Video | Instant Messaging | External Task | ||||
Common Properties
| Configurable Properties | Description |
|---|---|
| Service | Allows to select the target Service (within your tenant) for which the availability check and routing is performed for. 💡Usage notes:
|
|
Current Availability (Exit conditions) |
The activity has 3 exits based on the current overall team status (look-ahead). The availability depends on the User assignment type of your Service. 🤔 How can I determine the User Assignment Type?Team owners can access Distribution Service Settings and inspect the "User Assignment Type". |
Audio / Video
|
Current Availability (Exit conditions) |
Precondition: Task Parallelization is enabled for at least 1 user in the Service. With preconditions met, the Service availability changes as follows:
|
|||||||||
Instant Messaging
|
Current Availability (Exit conditions) |
Precondition: Task Parallelization is enabled for at least 1 user in the Service. With preconditions met, the Service availability changes as follows:
|
||||||
|
Current Availability (Exit conditions) |
Precondition: Task Parallelization is enabled for at least 1 user in the Service. With preconditions met, the Service availability changes as follows:
|
||||||
External Task
|
Current Availability (Exit conditions) |
Precondition: Task Parallelization is enabled for at least 1 user in the Service. With preconditions met, the Service availability changes as follows:
|
||||||