New Design for Attendant Console
This page describes both Attendant Console 1.0 and the new 2.0 redesign.
đĄ Note that Attendant Console 1.0 will be phased out in summer 2025. Once you switch to Attendant Console 2.0 in Attendant Settings, the switch is removed and it will no longer be possible to switch back to the old design.

đĄ Note: For more recently onboarded Nimbus customers, this choice might be disabled and you will be using the 2.0 design by default.
Permission Requirements for Search and Filter
Attendant Console 2.0 - Permissions
Attendant Console relies on User Permission consent to access company-internal user directories for search and filter.
â To use extended search, permissions on the Contact search must be granted both by you and your Tenant administrator, each using their User Permission dialog.
â Without any consent, the search will only cover Nimbus internal Address Books which are kept in the Administration backend.
 | Out of the Box | User Permissions granted | Admin Permissions granted |
---|---|---|---|
Free Text Search | Address Books only |
O365Â Outlook Nimbus Services |
O365Â Outlook Nimbus Services |
Filters | Address Books fields only |
Outlook Nimbus Services |
O365Â Outlook Nimbus Services |
Contact Groups | - | Available | Available |
Organization Tab | - | Shows only yourself and manager | Organization tab in the side panel, including manager and peers. |
Primary Contact Information | - |
Primary telephone number   Primary email address |
Contact cards now show all available fields. |
Secondary Contact Information | - | - | Contact cards now show all available fields. |
Example in the UI | - | - | Contact cards now show all available fields. |
đ€ How can I check if access is granted?
You can directly check in the search field which search directories are currently available.

đĄAttendant Console will automatically check and ask for missing or revoked permissions. If you think your search results are not comprehensive, you can always check the status icon, visit your User Preferences (Portal) > Permissions tab and consult your local Nimbus Administrator if problems arise.
đ€Â Which search directories are covered?
- The O365 / AD User Directory of your company.
- Microsoft Outlook / Exchange Server contacts (e.g. "People" in Outlook).
- Nimbus Address Books - managed by your service administrator via their Organization Units placement.
- Nimbus Services only show team members when the Team Visibility in the Tenant Administration is set accordingly. Otherwise you may not see any team details or only those of your own services.
â Depending on which sources are delivering results for your search terms, duplicate entries of the same contact may appear.
- Attendant Console will show a âSourceâ icon to indicate where the search / filter result came from.
- Your Tenant administrator can prefilter results by following Use Case - Filtering Attendant contact search via MS Graph.
- As Address Books may be limited by Organization Unit barriers, you can also implement shared lists by following our Use Case - Adding External Address Books via Power Automate.
Attendant Console 2.0
Getting started: Video Tutorial
We have created a series of short intro videos to highlight and explain the different areas and new UI designs of Attendant Console 2.0.
Attendant Console 2.0
Attendant Console 2.0 (AC2) is a complete rework of our previous Attendant Console (AC1). The goal was to completely streamline the experience without sacrificing any known features. While using AC2 you can expect the following features:Â
- A modern design, improved based on our most frequent Customer feedback.
- More information at a glance, featuring a new side panel with rich context information.
- A fresh look and User experience that shows its Attendant roots but puts more focus on the task at hand, changing dynamically during Customer interactions.
How to get started
â Attendant Console 2.0 needs to be enabled in your Nimbus Extensions Tenant Settings > Attendant Console before being available for selection.Â
â As a Tenant Administrator, you can activate Attendant Console 2.0 for all Users by clicking âOverwrite for all Usersâ in Extensions Tenant Settings.Â
âź Once the option is enabled on your tenant, individual Nimbus Users each can opt in to the experience by their Attendant Console Settings and check the âUse new Attendant Console Designâ option.
â The new design will become active immediately as the new default, starting with the next website refresh. Moving forward into Summer 2025 the new AC2 design will be the default for all Users, so the Switch toggle may not be available on your instance anymore.

Small Glossary
To better convey the Nimbus interaction scenarios within Attendant Console, we need to establish the following terms:
Term | Meaning |
---|---|
Contact | A searchable entry in the Attendant Console UI. Most-likely a company colleague, peer and/or Nimbus User. |
Consultation |
The process of the Nimbus / Attendant User consulting a Contact during an ongoing Customer interaction. The User usually swaps between both participants or escalates into a  Conference. |
Conference | The process of combining the call between User, Contact, and Customer into a call with all participants being able to talk to each other. |
Customer | A person reaching out for a Nimbus Service, thus creating a Task in Nimbus. May be understood synonymous with âCaller" or âClientâ. |
Task |
Tasks are handled via the Attendant queue. Shown as clickable âTask Cardsâ. Tasks can be of different modality (e.g. Email , Instant Messaging, Audio/Video, or an External Task with no necessary Customer interaction). |
User | The Attendant Console User, e.g. a Receptionist or Agent. Can refer to any âNimbusâ user as well. |
Overview
The new Attendant Console design consists of the following elements:Â
Header |
The header steers and displays your Service participation.  â Precondition: You need to be member of at least one Nimbus Service. The header will show:
đGood to know:
|
||||||||||||
Queue |
The queue lists incoming tasks as single task cards, combined for all your Services. Â â Precondition: Â In the header, you can directly impact your queue via the "On/Off" active toggle for the respective Service. You can only take tasks:
đGood to know:
|
||||||||||||
Active Session |
The core area for your Customer interaction. Whenever you accept a task from the queue, it will appear here as a task card within your active sessions widget. ![]() On active task cards you have the following call controls:
 |
||||||||||||
Contacts Search / Groups  đ More details in the Contact Search chapters below |
The Contact search is your primary area to work with while handling calls. It allows the following actions:
đĄNote that you can create max. 10 Contact groups and add up to 50 Contacts per Contact group. đ€Why are certain actions greyed out? This list is updated based on:
|
||||||||||||
Contact Side Panel  đ More details in the Side Panel chapter below |
Lists additional information, User fields, and context sensitive actions for your currently selected card (either task, Service, or a Contact). |
Contact Search
The Contact search lists, groups and filters Users during ongoing conversations. By default, the Contact search and list is empty and shows entries as you start typing.
Precondition: Granting Search Permissions
Attendant Console 2.0 - Permissions
Attendant Console relies on User Permission consent to access company-internal user directories for search and filter.
â To use extended search, permissions on the Contact search must be granted both by you and your Tenant administrator, each using their User Permission dialog.
â Without any consent, the search will only cover Nimbus internal Address Books which are kept in the Administration backend.
 | Out of the Box | User Permissions granted | Admin Permissions granted |
