Luware Knowledge

Nimbus Portal Nimbus Admin Nimbus Release Notes Luware Cloud Status
Home Nimbus Administration Operations

Service Operations

The Operations > Service view allows administrators to check on ongoing and historical sessions. Administrators can remove (stuck, hanging) tasks and download trace files for technical analysis. 

Service Operations - Showing example live tasks (to remove if stuck) on the left

The following elements are available:

Element Description
Service

Contains a search / selection field for Tenant and Service.

💡 No tasks and interaction results are shown until both entries are selected.
Tasks Widget

Corresponds with the → Tasks List below. Shows conversation states, same as they are visible on the respective service's live Dashboard.

  • Connected to a user
  • In Queue
  • In IVR
  • In IVR After Queue
  • Parked, Transferring
  • Dialing Out
  • Additional "invisible" states involve:
    • Establishing (a session)
    • In ACW (After-Call Work) 
    • Terminated when the call is terminated on Reporting side, but the task was not cleaned up in TaskManager.
    • Blocked when the task was not cleaned up in TaskManager and it is not possible to find a related call.
    • Ringing when Outbound Service Call / Call On Behalf is ringing to a user.
Last Interaction

Highlights the last → History interaction and task resolution.

💡 Also persists when the History is currently filtered to another view.
Interactions Lists service session outcomes as described further in the Nimbus Reporting Model.
Last Updated

Refreshes the entire view.

💡 Applied filters in the → History will remain intact.
Tasks List

Shows current ongoing tasks of the Tenant and Service. Shows conversation states, same as they are visible on the respective service's live Dashboard.

  • This view will automatically refreshes as new tasks are coming in. 
  • By default this table is grouped by task state. "Invisible" states are grouped under "other". 
    → See Tasks Widget description above for a list of task states.

INC Nimbus Task Removal Notice

☝CAUTION: Possible valid Task removal

This functionality allows to also remove productive and “valid” Tasks - including live Customer interactions. Note that removing valid tasks can lead to unwanted side effects and should be avoided.

🤔How to identify long-running tasks?

✅ We recommend the following:

  • First identify long-running tasks that have an unusual long “Time in State” or “Started Time”. 
  • Look out for other user-reported or Service-specific irregularities, e.g. hanging Flows in the Nimbus Power Automate Connector which could point to the Service receiving and manipulating the task, or which Modality being used.
  • Note that a long running task may actually be correct, e.g. a scheduled Outbound Call can sit in the system for a long while.
  • If technical issues occur, please get in touch with Luware support so the underlying issue can be addressed and analyzed on your Tenant.
 
 

🤔Why does a previously deleted task show up (again)?

A task can be deleted in Nimbus, but not on MS Teams side while ongoing and working. This is done to not affect potential live customer interactions.  In this case a task can reach or exit the queue – and be readded to Nimbus (as it is distributed), but now with less information (like missing CustomerID). The deletion of such a “lingering” task can take a while and may require several attempts.

✅ Removed tasks may reappear. Try deleting the follow-up task again. If task-related issues reoccur, please get in touch with Luware support so the underlying issue can be addressed and analyzed on your Tenant.

 
 

INC Luware Support Address

 Luware Website https://luware.com/support/
Luware Helpdesk https://helpdesk.luware.cloud 
Cloud Service Status https://status.luware.cloud/
Luware support contact details
 
History

Table with the following columns:

  • Direction of the call (inbound, outbound)
  • Date & Time when the session started
  • Source: Caller Identifier
  • Queued if task was queued within selected service
  • First Accepted Nimbus user who accepted the task for this service session
  • Opening Hours at the time of the task
  • Issues reported by the user (if any)
  • Result of the session as per Nimbus Reporting Model
  • Duration of the session
  • Actions (download Trace logs)

✅ Tenant Admin: Use the download trace files option to get a JSON file attachment for support cases.

🔎 Filters can narrow down the results shown:

Learn more about Filtering…

INC Filtering

When your current Nimbus view offers filters:

  • Click the filter icon for a filter selection menu.
  • Click on a filter name to directly add it and start.
  • Click the toggles to show or hide a filter.

When filters are already active:

Unless “All” is shown as filter content, your results are filtered.

  • Click ✖ inside a filter to clear its contents.
  • The filter itself will remain available for use.
  • To hide a filter again, use the filter menu. 
    ⮑ Doing so will also clear the filter from your search results.
 
 

🔎Task Results are the same as used in the Nimbus Frontent Portal UI, e.g. Statistics.

Show Task Results Legend…

INC Task Result Legend

Voicemail Conversation was recorded by workflow as a voice message.
Hangup before Accept Customer hung up before Nimbus could answer the call
Hangup in IVR Customer hung up during announcements or IVR prompts before the call entered the queue
Hangup in Queue Customer hang up the call during the time the task was queued
Hangup in IVR after Queue Session left the waiting queue and then Customer hung up during the following announcements
Hangup by Workflow Workflow has performed the disconnect of a session
Accepted by User A Nimbus user has answered the call
Reachability SLA KPI metric, percentage of queued tasks handled by Nimbus users
Acceptance SLA KPI metric, percentage of tasks accepted in waiting queue within the defined SLA interval
Hangup SLA KPI metric, percentage of calls that the Customer hung up in waiting queue before the defined SLA interval had elapsed
Transferred by Workflow Workflow executed the transfer action
Transferred by User User executed the transfer action
Transfer failed Workflow or User tried to execute the transfer action but it didn't succeed
Destination Accepted Outbound Task / Calls on behalf: the callee (destination) has accepted the call
Destination Declined Outbound Task / Calls on behalf: the callee (destination) has declined the call
Destination Not Reached Outbound Task / Calls on behalf: the callee (destination) did not pick up in time
User aborted Outbound Task / Calls on behalf: Aborted by user during dialout
Lost In Queue Outbound Task only: When max queue time reached
Cancelled by External System External Task only: Task was cancelled via Dashboard widget or Power Automate
Marked as Handled by User Email only: Task was marked as handled by Nimbus user
Marked as Handled by Workflow Email only: Task was marked as handled by Nimbus workflow
Standby Duty Accepted The call was accepted by a number from the list of Standby Duty numbers.
Task Results Legend

🔎 Related concept: These results are part of the Nimbus Reporting Model > Static Dimensions > “Service / User Sessions Outcomes”.

 
 
 

Data Privacy Settings

GPDR - Note that via Data Privacy Tenant Settings the customer identifiers in this view can appear obfuscated / anonymized. You may need to use filters and other search criteria to identify a certain session.

 
Customer Operations

The Operations > Customer view allows administrators to export and anonymize d...

Table of Contents