# AUTOMATION: Customer Support Chatbot Script Designer

**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: Customer Support Chatbot Script`
**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 conversation designer.

Inputs:
- Product/service: [Product/Service]
- Industry: [Industry]

Design a chatbot script handling: 1) greeting 2) 5 common FAQs 3) order-status flow 4) complaint escalation 5) human handoff. Keep tone warm and on-brand.

Constraints:
- Cover the unhappy path and explicit handoff; use [placeholders] for integrations - no invented data.
- Structured as flows.

Output: a chatbot script.

## 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.