AI & Workflow Orchestration Glean · Confluence · Jira

Help Desk Request
Orchestration Agent

One conversational entry point for 9 service desks and 120+ request types. From an employee’s question to grounded help or a validated Jira ticket.

96%Routing Accuracy
120+Request Types
15 minSaved / Request
Business Challenge

Requests were spread across 9 service desks, each with up to 8 portal groups. Submitting requests was trial-and-error, with users having to navigate various service desks before work could even begin.

Technical Challenges

The team’s agent prototype had stalled for multiple years due to three main failure points: Inconsistent routing, Unsupported JSM ticket creation, and Ungrounded deflection.

Design Decisions

01

Inconsistent Routing

Semantic matchingRouting Tables

A 2-Layered routing engine replaced semantic matching, sending each request to the right request type with 96% accuracy across 9 service desks.

02

Brittle Integration

Static REST payloadLookup Table

MCP reads required JSM fields at runtime, creating each issue type with the right custom fields without manual payload upkeep.

03

Ungrounded Deflection

Web searchTagged knowledge base

RAG checks a curated, tagged knowledge base first, surfacing relevant self-serve answers before creating a ticket.

AI Help Desk Agent System FlowColor-coded workflow showing Glean conversation, Confluence RAG lookup, and Jira Service Management issue creation.Source systemGleanConfluenceJiraYesNoYesNoYesNoEmployee StartsChatContext CaptureSubject and descriptionMapping TableIssue keyword matchingConfident Match?Follow-Up QuestionsAgent asks targeted questionsIssue TypeResolvedRAG LookupSearch grounded knowledge baseSelf-Serve ArticleFound?Present ArticleUser Satisfied?Self-ServiceResolvedMCP QueryIssue type required and custom fieldsPopulate PayloadMapped valuesUser ValidationConfirm ticket detailsIssue Created
  • One Front Door

    Employees describe the problem instead of navigating service desks and portal groups.

  • Knowledge Before Escalation

    Relevant articles support self-service and accompany requests that still need help.

  • Less Manual Upkeep

    Runtime field discovery keeps ticket creation aligned with Jira’s current requirements.