| Issue | Affected Area / Description | Possible Workarounds |
|---|---|---|
| Not all Workflow Activities are fully supported by Nimbus Unify yet. | When creating new “Unify” Type Workflows, certain Worklfow Activities may not be available in the list (yet). | Refer to NimbusOne Workflows for more details on which activities are supported. |
|
Transfers from Nimbus Extend to a Nimbus Unify service do not complete. Affects:
|
Extend services and agents on Extend services cannot transfer a call to a Unify service, neither by UPN nor by phone number.
Within Unify itself, these limitations do not apply, transfers work as intended.
This is a Microsoft issue, as the receiving service UPN is not correctly identified as a “Service”. Such a transfer can currently be configured, but it fails during the call. |
💡 In Workflows: Transfer to the PSTN number of the Unify service as External target and have “Leave Nimbus” enabled. 💡 During Transfers: Blind-Transfer to a Nimbus Service PSTN and let the user know their case will be treated as “new”. It creates a new Session in the target service and will correctly resolve. ☝️ This route may result in double call charges, because the call is routed out of Nimbus and back in. |
| Modality Support limited to Audio / Video. |
NimbusOne currently handles only Audio/Video Calls. Other Modalities (Email, Instant Messaging, External Tasks). are not supported yet. 💡Support for other modalities is being actively planned for. |
💡Use the baseline Nimbus My Sessions UI to handle other modalities (Email, Instant Messaging, External Tasks).
|
|
Transfers to a NimbusOne user are only possible from NimbusOne. |
Only NimbusOne users can transfer a call to another NimbusOne user. Agents on an Extend service, Extend Workflows and Unify Workflows cannot use a NimbusOne user as transfer target. | 💡 To reach an agent working in NimbusOne, transfer the call to a Unify service the agent is assigned to. |
Table of Contents