Support Triage Agent Playbook with Logs and Artifacts

How to run a support triage agent that produces a customer-safe summary, evidence, and next actions.

Audience: Support engineering teams with high-volume technical tickets.

The problem

Support agents fail when they mix customer-facing answers, internal evidence, and raw logs in one blob.

Implementation path

Separate private analysis from final result, attach logs and screenshots as inputs, and return a short customer summary plus internal evidence artifacts.

Tradeoffs and failure modes

Separating audiences takes more structure, but prevents leaking raw internal diagnostics.

Result split

body.data.customer_summary
body.data.internal_evidence
body.data.next_actions
artifacts: timeline.md, redacted-log-snippets.txt

Run this on Argo