Administrative Inbox Routing with Claude Code: Result JSON Schema
A production playbook for administrative inbox routing in administrative operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Back-office administrative teams
The problem
Back-office administrative teams need administrative inbox routing to run repeatedly against emails, attachments, sender metadata, policy rules, and routing labels. In administrative operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Define the outer result contract once, let the administrative inbox routing skill own body.data, and reject terminal output that does not match the expected schema.
Tradeoffs and failure modes
Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For administrative inbox routing, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Result shape
{
"schema_version": "argo.result.v1",
"summary": "administrative inbox routing completed",
"body": { "type": "admin_inbox_routing", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo