Today, Nimbus tells you whether a user is Ready or Not Ready to take a task. Not Ready Reason (NRR) adds the missing "why": a system-calculated reason shown next to that status, wherever it already appears in Nimbus.Â
🔎Not the same as Not Available Reason (NAR)
Not Ready Reason (NRR) and Not Available Reasons (NAR) sound alike but are unrelated features.Â
- NRR are automatically determined and shown by Nimbus, explained on this page.
- NAR are reasons manually selected by user. See the comparison table below.
Learn more…
INC NAR NRR Comparison
🔍 COMPARISON: Not Available Reason (NAR) vs. Not Ready Reason (NRR)
NAR and NRR may sound alike, but each answers different questions.Â
- NAR - Not Available Reason, are user-picked from a pre-defined list of Not Available Reasons (NAR).
- NRR - Not Ready Reason, is automatically determined by Nimbus for the user, based on their User State.
- Tenant Admins can configure if these reasons are tracked in Nimbus reporting, or be exposed to the Nimbus UI.
Learn more…
| Criteria | Not Available Reason (NAR) | Not Ready Reason (NRR) |
|---|---|---|
| Trigger Point | The user manually picks a reason in the Nimbus Assistant app when their Microsoft Teams presence changes to Away, Busy, or Do Not Disturb (after a period of inactivity or manual presence change in MS Teams). | Nimbus calculates the reason automatically whenever a user's presence, duty state, or task activity makes them Not Ready. No action from the user is required. |
| When to Use | Used to capture a business reason for a user's non-availability (for example "In a meeting" or "On a break") for later reporting. | Always on once enabled. Use it to see, at a glance, why Nimbus considers a user Not Ready, without waiting on the user to respond. |
| Where Shown in UI |
đź’ˇNot Available Reasons (NAR) provided and assigned per user. Shown by default in Nimbus Assistant UI prompts. âś… Optional Admin setting: Can also be surfaced with the Tenant Data Privacy Setting > "Display Not Available Reasons on Tooltips" ⮑ When enabled:Â
|
đź’ˇNot shown by default.. Automatically generated and shown once enabled.  ✅ Optional Admin setting: Can be surfaced with the Tenant Data Privacy Setting > "Display Not Ready Reasons on Tooltips" ⮑ When enabled:Â
|
| Tracked in Reporting |
✅Optional: Only if Tenant Data Privacy Setting > "Persist User States in Reporting" is enabled. ⮑ When enabled: In historical Nimbus Reporting as part of the Nimbus Reporting Model > Slowly Changing Dimensions > |
✅Optional: Only if Tenant Data Privacy Setting > "Persist User States in Reporting" is enabled. ⮑ When enabled: In historical Nimbus Reporting as part of the Nimbus Reporting Model > Slowly Changing Dimensions > |
âś… Preconditions
đź’ˇ Good to know: Users don't configure anything for NRR. Once enabled by a Tenant Administrator, they will be available for all users as Tooltips in the Nimbus Portal (widgets, headers, avatars).
Data Privacy and User Configuration:
- To enable the feature, head to Data Privacy Tenant Settings and turns on "Display Not Ready Reasons on Tooltips" to show the reason in tooltips.
- To also keep a historic record of Not Ready Reasons in reporting, enable "Persist User States in Reporting" in the same section. See the Nimbus Reporting Model.
Not Ready Reason in the Nimbus UI
You will see Not Ready Reasons in the Nimbus UI
 |
 |
