5 June 2025 - 1.112 Release Notes

🔖 This is a major update, bringing many new changes and improvements into Nimbus. This update is rolled out sequentially on our clusters:

Outbound Call with Workflow

Contact Center Service exclusive feature.

Using the Nimbus Power Automate Connector > Flow Actions “Schedule an Outbound Call with Workflow” it is now possible to call out to a destination (Customer) and then engage them with your Services using Audio/Video Workflows.

This allows to extend the Outbound Call features with further possibilities, e.g. by scheduling campaigns or automate certain call scenarios.

Related changes:

• Modalities Service Settings: Added new "Outbound with Workflow" option to the Settings. Allows the Service Owner to specify a workflow used for the Outbound Call with a workflow.
• Service Owners must use the new “Schedule an Outbound Call with Workflow” Flow Action to schedule the call. 
  ☝Note that the Flow Action currently allows to select only Contact Center services. Without the license, only regular (Outbound) Call On Behalf features are available (no Outbound with Workflow support). Also note that this feature is exclusive to the Upcoming Power Automate Connector (see note below).

Attendant Console 2.0 - Call Park

During an ongoing call in Nimbus you now have the possibility to “Park and Unpark” a call using either My Sessions and Attendant Console.  

While parking a call, the Caller can't hear you and is listening to wait music instead. You will be free in MS Teams to take other calls in the meantime, but stay “Not available” for any other Nimbus tasks. More details on Parking can be found below:

Parking

Supported Modalities: Audio/Video|External Task → Also see Limitations below.

 

Parking describes the process of long-term parking a Nimbus task without reflecting negatively on KPIs, allowing the Nimbus User to temporarily focus on other urgent work. Same as an “On Hold” status, the parked task can then be resumed by the same user. 

💡For the Customer there will be no difference being “Parked” or “Put on Hold”, but in a Nimbus context there are notable differences.
💡For the User either “Parking” and putting “On Hold” will be a blocking state, meaning no further Nimbus tasks are being distributed to them.

🔎Learn more: Parking and Holding a task in Nimbus

As Nimbus will treat Parking and Holding of tasks¹ differently, it is important to highlight the differences between those terms:

	Parking	Holding
User Intention	To pause a Nimbus task while being free for other – non-Nimbus related tasks or MS Teams calls.	To temporary mute the Customer and clarify something during this call, with the intent to get a timely response.
Nimbus User State	“Connected” and blocked for other Nimbus tasks	“Connected” and blocked for other Nimbus tasks
MS Teams User Session status	User gets removed from a MS Teams conference and can start a new Teams call. “Available” status in MS-Teams	User stays connected to a MS Teams conference and is blocked from further calls. "Busy in a Call” status in MS-Teams
Nimbus Reporting and Nimbus KPI Calculations	Park time will not be included into ConnectedTime KPIs.  Only the actual talking time is recorded.	Hold time will be included into ConnectedTime KPIs.  Even time not spent talking to the Customer is recorded.
Transcription	The transcription session will be interrupted while Parking. The transcription bot will re-join when session is unparked.	The transcription session persists while Holding.
Supervision	An ongoing supervision session will be interrupted while Parking and will NOT restart on unpark	The supervised session cannot be put on hold.
Customer Side	No differences for the Customer: Will hear waiting music until the call is resumed.

¹ It's worth noting that “task” in this context can be understood synonymously with “call”. A task can technically mean any modality & related interaction between Customer and Service (e.g. a Chat, Email, Call, etc.).

 

 

Parking in the UI

Nimbus will indicate the “Parking” status in various UI views. Your user interactions with the task are handled within My Sessions and Attendant Console:

My Sessions

Within My Sessions

Parking

✅ Precondition: A task / call has been accepted and is shown in My Sessions 

1. Within My Sessions locate the active task card (green) click on the “Park” button.
2. The following results will occur:
   ⮑ Your session is now “Parked”.
   ⮑ The task card will change to “grey” status to signal that it has been parked.
   ⮑ The "Connected Time" widget will change to “Parked Time”.
   💡The task card will show an “Elapsed Time" to indicate how long the session with the customer has been ongoing overall.
   ⮑ In the meantime you cannot interact with the Nimbus widgets for as Codes or Tags, as parking interrupted your ongoing task.
3. ONLY during an Audio/Video calls - while parking: 
   ⮑ You are removed from the call session.
   ⮑ Wait music will play for the caller.
   ⮑ Within your MS Teams you can now engage in (non-Nimbus) related calls.

Unparking

1. Within My Sessions locate the parked task card (grey) click on “Unpark”
2. The following results will occur:
   ⮑ The session is back to Connected state.
3. ONLY during an Audio/Video calls - while unparking: 
   ⮑ You will get an incoming invitation in MS Teams which you should accept to rejoin the call.
   ⮑ The waiting music is stopped for the Caller.
   ⮑ Your session with the Caller is resumed.
   ⮑ You and the Caller can hear and talk to each other again

 

 

