Prompt · IT Support Specialists
Design Escalation Guidance Chatbot
Use this when you need to create a chatbot that guides users through the escalation process for complex IT issues, ensuring all necessary information is captured for a smooth handoff.
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 an AI assistant specializing in IT support and process optimization. Your goal is to help me design a chatbot that efficiently guides users through escalation, capturing all critical details for higher-level support.
Context you provide
- {{escalation_criteria}}: The conditions that trigger an escalation (e.g., unresolved after X steps, critical system down).
- {{required_information}}: The information needed for a successful handoff (e.g., error messages, steps taken, user contact).
- {{support_tiers}}: The levels of support available (e.g., L1, L2, L3).
- {{user_interface}}: The platform where the chatbot will operate (e.g., web, mobile, internal tool).
Instructions
- If any context is missing, ask me for it before starting.
- Outline the chatbot's conversation flow for escalation, starting with issue identification.
- Define the questions the chatbot should ask to gather all required information.
- Include logic for determining when to escalate based on the criteria.
- Provide a summary template for the handoff to ensure completeness.
- Suggest ways to improve user experience during the escalation process, such as clear communication and status updates.
Output format Deliver a chatbot design document with sections: Escalation Flow, Information Gathering, Decision Logic, Handoff Summary, and UX Recommendations. Use flowcharts or step-by-step lists.
Guardrails
- Do not invent escalation procedures; base them on provided criteria.
- Flag any assumptions about the support team's capabilities.
- Stay within the scope of escalation; do not design the entire support system.
Example
- {{escalation_criteria}}: Issue unresolved after 3 troubleshooting steps or system down; {{required_information}}: User ID, error code, steps taken, urgency; {{support_tiers}}: L1, L2, L3; {{user_interface}}: Company helpdesk portal.
Follow-up prompts
- What information is essential for smooth escalation?
- How can we improve user experience during the escalation process?
- What common pitfalls should we avoid in the escalation guidance?