What you can find here
This page will always reflect the latest Release Notes, improvements and changes made to Nimbus.
Other areas of interest:
- Refer to the Release Note History for previous releases earlier this year.
- Updates on our Nimbus Power BI Template are distributed on request. Please refer to the Nimbus BI Template Release Notes for updates.
- Also visit the following sources to stay up-to-date on Nimbus in both features and (upcoming) maintenance:
INC External News Resources
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.
29 Apr 2025 - 1.110-1 Release Notes
🔖 This is a major update, bringing an improvement into Nimbus. This update is rolled out sequentially on our clusters:
| Cluster | Update on |
|---|---|
| United Kingdom 01 | 28/04/2025 |
| United States 01 / Australia 01 | 29/04/2025 |
| Switzerland 02 / Germany 02 | 30/04/2025 |
| Switzerland 01 | 04/05/2025 |
| Europe 01 | 07/05/2025 |
| Germany 01 | 11/05/2025 |
-
Added a new Toggle to Modalities Tenant Settings “Leave Nimbus on Blind Transfer” (default disabled).
Enabling this toggle allows fallback to Teams call handling and forwarding settings, but Nimbus Context Handover and Session Reporting will not be available for the target user.
Transfer behavior changes - FAQ
With the introduction of Context Handover – if the transfer target is a Nimbus user – Attendant - Blind Transfer does not transfer the original call anymore, but instead invites the target user to a MS Teams conference. This change results in Teams Call Forwarding settings not being applied anymore to Blind-transferred Nimbus calls.
🤔 Why was this change introduced?
Note: For Safe Transfers this has already working like this before, as Nimbus kept control of the Session during a Service-to-Service transfer.
For blind transfers from Services to Users we had to change the way we get new Participants into the conversation with the Customer. This was also necessary because the transfer target may not be a user of the same Service, and thus requires an own session for the Sessions List and Nimbus Reporting.
This change was also necessary to treat these Users as temporary “Service assets” and allow access to Nimbus Features such as
- Receive Conversation Context and Parameters on the My Sessions / Assistant / Attendant Console.
- Assign (additional) Codes and Tags to a Service session.
- Get call Transcription separated per user and session.
- Get reporting added to the Agent's and to their Supervisor's Nimbus Reporting Model
☝Important: Nimbus cannot control or read ANY User Call Forwarding Settings in MS Teams. The option is to either transfer or invite, on which MS Teams decides whether to use or not to use these settings.
| Before | After | |
|---|---|---|
| Nimbus Call Situation |
Nimbus initiates a physical transfer of the Customer to the transfer destination. Afterwards, Nimbus has no control over the session anymore. The last reporting session result is the result of the transfer. |
We invite the transfer destination User into an existing Conference. This is the only way for Nimbus to control the session, update the UI and , display and calculate reporting times, track KPIs, allow transfers, etc. |
| MS Teams Forwarding | Teams forwarding settings of the destination apply in case of no answer. | Teams ignores call forward settings of a destination user in case of Conference invites. |
🤔Which transfer scenarios are affected by this change?
Only Attendant - Blind Transfer.
Not affected are:
- Blind Transfers to PSTN (Nimbus ends session control anyways).
- Transfers to non-Nimbus Users.
- Transfers to Nimbus Services.
- Safe Transfers to any destination.
- Consultative Transfer to any destination.
- Transfer by Workflow to any destination. (Has similar toggles to “Leave Nimbus” already.
🤔How can I retain the “old” Nimbus behavior?
Enable "Leave Nimbus on Blind Transfer" setting on your Modalities Tenant Settings.
However, note that this will prevent Nimbus Reporting from reflecting any detail results from that User session, as well as prevent Context Handover (e.g. of Custom Context Parameters) between users.
24 Apr 2025 - 1.110 Release Notes
🔖 This is a major update, bringing many new changes and improvements into Nimbus. This update is rolled out sequentially on our clusters:
| Cluster | Update on |
|---|---|
| United States 01 / Australia 01 | 24/04/2025 |
| United Kingdom 01 | 28/04/2025 |
| Switzerland 02 / Germany 02 | 30/04/2025 |
| Switzerland 01 | 04/05/2025 |
| Europe 01 | 07/05/2025 |
| Germany 01 | 11/05/2025 |
Transfer Sessions: Now supported for Transfer, Call Hold and Consultation
Attendant Console - Attendant can now handle transfer, hold and consultation on a previously transferred session. The corresponding limitations that disabled the options in the UI have been removed.
☝Please Note:
- Transfer-after-Transfer scenarios are only supported for Attendant Console 2.0.
- Assistant only supports “Blind Transfer”. For other (Safe, Consultative) transfer scenarios, please use Attendant Console 2.0.
- Context Handover concepts and limitations apply for each transfer, meaning that Parameters and Context can be updated in-between Sessions and may differ in-between sessions shown in the Sessions List.
Transcription: Now distinguished by Service or User Session
INC Beta Feature
This feature is in BETA status and may not yet be available to all customers. Functionality, design, and scope may change significantly over time.
INC Upcoming Connector Feature
Upcoming Features / Ongoing Certification
🔜This feature is not yet part of the certified Nimbus Power Automate Connector. To test this functionality, you can manually download and install the latest upcoming (V1) connector as Custom Connector. However – once the functionality becomes officially available – you need to perform a manual Connector Migration of your flows.
Individual Sessions can now be transcribed either on User or Service level. Administrators can configure the Nimbus Power Automate Connector to either hand over the entire (previous) conversation transcript or start over on a User Session level.
-
Nimbus Power Automate Connector Additions:
-
Updated existing Trigger Event “When the virtual user assistant has an update”.
- Return new fields in VoiceTranscriptionReady event:
UnifiedSessionId- Set to respective Unified Session IdUserSessionId- Set to respective User Session Id.
- Return new fields in VoiceTranscriptionReady event:
-
Updated existing Flow Action "Get virtual user assistant data" with new field:
Added new (optional)UserSessionIdparameter in addition to the existing (madnatory)ServiceSessionId
Behavior rules - depending on provided values:- If
ServiceSessionIdandUserSessionIdare set, a validation is performed if User Session Id belongs to specified Service Session Id- if NO then the flow will fail with an error.
- if YES then return transcription only for the specified User Session
- If only
ServiceSessionIdis set, the transcription data for all available User Sessions within the Service Session is sent.
💡This is the default behavior for all existing flows, as theUserSessionIdis optional.
- If
-
Updated existing Trigger Event “When the virtual user assistant has an update”.
Transcription Transfer Notes:
- The transferring Service determines the behavior: The originating Extensions Service Settings are taken into account for all Users a Session is being transferred to. These Users are temporarily treated as “asset” of the original service and – if configured in the original service – will see the according Transcription widget in their My Sessions.
- License Requirement: Each Users need a Transcription license enabled in their General User Settings.
Other Improvements
-
System Fields and Parameters KB page updated to include
UnifiedSessionIdas well as minor comment updates on existing Id. - UI Improvement: Virtual Assistants Service Settings are no longer shown with User Assignment Type “None”, as there are no users to Assist.
💡When the User Assignment Type changes from “Skill-based” to None, Virtual Assistants settings are not reset. - Update Power BI Template 1.110. Learn more in the Nimbus BI Template Release Notes.