Services can be deleted either manually via the Administration UI or via Nimbus API > Delete Service method.
- Via Service Administration Interface: By clicking the "Delete" icon next to the Service you mark it for "Pending Deletion" in the Administration.
-
Via Nimbus API: Deleting a Service will also mark the service to the same effect.
☝ Note that only services with User Assignment Types “Skill-based” and “None” can be deleted via API.
☝ Service Deletion - Please Note:
✅ Marking a service for deletion has the following effects:
⮑ A warning will appear, requiring you to confirm and consent to the deletion request.
⮑ The mark will IMMEDIATELY disable the service.
⮑ Incoming calls will be answered with a static announcement.
⮑ Afterwards the service will show with the State “Pending Deletion”.
💡 If you need to undo a pending deletion, please contact your Nimbus support representative.
✅Confirming deletion via Provisioning Script. The service pending for deletion will continue to exist until the deletion is confirmed via the Provisioning PowerShell script run. After the Script ran through:
⮑ … the application instance of the marked service will be permanently removed
INC Reporting Data Access after Service Deletion
☝️Data Access after Service Deletion
INC Preview Feature
This feature is in PREVIEW and may not yet be available to all customers. Functionality, scope and design may change considerably.
💡Preview Note: Deleted Service data access is currently restricted to “Tenant Administrators”. The “Service Supervisor” access described below is being rolled out gradually to all customers. We will inform about this via the Release Notes.
Deleting a service does not immediately erase its reporting history. Within the data retention period described in our Whitepaper documents, that service's past sessions stay available through the OData Feed (and any Nimbus Power BI Template reports built on it) – but only to users whose permissions still apply.
🤔 Which Nimbus Reporting session data1 stays available?
- Service Sessions
- Unified Sessions
- User Sessions (service-related)
- Transfer Sessions
🤔 Who keeps access to data from deleted services?
Access after deletion is decided by the Organization Unit (OU) that owned the service at the moment it was deleted:
- Tenant Administrator – always keeps full visibility.
- Service Supervisor – keeps access to the deleted service's historical sessions for as long as they remain responsible for that OU.
- Service Owner / Team Owner (Limited) – lose access once the service is deleted. Their access is tied to the service itself, so when the service no longer exists, neither does their visibility of it.
💡 Good to know
- 1 Session related data such as Tags, Codes, Callers, Transfer targets are also included.
- Permissions for a deleted service can no longer be changed – visibility stays permanently tied to the OU that owned it at deletion.
- If that OU is later deleted as well, only the Tenant Administrator can still see the data, and this cannot be reassigned.
- When the data retention period ends, the session data is removed for everyone.