Customer Support Reply Workflow

Prompt

Run the Customer Support Reply Workflow for the goal below.

Goal: Triage a general support request, give a verified answer when authorized, or route it to the right human owner.

Inputs (replace each placeholder with verified information):
- User request and safe contact channel: {{add verified input}}
- Account, order, or submission reference if relevant: {{add verified input}}
- Verified status and source of truth: {{add verified input}}
- Current policy or support runbook: {{add verified input}}
- Severity, data sensitivity, and authorized actions: {{add verified input}}
- Escalation owner and response condition: {{add verified input}}

Method:
1. Confirm the request and collect only the minimum information needed; never ask for passwords, secret keys, or full payment data.
2. Classify topic, urgency, user impact, privacy or security sensitivity, and whether identity verification is required.
3. Check the authorized source of truth; separate confirmed status from unknowns and do not diagnose beyond available evidence.
4. Write a plain-language reply with what is known, needed, allowed, and the next action or update condition.
5. Take only documented reversible actions and log them; escalate security, privacy, payment, legal, safety, access-loss, or policy exceptions to the named owner.
6. Require human approval for consequential actions and close only when the acceptance condition is confirmed; otherwise retain an owner and state.

Return exactly these reviewable outputs:
- Triage category, severity, and evidence
- Support reply and minimum missing-information list
- Action or escalation log with owner
- Resolution acceptance or next-update condition

Human review boundary: This is general triage, not specialist, medical, legal, financial, or security advice. Do not expose sensitive data, bypass identity checks, or promise outcomes or timelines not confirmed by the responsible owner.