This page will always reflect the latest Release Notes, recent improvements and changes made to Nimbus.
Other Information Resources:
- Our Release Note History contains information on all previous releases from 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
📣Important Announcements
Please take note of the following long-term and ongoing announcements below:
☝Attendant Console 1.0 Deprecation Notice by End of June
INC Attendant Console Deprecation Notice
Deprecation Notice: Attendant Console 1.0
☝ With an upcoming release by end of June 2025 Attendant Console 1.0 will be discontinued in favor of the new Attendant Console 2.0 design.
- AC1 functionality and toggles within the Attendant Settings will be removed. This rollout will be gradual across our Nimbus clusters, defaulting all Nimbus Users who haven't switched yet into the new Attendant Console 2.0 design.
- As part of the transition, AC1 parts of the KB (Screenshots in particular) may mismatch with the current design. Related pages of the KB will not be updated anymore and gradually removed as well.
☝Microsoft to enforce PSTN License Checks by End of September
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.
✅Replacement of Assistant Installers (only on Certificate Error)
✅ Admin action required: Assistant installer certificate renewal
Assistant Installation - Assistant Setups (Nimbus Assistant Client Setup.msi) got recertified on12.05.2025 as previous certificates have expired. Due to this, any older installers will no longer work since end of May.
- If you intend to (re)install Assistant in the near future, please request the newest installers via Customer Success.
- Already existing installations of Nimbus Assistant will continue to work unaffected.
End of announcements. Regular release notes continue below.
26 June 2025 - 1.113 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 | 26/06/2025 |
United Kingdom 01 | 30/06/2025 |
Switzerland 02 / Germany 02 | 02/07/2025 |
Switzerland 01 | 06/07/2025 |
Europe 01 | 09/07/2025 |
Germany 01 | 13/07/2025 |
Virtual Users: Nimbus AI-Driven Service bots
INC Beta Feature
This feature is in PUBLIC PREVIEW and may not yet be available to all customers. Functionality, scope and design may change considerably.
Virtual Users are helpful self-service bots that can meet Customer requests without the need of a Nimbus queue. You can configure them at your convenience, to be used variably within your Nimbus Workflows. The benefits are as follows:
- Responsive: A bot can answer your customers immediately, without having to wait in queues.
- Flexible: Via individual “Initial Message” and interchangeable bot configuration, the Customer can be engaged as you need to.
PRECONDITIONS
- Contact Center Licensing: Note that Virtual Users are exclusive to Contact Center services.
- Virtual Users require Bots and Bot Response Templates to be configured.
- A Speech Recognizer (Transcriber) is configured to convert the Customer voice into text for the bot to process.
🔎RECOMMENDED READING:
- Getting started: Best Practices - Virtual Users in Nimbus - Helpful thoughts and considerations before you implement AI in your Services.
- Detailed Admin step-by-step: Use Case - Setting up a Nimbus Virtual User using Copilot for a first setup of your Virtual User.
- Advanced Scenarios involving both Copilot and Flow: Use Case - Building a Classification Agent | AI Use Case Category.
Related changes in Nimbus
- Added the following items to the Configuration (Admin-UI only)
- Virtual Users - AI-driven self-service bots that you can add to your Workflows
- Bots - Allow configuration of external AI services (API and Authentication settings) to be used in Virtual Users.
- Bot Response Templates - allow to map Bot responses to be used Nimbus parameters and the new “Add Virtual User” activity.
-
Workflows > Conversation Handling Activities - New “Add Virtual User” activity. This activity engages the preconfigured Virtual User with the customer.
- Queue is not necessary, as the Conversation is immediately established.
- ☝Note: Initially this activity and related Virtual Users are limited limited to handling Audio/Video modality tasks.
-
System Fields and Parameters - added new fields:
$(Caller.Sentiment) (UI: Customer Sentiment)
$(Caller.Intent) (UI: Customer Intent)
- Initially these fields are blank, for future use.
- New Use Cases to ease into this feature - more to follow soon™:
Nimbus API: Manage Licenses, User Configuration Details, Copy and Delete
- The Nimbus API has been greatly expanded and now supports the following new methods:
- GET Details of Existing User - Allows to query all configuration details of an existing Nimbus user.
-
GET License usage - Performs a check in available Nimbus licenses, as also reflected in the Admin UI: License Management.
- Total number of licenses purchased.
- Total number of licenses in use.
- Total number of licenses available.
- COPY an existing User* - Creates a copy of an existing user, using their Nimbus User settings as template.
- DELETE an existing User* - Removes a User profile from the Nimbus Admin Portal. The User is also removed as Service Agent/Service Owner from the services where applicable.
* Note that only manually added users for Contact Center and Skill-based services can be handled. Users of Services with an “MS-Teams-based” User Assignment Type will be rejected by the API command.
Workflow Activity - Mark / Disconnect as Handled
Mark as Handled
- Audio/Video Activity for Inbound / Outbound direction workflows.
-
Conversation Handling Activities - New Activity: “Mark as Handled”: - When this activity succeeded it will mark the task with a result “Workflow Marked As Handled” in Nimbus Reporting.
☝ KPI Impacts: When using this feature, note that Service Session Results and related Outcomes in the Nimbus KPI Calculations can be significantly impacted. Whenever this Activity is passed in your workflow, the final session results will not NOT change anymore, even if potential task result-changing interactions take place within the same workflow.
Disconnect as Handled
- Email Activity for Inbound direction workflows only.
-
Conversation Handling Activities - Renamed Activity: “Disconnect as Handled”: Renamed from “Mark as Handled” to differentiate its use. In comparison to the regular “Disconnect” activity, “Disconnect as handled” has a failed exit.
☝ “Disconnect as Handled” should should still be followed-up upon with a “Disconnect” activity as a fallback in case moving an Email within the Inbox fails.
Flow Action: Check Opening Hours
INC Upcoming Connector Feature
🔜Pending Connector 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 on your tenant.
☝Please Note: By design, any custom-Installed connectors do not update automatically. Once the functionality becomes available in the certified connector you need to perform a manual Connector Migration of your flows.
Flow Actions > General Flow Actions > “Get Opening Hours”: Checks against first applicable status as per:
- Primary Opening Hours calendar of Service, THEN ….
- Secondary Opening Hours calendar of Service …
… at the selected date and time. When no date/time is passed, the service status is checked at the time when this flow action is triggered.
Customer Insights
INC Gradual Feature rollout
Features described in the following are gradually rolled out on Nimbus clusters. They may not be available on your Tenant yet.
The Customer Insights view allows Team/Service Owners and Service Supervisors to search for a customer by UPN, EMail or Phone Number and follow the entire Task flow in Nimbus by diving deeper into the single Service and User Sessions related to that Customer interaction.

Elapsed Time Display
The Nimbus UI now shows an additional “Elapsed Time” in session on both Attendant Console and My Sessions. “Elapsed Time” will always continue counting the overall task runtime in the background, even while Parking / Holding a task.
In Attendant Console the “Elapsed Time” is shown as an extra column within the task card itself. | |
![]() |
![]() |
Other changes and improvements
-
Supervision:
-
Dashboard Supervision Widgets: A toast message will be shown when Supervisors try to engage in a Session that is currently On Hold.
Related KB page rework to make the On-hold and Parking scenarios more clear, also including limitations when MS-Teams is used in parallel. - Attendant Console - (unchanged behavior): Supervised sessions cannot be put on-hold. A tooltip will show why the UI button is inactive.
- Task Management - Rollout on all clusters is now complete, according messages removed.
-
Dashboard Supervision Widgets: A toast message will be shown when Supervisors try to engage in a Session that is currently On Hold.