Ask a sales team why they distrust an automated assistant and the answer is rarely “it gives wrong answers”. It is “I don’t know when it will hand things to me”. Escalation rules fix that. Written well, they tell the agent exactly when to stop, tell the team exactly what to expect, and make the whole system predictable.
Start from moments, not from technology
Gather three people who handle enquiries and ask one question: “When would you want to be pulled in immediately?” Write down the moments they describe in their own words—an angry customer, a budget over a certain size, someone asking about a refund, a question about a medical condition. Those moments are your first rules.
Make each rule specific and testable
A rule such as “escalate complex questions” cannot be tested. Rewrite it until a colleague could look at a conversation and say whether the rule should have fired. Compare:
- Vague: “Hand over if the customer seems unhappy.” Specific: “Hand over when the customer mentions a complaint, a refund, a previous bad experience, or uses the word ‘unacceptable’.”
- Vague: “Escalate big deals.” Specific: “Notify the sales director when the stated budget exceeds €1,000,000 or the customer represents a company with more than 200 staff.”
- Vague: “Don’t give medical advice.” Specific: “If the customer describes symptoms, asks whether a treatment is suitable for them, or mentions medication, reply with the approved safety message and hand over to clinical staff.”
Cover the four standard triggers
- The customer asks for a person. Always honoured, always immediately.
- Low confidence. The agent cannot find an approved answer; it says so and hands over rather than guessing.
- A business trigger. Value, urgency, sector-specific risk, or a request outside the agent’s permissions.
- A safety trigger. Any sign of distress, emergency or harm gets a clear message and a human, every time.
Decide what travels with the handoff
The handoff is only useful if the colleague can act without asking the customer to repeat themselves. Define the summary: who the customer is, what they asked, what was captured, what the agent already said, and why the rule fired. Decide the channel—email, team chat, a shared inbox, a phone call for emergencies—and the expected response time. Then tell the customer what will happen next, in one honest sentence.
Test the rules before launch, then keep score
Write one test conversation per rule and run it in test mode. Failed tests are fixed, not waived. After launch, review a sample of handoffs each week: were they necessary, were they timely, did anything slip through? Adjust thresholds and wording, version the rules so every change is traceable, and share the numbers with the team. Trust grows from seeing the rules work.
A good escalation rule is one your most sceptical colleague would sign.