---|---|---|---|
Free Text Search | Address Books only |
O365Â Outlook Nimbus Services |
O365Â Outlook Nimbus Services |
Filters | Address Books fields only |
Outlook Nimbus Services |
O365Â Outlook Nimbus Services |
Contact Groups | - | Available | Available |
Organization Tab | - | Shows only yourself and manager | Organization tab in the side panel, including manager and peers. |
Primary Contact Information | - |
Primary telephone number   Primary email address |
Contact cards now show all available fields. |
Secondary Contact Information | - | - | Contact cards now show all available fields. |
Example in the UI | - | - | Contact cards now show all available fields. |
đ€ How can I check if access is granted?
You can directly check in the search field which search directories are currently available.

đĄAttendant Console will automatically check and ask for missing or revoked permissions. If you think your search results are not comprehensive, you can always check the status icon, visit your User Preferences (Portal) > Permissions tab and consult your local Nimbus Administrator if problems arise.
đ€Â Which search directories are covered?
- The O365 / AD User Directory of your company.
- Microsoft Outlook / Exchange Server contacts (e.g. "People" in Outlook).
- Nimbus Address Books - managed by your service administrator via their Organization Units placement.
- Nimbus Services only show team members when the Team Visibility in the Tenant Administration is set accordingly. Otherwise you may not see any team details or only those of your own services.
â Depending on which sources are delivering results for your search terms, duplicate entries of the same contact may appear.
- Attendant Console will show a âSourceâ icon to indicate where the search / filter result came from.
- Your Tenant administrator can prefilter results by following Use Case - Filtering Attendant contact search via MS Graph.
- As Address Books may be limited by Organization Unit barriers, you can also implement shared lists by following our Use Case - Adding External Address Books via Power Automate.
đ€ Which fields are covered by the search?
đĄNote: At any time, Nimbus & Attendant Console can only read Contact details from directories, not edit them. If you discover missing fields or false details in the search, Contact your local IT administrator.
INC Supported User Search Fields
Supported fields for Attendant Console 1.0 (AC1)
Prerequisites: User.Read.All permissions must be granted to use search features. As a Tenant Admin, head to the Nimbus Portal > User Preferences (Portal) > Permissions> Advanced Search and manage consent for your entire tenant. â Also see Nimbus User Permissions for more details.
Legend
â
Fields are supported by search.
đ Fields support "CONTAINS" search operator.
Example: Searching for 'cha' will find 'Chadrick' but also 'Michael'
Â
â These fields support filter capabilities which can be used to narrow down a search.
â KNOWN LIMITATIONS:Â
- The search covers the predefined Nimbus Address Books fields, but no custom fields can be searched.
- Filters need to be part of the search syntax. You can switch to Attendant Console 2.0 for a much-improved filtering experience.
 Attendant Console 1.0 (AC1) supported search fields table:
Searchable Field | O365 Directory |
Outlook Address Book | Nimbus Address Books |
Nimbus Services | Notes |
---|---|---|---|---|---|
Display Name | â Â | â đ | â đ | Â | First name / Last name combination |
First Name | â Â | Â | â đ | Â | First name |
Last Name | Â | Â | â đ | Â | Last / Family name |
Initials | Â | Â | â đ | Â | Initials (e.g. "JK") |
Surname | â Â | Â | Â | Â | Surname |
â Â | â | â đ | Â | Email Address | |
User Principal Name (UPN) | â  |  | â đ |  | Consists of: user name (login name), separator (the @ symbol), and domain name (UPN suffix) |
Job Title | â â â | â đ â â | â đ â |  | Job Title |
Business Phones | Â | Â | â đ | Â | Business Phone |
Home Phones |  |  | â đ |  | Home Phone |
Mobile Phones | Â | Â | â đ | Â | Mobile Phone |
IM Address | Â | Â | â đ | Â | IM SIP Address |
Street | â | Â | â đâ | Â | Street Address |
City | â â â |  | â đ |  | Code and City |
Company |  | â â â | â đ |  | Company |
Country | â â â | Â | â đ â | Â | Country of Origin |
Department | â â â | â â â | â đ â | Â | Department |
State | â â â | Â | â đ â | Â | State |
Postal Code | â | Â | â đâ | Â | Postal Code |
External.CustomField1-10 | Â | Â | â đ | Â | Custom Field |
Supported fields / filters for Attendant Console 2.0 (AC2)
Attendant Console 2.0 (AC2) supported search fields and filters tables:
INC Supported Search Fields and Filters (AC2.0)
Free Text Search
Prerequisites: The full search functionality only applies if permissions are granted. See Attendant Console 2.0 - Permissions.
Legend
â
Fields are supported by Free Text Search
âLimited by "starts with" logic
âïžNeeds at least 3 characters to start searching
Search within | "All" Tab |
Configured Groups |
||||
---|---|---|---|---|---|---|
Fields |
O365 Directory |
Outlook Address Book |
Nimbus Address Books |
Nimbus Services |
Nimbus Address Books |
All Sources |
Display Name |
â
ââïž |
â
ââïž |
â
âïž |
â
âïž |
â
|
â
|
Contact Details |
â
ââïž |
â
ââïž |
â
âïž |
â
âïž |
â
|
â
|
Note |
 |
 |
â
âïž |
 |
â
|
â
|
First Name | Â | Â | â
âïž |
 | â
|
 |
Last Name | Â | Â | â
âïž |
 | â
|
 |
UPN (User Principal Name) | Â | Â | â
âïž |
 | â
|
 |
 |  | â
âïž |
 | â
|
 | |
IM Address | Â | Â | â
âïž |
 | â
|
 |
Business Phone | Â | Â | â
âïž |
 | â
|
 |
Mobile Phone | Â | Â | â
âïž |
 | â
|
 |
Home Phone | Â | Â | â
âïž |
 | â
|
 |
Company | Â | Â | â
âïž |
 | â
|
 |
Department | Â | Â | â
âïž |
 | â
|
 |
