Read three sources and their freshness. Supply the missing pickup location.
AI-native IT service management
Useful autonomy.
Visible boundaries.
A support ticket needs more than a good answer. It needs evidence, a specific action, and someone who knows what they’re accepting.
Try one request ↘Original project · Dec 2024–Mar 2025
Contract · Project scoping, product and visual design
The original designs brought context retrieval, reply drafting and human review into a ticket workflow. Release status and measured outcomes remain unconfirmed.
Further exploration · 2026
One ticket. Every decision in view.
Synthetic public example · Local simulation · No connected systems or real permissions
a/Agent workspaceReady
Activity record 0 events
The design decisionKeep the request still.
Keep the request still.
Make the work inspectable.
The ticket anchors the conversation. The adjacent panel exposes the policy, prior attempt and asset record behind the proposal. A missing pickup location pauses the plan instead of becoming an invented fact.
Accepting a plan and running it are separate states. When execution fails, the completed research stays in place. Recovery retries one failed operation, with its original scope intact.
Accept one replacement request for LT-2048. Sending and purchasing are separate.
A missing permission blocks creation. Retain the accepted plan and retry that step.
Save RR-208 and prepare a reply. Fulfillment and knowledge publication remain open.