---
title: Q&A agent
slug: neurons-for-itsm/admin-user-help/enu/latest/qanda-agent
docTags: 
createdAt: 2026-07-14T19:16:45.871Z
---

**Minimum Version**: Ivanti Neurons for ITSM 2026.1

The Q\&A agent lets users ask questions about incidents—like checking status, viewing recent incidents, or getting details—and receive instant answers without manual navigation.

To enable and configure the Q\&A agent, do the following:

1. Log in to Neurons for ITSM as an Administrator.
2. Open the Configuration console and select **AI Configuration Hub** > **Agentic AI** > **Agent Settings**.
3. Enable the Q\&A agent using the toggle button.
4. Click **Configure** to further set up the agent.
5. From the **Select active business objects** dropdown, select the types of business objects that the Q\&A agent can respond to. You can select Incident, Service, or both for the Q\&A agent.
6. Under **Messaging** > **Max iterations**, set the number of attempts or exchanges that the Q\&A agent will undertake during a session to resolve a user's query.
7. Enable the **Allow transfer to live agent** toggle to transfer the interaction to your Service Desk Human Agent in case the Agentic AI bot cannot solve the user's request.

:::hint{type="info" indent="1"}
Along with this toggle, you must also enable the **Allow transfer to live agent** toggle in **Global Settings&#x20;**> **Escalation Handling**.
:::

8. Under **Advanced settings** > **Q\&A Description**, define the scope of the Q\&A agent by detailing the types of Q\&A the agent can handle. You can also provide some example queries related to Q\&A to help the agent better understand the context. When users ask queries other than those defined here, the agent considers them out of context and replies to users accordingly.

:::hint{type="danger" indent="1"}
Modifying the intent description might result in unpredictable agent behavior. We recommend that only users with experience in LLM prompt engineering make these changes.
:::

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/js8FLI7oT6RDtCwQ35dIk_agentic-ai-qa-settings.png" position="flex-start" size="100" width="1116" height="835" githubPath="Admin-User/Content/AITSM/images/agentic-ai-QA-agent.png" darkWidth="1116" darkHeight="835" showCaption="true" caption="Q&A agent configuration" indent="1"}

:::hint{type="info"}
Fields marked with an asterisk (\*) are mandatory.
:::

## Analytics

To view the performance metrics and usage statistics for your Q\&A agent, open the Configuration console and select **AI Configuration Hub** > Agentic AI > Agent Settings > Q\&A agent > Configure > Analytics.

The **Analytics** page provides the performance of the Q\&A agent. It helps you monitor the following metrics:

- **Number of QA Agent Interactions**: The total number of unique conversations handled by the Q\&A agent.
- **Number of QA Interactions transferred to Live Agents**: The number of Q\&A conversations that were escalated to a Live Agent.
- **QA Live Agent Transfer Rate**: The percentage of Q\&A Agent conversations that were escalated to a Live Agent.
- **Effective QA Agent Calls**: The total number of times the Q\&A Agent was triggered to process a user query.
- **Total number of Incident related messages**: The number of Q\&A search queries classified as incident-related.
- **Total number of SR related messages**: The number of Q\&A search queries classified as service request related.

:::hint{type="info"}
The Time Range filter allows users to specify the period for which analytics data is displayed. Metrics on the Analytics page are updated based on the selected time range.
:::

## Limitations

- The Q\&A agent can only inquire about the status of existing incidents and service requests. It cannot modify, update, or create a service request offering. As a result, queries such as I want to modify Service Request 14572 and I want to order a Dell printer instead of an HP printer are not supported, and the agent responds to such queries with an error message.
- Certain keywords, such as active and logged, result in null Q\&A responses. For example, Show my active service requests or Show my logged incidents and requests returns no results, whereas using alternative terms like open or submitted returns the expected list of incidents or service requests.
- During Live Agent Transfer, a conversation summary should be sent to the Live Agent at the beginning of the session. This functionality is currently not working.
- At the end of a Live Agent Transfer session, users are not informed about what to do next. However, when the session ends, the Agentic AI is reset and users should initiate a new prompt, even if no live agent was available.
- The Agentic AI handles only IT‑related issues. Other Line of Business (LoB) queries, such as HR, Facilities, and other non‑IT requests are not supported.