Job Title | Â | Â | â
âïž |
 | â
|
 |
Country | Â | Â | â
âïž |
 | â
|
 |
State | Â | Â | â
âïž |
 | â
|
 |
City | Â | Â | â
âïž |
 | â
|
 |
Postal Code | Â | Â | â
âïž |
 | â
|
 |
Street Address | Â | Â | â
âïž |
 | â
|
 |
External Custom Field 1-10 | Â | Â | â
âïž |
 | â
|
 |
Filters
Note: Filters only work if this field is actually used for the contact.
Search within | "All" Tab |
Configured Groups |
|||
---|---|---|---|---|---|
Fields |
O365 Directory |
Outlook Address Book |
Nimbus Address Books |
Nimbus Services | All Sources |
City |
â
â |
 | â
|
â
â |
â
|
Company |
 | â
â |
â
|
 |
â
|
Country |
â
â |
 | â
|
â
â |
â
|
Department |
â
â |
â
â |
â
|
â
â |
â
|
Initials |
 |  | â
|
 | â
|
Job Title |
â
â |
â
â |
â
|
â
â |
â
|
Postal Code |
â
â |
 | â
|
â
â |
â
|
State |
â
â |
 | â
|
â
â |
â
|
Street Address |
â
â |
 | â
|
â
â |
â
|
Note |
â
|
â
|
â
|
â
|
â
|
Search Concepts
Use the following tabs to learn more about the different aspects of the search in AC2.
âAllâ Search
Search All
Via Search field within the âContactsâ you can search Contacts at any time - during or outside an ongoing Nimbus tasks. Search results are narrowed down as you type.Â
By using Filtering or Grouping, you can already start with narrowed-down Contact lists, e.g. your most used transfer destinations, Nimbus Services, or people from specific departments.

Using the "All" Search you can search for:
- Contacts: The default option.Â
- Notes: If notes were defined for a Contact, you can search for note contents.
-
PSTN numbers / SIP addresses: You can also enter unknown PSTN numbers or enter a valid SIP address.
âCall actions may be limited in this case, as the target cannot be resolved by Nimbus (e.g. unknown phone license or modality support). - Nimbus Services: You can search Services as single entries. Works for both MS Teams-based and skill-based Services.
Filtering
INC Filtering
When your current Nimbus view offers filters:
When filters are already active: Unless âAllâ is shown as filter content, your results are filtered.
|
![]() |
â Important Design Limitation: FilteringÂ
Your entire company User directory (via âAllâ tab) underlies Microsoft Graph search limitations.
đ€ How does this affect my search experience?
- You have to enter at least 3 characters to trigger a search.
For example: You need to type at least âMarâ to find a name like "Maria".
- A âContainsâ search will not work,Â
For example: typing âariaâ to find âMariaâ will not return any results.
- Adding filters can be mutually exclusive. Adding additional filters will be prevented.Â
For example: A âCompanyâ filter available only in Microsoft Outlook would exclude all other directories (O365, Address books, Nimbus Services).Â
âź A tooltip is shown whenever a filter combination is not possible.
- Previously applied filters (from Groups) will be set inactive in âAllâ search.
âź While searching within the âAllâ tab, Attendant will show mutually exclusive filters temporarily as inactive.Â
âź To maximize possible search results the âlargerâ filter sets are used (e.g. supported by more sources ).
â To avoid these limitations we recommend to create Contact Groups and use âGroupâ Search whenever possible.
"Group" Search
Search Contacts / Groups
Contact Groups allow you to have any selection of Contacts ready, without a prior search necessary. By default a âFavoritesâ Contact Group allows you to mark individual Contacts via the â Star icon. đĄAdvantage of using Groups: Contact Groups  - including the default âFavoritesâ  group that comes with your Attendant Console - do not share the âAllâ Search limitations. Nimbus allows you to directly start searching as you type the first letter, using the full set of available filters and fields.

Using the Contacts Group search field, you can search for:
- Contacts: The default option.Â
- Notes: If notes were defined for a Contact, you can search for note contents.Â
-
PSTN Numbers / SIP addresses: You can also enter unknown PSTN numbers or enter a valid SIP address.Â
âCall actions may be limited in this case, as the target cannot be resolved by Nimbus (e.g. unknown phone license or modality support). - Nimbus Services: You can search Services as single entries. Works for both MS Teams-based and skill-based Services.
Managing your Contact Groups
You can manage your Contact Groups within your Attendant Settings.Â
Attendant Console 2.0 - Contact Groups
Contact Group Limitation
đĄNote that you can create max. 10 contact groups and add up to 50 contacts per contact group.
- Head to Attendant Settings.
- Within the âContact Groupsâ section, click on âCreateâ Â to start a new group, or âEditâ an existing one (including your Favorites).
- Define / Change your Group Name as it will appear in your Attendant later.
- Click âAddâ to define contacts.Â
- Start typing to search for users.đĄThe search triggers as you enter 3 letters or more. Click on user names to add them to your Contacts.
-
Rearrange the order of users via the handles as you want them to appear within your group.Â
- Once satisfied with your Contact Group, click âSave & Applyâ.
âźYou will be brought back to the âContact Groupsâ overview with your new group added to the bottom of the list. - Order your new Group as you would like it to appear.
-
Optionally turn (any existing) groups invisible to keep for later.
- When satisfied with your groups, close your settings.Â
âź Your new Contact Group will now appear in your defined order.
Filtering
INC Filtering
When your current Nimbus view offers filters:
When filters are already active: Unless âAllâ is shown as filter content, your results are filtered.
|
![]() |
Results / Contact List
Search Results
Search results are listed directly below your search field. You can switch between grid or card view, each listing the following details:
Column |
Description |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | Shows the Display Name and Status of either Contacts or Services with the following detail elements:
đAbout Availability States![]() đ€ What are Availability states?In addition to your MS Teams presence, Nimbus also tracks User States internally, marking you as âAvailableâ for task distribution. Availability can be impacted by a variety of factors in Nimbus, such as:Â
đLearn more about this on the User States page. Â
Â
đ€ No status / availability shown at all?When the presence state cannot be resolved - or does not apply for that type of source - no icon will be shown.Â
đFor IT Admins: Also ensure that the Communication by Nimbus is not blocked by your Proxy / Firewall infrastructure, as explained in the Installation Prerequisites. Â
Â
Â
 |
