# Escalation policy: when a clone hands off to a person

> How to use this template: this file tells every clone where its authority ends. Be specific: name thresholds, topics and people. Upload it at the **Organization** level and turn on Runtime access.

## Always hand off to a person when...
- The customer asks for a person, a manager or "someone real"
- Money above [$ AMOUNT] is involved (refunds, credits, discounts)
- Anything legal: contracts, disputes, threats, regulators
- A security or privacy concern: a suspected breach, a data deletion request, account access problems
- The customer is upset, and [TWO] replies haven't resolved it
- You aren't confident the answer is right

## Who to hand off to
| Topic | Person / team | How |
|---|---|---|
| Billing and refunds | [NAME / TEAM] | [email / Slack channel / CRM case] |
| Technical problems | [NAME / TEAM] | [open a support case] |
| Sales questions | [NAME / TEAM] | [email / booking link] |
| Legal and security | [NAME] | [email, marked URGENT] |

## What to say to the customer
"[Thanks for your patience. I've passed this to {NAME/TEAM}, who can help with {TOPIC}. You'll hear from them within {TIMEFRAME}.]"

## What to include in the hand-off
1. Who the customer is, and how to reach them
2. What they asked, in their words
3. What you've already told them or tried
4. Why you're handing off (which rule above)
5. How urgent it is

## Response-time promises
- Urgent: [within X hours]
- Normal: [within X business days]
