Luware Nimbus instances are hosted in Microsoft Azure data centers located in Switzerland, the United Kingdom, and Germany.
Luware is ISO 27001 and ISO 9001 certified and is currently undergoing the SOC 2 Type II audit report.
Luware Nimbus is available through our global network of channel partners. Our authorized partners are experts in Microsoft Teams telephony and can assist with the design, implementation, and support of Luware Nimbus.
Of course. You get a free, productive 30-day trial when you place an order. You can cancel your order within that 30-day trial period at no charge. This does not include any onboarding package or support.
Yes, your organization needs Microsoft Teams and Microsoft Teams Phone to use Luware Nimbus. Luware Nimbus is a custom application for Microsoft Teams and uses the Teams Phone System for all contact center and call control experiences.
If you need help migrating to Microsoft Teams, please contact one of our partners.
Yes. Luware Nimbus works with Microsoft Teams Calling Plan, Direct Routing, and Operator Connect.
Yes. Luware Nimbus works on all devices that the Microsoft Teams application works on and can also be used in the browser version.
Luware Nimbus only needs to be added once by a Teams administrator through the corporate Teams Application Admin Center. Once added, it becomes available to the entire organization through the Teams App Store. Integration is as simple as adding it as a new tab within any Teams channel. Typically, a basic installation can be completed in as little as an hour, making it efficient and hassle-free.
Make sure that at least one company representative with global administrator rights is present to install Luware Nimbus. To speed things up, it is also useful to prepare the appropriate Microsoft Teams teams to which you want to add routing services and check if you have any unused phone numbers that can be used for testing.
A Customer Success representative will provide you with the necessary installation files to the customer during the onboarding process.
The provisioning script is an automated solution designed to streamline the provisioning process. Written in PowerShell, the script makes it easy to connect to our environment and make the necessary changes to your infrastructure so that your environment is properly configured to take advantage of the capabilities of Luware Nimbus.
Service-based modules (Advanced and Enterprise Routing) allow you to distribute calls among a Microsoft Teams-based team. Depending on the distribution type, for example, longest idle, the team member who has been inactive the longest will receive the next call.
In user-based modules (Contact Center), the distribution of tasks and calls is not tied to any team membership.
A skill profile can be defined for each user and calls can then be distributed to the best-qualified user.
We are currently working hard to develop multi-channel routing solutions for Luware Nimbus. The first multichannel modalities will be introduced in 2023 and more can be expected in the future. Upcoming features and their expected release dates can be found on our roadmap.
All native Microsoft Teams functionality comply with established accessibility standards. This includes taking calls, searching for contacts, transferring calls, and placing calls on hold. Moreover, Microsoft Teams has screen-reader support for people with visual or cognitive impairments.
Luware Nimbus has also been tested against certain user experience guidelines and incorporates features for better accessibility such as dark/light mode and font size adjustments. However, Luware Nimbus is not tested against the complete list of accessibility rules for accessible web apps.
Guest users need the following permissions in Azure AD to read the presence status of the agents:
No, multi-factor authentication (MFA) must be disabled for the two guest users for presence tracking to work. If your organization requires MFA for security reasons, the guest users should be allowed to log in using conditional access policies only from trusted locations without MFA.
To query presence states within Luware Nimbus, guest users log in from specified IP addresses from Microsoft Azure datacenters. Conditional access can be used to specify that users can only log in from the specified IP addresses.
For a detailed description of how to use conditional access policies and trusted locations to ensure security, click here.
No, presence tracking cannot completely replace Teams federation. In the event that presence tracking encounters a problem, such as a disruption in the Microsoft tenant, Luware Nimbus is designed to seamlessly switch to Teams federation as a fallback. This ensures continuity and prevents potential system downtime.
More information can be found here.
To create low-code automation and integrations with Power Automate, you need a Luware Nimbus Enterprise Routing or Luware Nimbus Contact Center license and at least one Microsoft Power Automate Premium license in your organization. We recommend using a “service” user that acts as the owner in all Luware Nimbus services and defines and executes the Power Automate flows accordingly.
For detailed information about Power Automate licensing, see the Microsoft Power Platform Licensing Overview.
Only the owner of the flow needs a premium license.
Absolutely. We offer two distinct methods of achieving this:
We welcome your feature requests and are committed to improving our offerings to meet your needs. Simply contact your dedicated Customer Success or Sales representative. They are eager to hear about your unique requirements and will work with you to explore potential solutions. To facilitate this process, please provide detailed scenarios that highlight the specific ways you see the new feature benefiting you. Your input is invaluable in helping us tailor our services to your needs.
Don’t hesitate to contact one of our Luware Nimbus experts. They’ll be happy to help you in any way they can.