||||||||||||
Contact Details |
Both for Users and Nimbus Services shows in prioritized order, if available in User directory:
|
||||||||||||
Note |
Within the Contacts area you are also able to add notes on individual Contacts. ![]() Functionality:
âIMPORTANT: Data within Notes is sharedLearn moreâŠ
Â
Â
đĄ We strongly recommend you to store any confidential of business-relevant User information in separate systems and databases with authentication. Â
 |
||||||||||||
Call Actions |
Each card in your Contacts has a series of call actions that become available depending on the current call situation and chosen target.  ![]() Available options are:
|
Things to keep in mind
- All your search results are narrowed down by BOTH your Contact Groups AND currently applied Filters. Keep this in mind when switching between groups as you may not see entries you expect to be listed.
- All Contact cards can be selected, opening a Side Panel with further context information and actions. More on this below.
Side Panel (Card Details)
The Side Panel provides useful context information and related actions. It's shown on the right-hand side as you click cards either in the Queue, Active Sessions, Contacts area.
For Contacts | For Services | For queued / active Task Cards |
---|---|---|
Contacts within your company (including Nimbus users) will show additional tabs with information and context actions, such as Calendar, Email and Chat functions and Organization details. | Services will reveal service contact details and - if you're also a user of this service - Â the availability status of other users. | Cards shows basic âSession Detailsâ. Fields may be âEmptyâ if nothing has been retrieved from external sources, such as an external CRM, Nimbus Address Books by using the Nimbus Power Automate Connector. |
![]() |
![]() |
![]() |
âNote that information depends on your granted Attendant Console 2.0 - Permissions, as well as permissions granted by your IT department. For example: If a Contact's calendar is not shared with you, you may not see any events on it.Â
Side Panel Tabs
The side panel is divided into the following tabs1:
Tab Name | Contact card | Service card | Queue/Active task card |
---|---|---|---|
Info |
|
|
|
Calendar |
Calendar view
|
Not available | Not available |
Instant Messages |
Shows a selection of available Instant Messaging  destinations, allowing to open an empty chat window with the Contact. â During an active session:
|
Not available | Not available |
Shows a selection of available Email destinations2, allowing to open an empty mail draft towards the Contact. â During an active session:
|
Not available | Not available | |
Users | Not available |
Shows the available Users in that Service, sorted alphabetically  |
Not available |
Organization | Shows direct reports, managers, peers, sorted alphabetically. | Not available | Not available |
Notes
1 Please note that full availability of tabs relies on Attendant Console 2.0 - Permissions granted and is also dependent on the source directory where the information is retrieved from. For example: Outlook Contacts don't have a calendar and organization tab available.
Learn more about Attendant Console Permissions
Attendant Console 2.0 - Permissions
Attendant Console relies on User Permission consent to access company-internal user directories for search and filter.
â To use extended search, permissions on the Contact search must be granted both by you and your Tenant administrator, each using their User Permission dialog.
â Without any consent, the search will only cover Nimbus internal Address Books which are kept in the Administration backend.
 | Out of the Box | User Permissions granted | Admin Permissions granted |
---|---|---|---|
Free Text Search | Address Books only |
O365Â Outlook Nimbus Services |
O365Â Outlook Nimbus Services |
Filters | Address Books fields only |
Outlook Nimbus Services |
O365Â Outlook Nimbus Services |
Contact Groups | - | Available | Available |
Organization Tab | - | Shows only yourself and manager | Organization tab in the side panel, including manager and peers. |
Primary Contact Information | - |
Primary telephone number   Primary email address |
Contact cards now show all available fields. |
Secondary Contact Information | - | - | Contact cards now show all available fields. |
Example in the UI | - | - | Contact cards now show all available fields. |
đ€ How can I check if access is granted?
You can directly check in the search field which search directories are currently available.

đĄAttendant Console will automatically check and ask for missing or revoked permissions. If you think your search results are not comprehensive, you can always check the status icon, visit your User Preferences (Portal) > Permissions tab and consult your local Nimbus Administrator if problems arise.
đ€Â Which search directories are covered?
- The O365 / AD User Directory of your company.
- Microsoft Outlook / Exchange Server contacts (e.g. "People" in Outlook).
- Nimbus Address Books - managed by your service administrator via their Organization Units placement.
- Nimbus Services only show team members when the Team Visibility in the Tenant Administration is set accordingly. Otherwise you may not see any team details or only those of your own services.
â Depending on which sources are delivering results for your search terms, duplicate entries of the same contact may appear.
- Attendant Console will show a âSourceâ icon to indicate where the search / filter result came from.
- Your Tenant administrator can prefilter results by following Use Case - Filtering Attendant contact search via MS Graph.
- As Address Books may be limited by Organization Unit barriers, you can also implement shared lists by following our Use Case - Adding External Address Books via Power Automate.
2 Please note that clicking an Email destination link may not work out of box if the URL for the Mailto:
Protocol was not registered with a default App (e.g. Outlook) on your PC.
Learn how to register the URL with your Outlook App
INC Register MS Outlook Email Protocol
To register a clickable URL:ms-outlook
protocol with your MS-Outlook application, perform the following steps:
- Open your start menu, then search for âDefault Appsâ and open it.
- Into the âSet a default for a file or link typeâ field, enter
MS-OUTLOOK
- Click on âOutlookâ.
- Confirm with âSet defaultâÂ

â Note: This example is for Windows 11 and assuming that Outlook was already installed by your administrator on step 3.Â
đĄThe procedure of registering an App may look different depending on your OS version and UI language, but the process remains largely the same.
Â
3 Nimbus provides a baseline of System Fields and Parameters during a call. Any further retrieval of Customer context (e.g. clear name, address, IVR choices) must be retrieved via Nimbus Power Automate Connector in conjunction with your Service Workflows.
Â
Attendant Console 1.0
Attendant Console 1.0
Attendant Console is an optional application to Nimbus that allows you to handle incoming calls like a front desk operator. The main goal is to attend to Nimbus caller needs more directly and personally, e.g. in a Call Transfer scenario, forwarding them to a target of your choice.Â
PRECONDITIONS
- Attendant Console is a separately licensed Nimbus Feature and can be enabled per user via User Administration. After the license is enabled for your user account, an "Attendant Console" entry becomes available in your main menu.    Â
- You need to be part of at least one Nimbus service in order for Attendant Console to show as an option.
â User Permissions: Attendant Console will check and ask for consent to Required User Permissions on your behalf. These permissions allow Attendant Console to read calendar details, IM presence as well as your user directory for searching. Permissions are managed in your User Preferences (Portal).
â Exchange Contact and Licensing; Special requirements apply for Microsoft Exchange (Calendar access).
Show Exchange requirements
â Exchange license and user permission requirements
To inspect a contact's calendar, the following requirements must be met:
- User Permissions - Exchange Calendar View User Permissions must be granted in order to access a contact's calendar on your behalf.â This is usually done by your tenant administrator.
-
Exchange Licenses: Both you and the contact need any of the following Exchange Online plans:
- EXCHANGE_S_STANDARD
- EXCHANGE_S_ENTERPRISE
â Target user modality: Special requirements on modality licensing apply to serve all channels of communication:
MS Teams / PSTN license requirements
â MS Teams licensing and modality restrictions
- If the target contact does have a MS Teams license but no voice (PSTN) license, the transfer to UPN is disabled. Chat is possible.
- If the target contact does not have a MS Teams license, the account is shown, but transfer to UPN and Chat buttons are disabled.Â
-
MS Teams Licenses: Any of the following licenses apply:Â
- STANDARDPACK
- ENTERPRISEPACK
- ENTERPRISEPREMIUM
- ENTERPRISEPREMIUM_NOPSTNCONF
- TEAMS_EXPLORATORY
â On all Attendant transfer scenarios, please also consider the known limitations below on this page.
Overview
On first start, Attendant Console will not show a lot of content to you, so we'll demonstrate some features on this example screenshot. Refer to the chapters below for further information.

Call Queue & Service Selection
The queue lists incoming customer calls for all your services. You can directly impact your queue via the "On/Off" active toggle for the respective service.
- The service toggle functionality has the same effect as toggling the status in the "My Overview" or "Services Overview" Nimbus tabs respectively. Your team owners can also set this toggle for you, with immediate effect.
- Note that you can only take calls when your Attendant State (see below) widget is shown as "Active" (green).Â
- When being part of - and active (green) for - multiple services, the queue items are accumulated or removed in real-time, always sorted by longest waiting callers.Â
Caller Context
The queue has a call context feature that ties into the Microsoft Power Automate Connector of Nimbus to retrieve additional caller information. The amount and content of fields shown varies depending on which data (e.g. from a CRM System or Active Directory) is available to Nimbus.

Information Widgets
The top row of Attendant Console consists of a set of status widgets to help inform you about the most important metrics on your current call.
Widget Title |
Description / Purpose |
---|---|
In Queue |
Numerical representation of callers in the queue. đĄ Entries in the queue are directly impacted by your "enabled" toggle in the team selection. |
Longest Waiting | Shows the highest waiting time entry in the incoming call queue at a glance. |
Service Info |
Shows service line info depending on your call state:
đ Their use and status changes are explained in Call Handling. |
Conversation     State |
Displays Info during an active call. Changes states to either:
When Idle - displays "No Conversation / No Data" đĄ As there can be two ongoing simultaneous calls (e.g. Call-park scenario), this widget will focus on the call with the external customer. |
Attendant State |
Shows if you are in a "selectable" User State for calls. Works like "green/red" signal. â Preconditions for a green status are as follows:
|
Services | Allows you to "enable" yourself for call selection in one or several teams.      đĄ Disabling yourself in a team will remove you from the list of team members available for the call selection algorithm. The incoming call queue will be updated accordingly. This has the same effect as enabling yourself within other areas of Nimbus, e.g. My Overview or Services Overview, respectively. The state can also be toggled by your team owner. |
Contact Search |
đ Find more details on this UI element further below. |
Conversation Hub
The conversation hub is the central area to handle your calls. The hub is split into 3 sections to display your current incoming caller state:Â
-
Incoming - signals any incoming tasks distributed to you (automatically) by Nimbus Workflows. Â
đĄ Incoming calls will ring alongside in your MS Teams Client. - Active - your current task or conversation. You can use the call controls to handle your active callers.
- Park - an area to park calls. In most scenarios, it is used to park a calling customer while you consult someone from the contact search. You can use the call controls to handle your parked callers.

Task control elements
Each area in the hub has individual, context-sensitive controls which show depending on your currently handled task and relevant modality situation:
Control |
Applies to modality | Description |
---|---|---|
Swap | Audio / Video | Switches the caller's position between "Active" to the "On Hold" area. |
Merge | Audio / Video | Merges the call into a conference between all participants. |
Terminate |
Audio / Video Instant Messaging |
Ends an active task from other supported modalities: Â
|
Park / Unpark |
Audio / Video | Puts the calling customer from the "Active" to the "Park" area and vice-versa. |
Accept/Decline   |
Audio / Video External Task Instant Messaging |
|

