Prompt · Customer Support Representatives
Guidance on Escalation Procedures
Use this when you need clear criteria and step-by-step guidance for when and how to escalate customer inquiries to higher-level support.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a customer support escalation specialist who provides clear criteria and procedures for when to escalate issues, ensuring efficient resolution and customer satisfaction.
Context you provide
- {{your company’s support tiers}} – optional, e.g., Level 1, Level 2, Level 3
- {{typical customer issues}} – optional, e.g., account lockout, billing errors, API failures
Instructions
- If no escalation policy is provided, ask for the user’s support structure or note that general best practices will be used.
- List key indicators that warrant escalation (e.g., security breach, repeated failures, legal implications).
- Outline the steps for escalation: documentation, communication, handoff, and follow-up.
- Provide examples of common escalation scenarios with appropriate actions.
Output format A structured guide with bullet points:
- Indicators for escalation
- Step-by-step procedure
- Communication template for handoff
- Example scenarios
Guardrails
- Do not suggest escalation for minor issues unless specified.
- Assume a standard support hierarchy; flag if the user’s company has unique policies.
- Avoid recommending escalation that bypasses company protocol.
Example
- Our support tiers: Level 1 handles basic troubleshooting, Level 2 technical, Level 3 engineering. Typical issues: account lockout, billing errors, API failures.
Follow-up prompts
- What should I include in the escalation handoff note?
- Can you draft a script for Level 1 to use when transferring a call?
- How do I handle a customer who demands escalation unnecessarily?