IT Ticket Prioritization Agent

Agent Description:

The IT Ticket Prioritization Agent template streamlines the IT service management (ITSM) lifecycle by polling external ticket sources, computing a weighted Priority Score based on downtime markers and system impact, and dynamically branching the workflow. Critical issues are immediately escalated via automated alerts to engineering teams, while standard requests are handled by a resolution engine that queries a structured knowledge base for actionable remedies.

Purpose and Components
  • Purpose: This agent is designed to automate the triage and resolution of IT support requests by analyzing ticket content, calculating urgency metrics, and routing issues to specialized response paths. It enables IT departments to handle high-volume ticket influxes by separating business-critical outages from routine troubleshooting requests.

    The agent improves operational reliability and response times by:

    • Automating the ingestion and normalization of raw ticket data from external IT sources.

    • Applying quantitative scoring logic to eliminate manual triage bias.

    • Categorizing incidents into CRITICAL and STANDARD tiers based on system impact and SLA risk.

    • Broadcasting immediate emergency alerts for high-priority outages via Slack or Teams.

    • Drafting empathetic, human-readable support responses with technical next steps for standard issues.

  • Components:

    • Ticket Data Fetcher: Retrieves raw JSON ticket batches and normalizes fields into a standardized schema (TicketID, Reporter, Subject, Description).

    • Priority Analyzer: The logic engine that assigns numerical values to Urgency and Impact to calculate a weighted Priority Score.

    • Traffic Routing Node: Acts as a logic gatekeeper, inspecting routing tags to direct the workflow toward escalation or resolution.

    • Incident Escalation Agent: Handles high-stakes issues by broadcasting alerts to emergency channels and updating ticket notes.

    • Response Architect Agent: Resolves standard issues by querying a SQLite database of remedies and providing actionable technical steps.
Supported Capabilities

  • External API polling and JSON-to-Schema normalization

  • Automated keyword extraction (Access, Connectivity, Applications)

  • Weighted Priority Scoring: S = (U × 0.4) + (I × 0.4) + (R × 0.2)

  • Downtime marker detection (for example, "cannot login", "not syncing")

  • System-based impact evaluation (Infrastructure vs. Local Endpoints)

  • Conditional workflow branching based on Routing_Tag

  • Automated SQLite database querying for technical remedies

  • Emergency broadcasting via Slack, Teams, or Email API

  • Standardized, empathetic support email drafting

LLM Used

  • OPENAI GPT_4O_MINI for the parent coordinator and all specialized triage and drafting sub-agents.

    Note: To learn more about the LLM and to modify its behavior, refer to the Configuring LLM settings section.

Sub-Agents

1. Ticket Data Fetcher Agent

  • Role:Ingestion Specialist
  • Scope:Retrieval and normalization of raw data from external IT sources.
  • Description:Executes requests_get to poll the IT ticket batch. It maps raw input fields to a standard schema and tags critical keywords (VPN, Login, Sync) to aid categorization for the next agent.

2. Priority Analyzer Agent

  • Role:Impact Logic Engine
  • Scope:Quantitative scoring and categorization of ticket severity.
  • Description:

    Assign values (1–10) to Urgency and Impact variables.

    Calculate the final score:

    S = (Urgency + Impact) / 2

    Apply tags based on the score:

    • CRITICAL if S > 8.0

    • STANDARD if S ≤ 8.0

3. Traffic Routing Node

  • Role:Logic Gatekeeper
  • Scope:Directing the workflow toward specialized resolution paths.
  • Description: Inspects the Routing_Tag without modification. Forwards CRITICAL tickets to the Escalation Agent and STANDARD tickets to the Response Architect.
  • LLM Used: Default (inherits from parent).

4. Incident Escalation Agent

  • Role:Emergency Response Automator
  • Scope:Managing high-stakes issues requiring immediate notification.
  • Description: Generates an "Incident Alert" summary for high-priority tickets. Broadcasts details to the IT Emergency channel and updates Jira notes to confirm automated escalation.
  • LLM Used: Default (inherits from parent).

5. Response Architect Agent

  • Role: Support Content Creator
  • Scope:Automated triage and user communication for standard volume tickets.
  • Description: Queries the it_remedies database using keywords. It provide 2–4 concrete next steps (for example, flushdns commands) or fallbacks to the system admin if no match is found.
  • LLM Used: Default (inherits from parent).
Tools Used:
  • Request - Get: Polls the external IT_TICKET.json endpoint for the latest support requests.
  • SQL - Toolkit: Queries a SQLite database of IT remedies to retrieve technical fix steps and action text.
Note: For details on modifying the Tools, refer Tools Library section.
Agent Workflow Behavior Summary

  1. Ingestion: The Ticket Data Fetcher pulls a batch of tickets and standardizes them (e.g., mapping issue_title to Subject).

  2. Scoring: The Priority Analyzer scans for downtime markers. A ticket with "VPN Gateway" as the reported system and "cannot connect" as the issue receives a score above 8.0.

  3. Path Divergence:

    • CRITICAL Path: Sent to the Escalation Agent for immediate Slack/Teams broadcast.

    • STANDARD Path: Sent to the Response Architect, who looks up "VPN" in the SQL database to provide fix steps.

  4. Final Output: Either an immediate broadcast alert to engineers or a human-readable support response to the user.

Sample Questions:

  • I am having issues with Duplicate Transactions can you help me with that