đĄNotes and Tips
- A declined task will be redistributed to the queue. If no other service user (team member) is in an available User State, the task may be redistributed to you.
- Certain controls such as merge or switch may appear multiple areas of the conversation hub. They usually have the same function of merging or switching an active or parked entry respectively.
- Note that not all call controls are visible at all times. Some become enabled or visible in context, e.g. when you handle a parked caller, search for a contact, or only if the target supports the according modality.
- Some actions within the conversation hub can be controlled via drag & drop as an alternative method to clicking the controls.
Contact Search
The contact search lists and stores your call targets during ongoing conversations. By default, the contact search and list is empty and shows entries as you start typing.
PRECONDITIONS
- Search features heavily rely on your Required User Permission consent. Â
đĄAttendant Console will automatically check and ask for these permissions if not granted already. - The Search also relies on your internal O365 directory fields and Nimbus-managed Address Books which are kept in the Administration backend. If you discover missing or false user details in the search, contact your service or tenant administrator.
The search feature has the following UI elements:
Element | Description | |
---|---|---|
Contacts (Live Search)      |
Searching for usersBy default, you can search for users by Name and Job Title as displayed in the result columns below the search field. The list of entries narrows down as you type. ![]() |
|
Applying fields to filter search resultsYou can also apply filters to narrow down huge lists by clicking "Select Fields" . Â
| ||
Searching for PSTN NumbersYou can also use the search field to call unknown numbers by entering a valid SIP-address. However, in such cases the call actions may be limited.![]() | ||
Searching for ServicesYou can search for Nimbus services and list up to 8 available team members of that service. Works for both MS Teams-based and skill-based services. â Precondition: Services only show team members when the Team Visibility in Attendant Console in the Tenant Administration is set accordingly. Otherwise you may not see any team details or only those of your own services.Â
| ||
Settings | Attendant can be customized according to your needs by accessing the settings next to the search field. ![]() đ Visit Attendant Settings to learn more about each option.   |
Search Result Columns
The contact search lists the following table columns:
Column |
Description |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Source |
Displays the source directory/team/service behind the corresponding contact in form of an icon:
Depending on which sources are providing results for your search terms, duplicate entries of the same contact may appear. Your Tenant administrator can pre-filter available search results by following the steps in Use Case - Filtering Attendant contact search via MS Graph.  Address Books added via the Nimbus configuration are also managed by your service administrator. However, you can manage address books as Excel files in your team and sync them automatically. Refer to our Use Case - Adding external Address Books via Power Automate. Â
â Note that not all search fields are supported by each source. Show fields supported by Nimbus user searchINC Supported User Search FieldsSupported fields for Attendant Console 1.0 (AC1)Prerequisites: User.Read.All permissions must be granted to use search features. As a Tenant Admin, head to the Nimbus Portal > User Preferences (Portal) > Permissions> Advanced Search and manage consent for your entire tenant. â Also see Nimbus User Permissions for more details. Â
Legendâ
Fields are supported by search.
Â
 Attendant Console 1.0 (AC1) supported search fields table:
Â
Â
Supported fields / filters for Attendant Console 2.0 (AC2)Attendant Console 2.0 (AC2) supported search fields and filters tables: INC Supported Search Fields and Filters (AC2.0)Free Text SearchPrerequisites: The full search functionality only applies if permissions are granted. See Attendant Console 2.0 - Permissions. Â
Legendâ
Fields are supported by Free Text Search Â
FiltersNote: Filters only work if this field is actually used for the contact.
Â
Â
Â
Â
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Name     (and Presence State Icon) |
đĄ For single contacts: You can hover over a contact avatar to get more information. Clicking on the avatar shows the organizational structure with manager and peers.
đĄ For Services: Hover over a service to get the information. Click on the service avatar to see service team members and their status.
đ€ No state / availability shown at all? When the presence state cannot be resolved - or does not apply for that type of source - no icon will be shown. For external contacts, this may be blocked by IT policies or firewalls. For internal contacts, this can be caused by users (or your Tenant Administrator) not having granted Required User Permissions to Nimbus. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Name | Resolved clear user or service name for the identified contact. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Context | Displays additional fields such as Email, IM, Department if provided via the user directory. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Job Title | Provides a job title field, if provided via your tenant user directory. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Note | Allows you to take notes. See section Contact Notes below. |
Contact Actions
Actions relate in context of your currently active call in the conversation hub, e.g. an action transfers the current caller to the selected contact in your search or sends a message with call details.
đĄ If an action cannot be used by the corresponding contact - or is not applicable for the current call situation - controls are disabled for that entry.
![]() Â |
Safe Transfer to this contact.     Your current caller will remain in the call with you until connected. |
đ€ Why are certain Contact Actions disabled?  If no "Business phone" or "Mobile phone" numbers are registered for the contact in Microsoft Entra ID, the transfer to phone actions are disabled. Nimbus can only detect numbers registered via Microsoft Entra ID, not Teams-internally assigned Line URIs. â This is the default state for Teams Auto Attendants and Call Queues. If you require these to be reachable via Blind Transfer, then you will need to add at least one number to their Microsoft Entra ID account. Also refer to the known limitations below on this page. â To avoid lost calls in any transfer scenario, please carefully consider known limitations as well. Â
  |
