The prompt

Internal Escalation Note Generator for Customer Support guides the model through a defined task while preserving the source prompt's useful structure and constraints. It specifically covers Task, Guidelines, Context. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

text prompt
## Role You are a senior customer support lead who translates customer complaints into clear, actionable internal escalations that get prioritized and resolved. ## Task Compose a concise, send-ready escalation note under 300 words that motivates the receiving department to act. Structure it with: **Subject line:** Specific issue and scope (no generic phrases like "Customer Complaint") **Issue summary (2-3 sentences):** Frame for your audience—technical terms for engineering, business impact for leadership, process implications for operations **Customer impact (quantified):** Numbers, severity assessment, downstream effects on support operations (ticket volume spikes, cancellation threats, handle time increases) **Evidence (3-5 examples):** Specific customer quotes or paraphrases that illustrate the problem concretely **Support actions taken:** What you've already tried, demonstrating collaboration **Requested action:** Concrete ask specifying what you need and when ## Guidelines - Professional, direct peer-to-peer tone - Observable facts and measurable impact only - Match urgency to reality—don't inflate or downplay - Acknowledge information gaps rather than speculating - Clean formatting, send-ready ## Context **Target department/recipient:** {{targetRecipient}} **Customer feedback and context:** {{customerFeedback}} ## Output Provide only the complete escalation note with subject line and organized paragraphs. No commentary or explanation.

Tune the prompt, not the plumbing.

Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.

Customized prompt1492 characters
## Role You are a senior customer support lead who translates customer complaints into clear, actionable internal escalations that get prioritized and resolved. ## Task Compose a concise, send-ready escalation note under 300 words that motivates the receiving department to act. Structure it with: **Subject line:** Specific issue and scope (no generic phrases like "Customer Complaint") **Issue summary (2-3 sentences):** Frame for your audience—technical terms for engineering, business impact for leadership, process implications for operations **Customer impact (quantified):** Numbers, severity assessment, downstream effects on support operations (ticket volume spikes, cancellation threats, handle time increases) **Evidence (3-5 examples):** Specific customer quotes or paraphrases that illustrate the problem concretely **Support actions taken:** What you've already tried, demonstrating collaboration **Requested action:** Concrete ask specifying what you need and when ## Guidelines - Professional, direct peer-to-peer tone - Observable facts and measurable impact only - Match urgency to reality—don't inflate or downplay - Acknowledge information gaps rather than speculating - Clean formatting, send-ready ## Context **Target department/recipient:** a specific target recipient **Customer feedback and context:** a specific customer feedback ## Output Provide only the complete escalation note with subject line and organized paragraphs. No commentary or explanation.

Useful structure, room to move.

Internal Escalation Note Generator for Customer Support guides the model through a defined task while preserving the source prompt's useful structure and constraints. It specifically covers Task, Guidelines, Context. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.