INC Parking and Task Parallelization Limitations

☝KNOWN PARKING LIMITATIONS

We are actively working on further improvements for the following items:

  • Audio/Video modality only: While being at the maximum limit of parked tasks a user is still shown as “Available” in MS Teams, leading to the assumption that they can receive further calls. Nimbus will not distribute any tasks, but any incoming (blind / safe) transfers to those users will not succeed.
 

🔎DESIGN NOTES

  • With Task Parallelization enabled, up to 20 simultaneous tasks  are now allowed in parallel per user at any time. Nimbus development is improving the UI according to customer feedback. However, the intent will never be to “park” tasks long-term.
  • Call On Behalf and “Pickup” Task Queue and Distribution restrictions: While a user has reached the maximum number of parked sessions, the “Call on Behalf” and “Pickup” buttons on the UI will be disabled to adhere to the task limit. 
    • This is a separate mechanism from the “Enable Quick Switch Between Tasks” setting: Quick switch lets Call on Behalf and Unpark auto-park the currently active task to make room, but it cannot bypass the user's overall or per-modality task limit. → See "Switching between tasks" on the Task Parallelization page.
  • “Unpark” button availability: By default, Unpark is disabled while another task is active. With "Enable Quick Switch Between Tasks" enabled for the user, this restriction is lifted – Unpark stays available while another task is active, and Nimbus parks the active task automatically first.
  • After-Call Work (ACW) no longer applies to tasks once Task Parallelization is enabled for the user, to prevent conflicts and non-transparent timing constraints between parallel tasks. 
    • Note that this does not apply for active Audio/Video tasks - if an active (non-parked) call is terminated, the ACW will start. 
    • When a user also has "Enable Quick Switch Between Tasks" turned on, unparking another task (or starting a Call on Behalf) while in ACW ends that ACW automatically, provided it can already be ended (early end allowed, or already extended).
  • While being “Parked”, External Tasks cannot be removed via Nimbus Power Automate Connector nor Personal Dashboards. This is intentional design as the task is considered as currently being actively handled.
  • Nimbus Assistant will reflect the (parked) session in a simplified manner. When Task Parallelization is enabled, “Parked" sessions will be shown with a link to My Sessions where unparking and detail work is done. When Task Parallelization is disabled, a simplified “In a call / On Hold” status will be shown.
    💡Rationale: Nimbus Assistant will remain an intentionally designed side-view app to notify about pending tasks. It is not purpose-build for full on task management, which is why My Sessions and Attendant Console are created to display handle tasks in parallel, with specific modality needs in mind.

General technical limitations (wont fix):

  • While being Busy in a call / DND / Offline in MS Teams, users can still unpark existing sessions. However, MS Teams may then not send an invite back into the (call) session. → Nimbus won't introduce any validation here, leaving it up to users to decide when to unpark.
  • While handling Instant Messages and External Tasks, MS Teams presence is not updated, but Nimbus tasks are active.
    💡Rationale: 
    • Nimbus has no active control over MS Teams presence (read only) and cannot prevent a user from working on IM and EXT, even while the tasks are parked in the UI. 
    • Also, when a user switches between two different chats or external tasks outside the My Sessions or Attendant Console UI, Nimbus will not automatically learn about this task update.

☝General recommendation: Instruct users to use the Nimbus Portal UI to ensure tasks are parked / put on hold / resumed properly, e.g. to reflect correct reporting on connected time for each parallel task.

 

Table of Contents