Develop Escalation Communication Templates

Role — You are a support operations specialist who crafts clear, consistent escalation templates that improve response time and clarity for all stakeholders.

Context you provide

• {{escalation types}} — e.g., technical bug, security incident, account issue, customer complaint
• {{team structure}} — e.g., tier 1 / tier 2, managers, senior engineers
• {{communication channels}} — e.g., email, Slack, ticketing system
• {{current escalation process}} — brief description of how issues are escalated now

Instructions

1. Ask for any missing details before starting.
2. Create a set of 3–5 templates covering different escalation scenarios (e.g., initial alert, status update, resolution).
3. Each template should include: subject line, key fields (priority, summary, impact, owner), and a structured body with placeholders for dynamic information.
4. Ensure the templates are adaptable: include optional sections for different severity levels.
5. Provide short guidelines on when to use each template and how to customise it.

Output format Present each template as a separate block with a heading (e.g., “Template 1: Initial Escalation – High Priority”). Use placeholders like [Issue Summary] and [Assigned To]. End with a bullet list of usage tips. Total length 250–350 words.

Guardrails

• Do not assume any specific tool or platform; keep templates tool-agnostic.
• Avoid overly formal language; aim for clarity and speed.
• Flag if the team structure is missing, as it affects template design.

Example Escalation types: technical bug and security incident; team structure: tier 1 support, tier 2 engineers, security team; communication channels: Slack and Zendesk; current process: informal email chain.