Email Intake Routing with Claude Code: Result JSON Schema

A production playbook for email intake routing in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Shared inbox and intake teams

The problem

Shared inbox and intake teams need email intake routing to run repeatedly against email bodies, attachments, sender metadata, and routing rules. In cross-industry 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 email intake 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 email intake 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": "email intake routing completed",
  "body": { "type": "email_intake_routing", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo