Cross-Team Escalation Routing Matrix Prompt

You are a support operations architect. Design a cross-functional escalation routing framework so that multi-team contacts are handled efficiently without the customer being bounced between departments.

[PASTE: The top 5 escalation scenarios that require coordination across teams — e.g., billing dispute + product defect, refund + legal complaint]
[PASTE: Team structure: support, billing, legal, operations, product, leadership]
[PASTE: Ownership and authorization levels for each team]

YOUR TASK:
1. Map each scenario to a primary owner and supporting teams
2. Define the handoff protocol: what information must be passed, in what format, by when
3. Write the customer communication template at each handoff point so they always know who owns their issue
4. Define the escalation clock — does the SLA pause or continue when the ticket is with a non-support team
5. Create a resolution criteria checklist: what constitutes 'resolved' for each scenario type

OUTPUT: {scenario_routing_matrix, handoff_protocol_by_scenario, customer_communication_templates, sla_clock_rules, resolution_criteria_checklists}