---|---|---|
![]() Â |
Blind Transfer to this contact.     â A blind transfer may be lost and not returned to you. This is also the case if the contact is not responding or taking the call to voicemail. |
|
![]() Â |
Consultation Call to this contact. You can swap between clients and merge the conference session.     In the meantime, your original caller is put into Park position, listening to waiting music. |
|
![]() Â |
Call To this contact. Unlike a Consultation Call, this does not create a conference.     You can only speak to either the caller (customer) or your contact from the search. |
|
![]() Â |
Send IMÂ / Connect via MS Teams.
|
đĄ The template selection (during a call) determines what language will be used to prefill an Email  or Instant Message for your contact. ![]() ![]() |
![]() Â |
Send  Email to the contact.
|
|
![]() Â |
Calendar of the contact to inspect.    | Only shown when an exchange calendar was found.  If the contact does not have an Exchange license, the calendar functionality is disabled. â See -â Exchange Requirements on top of this page. |
![]() Â |
Add to Favorite Contacts. Contact entries of your choice are pinned in the "Favorites" group for future calls. | ![]() đ Good to Know: You can also use the Attendant Settings to define further contact groups to sort and display users in. |
Read the Attendant - Safe Transfer scenario to see an everyday`s example of these features.
Contact Notes
Within the Contact Search, you are able to add notes on individual contacts.

Functionality:
- You are able to pick between 3 different types of Notes: Standard, Info and  Warning.  đĄThis icon choice is cosmetic and merely impacts the look and feel of the note when being clicked.
- The note's title field will be shown in the Note column first. When title is not defined, the contents are shown instead.
- Clicking on any existing note allows you inspect detail contents and edit/delete the note.  Â

đĄTip: You can also search for note contents by selecting the âNoteâ field / filter in the Contact Search:   Â

âBe advised while taking notes:Â
- Notes are publicly shared with other Attendant Console users on your tenant. Keep in mind that potentially private information could be exposed in this way.Â
- Deleted notes cannot be restored. A confirmation dialog is shown prior to note deletion. Removing a note will remove that information immediately for all other Attendant Console users as well.
- Every Attendant Console user has the same rights to read and edit notes. â We therefore strongly recommend to store confidential, legally- or time-sensitive information outside of Notes, e.g. in a separate system that requires authentication.
Â
Known Limitations
INC Attendant Console Limitations
đĄThe following limitations are specific to Attendant Console functionality:
Consultation to PSTN linked to O365 Account
âConsultation to PSTN linked to an internal O365 Account can cause problems in sessions.Â
â Workaround:Â When starting an internal consultation call it is best to select the UPN from the contact's dropdown.Â
đ€What causes this? Calls to the user's phone number assigned in teams can lead to various problems due to the MS Teams-internal redirection. This is due to an issue on Microsoft side which Attendant Console cannot circumvent. We continue to monitor the situation and will update this limitation as it is resolved.
đ€What are the effects?
- It might take 10-15 seconds for the call to appear on a PSTN consultant's mobile phone.
- The "On Hold" button will be disabled during a merged call conference.
- In the Teams Reporting view the latest consultation callout result overrides the user/service session outcome. This means that a failed consultation attempt may adversely impact KPI although an Attendant took the call
- In Nimbus Reporting Model the HoldCnt and HoldTime fields include only the time when a customer was "on hold" during consult sessions. Park attempts are not included.
Calls taken from Luware Interact: Limited call options
Audio/Video âInteract-specific limitation for Attendant Console: Calls from Interact taken via Attendant Console will not support âŠ
- Blind Transfer, âŠ
- âPickupâ Distribution Types, or âŠ
- Transfer to Voicemail.
INC Transfer Limitation List
đĄIn the following we list all known Transfer limitations, either by design or external circumstances.
Transfer to PSTN - Licensing and Limitations
INC Transfer to PSTN Limitation
âOut of the box, Nimbus and related addons can only perform PSTN transfers according to Microsoft's licensing and constraints.
INC PSTN License Check Enforcement Notice
âAhead Notice: Microsoft enforcing PSTN license checks for bot calls
Amendment 07.05.2025: Microsoft has moved the date from June to end of September.
From: https://devblogs.microsoft.com/microsoft365dev/enforcement-of-license-checks-for-pstn-bot-calls/Â
Topic: Microsoft announced changes to PSTN license checks for bots. From the Blog Post of Microsoft:
As part of Microsoftâs feature parity with Teams Phone extensibility, weâre announcing the enforcement of Phone System license checks for Bot-initiated transfers to Teams users. This current gap in our systems will be addressed in September 2025.
Microsoft Teams requires that Teams users behind applications such as queue applications require a phone system license and the user to be Enterprise Voice Enabled. Weâre aligning the Microsoft Graph API with that requirement.âŻÂ
What is the change?
Effective September 30, 2025:
- Teams users will still have the option to transfer calls to other Teams users manually even if they donât have a PSTN phone system license.
- Bot-initiated transfers and add participant requests to non-phone system enabled users will be blocked.âŻÂ
đ€How does this affect Nimbus? Nimbus uses bots to initiate and monitor (safe) transfers and create call conferences. If Microsoft decides to pull through with this change by September 30, 2025, all Nimbus transfers and consultation calls will be blocked and fail without any possible workaround or error handling.
â Required Action for Tenant Administrators / Service Owners: Â This change mandates the use of a PSTN License on all Users you either transfer to or start a consultation call with.
đ€Which PSTN license do I need to acquire?
As of 2023, "Microsoft Teams Phone Standard" licenses are no longer supported by Microsoft. Previously, those licenses were viable for Nimbus. Regardless if you are using Direct Routing, Calling Plans, Operator Connect, the "Microsoft Teams Phone Resource Account" license is now always required.Â
Your Setup | Required License |
---|---|
Direct Routing |
"Microsoft Teams Phone Resource Account" Â |
Calling Plan |
"Microsoft Teams Phone Resource Account" + "Microsoft Teams Domestic Calling Plan" or "Microsoft Teams Domestic and International Calling Plan" or "Microsoft Teams Calling Plan pay-as-you-go" + "Communication Credits" (if these aren't already included as part of your plan) |
Operator Connect  |
"Microsoft Teams Phone Resource Account" |
âPlease note that Luware staff cannot give recommendations on which license plan is best suited for your needs. Depending on your scenario, additional Teams App licenses may be required. Exact details are to be discussed with your Microsoft contacts.
đAlso see: https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/virtual-user
đ€How does PSTN licensing affect Service and call transfers?
Assuming that the initially called Service has (no) PSTN license assigned - the following scenarios may unfold:
Scenario A - Service A has a PSTN license. Transfers to other Services occur.
âź The PSTN license carries over throughout transfers to other Nimbus Services B and C.
âź As the license carries over, a PSTN transfer to an external target is possible from either Service.
Scenario B - Service B has no PSTN license. A Transfer to Service C occurs which has a PSTN license.
âź The customer skips over Service A and manages to reach Service B instead.
âź The PSTN license is missing on Service B, so nothing is carried over to Service C.
âź Even if Service C has its own PSTN license, a PSTN transfer to an external target is not possible.

đLearnings:
- Nimbus will use the PSTN license â and create a (transfer) Session â from the FIRST Service responding to a call.Â
- Regardless of how many internal Service transfers are performed thereafter, the FIRST Service PSTN license remains in effect.Â
- If a PSTN license is missing, the transfer task will fail and be treated accordingly by the System.1
- Even if a Service being transferred towards has a PSTN license, it cannot be added in post, as the Call Session is already ongoing from the first-responding Service.
â For your licensing needs this means: If you require PSTN transfer functionality, you'll need to ensure that this Service is handling all your incoming calls.
- For ONE first-level / Front Desk Service, you'll need a PSTN license for this particular Service.
- For MULTIPLE first-level Services scenario, you'll need PSTN licenses for all first-level Services.
1đ Assumption: Workflow takes the normal âExitâ Announcement route and Service Session will conclude with a âTransfer failedâ outcome. For more details on analyzing your Reporting results, refer to Nimbus Reporting and Static Dimensions > "Service Session Outcomes"
âNote that handling and tracking of running cost for PSTN licenses is outside of the Luware support scope. If you however require assistance in extending and/or configuring your Nimbus Services for PSTN, our support will gladly assist you:
Luware Support Address
 Luware Website | https://luware.com/support/ |
---|---|
Luware Helpdesk | https://helpdesk.luware.cloud |
Cloud Service Status | https://status.luware.cloud/ |
Transfers and Context Handover
INC Context Handover Limitations
The Transfer of Custom Context Parameters works within Attendant Console. Currently Supported Scenarios are:
- Attendant - Safe Transfer â To User or Service
- Attendant - Blind Transfer â To User or Service
- Attendant - Consultation Call â Session Transfer not supported.2
Transfer | âŠto User | âŠto Service |
By User on |
â
Call Data + Customer.Custom Fields âŹ/â Custom Context Parameters only if enabled in respective Service Settings. |
â All Call Data + Custom Fields, System Data and |
By Service⊠| â No Context gets transferred.1 |
â All Call Data + Custom Fields, System Data and |
CONTEXT TRANSFER LIMITATIONS
The following Context Transfer limitations are known. We are actively working to improve this in a future update.
- 1 Workflows > âTransferâ Workflow Activity: A Custom Context Transfer from within a Service workflow to any target will not work.
-
2 No Transfer out of Conferences: All MS Teams Conference calls - e.g. those created during Consultation via Attendant - do not support transfers, which also prevents Context Parameters from being handed over.
â If you require Context to be transferred, use Blind Transfer or Safe Transfer scenarios respectively.
Transfers and RONA State
INC Transfers and RONA State
â Note: Only applies if âPersistent RONAâ is enabled via Distribution Service Settings.
-
When the target User is already is in RONA state.
âźÂ A message will be shown after a transfer attempt is made: âTransfer cannot be started to a User, who is in a Nimbus Taskâ. There will be no User Session for Nimbus Reporting.2 -
When the target User ignores / doesn't answer the transfer (e.g. Timeout), Nimbus will not flag users with RONA state1.
âźÂ User Session in Nimbus Reporting marked âCancelledâ2 - When the target User actively declines a transfer will also not flag users with RONA state.Â
âźÂ User Session in Nimbus Reporting marked as âDeclinedâ.2
1đ€ Why is RONA not applied in this the case? There is no persistent RONA state if User has not been selected by the Nimbus Task Queue and Distribution.Â
2 Depending on the Attendant Console transfer scenario (safe/blind), the call will return to the initial User or be lost. This is not related to RONA behavior.
Transfer to Teams Auto Attendant and Call Queues
INC Transfer to Teams Auto Attendant and Call Queues Limitation
âTransfers towards the UPNs of Teams-native Auto Attendantsâ or Call Queuesâ Resource Accounts will fail. Based on the PSTN connectivity option used, transfers towards the Resource Accounts' assigned phone numbers will work as summarized in the table below.
Transfer Type | Direct Routing | Calling Plan | Operator Connect |
---|---|---|---|
Attendant - Safe Transfer | đ | â | â |
Attendant - Blind Transfer | â | â | â |
Attendant - Consultation Call | đ | â | â |
Workflow Conversation Handling Activities  > Transfer > âLeave Nimbusâ disabled |
đ | â | â |
Workflow Conversation Handling Activities  > Transfer > âLeave Nimbusâ enabled |
â | â | â |
đ€ Why are transfers failing? Is there a workaround?
đAnalysis: This is caused by Microsoft Teams limitations on what voice applications (such as Call Queues, Auto Attendants, and Nimbus) are allowed to do. This cannot be circumvented by Nimbus.
đ Workaround: For these transfer types to work, Reverse Number Lookup (RNL) has to be disabled in the Resource Account's Phone Number Assignment. RNL can be disabled by executing the following Teams PowerShell command:
Set-CsPhoneNumberAssignment -PhoneNumber <phone number assigned to the CQ/AA resource account> -ReverseNumberLookup SkipInternalVoip
âź After disabling RNL for a Phone Number Assignment, Teams will automatically forward the call to the Direct Routing SBC, which then needs to redirect it toward the Resource Account of the Call Queue or Auto Attendant.
Transfers and Nimbus Reporting Outcomes
INC Transfers and Nimbus Reporting Outcomes
đRule: Last Outcome
 Rule for Nimbus Reporting > Outcomes & Sessions List Task Results: The overall Service Session outcome in a âTransferred-by-user Scenarioâ is set according to the outcome of the last User Session.
Transfer Scenario | User A - Session 1 Outcome | User B - Session 2 Outcome | Expected Service Session Reporting Outcome1 |
---|---|---|---|
User A blind / safe transfers to Internal Destination B, which accepts | Transferred Internally | Accepted | User Internal Transfer Successful |
User A blind3 transfers to Internal Destination B, which does not respond (ignore) | Internal Transfer Failed | Cancelled | User Internal Transfer Failed |
User A safe4 transfers to Internal Destination B, which rejects, Customer terminates afterwards. | Accepted | Declined | User Accepted |
User A transfers to Destination B Voicemail 2,5 directly | Transferred Internally | None, as no User Session is created for user B.2 | User Internal Transfer Successful |
1 See Nimbus Reporting Model > Â Static Dimensions > âUser Session Outcomesâ
2 Voicemail and Reporting: Any direct "Transfer to Voicemail" Actions via Attendant Console are not creating a new User Session or any related User State checks for the Nimbus Reporting Model.
3 Blind Transfer behavior: When the destination doesn't accept â and has Voicemail or any other forwarding activity enabled â the transfer will not reach Voicemail nor the forwarding target. This is expected Contact center behavior and avoids the loss of calls.
4 Safe Transfer / Voicemail behavior: When the destination doesn't accept - and has Voicemail enabled - the transfer will NOT reach the Voicemail. This is expected Contact Center behavior to avoid a potential call loss.Â
5 Disabled Voicemail: Nimbus cannot check ahead if voicemail is enabled for a user, but the âTransfer to Voicemailâ UI element is always shown. Also refer to the âTransfer to disabled Voicemailâ limitations.
Transfers to disabled Voicemail
INC Voicemail Limitations
âKNOWN LIMITATION: Currently, there is no way to check ahead if a (target) user has voicemail features enabled. This is a design limitation by Microsoft which Nimbus currently cannot circumvent.Â

Additionally, the voicemail feature may also be deactivated as part of a tenant-wide IT policy by your administrator. There are also known cases where Microsoft accepts transfers to voicemail but the recipient has no means to check (e.g. MS Teams Client / License restrictions). We highly recommend using this feature only in case voicemail is enabled for the Microsoft Teams user.
Â
Â
Â
Â