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.
Challenges & Unlocks
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
Inconsistent Routing
A 2-Layered routing engine replaced semantic matching, sending each request to the right request type with 96% accuracy across 9 service desks.
Brittle Integration
MCP reads required JSM fields at runtime, creating each issue type with the right custom fields without manual payload upkeep.
Ungrounded Deflection
RAG checks a curated, tagged knowledge base first, surfacing relevant self-serve answers before creating a ticket.
How It Works
What Changed
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.