Due to how Nimbus Unify connects with the Microsoft Ecosystem, certain Workflow Activities may slightly differ in their behavior towards Nimbus Extend. This page is to give a comparison on Workflow Activities.
💡Good to know: The workflow configuration and service setup remains the same in Nimbus Unify. Luware development will attempt feature parity with existing Nimbus functionality, or at least simulate near-identical behavior between workflow activities.
INC Workflow Activity License Matrix
| Service License | Service Integrations | |||||
|---|---|---|---|---|---|---|
 |
 |
 |
 |
Supported by Nimbus |
||
|
|
Advanced Routing |
Direct Call Handling |
Enterprise Routing |
Contact Center |
Extend | Unify |
| Accept | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Add Virtual User1 | ✔️ | ✔️ | ✔️ | ✔️ | 🔜 | |
| Announcement | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Availability-based Routing | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Cancel Task | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Check Opening Hours | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Check Parameter (parameter-based routing) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Check Task | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Collect Information | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Delay | ✔️ | ✔️ | 🔜 | |||
| Disconnect | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Disconnect as Handled (Email) | ✔️ | ✔️ | 🔜 | |||
| Distribution Priority (set Task Priority) | ✔️ | ✔️ | ✔️ | ✔️ | ||
| Get Available Users | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Get Queue Position | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Initiate Callback | ✔️ | ✔️ | ✔️ | ✔️ | ||
| Input Customer (IVR) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Input Customer Advanced | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Mark as Handled | ✔️ | ✔️ | ✔️ | ✔️ | ||
| Message | ✔️ | ✔️ | ||||
| Origin Routing | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | 🔜 |
| Play Music | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Queue | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Queue Task | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Record Consent | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | 🔜 |
| Reply | ✔️ | ✔️ | 🔜 | |||
| Save to Parameter | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Standby Duty | ✔️ | ✔️ | ✔️ | ✔️ | 🔜 | |
| Transfer | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | 🔎4 |
| Voicemails | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | 🔜 |
| Wait for (external) Parameter | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Web Request | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Call Distribution modes within "Queue / Queue Task" activity | ||||||
| Broadcast | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Pickup2 | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | |
| Direct | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Features related to Workflows | ||||||
| Basic Call Templates | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| IVR Transfer Templates | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Configurable Opening Hours | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
1 Requires an extra license to be applied. Refer to Virtual Users configuration or your License Management.
2 The Pickup button is available for both MS Teams-based and Skill-based routing services, however with behavioral differences in the Nimbus UI. Refer to Distribution Types for more details on how Pickup modes operate in comparison.
3 Luware Nimbus supports the two Microsoft integration models for bringing a Contact Center as a Service (CCaaS) solution to Teams Phone: Extend and Unify. Compared to Extend, the new Unify model requires separate Workflows. Luware development aims to reach feature party, supporting most workflow activities with identical behavior wherever possible.
4 This activity is supported, but certain limitations. Refer to Conversation Handling Activities > Transfer documentation for details.
5 Direct Call Handling is not a distinct service license. The license is held by the user (base Direct Call Handling Nimbus license add-on); the Direct Call service is automatically provisioned with Enterprise Routing Features, created specifically for that user. No separate MS Teams Team is required. This service not consume a regular Nimbus service license. Workflow activities listed can be executed for direct calls.