OData Query: Enforced Pagination: We made improvements to the existing Nimbus OData Feed 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 and parallel data set queries. 🔎Added with this update:
Limited the number of records in the OData feed response to 10000 per page.
The OData query supports clients to page through the result set without having to dynamically adapting the OData filter.
✅Checking pagination readiness: When using the Nimbus Power BI Template version 1.122 or above, you can expect @odata.nextLink to work out of box with no further action required. 🔎 Download links can be found on top of the BI Template page itself. When you are accessing the 3rd-party solutions, please visit our OData Feed page and read the chapter on “Result pagination”. On most modern OData clients, @odata.nextLink pagination works without any additional actions required.
Data Privacy Settings: Caller Anonymization: 💡This feature was added with the last release and enabled only on customer request. With this release, it is available to all Nimbus customers. 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. Call Data for inbound and outbound calls can now be anonymized using the new “Caller Anonymization” feature.🔎Added with this update:
Caller Anonymization - new configuration item in the Service Administration. In the configuration item, you can define how incoming PSTN numbers are identified for anonymization (e.g. opt-in numbers by specific region) by using regular expressions.
Data Privacy Service Settings tab added. Allows to steer the "Caller Anonymization" feature per service (default: disabled).
When enabled, Caller Anonymization will mark Customer identifying fields in the Nimbus UI as “Anonymized on request”.
KB Update: Updated System Fields and Parameters tables with a new “Caller Anonymization” columns and a separate chapter at the bottom to highlight the scope of this feature.
Outbound call and Call on behalf now support various transfer scenarios and destinations
Attendant: Transfers and Consultation Calls for Outbound Sessions: Transfers and Consultation Calls are now possible for Outbound Call Sessions. This allows Nimbus users to engage with the customer first, then redirect them directly to an internal expert for further consultation. For the customer, this means minimized wait times with no further service calls required in order to get connected to the right expert.
Attendant - Consultation Call (internal or external) User / Phone Number. Nimbus Services are not yet supported. 💡Updated reporting behavior for these actions: In a multi-service scenario, where the first service handles the outbound task, and then transfers to another service, the task direction on the receiving service will be set to inbound.
Concluded (Historical) Sessions for both inbound and outbound PSTN calls can now be anonymized using the new “Caller Anonymization” feature.
Data Privacy Settings: Caller Anonymization: Caller Anonymization helps organizations to reduce exposure of personally identifiable information, supporting stricter privacy and compliance requirements. It limits what frontline users see, without blocking the workflow needed to help the caller. This lowers data‑handling risk while keeping service quality high.
🔎Added with this update:
Caller Anonymization - new configuration item in the Administration. Used to centrally define how incoming PSTN numbers are identified for anonymization (e.g. opt-in numbers by specific region) by using regular expressions.
Data Privacy Service Settings tab added. Allows to steer the "Caller Anonymization" feature per service (default: disabled).
Default disabled for all services. Once enabled, either all incoming PSTN calls OR the list of defined “Caller Anonymization” regular expressions will be applied.
Assistant - UI size was increased slightly. To accommodate new Consultation Call UI elements, Assistant will increase size temporarily, but return to the new standard height afterwards.
13 January 2026 - 1.121 + 1.122 Release Notes
🔖 This was a major update, bringing many new changes and improvements into Nimbus. This update was rolled out sequentially on our clusters:
New Nimbus API Methods - We have added new methods to the Nimbus API to enhance functionality and improve integration options. Read about the business value and find detailed descriptions below. Administrators can leverage the API to quickly provision, copy or delete services and their configuration.🔎 Added with this update:
POST Create Service - The Create Service method creates a new services with the user assignment type “None”.
GET Service Details - The Get Service Details method returns the details of a service and is needed for copying an existing service.
POST Copy Service - With this method, you can create a new skill-based service with the same licenses and configurations as the copied service it is based on.
POST Delete Service - Removes a service from Nimbus, marking it for deletion.
Consultation Call to Service - allows users to consult with a service before transferring a customer call, ensuring smoother handovers with context and parameters already included in the session. Users can now start Consultation Calls to Nimbus Services while staying with the Customer during the entire time.🔎 Added with this update:
Related KB changes: New Consultation Call concept page with explanations, considerations, limitations listed in one place.
Workflows: New “Origin Routing”Check Activity. Allows to route workflows on the receiving service, e.g. to bypass the regular service queue or shorten announcements for incoming consultation calls from another Nimbus service.
Added remarks for Unified Sessions to distinguish between the InitialCaller (customer) durations and the duration during a consultation call to service, where two service sessions with the same customer overlap.
Service Session Outcomes 6 and 7 updated descriptions. Consultation Service Sessions can be identified by Static Dimensions TaskType = “Consultation Call with Workflow (6)”.
Facts - Columns and Data Types - added the new objects starting with InitialCaller in the name and updated the descriptions for the corresponding pre-existing objects in the Unified Sessions section.
InitialCallerConnectedTime1
InitialCallerHoldCount1
InitialCallerHoldTime1
InitialCallerIVRTime
InitialCallerQueueTime Notes: 1💡Reminder:HoldTime is included in the ConnectedTime.
Data Aggregation - No technical changes expected, but consultation calls to services can now involve multiple users and may also create more user and service sessions.
Preview: Universal Message handler with WhatsApp integration - The new WhatsApp integration to Nimbus adds a convenient business and service communication channel for customers. For instance, support teams can handle inquiries via WhatsApp, improving responsiveness and customer satisfaction. The WhatsApp Integration allows to provide a Front Desk Service Chat, either handling the incoming tasks directly or transferring them to other services🔎 Added with this update:
Nimbus:
Modalities Service Settings - Now support separate toggles for Interact and WhatsApp, to allow for individual configuration. 💡Already existing website integrations via Interact (widgets) will continue to function normally and are unaffected by this update. WhatsApp can be used as an additional integration method in parallel.
My Sessions - now allows for Chat interaction using WhatsApp business accounts. 💡Nimbus is leveraging the cloud communications platform Twilio as integration for the WhatsApp Business channel - more integrations are planned and coming soon™.
Assistant - now provides deep links to jump into a WhatsApp Instant Messaging session within My Sessions.
Assistant / Attendant Console - Added support to Accept, Decline, Terminate + ACW Extend IM sessions via WhatsApp.
Workflow Activities - Greatly extended the IM-compatible Workflow Activities for WhatsApp.
Distribution Policies - Updated notes for “Last User Routing” for the Instant Messaging modality, specifically in scenarios, where multiple integrations are in place (Interact / WhatsApp).
Preview: Direct Call Reporting - Direct Call Reporting provides visibility into calls outside of standard Nimbus, helping supervisors monitor all interactions for quality and compliance, also by improving overall reporting accuracy. A business case example is using these insights to optimize staffing and ensure regulatory adherence. BI Specialists can now gather metrics on calls made directly to (Nimbus) users in their MS Teams client.🔎 Added with this update:
