Not Available Reasons

Not Available Reasons (or N/A Reasons, NAR) are reasons that a user must specify after becoming idle, either through inactivity or by manually selecting a User States that Nimbus considers as "Not Available" (Away, Busy, DND). The reasoning must be provided via the Assistant app UI and is stored for Power BI as part of the Nimbus Reporting Model.

The Assistant UI, requesting and showing reason for each N/A phase.



Data Privacy and User Configuration: 

GDPR As this Nimbus Feature concerns user privacy, the feature needs to be enabled by a Tenant Administrator first.

  1. Head to Tenant Administratiion > "Data Privacy" section and enable "Persist User States in Reporting". 
    ⮑ Note that enabling this will allow Nimbus to keep a historic track record of User States in the Nimbus Reporting Model.
  2. Within Admin > Configuration locate the now enabled Not Available Reasonsentry. Further steps are explained below.

Creating N/A Reasons

  1. Log in to the Admin Portal with any Administrator Role with access to the configuration
  2. Head to Configuration > Not Available Reasons
  3. Create or Edit any of the existing Not Available Reasons.
  4. Define a Name for the reason.
    💡 This is also how it will appear for the users of Nimbus in other menus.
  5. Set an Organization Unit.
    💡 Note that you can change the visibility of these reasons. Users will still get to select the reason until it is removed from their account in the User Administration. → See next step.
Creation of N/A Reasons in the Administration Backend

Applying N/A Reason to Users

  1. In Admin Portal, head to the User Administration
  2. Select the user you want to edit. ✅ Reminder: Ensure that the user has a Contact Center license so the N/A Reasons tab is shown.
  3. Select the N/A Reasons tab.
  4. Enable “Not Available Reasons”
  5. Click "+Add" and provide at least one (or multiple) N/A reasons for the user to pick from.  
    💡 You can re-order the entries via drag&drop to make sure the most important reasons are on top.
Application of N/A Reasons to a User

Usage of N/A Reasons

Once assigned to a user N/A reasons can be provided when using Assistant as soon as a user went into a User presence state status that Nimbus considers as “non-selectable" such as:

  • DND
  • MS Teams "Busy in a call"
  • Busy (see notes) 
  • Away (see notes)
  • A user can be considered as available when "Calls will be distributed to the User" is enabled within the Distribution Service Settings > Conversations Distribution section of the respective services. In such cases, no N/A will be shown.
  • Vice-versa this also means that N/A reasons could be needed for Service A during "Away", while Service B considers the user available during "Away".
  • Reasons can be provided retroactively, meaning that users can change their MS Teams presence multiple times and provide each "Not Available Reason" later by using the Assistant UI.


GDPR Power BI tracking of User States includes both N/A reasons and the duration of unavailability. A reason period will start from the point a user changes to not available state until being either:

  • ... back in an "Available" state.
  • ... opting into an "Off Duty" State by selecting an according Responsibility Profile .
  • ... going offline in MS Teams.

Table of Contents