What's new in Nimbus

Discover what’s coming next in Nimbus

⭐Take a look at what’s coming next in 2026 — new features and improvements are on the way!

💡Note that we will roll out these features gradually across all clusters, starting at the expected date scope below. Once features are released, you can find detailed descriptions and specific availability dates for your Nimbus cluster in the Latest Release Notes or – in case of past releases – the Release Note History.

 

📆Expected in January

Attendant: Transfers and Consultation Calls for Outbound Sessions

Outbound call and Call on behalf now support various transfer scenarios and destinations

Transfers and Consultation Calls are now possible for Outbound Call Sessions. This allows Nimbus users to engage with the customer first, then transfer them to another expert. For the customer, this means minimized wait times with no further service calls required in order to get connected to the right expert.

🆕What will be added to Nimbus?

Now when there's a connected Outbound Call of any type, users can make:
  • Support all scenarios for both both scheduled and manually engaged Outbound Calls / Call on Behalf of a service.
  • Safe/blind transfers to any destination -- the same as for Inbound.
  • Consultation Calls to all destinations except services. This feature will come at a later date.
  • Updated reporting to reflect these new actions.

📆Expected in February

New Feature: Caller Anonymization

Call Data for inbound and outbound calls can now be anonymized using the new “Caller Anonymization” feature.

Caller Anonymization is a new feature added to Nimbus which helps organizations to reduce exposure of personally identifiable information, supporting stricter privacy and compliance requirements.

🆕What will be added to Nimbus?

  • A new configuration page: "Caller Anonymization” to centrally manage how incoming PSTN numbers are identified (e.g. by region) with the use of regular expressions.
  • New settings tab (per service): “Data Privacy” to enable the feature.
  • During the call, customer identifying details will be shown as “Anonymized on request”, which persists through reporting.
  • Initial release: Only A/V inbound and outbound. No support for Transcription.

Agents can now swap back and talk to the customer while waiting in a Service B queue.

Consultation Call to Service: Improved Customer Experience 

We have made improvements to the Consultation Call to Service feature. Agents can now stay with customers during internal service calls while waiting for the service target to reply. This improves direct interaction and keeps the customer engaged during longer wait times.

🆕What will be added to Nimbus?

  • Possibility for the agent to stay with the customer right after initiating the Consultation Call to Service.
  • Added controls for the agent to swap between the consultant and the customer during ongoing consultation.
  • Further improvements to the initial release of this feature, removal of technical limitations.

 

 


Paginated refresh on the Nimbus OData Service interface

Improvements to OData Query Performance

We made improvements to the existing Nimbus OData queries to enforce paginated results. This limits the number of records in the response, ensuring to avoid timeouts, API constraints and other errors related to large data set queries.

🆕What will be added to Nimbus?

  • Limit the number of records in the OData feed response to 10000 per page.
  • Ensure that the OData query supports clients to page through the result set without having to dynamically adapting the OData filter.

Table of Contents