Attendant 2.0

Within Attendant Console

Attendant Console 2.0 - Call Park

During an ongoing call in Attendant Console, you have the possibility to park a call. While parking a call, the Caller can't hear you and is listening to wait music instead. You will be free in MS Teams to take other calls in the meantime, but stay “Not available” for any other Nimbus tasks.

🔎 Related concepts: The steps below refer to UI elements and concepts explained on the Attendant Console main page. Note that steps below describe a typical Audio/Video call behavior, but some Parking concepts (UI buttons and behaviors) also apply for handling External Tasks – e.g. a Task without any Customer or MS Teams interaction being necessary.

 

Park Call

The scenario is handled as follows:

✅ Precondition: Behavior applies for Audio/Video calls only. Starting point: an incoming call must is shown in the queue.

1. Accept the incoming call.
   ⮑ The call is shown in “Active Sessions”
2. To park the call, click the Park button:
   
3. The following results will occur:
   ⮑ Wait music will play for the Caller while parked.
   ⮑ You and the Caller cannot hear each other anymore.
   ⮑ The call is shown in “Parked Sessions” and the card shown with grey border.
   ⮑ A separate “Parked” timer starts counting.
   ⮑ You are removed from the MS Teams call.
4. Within your MS Teams you can now engage in (non-Nimbus) related calls.

Unpark Call

1. To unpark the call, click the Unpark button.
   
2. The following results will occur:
   ⮑ You will get an incoming invitation in MS Teams which you should accept to rejoin the call
   ⮑ The waiting music is stopped for the Caller.
   ⮑ Your session with the Caller is resumed.
   ⮑ You and the Caller can hear and talk to each other again.

Hanging up on an “on-Park” Caller

You can also directly hang up on (end) an existing parked call. This will immediately free you up to take the next Nimbus task.

☝Before using "Hangup": 

• Note that a red button warning color signals that in this case the Caller is affected directly.
• The Caller will not get any prior notification - the wait music and call just ends for them.

 

 

 

Other UI Areas

Within other UI Areas you can also see a “parked” call state reflected. However, note that you cannot influence it. Examples include: 

The “Parked” state in the Live View area.	“Parked” state filters for your Personal- and Non-Personal Dashboards e.g. within the “Live Service Tasks Tabular” Dashboard Widgets.

 

 

Limitations

INC Parking Limitations

KNOWN PARKING LIMITATIONS

• Task Parking is currently not supported for Email |Instant Messaging modality tasks. This functionality will be rolled out later in 2025.
• Assistant  - will currently not reflect the “Park" status. The User is just shown as “In a call”.

 

BY DESIGN (not limitations)

• Parked calls do currently not enable handling of multiple Nimbus tasks simultaneously. This functionality will be rolled out later in 2025.
• “Parked” External Tasks cannot be removed via Nimbus Power Automate Connector nor Personal Dashboards.
• Call Parking is not available in Attendant Console 1.0 - Calls will be shown as “On Hold”. Parking is supported using AC2.0 or My Sessions.

 

 

Related changes:

• KB: New concept page Parking to explain how this feature can be used.
• KB: New Attendant Console 2.0 page: Attendant - Call Park and Unpark to explain the Audio modality behavior during call park.
• My Sessions now also supports Parking.
• Personal Dashboards “Parked”  state. Added “Parked” as status to Dashboard Widget Properties  "States" and "Filters" tables accordingly.
• Facts - Columns and Data Types - Updated UserSessions and ServiceSessions tables with new ParkCount and ParkTime variable.
• Data Aggregation - User Session Aggregates table updated with new columns. CntPark, SumParkTime, AvgParkTime.

Email Draft Saving

Email Drafts are now stored and retrieved from Mailboxes and can be resumed (or discarded) via My Sessions.

Related changes:

• Email Draft Saving: During Email Handling Users can now opt to “Save Drafts” of an Email to resume at a later point of time. 
• Unsaved Changes warning: Whenever you switch away from the Email task (e.g. to a different Nimbus view or Task within My Sessions), an “Unsaved Changes” popup will remind you whenever your Draft was not changed.
  ☝Note: There is no automatic saving of Drafts. Whenever you forcibly close the browser window, any unsaved changes will be lost.

Other changes and improvements

• Service Settings: Renamed “Virtual Assistant” settings tab to “Companion”. This is done in preparation of future changes coming to Nimbus. The “Virtual Assistant” configuration of Transcription functionality remains unchanged as of now and will be extended in future.
• Task Management - Now performs automatic updates in 1 minute intervals. The page will now be enabled in every cluster with this rollout.
• Various smaller UI improvements to My Sessions.
• Administration Overview and related Configuration Listings:  Improved text “Chip" cutoff behavior when multiple items are listed as 1:n references, e.g. “Used in Service” or “Organization Units” table columns.