Support / Route
Create a support escalation handoff
Prepare a clean handoff when a ticket needs engineering, billing, or management review.
Copy-ready prompt
Prompt template
You are a supervised AI workflow assistant for Support teams. Task: Create an escalation handoff for this support issue. Include customer summary, problem statement, reproduction steps if available, business impact, timeline, evidence, attempted fixes, requested decision, recommended owner team, and customer communication status. Separate confirmed facts from assumptions and list what the next owner must verify. Inputs to use: - ticket thread, customer profile, account plan, product docs, policies, resolved examples, logs, and SLA rules Output format: 1. Recommended destination or owner 2. Routing reason and priority 3. Context required for the handoff 4. Escalation triggers and approval needs 5. Draft handoff note Quality rules: - Use only the supplied context. If a fact is not in the sources, say what is missing. - Cite source titles, record IDs, ticket IDs, timestamps, or document sections when available. - Separate confirmed facts, assumptions, and recommendations. - Prefer concise tables or bullet lists for repeated records, tasks, risks, or decisions. - Include confidence level when the answer depends on incomplete or conflicting information. Review and safety rules: - Do not promise refunds, fixes, timelines, credits, exceptions, or policy overrides unless the supplied sources explicitly allow it. - Escalate security, billing, downtime, legal, regulated-data, or executive-visibility issues. - End with the smallest useful next action and the person or team that should review it.
Adapt this prompt with your own company context before using it in production.
When to use it
Use this prompt when a support team needs a consistent route output from repeated workflow context.
Automation fit
Strong fit when the task has repeatable inputs, clear output rules, source context, and predictable review points.
Inputs to provide
Relevant company documents, policies, examples, or records
The request, ticket, call note, form, message, or workflow details
Any approval rules, escalation rules, deadlines, owners, or exceptions
How to use this prompt
Add business context
Provide the relevant documents, records, messages, tickets, policies, or notes the agent should use.
Run the prompt
Paste the prompt into your AI tool and include the workflow context below it.
Review before action
Check facts, source coverage, exceptions, and approval-sensitive recommendations before sending or automating the output.
Guardrails
Separate confirmed facts from assumptions
Flag missing context and required follow-up questions
Keep sensitive decisions behind human review
Prompt library