Zia Agents

Zia Agents are AI-powered assistants that understand user queries, retrieve relevant information, and assist with actions. You can customize agents for your organization by configuring the required knowledge base articles and tools. These configurations define what information an agent can access, which service desk events it can observe, and how it will respond to user queries.

Zia Agents can be accessed through Ask Zia, the conversational bot.

Benefits

Optimize service desk operations by reducing manual effort for technicians, improving response accuracy, and enabling faster issue resolution.

Role Required: SDAdmins

Quick Links

 

Create Agents

Enable Custom Agents

  1. Go to Setup > Zia > Agents.

  2. If you are accessing for the first time, click Create Agents.

 

  1. Otherwise, enable Custom Agents and click Manage Agents.

You will be directed to the Zia Agent Studio.

Prerequisites

Before creating an agent, configure the following:

 

Tools

Tools are APIs that allow agents to perform specific actions.

 

Knowledge Base

The knowledge Base is a centralized repository of articles, FAQs, and documents that agents use to respond and take action.

 

 

Agent Studio

Agents can be created manually from scratch or with assistance from Zia AI.

 

Create Agents From Scratch

 

Basic Information

Provide the following details:

 

Knowledge Base

 

 

Tools

 

Additional Settings

 

 

Create Agents with Zia AI

 

 

Deploy Agents

Deployed agents are available under Setup > Zia > Agents.

 

Configure Agent Accessibility

After deployment, configure who can access each agent.

  1. Go to Setup > Zia > Agents.

  2. Use the toggle to enable or disable the agent for technicians and requesters.

  3. When enabled, the agent is available to all technicians and requesters, by default.

  4. To restrict access:

 

 

List View Operations

 

 

Access Zia Agent from Ask Zia

 

Ask Zia executes the requested action by using Zia Agents.

 

Use Cases

PIR Generator Agent

Creating post-incident reports (PIR) for major incidents can be time-consuming. The PIR Generator Agent simplifies this by automatically generating a structured report from a ServiceDesk Plus ticket by using the ticket ID.

The agent fetches ticket details and produces a comprehensive report covering the incident summary, timeline, root cause analysis, impact assessment, action items, and lessons learned.

Configure the PIR Generator Agent

Here are the step-by-step instructions to configure the PIR Generator Agent.  

Prerequisites

Before creating the agent, configure the following tools in Zia Agent Studio:

Tool

Purpose

GetTicketID

Retrieves the internal ticket ID from the display ID provided by the user.

getTicketDetails

Retrieves complete ticket details by using the internal ticket ID.

 

Create YAML files and add the following APIs to fetch the ticket ID and ticket details.

GetTicketID API

openapi: 3.0.1
info:
  title: Get Ticket Id
  description: >
    Retrieves requests using search criteria. To search by display_id:
    take the user-provided display_id value and construct the input_data
    query parameter as a JSON string.
  version: 1.0.0
servers:
  - url: https://sdpondemand.manageengine.com
    description: Production Server
security:
  - OAuth2:
      - SDPOnDemand.requests.ALL
paths:
  /app/{portal}/api/v3/requests:
    get:
      summary: Get Ticket Id
      operationId: GetTicketID
      parameters:
        - name: portal
          in: path
          required: true
          schema:
            type: string
        - name: input_data
          in: query
          description: >
            A JSON string containing list_info with search_criteria.
          required: true
          schema:
            type: string
            example: '{"list_info":{"search_criteria":[{"field":"display_id","condition":"is","value":"1042"}]}}'
      responses:
        "200":
          description: Requests retrieved successfully.

 

GetTicketDetails API

openapi: 3.0.1
info:
  title: Get Complete Ticket Details
  description: >
    Retrieves complete details of a request/ticket using its internal ticket ID.
    This is NOT the display_id shown to users.
  version: 1.0.0
servers:
  - url: https://haarvi.sdpondemand.manageengine.com
    description: Production Server
security:
  - OAuth2:
      - SDPOnDemand.requests.ALL
paths:
  /api/v3/requests/{ticket_id}:
    get:
      summary: Get Complete Ticket Details
      operationId: getTicketDetails
      parameters:
        - name: ticket_id
          in: path
          description: The internal numeric ID of the ticket (e.g. 106556000006930024)
          required: true
          schema:
            type: string
      responses:
        "200":
          description: Ticket details retrieved successfully

Create Tools

  1. Go to Tools.

  2. Click New Tool Group.

  3. Provide name for the tool group.

  4. Under Schema, select Predefined Service and upload the YAML files.

Create the Agent

  1. Go to Setup > Zia > Agents.

  2. Enable Custom Agents and click Manage Agents. You are directed to the Zia Agent Studio.

  3. Click Create From Scratch.

Basic Information

 

Field

Value

Agent Name

PIR Generator

Agent Description

Generate a post-incident report from the ticket data

Model Configuration

Zoho

Model

Qwen Text 30b MOE

Agent Role

PIR Generation Specialist

Agent Instructions

Instructions to guide the agent are provided in the PDF.
Copy and paste them into the Agent Instructions field.

 

 

 

Knowledge Base

Upload relevant knowledge base articles to guide the agent. Click Continue.

Tools

 

Additional Settings

The PIR Generator agent is now ready to use.

How to Use the PIR Generator Agent

  1. Go to Ask Zia.

  2. Click Zia Agents.

  3. Provide the instruction to generate PIR.

For example:

  1. The agent fetches the ticket details and generates the PIR automatically.

PIR Output

The generated report includes the following sections:

Section

Description

Incident Summary

Overview of the incident, including subject, category, priority, and status

Timeline

Chronological sequence of events from detection to resolution

Root Cause Analysis

Underlying cause of the incident based on ticket data

Contributing Factors

Factors that amplified the incident

Impact Assessment

Incident duration, affected users or services, and SLA breach status

What Went Well

Positive aspects such as detection speed and response coordination

What Needs Improvement

Gaps in detection, escalation, or process failure

Action Items

Follow-up tasks derived from the resolution and ticket data

Lessons Learned

Takeaways to improve future incident response


If ticket summary is unavailable in the ticket, the agent generates the PIR by using the remaining available data.