The "Services" view allows administrators to manage, edit and remove existing teams under their tenant.
This view is available to all admin roles of Nimbus.
The main table lists Service details as follows:
|Column||Description / Purpose|
Clear Name of the Service
Retrieved from the to the "Team" name of Microsoft Teams upon Service creation
When assigned via Service Settings > PSTN a number is shown here.
Please make sure to read the Installation Prerequisites on details and limitations regarding PSTN / Phone number assignment.
The states (from top to bottom) are as follows:
Date when Service was first provisioned.
Also see: Nimbus Installation
User Assignment Type
Shows how (new) users are assigned to this service:
Why is this setting locked on existing services? The assignment type is determined during service creation.
|Number of Users|
For "Microsoft Teams Based" services this number corresponds to the team members + owners combined, as retrieved from Microsoft Team's channel.
Services with user assignment type "None" do not have users.
|Enterprise||→ See Enterprise Features below.|
|Quick Access (Icons)|
Creating a new Service
Services manually created via administration are detached from the usual "Microsoft Teams Based" Nimbus services. Their user assignment is currently by default "None" and special rules apply.
Noteworthy points on "IVR" service creation
When creating a "no-user" service, the following points are worth noting:
- Service Provisioning steps are still required, the service is otherwise not operable.
- The service does not relate to a "Team" and thus is not assigned to a channel or user list. The main purpose of such a service is call forwarding (e.g. an "IVR Service").
- "Queue" Activities in Workflows are not allowed as they would would require assigned service users for call distribution. By default an IVR Workflow Template is provided as a valid example. Workflows with "Queue" steps are omitted from the list.
- Context and Extensions tabs (usually shown in Service Settings for Nimbus users) are hidden as there is nothing to handle or configure in that aspect.
All "Administration" user roles have the possibility to access and edit these type of services (on their respective tenant).
As administrator you have access to the task list as it is also shown in the Dashboard of the corresponding Service. The main difference here is that you are able to remove
Since task lists can get very large, make use of the filter by typing into the free-search field.
Removing Tasks / Unblock Calls
You can remove tasks (running calls) from the list. Removed tasks are marked as "failed" in the backend, but are not shown in the Service's Reporting.
Note that any task can be removed from the list - including those that are still running normal.
- Use this function only when a task is getting "stuck" (e.g. due to an erratic call state or system backend malfunction).
- Please note that task removal will also immediately terminate related call sessions and affect reporting entries.
Make sure to inform any involved users / service owners before using this function.
This should be done as an exception to unblock services or users. Let us know about any ongoing or reoccurring issues that cause "hanging" tasks so the underlying issue can be addressed. You can reach us via the following means:
Runbook and Powershell Scripts
These scripts allow you to automate the Service on-boarding process. The scripts are useful in case you need to:
- Onboard a series of Services within your tenant
- Regularly (expect to) update Service details such as the a Service's UPN or E.164 Number.
Nimbus will be equipped with additional Enterprise Routing features that can be enabled per Service.
What are Enterprise Routing Features:
Allows the use of the following features for the service:
- Additional Workflow Templates
- Additional Workflow Activities to use in the templates, e.g. include parameters via Microsoft Power Automate Connector.
- Additional Context (TCC, SCC, Tags) enabled in the My Sessions view for each user (Configured in Service Settings).
Once enabled, Enterprise Routing features are immediately available for the respective Service.
Disabling Features - Downgrade
To disable Enterprise Routing licensing, any used Enterprise Routing Features must be removed. A tooltip will inform about any constraints that prevent disabling the Enterprise Routing toggle.
- Refer to the list Nimbus Features for a full overview
- Go to the service's Workflow.
- Switch to a non-enterprise Workflow (e.g. a Workflow Template) or remove the template
or (if you want to keep your custom workflow)
- ... within an workflow, remove steps / change settings as follows:
- Any "Task" workflow steps (Queue Task, Check Task, Cancel Task)
- Within any "Queue / Enqueue" step, change any "Distribution Type" to a non-Pickup type.
- Remove any workflow steps that are part of the Enterprise Routing scope.
Once the steps are done get in contact with your service partner or Luware to disable the feature for your service. You can reach us via the following means: