Documentation forSolarWinds Service Desk

SolarWinds Virtual Agent

On this page

Introduction

The SolarWinds Virtual Agent, available in Advanced and Premier packages, is a conversational self-service chatbot available with SolarWinds Service Desk (SWSD). The Virtual Agent uses artificial intelligence (AI) technology to solve users’ ordinary issues without service desk interaction. It mimics human interaction, learning and adapting through smart conversation. It understands the user’s language, asks additional questions to gain context, responds to user queries in real-time, and provides a hand-off to a human service desk agent when required. The Virtual Agent is available to users 24/7.

The Virtual Agent helps requesters (portal users) quickly resolve issues without involving a service desk agent. This approach improves self-service and reduces the number of incidents received through the service desk. The Virtual Agent can help users with simple or routine issues, allowing your service desk real agents to focus on more important, complex tasks. Use of the Virtual Agent improves service desk productivity accelerates response times, reducing Mean Time To Resolution (MTTR).

The Virtual Agent's Cognitive Analytics console provides administrators with a wide range of metrics and analytics.

The Virtual Agent can:

  • Answer frequently asked questions.

  • Point to tutorials, knowledge articles, and how- to information, all of which is stored within the Virtual Agent.

  • Query or update records, such as the status of an incident, service request, or task.

  • Resolving multi-step problems.

  • Collect issue-related information that can be forwarded to a service desk agent and save significant triage time.

  • Use Natural Language Processing (NLP) capabilities that allow users to engage in natural and intuitive conversations.

    Users can enter queries in any language the user sets up as the preferred language in their SWSD account profile (see Select your language). The Virtual Agent uses Google translation to translate user queries from non-English to English so it can respond. This language translation helps the Virtual Agent learn using Fast Training and does not require the Virtual Agent to be retrained on non-English languages.

  • Redirect users to chat with a live agent if the Virtual Agent couldn’t provide the needed assistant. (This feature must be configured in your global Service Portal settings.)

In addition, the SolarWinds Virtual Agent can be configured with the following channels: Web, Mobile, MS Teams, and Slack.

Prerequisites

For the Virtual Agent to work, it must be enabled in the service portal global settings of your company's instance of SWSD. If you want your employees to be able to use the Virtual Agent through Slack and/or MS Teams, you must also integrate those applications.

1. Enable in Service Portal Global Settings.

2. Integrate SWSD with Slack and/or MS Teams.

Navigation

Organizational level Landing Page Service provider level Service Portals
Organization > Global Settings > Landing Page > Virtual Agent Service Provider > Global Settings > Service Portal > Virtual Agent

The user experience in the Virtual Agent

Before logging into the Service Portal, users can select their preferred language. See Select your language.

When users open the Virtual Agent from your Service Portal, they are greeted with options to:

  • Show open tickets.
  • Create new incident.
  • Show open tasks.
  • Search knowledge.
  • Show assigned tickets.
  • Request new service.

The options available in the list are specific to the tasks the current user is allowed to perform. For example, if the user role does not allow the creation of new incidents, that button will not be available for the user to see.

The ESM customer user experience

For end users whose company is an ESM customer of SWSD, the user experience can be slightly different. If the end user opens the Virtual Agent from the Organization landing page, the first question the Virtual Agent will ask is which service provider the end user needs help from. After that, end-user options are the same.

At any time, an ESM end user can switch to a different service provider.

Go to Home or Chat History

From the button bar at the top right, users can click the Home button to return to the original welcome message. Also, at any time users can type Home into the message bar to go to the original welcome message.

Clicking the Chat History button displays a complete history of chat communications.

Show open tickets

When Show open tickets is clicked, a list of all open tickets created by the user displays.

  • The number of tickets displayed is dependent on the channel through which the user is working, for example, web, mobile app, Slack, or MS Teams. The user can advance through the pages to see tickets that do not display on the first page. The Virtual Agent displays up to 100 tickets on multiple pages. To see more than 100, click View all tickets.

  • The user can enter a specific ticket number to see the details of that ticket.

  • The user can click on any ticket number or ticket name to see more information about the ticket.

  • From an open ticket, users can add a comment.

    Slack users who want to ensure that comments are recorded in tickets must click the Add comment button before typing the comment.

To see closed tickets or all tickets, the user can type into the message field:

  • Show closed tickets
  • Show all tickets

Create new incident

When Create new incident is clicked, a Create Ticket form opens. The user enters a title (required) and optional description, then selects a category. If a subcategory is required for that category, the user must also select a subcategory. When the user clicks Create, the Virtual Agent first searches for knowledge related to title the user entered and asks the user to review the knowledge articles for a solution. The user can click Cancel if one of the articles resolves the issue or Proceed to continue with the creation of a new incident.

When the ticket is created SWSD provides details of the ticket and the option to add a comment. See Add a comment.

Show open tasks

When Show open tasks is clicked, a list of all open tasks assigned to the user displays.

The number of tasks that displays is dependent on the channel through which the user is working, for example, web, mobile app, Slack, or MS Teams. The user can advance through the pages to see tasks that do not display on the first page. The Virtual Agent displays up to 15 tasks on multiple pages. To see more than 15, click View all tasks.

From the list, the user can click any task or approval in the Task Type column to see a summary of the task. From the summary the user can click on task name to open the details of the task.

  • From an open task, users can complete the task.

  • From a closed task, with type Task, users can reopen the task by clicking Undo.

To see closed tasks, users can type into the message field: Show closed tasks.

Search knowledge

When Search knowledge is clicked, the user can type a search term into the message bar. Knowledge articles that match the search term display. The user can decide whether a knowledge article was helpful and provide feedback that will help the Virtual Agent improve.

Request new service

When Request new service is clicked, the user can type a term related to the requested service. Any services related to the search term will display in a dropdown list. If no services match the search term, a list of all new services displays. The user can select an item from the list, and then place the order. The Virtual Agent will redirect the user to the SWSD application and a form will display to collect information.

No exact query match

If a user types something into the message bar but the Virtual Agent cannot find a relevant match, it will tell the user it did not understand the query and offer some solutions. For the example below the user typed in Update ticket. The Virtual Agent offered two options (check ticket status and create new incident), but those are not specifically related to Update ticket.

However, if the user knows the specific ticket number, the number can be typed into the message field and the status of the ticket displays.

Related topics