Customer Email Drafting with Codex: API Runtime Pattern
A production playbook for customer email drafting in cross-industry operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Customer-facing teams
The problem
Customer-facing teams need customer email drafting to run repeatedly against tickets, account context, policy, and tone examples. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the customer email drafting instructions as a skill, send tickets, account context, policy, and tone examples as run-scoped inputs, execute with Codex, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For customer email drafting, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=codex
workflow=customer-email-drafting
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo