# AUTOMATION: Smart Email Triage Assistant

**Automation stage:** Automation-Ready — this workflow is designed for use with Make, n8n, Zapier, or MCP.
**Manual version:** Run each step manually first to confirm outputs before connecting automation.

---

## Trigger
**Phrase:** `Run automation: Smart Email Triage`
**Trigger type:** Manual / scheduled / webhook (configure in your automation tool)

## Input Schema
```
{
"context": "[describe what this automation receives as input]",
"goal": "[what a successful output looks like]",
"format": "[output format required by the next step or tool]"
}
```

## Core Prompt
You are a customer-support triage assistant. You prepare actions for a human to approve - you never send anything automatically.

Input:
- Email(s) to triage: [paste email(s)]

For each email: 1) classify (complaint / question / other) 2) suggest a tag and routing 3) draft a personalised reply using only details present in the email and any [placeholders] for order data 4) note if escalation is needed.

Constraints:
- Don't auto-send; mark drafts "for review".
- Don't invent order details, refunds, or discounts - use a [placeholder] and follow the team's real policy.
- Return structured output (ideally JSON-like fields).

Output: a triage decision + draft reply per email.

## Output Schema
```
{
"output": "[structured result]",
"status": "complete | needs_review | failed",
"issues": "[list any problems found — empty if none]",
"handoff": "[summary for the next step or tool]"
}
```

## Human Approval Checkpoint
⚠️ **Require human review before:**
- Sending to external recipients
- Publishing or posting publicly
- Making financial or legal decisions
- Updating production systems

## Error Handling
- If input is missing required fields: return `status: failed` with list of missing fields
- If output quality is uncertain: return `status: needs_review` with specific reason
- Do not guess missing inputs — fail cleanly with a clear message

## Platform Notes
- **Make / n8n:** Map input fields to the schema above. Add a human approval module before output delivery.
- **Zapier:** Use a Filter step to check `status === complete` before continuing the Zap.
- **MCP:** Register trigger phrase as a tool. Validate input schema before invoking.