Luma Virtual Agent (Luma VA) is an advanced support agent designed to assist end-users by understanding and processing their requests using advanced AI technology. With the power of large language models (LLM) and Generative AI, Luma VA can understand what users are asking for and provide the right information or assistance. It identifies user intent, understands their emotions, and offers relevant solutions, making the support experience smooth and efficient. This page explains how Luma VA works and what you can expect.
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Initiating a Conversation
When an end-user initiates a conversation with Luma VA, the system uses Generative AI to comprehend the user's request. This involves identifying the user's intent and responding appropriately. Here’s a step-by-step breakdown of how Luma VA processes user interactions:
...
Intent Identification: Luma VA uses advanced AI to determine the intent behind the user's request
. It analyzesby analyzing the language used
to understand what the user is seeking. It identifies one of the following intents:
Small Talk: Casual or non-task-specific conversation.
Seeking Knowledge: The user is looking for information.
Reporting a Problem: The user is reporting an issue.
Requesting a Service: The user needs a service.
Looking for Ticket Data: The user is searching for information on their existing tickets.
By accurately identifying the intent, Luma VA ensures that each request is handled appropriately and efficiently.
Sentiment and Tone Analysis: Luma VA can detect the sentiment and tone of the user's message.
It adjustsBy analyzing these elements, Luma VA adjusts its responses based on the user's emotions, ensuring a more empathetic and
suitable interaction.appropriate interaction. This ability enhances user satisfaction by making the interaction feel more personalized, helps in de-escalating potentially tense situations, and provides support that is sensitive to the user's current state.
Categorizing Requests: Based on the identified intent, Luma VA categorizes the request into one of the following:
Knowledge Request: The user is looking for information.
Problem Report: The user is reporting an issue or a problem.
Service Request: The user needs a service.
Ticket Data Search: The user searches for existing ticket information.
Handling Different Request Types
Knowledge Request
When a user seeks information:
Luma VA searches the internal Knowledge Base for relevant articles and presents the information to the user.
Luma searches the internet for relevant information if the information is not found.
Problem: These requests involve IT-related support issues, such as hardware failures, software errors, network disruptions, security incidents, service unavailability, data loss, user errors, etc. Non-IT-related issues may include facility-related problems, access control and security issues, general inquiries, telecommunications issues, equipment malfunctions, office supplies requests, travel arrangements, employee onboarding and offboarding, and more.
Data Request: The request for raw data, facts, or specific details, such as ticket information or details from any system.
Knowledge: This is a request where the user seeks precise instructions or solutions to specific topics. These may include requests for Knowledge Articles, step-by-step instructions, troubleshooting guides, frequently asked questions (FAQs), and other detailed information.
Service Request: This option is used when the user wants to request a service or place an order. It covers a wide range of requests, including IT-related support for changes in infrastructure, systems, applications, or other IT components, as well as non-IT services.
Ambiguous: This category is used when the user's request cannot be definitively deduced or interpreted from the text, necessitating further clarification to eliminate uncertainties. It applies to vague, unclear, or difficult-to-understand requests that require additional information to establish clarity.
This categorization ensures that each request is directed to the appropriate process, allowing for efficient and accurate handling of user needs.
Handling Different Request Types
...
Problem Report
When a user reports a problem:
...
Luma VA searches the internal Knowledge Base for pre-configured services and relevant articles.
The information is presented based on how confident the system is about the found information.
If information is not found in the internal Knowledge Base, the system is not confident in the search results, or the user does not like the results, fallback is triggered.
Luma VA collects the required information from the user and submits the service request to the appropriate team for action.
Knowledge Request
When a user seeks information:
Luma VA searches the internal Knowledge Base for relevant articles and presents the information to the user.
Luma searches the internet for relevant information if the information is not found.
Ticket Data Search
When a user searches for ticket information:
Luma VA uses Natural Language Processing (NLP) to understand and process the query.
It retrieves and presents relevant ticket data to the user.
User can now take further actions on their ticket based on ITSM practices configured in their system.
Ambiguous Requests
When the user’s request is ambiugous and system cannot understand the intent,
Luma prompts the user to rephrase or provide more details on their query.
In case, an unknown acronym is used in the phrase, Luma prompts the user to confirm its understanding.
System categorizes the request again and presents the information according to the new intent and category.
Managing Feedback
Luma VA captures and collects feedback from every user interaction. This feedback is essential for improving the system's accuracy and performance. Here’s how feedback is managed:
...
Info |
---|
The behavior described is fully configurable and can be updated to meet your organization's specific requirements. The above behavior represents the current Out-of-the-Box (OOTB) behavior configured in Conversation Startup skills, which can be easily customized to fit your needs. |