Write an escalation email
Writes an escalation to a manager, vendor or another team that states the issue, its impact, what was already tried and the specific decision or help needed by a date, without blame.
An escalation asks someone with more authority or reach to unblock something you cannot unblock yourself. It works when the reader can act on it in two minutes: the ask and deadline are at the top, the impact is concrete, the history shows you made reasonable attempts, and the tone is factual rather than accusatory. It backfires when it is a complaint about a person, when it skips the people directly involved without warning them, when the ask is vague ("please help"), or when it arrives as a surprise to someone who will be embarrassed by it.
Write an escalation email. Only if [RECIPIENT] is given: Recipient:
Only if [HISTORY] is given:
- If you cannot tell what is blocked, the impact, or what the recipient could do about it, ask up to three short questions and stop.
- Check whether escalation is the right move now: has the direct owner been asked clearly, with a deadline, and told the matter would be escalated? If not, say so in "Check before escalating" and include a one-paragraph heads-up message to the direct owner first. Still write the escalation, ready for later.
- Define the ask precisely: a decision (choose A or B), an action (assign an engineer, approve spend, call the vendor), or a priority call, with a date and the reason for that date.
- Write the email:
- Subject line: "[Decision/Help needed by date]: short issue".
- First two lines: the ask, the deadline and the impact if nothing changes.
- Context in three to five bullets: what is blocked, since when, impact in numbers where the facts allow, and who is affected.
- What has been tried, as a short dated list, stated neutrally.
- Options if helpful, with your recommendation.
- A closing line offering a 15-minute call and stating what you will do in the meantime.
- Recommend who to copy and who must be told before sending.
- Factual and neutral: describe actions and results, not people's character or motives. No sarcasm, no "per my last five emails".
- Use only facts from the input; mark missing figures or dates
[NEEDED: …]. - Keep the email under about 250 words; put long threads in an attachment or link, not in the body.
- For a vendor, refer to the contract or service level only if the input mentions it, and do not threaten legal action unless the user says that is the intent.
- If the issue involves harassment, discrimination, safety or a possible legal breach, say that the right channel may be HR, a safety officer or legal rather than a normal escalation.
Check before escalating
Whether the direct owner has been given a fair chance, and the heads-up message if one is needed. "Ready to escalate" if so.
Escalation email
Subject line and the email.
Notes
Who to copy, who to tell first, [NEEDED: …] items, and when to follow up if there is no answer.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- level
- Beginner
- made for
- Project / program manager, People manager, Anyone, personal use, Operations
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install write-escalation-email --target claude-codenpx skills add hermes-hq/hodios-dist --skill write-escalation-email -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-writing-communication@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of EmailWrite a follow-up to an unanswered email
Writes a polite follow-up to an unanswered email that adds new context, makes the ask easier to answer and sets a gentle deadline, in three escalation levels from nudge to final note.
write-follow-up-emailWrite a decision memo
Writes a one-page decision memo with the decision needed and by when, context, options with honest trade-offs, a recommendation and next steps. Use when asking a manager to approve something.
write-decision-memoWrite a project status report
Writes a project status report with an evidence-based RAG status, progress, risks, decisions needed and next steps, formatted as an email, a document or a single slide.
write-status-reportDecline a request gracefully
Declines a request or invitation clearly and kindly in the first lines, gives an honest brief reason if wanted, offers only real alternatives and preserves the relationship.
decline-request-gracefullyReply to an email
Drafts a reply that answers every question and request in a received email from your stated position, matches its formality, proposes next steps and flags points you have not decided.
reply-to-emailTriage an inbox
Sorts a batch of emails into reply, delegate, schedule and archive by your priorities, flags suspicious messages, and drafts the short replies and delegation notes.
triage-inbox