✅ NimbusOne Prerequisites

✅ Before you start: NimbusOne builds upon Nimbus. If you are completely new to Nimbus, start with the common Installation Prerequisites. 

💡 Good to know: Luware NimbusOne uses the existing the Tenant, Service and User Administration concepts of the main Nimbus interface. There will be slight differences in how the individual UIs look, but otherwise the administration concept remains the same.

✅ Licensing and related feature Setup

• Contact Center requirement: NimbusOne Services and Users requires a Contact Center license, as both use Nimbus Features from that License Type. Administrators can access License Management to distribute accordingly.
  • As NimbusOne services are treated like Contact Centers, the setup is close to the descriptions in Use Case - Setting Up a Contact Center.
  • Contact Center users will also be referred to as Agents. Once assigned Further steps, such as assigning Responsibility Profiles with according Skills and Responsibilities. 

✅ Activating NimbusOne / Unify

To start using NimbusOne please perform the following steps:

1. In your Extensions Tenant Settings, enable “Use Nimbus Unify”. 
   This allows NimbusOne to access your Tenant Data via the Nimbus Unify integration.²
2. For your Services: 
   1. In your Service Administration, you need to provision a new “Nimbus Unify” service.
   2. Once the Unify service is provisioned: You can start adjusting Service Settings. Note that certain options inside tabs, as Distribution, Workflow Activities and Extensions may differ to Nimbus Extend Services usually signaled with “Unify” wording^1,2.
3. For your Users: In your General User Settings, enable “Nimbus Unify” for each user you want to use NimbusOne.

¹ 🔎Please Note: NimbusOne strives to achieve Nimbus Feature parity with the known Nimbus Extend integration. For an overview of current limitations, workarounds and the current feature set, refer to our NimbusOne FAQ and Troubleshooting page.

²🔎Why is this “Unify” separation necessary? Unify uses a different Integration Model to steer call sessions, allowing for a seamless integration with CRMs such Salesforce or Dynamics 365. For further information on this, refer to the Integration Model Comparison.