- Status tooltip: hovering a user's Not Ready status (My Overview, My Sessions, Attendant Console, Services Overview, Live View) shows the calculated reason.
- Nimbus Assistant: the same reason appears in the Assistant banner tooltip (on hover) for the signed-in user.
- Dashboards: an optional Not Ready Reason column is available on the User State Tabular and User Supervisor Tabular widgets. See Dashboard Widget Properties.
- Services Overview and Live View: per-service if there is a specific user in a service reason – or the overarching user NRR if the entire user is Not Ready.
How It Works
Whenever Nimbus considers a user Not Ready for new tasks, it calculates one specific reason from three categories: the user's Microsoft Teams presence, their duty (Responsibility Profile) or service enablement, or current task activity and capacity. Only one reason is shown at a time.
| Category | Reason (as shown) | What It Means |
|---|---|---|
| MS Teams Presence | Presence - Unknown | Nimbus could not determine the user's Microsoft Teams presence. |
| Presence - Offline | The user is signed out of Microsoft Teams. | |
| Presence - Appear Offline |
The user has manually set their Teams presence to Appear Offline. đź’ˇ Only applies when the Admin enabled Emergency Manual Presence Mode in the Extensions Tenant Settings. |
|
| Presence - Away | The user's Teams presence is Away and Distribution Service Settings > “Conversation Distribution” is set to “Not distributed”, which makes the user overall not ready. | |
| Presence - Be Right Back | The user's Teams presence is Be Right Back and Distribution Service Settings > “Conversation Distribution” is set to “Not distributed”, which makes the user overall not ready. | |
| Presence - Busy | The user's Teams presence is Busy and Distribution Service Settings > “Conversation Distribution” is set to “Not distributed”, which makes the user overall not ready. | |
| Presence - Busy in a Call | Teams has detected the user is in an active call and Distribution Service Settings > “Conversation Distribution” is set to “Not distributed”, which makes the user overall not ready. | |
| Presence - Busy in a Meeting | Teams has detected the user is in an active meeting and Distribution Service Settings > “Conversation Distribution” is set to “Not distributed”, which makes the user overall not ready. | |
| Presence - Do Not Disturb | The user's Teams presence is Do Not Disturb. | |
| Duty / Service Enabled state | Off Duty | The user is in an “Off Duty” Responsibility Profile |
| Off Duty and Inactive | The user is Off Duty and disabled in all MS-Teams based User MS-Teams based Assignment Services | |
| Inactive | The user is disabled in all MS-Teams based User MS-Teams based Assignment Services | |
| Tasks and Capacity | On a Task | The user is currently handling a Nimbus task. |
| On a Task (Blocking) |
đź’ˇWith Task Parallelization enabled on the user. The user's current task is preventing them from taking on additional tasks. |
|
| In RONA | The user missed a call or task and Nimbus temporarily set them Not Ready (RONA). | |
| In ACW | The user is in the ACW period following a task. | |
| In Extended ACW | The user is in the Extended ACW period following a task. | |
| At Task Limit | The user has reached their configured task capacity and cannot take on more tasks right now. |
🔎 “Not Ready Reason” on Service Level
Take Note: Some settings make a user Not Ready for one service while they remain Ready for another. Not Ready Reason on Service Level show this on a per-service basis, in the tooltips of the Services Overview and Live View. Individual “Readiness” is defined via the Service's Distribution Service Settings and is not persisted to reporting.
| Reason (as shown) | What It Means |
|---|---|
| Not Distributed - Away | This service treats the user's Teams Away presence as Not Ready, even though the user may be Ready for other services. |
| Not Distributed - Busy | This service treats the user's Teams Busy presence as Not Ready. |
| Not Distributed - In a Call | This service treats an active Teams call as Not Ready. |
| Not Distributed - In a Meeting | This service treats an active Teams meeting as Not Ready. |
INC NAR NRR Comparison
🔍 COMPARISON: Not Available Reason (NAR) vs. Not Ready Reason (NRR)
NAR and NRR may sound alike, but each answers different questions.Â
- NAR - Not Available Reason, are user-picked from a pre-defined list of Not Available Reasons (NAR).
- NRR - Not Ready Reason, is automatically determined by Nimbus for the user, based on their User State.
- Tenant Admins can configure if these reasons are tracked in Nimbus reporting, or be exposed to the Nimbus UI.
Learn more…
| Criteria | Not Available Reason (NAR) | Not Ready Reason (NRR) |
|---|---|---|
| Trigger Point | The user manually picks a reason in the Nimbus Assistant app when their Microsoft Teams presence changes to Away, Busy, or Do Not Disturb (after a period of inactivity or manual presence change in MS Teams). | Nimbus calculates the reason automatically whenever a user's presence, duty state, or task activity makes them Not Ready. No action from the user is required. |
| When to Use | Used to capture a business reason for a user's non-availability (for example "In a meeting" or "On a break") for later reporting. | Always on once enabled. Use it to see, at a glance, why Nimbus considers a user Not Ready, without waiting on the user to respond. |
| Where Shown in UI |
đź’ˇNot Available Reasons (NAR) provided and assigned per user. Shown by default in Nimbus Assistant UI prompts. âś… Optional Admin setting: Can also be surfaced with the Tenant Data Privacy Setting > "Display Not Available Reasons on Tooltips" ⮑ When enabled:Â
|
đź’ˇNot shown by default.. Automatically generated and shown once enabled.  ✅ Optional Admin setting: Can be surfaced with the Tenant Data Privacy Setting > "Display Not Ready Reasons on Tooltips" ⮑ When enabled:Â
|
| Tracked in Reporting |
✅Optional: Only if Tenant Data Privacy Setting > "Persist User States in Reporting" is enabled. ⮑ When enabled: In historical Nimbus Reporting as part of the Nimbus Reporting Model > Slowly Changing Dimensions > |
✅Optional: Only if Tenant Data Privacy Setting > "Persist User States in Reporting" is enabled. ⮑ When enabled: In historical Nimbus Reporting as part of the Nimbus Reporting Model > Slowly Changing Dimensions > |