### Prompt – Automated Support Agent Workflow Blueprint
**Context**
- **Industry / domain** (e.g., SaaS, e‑commerce, fintech): {{domain}}
- **Primary support channel** (e.g., email, chat, ticketing): {{channel}}
- **Key compliance framework** (e.g., GDPR, HIPAA): {{compliance}}
- **Tools to integrate** (comma‑separated, e.g., Zendesk, GitHub, Slack): {{tools}}
- **Typical request categories** (list 3‑5): {{categories}}
- **Escalation threshold** (e.g., after 2 failed attempts or sentiment < 0.3): {{escalation}}

**Task**
1. Assume the role of a senior support engineer.
2. Produce a **Standard Operating Procedure (SOP)** in markdown with sections:
   - `## Overview`
   - `## Integrated Tools`
   - `## Request Handling Flow`
   - `## Compliance & Logging`
   - `## Escalation Triggers`
   - `## Monitoring & Metrics`
3. Generate a **JSON configuration** that a workflow engine could ingest, containing:
   ```json
   {
     "domain": "{{domain}}",
     "channel": "{{channel}}",
     "compliance": "{{compliance}}",
     "tools": [{{tools_json}}],
     "flow": [{"step": "...", "action": "..."}],
     "escalation": "{{escalation}}",
     "metrics": ["response_time", "resolution_rate"]
   }
   ```
4. Append a **Quality Checklist** (5 items) to ensure the blueprint meets security and reliability standards.

**Quality Bar**
- SOP must be concise (< 1500 words) and fully actionable.
- JSON must be **valid** and pass a schema validation test.
- All compliance steps must reference the named framework.
- Include at least one **fallback to human** trigger.

**Constraints**
- Do not reference proprietary internal APIs.
- Keep language neutral; avoid vendor‑specific jargon unless listed in `tools`.
- Return **only** the markdown SOP followed by the JSON block and checklist.