Support reply drafting with approval

• Input: an inbound support ticket
• AI summarizes the issue (Haiku, ~400ms)
• AI drafts a reply (Sonnet, requires approval before send)
• Human reviews + approves in /dashboard/review
• Approved reply "sent"; every step logged + Langfuse-traced

High-volume pain point, immediate workload reduction. Shows that Vocion is not just text generation — it handles control flow + human review. Every reply is traceable to the exact prompt version that produced it.

1. 1Submit a ticket via /dashboard/workflows/support_triage/run (or via chat: "Draft a reply to...")
2. 2summarize_ticket operation runs (Haiku 4.5)
3. 3draft_reply operation runs with the summary as context (Sonnet 4.6)
4. 4Workflow pauses; draft lands in /dashboard/review
5. 5Approve → "sent" envelope recorded (stub action in v0.4.0; real Gmail/Zendesk integration is the v2 ask)

vocion-demos/demos/support-reply/
  context/support-demo/
    context.yaml
    operations/
      summarize-ticket/{skill.yaml, prompt.md}
      draft-reply/{skill.yaml, prompt.md}
    workflows/
      support-triage/workflow.yaml
    sample-tickets/                # 8 realistic tickets (shipping, refund,
      T-1001-shipping-delay.md     # billing, angry escalation, thank-you, etc.)
      ...
  scripts/dev.sh                   # boots the demo on :3001

1. 1Pick a sample ticket on the workflow runner — or type your own
2. 2Watch summarize → draft stream in (each step is a Langfuse trace)
3. 3Drafts land in /dashboard/review with the full reasoning + sources
4. 4Approve → "sent" card with the rendered email body
5. 5Every reply traceable to its prompt version + cost in /dashboard/observability

The demo runs against the umbrella repo's docker-compose Postgres. Two minutes from clone to dashboard:

git clone --recurse-submodules https://github.com/vocion/vocion-local.git
cd vocion-local
./bootstrap.sh
docker compose up -d
cd vocion-demos/demos/support-reply && ./scripts/dev.sh

Sign in at https://demo.vocion.ai/sign-in — the demo creds banner autofills demo@example.com / demo123.