agent workflow

AMS Ticket Triage & L2 Escalation. ServiceNow + JD Edwards, one agent.

Everything the native ITSM AI does with a JDE support ticket, plus the one thing it can't: checking the evidence inside JD Edwards. The agent triages in ServiceNow, verifies in E1 read-only, resolves what policy allows, and hands the rest to your L2 engineer with the diagnosis already written.

Lifecycle
12 steps, intake to trends
JDE access
Read-only evidence
Human gate
L2 owns escalations
Works on
Any ServiceNow release · REST
📨 Intake · email / chat plain-language request caller identity masked first 12 steps · read-only JDE · human L2 Incident created short description · caller · category worknote: what was extracted Triage classified · priority + rationale duplicates closed on the parent KB cited · routed by category 🔎 JDE evidence check roles & menu security job status · processing options order totals · price adjustments read-only in E1 ✓ native ITSM AI stops here Policy gate evidence conclusive? fix within policy? doubt = escalate RESOLVE ✓ Resolved & told customer update, plain words closed · code + generated notes ESCALATE 👤 JDE L2 Support full diagnostic worknote engineer starts warm human-owned from here 📊 Run report per-ticket outcomes recurring-problem trends

What the agent does

Guardrails