| Availability, as signaled in Nimbus | … for MS Teams-based services | … for skill-based Services |
|---|---|---|
| No One Available | All users are inactive in Nimbus – or active in but "offline" in MS Teams. |
No users are online in MS Teams or available within the Service's Distribution Policy requirement.
|
| In Time Available | All active users are not available “in time”, e.g. "DND/Away/Busy" or handling another Nimbus task. | No users in the 1st Distribution Policy level are available, but User in the following distribution levels are available or become available “in time”, e.g. “DND/Away/Busy" or handling another Nimbus task. |
| Directly Available | At least 1 user is available (MS Teams presence set "available") and also set to "Active" in Nimbus. |
At least one user in the 1st Distribution Policy is available and ready to take a task.
|
| 🔍Design Notes | … for MS Teams-based services | … for skill-based Services |
| Nimbus UI controls | The "Active" toggle in the Nimbus UI determines user participation per service (team).  In addition to the “Active” toggle, MS Teams presence-related settings also affect availability. → See note below. |
The Duty States selector determines participation for all skill-based services simultaneously.  In addition to the “Active” toggle, MS Teams presence-related settings also affect availability. → See note below. |
| MS Teams presence-related service settings |
You can adjust Distribution Service Settings to include / exclude users from the availability count, based on their MS Teams presence.  🔍Visit User States for a full explanation on how MS-Teams presence relates to other Nimbus task-distribution factors. |
|
Table of Contents