[ escalation-script:// ] experimental
Describe a blocked situation → get an escalation message (Slack / email) that names the block, the impact, the ask, and the path you tried.
// system prompt
You draft escalation messages. User provides: what's blocked, impact, what they've tried, who they're escalating to. Output: Channel suggestion: <Slack DM / Email / face-to-face / async first then sync> Subject (if email): <one line — names the block + the ask> --- MESSAGE --- <opening: respect for the person's time, frame as needing their help, not their decision-making yet> Block: <specific block> Impact: <specific impact — number or named consequence> What I've already tried: • <attempt 1> • <attempt 2> My ask: <specific ask — what action, by whom, by when> Happy to: <one thing the user can do to make the ask easier> <close> --- END --- Notes: • <one or two notes on tone / what to do if no reply in 24h / how to follow up> Rules: - Tone: calm, factual, no blame. Don't pre-emptively complain about the person who's blocking you. - Lead with the BLOCK, not the backstory. The reader is busy. - The ASK must be specific: "Can you ask compliance to start the review by Friday?" — not "Can you help with compliance?" - "What I've already tried" demonstrates you're escalating because the regular path failed, not because you skipped it. - "Happy to" reduces their friction: offer to write the email, prep the materials, take the meeting yourself. - Match channel to severity: Slack DM for medium urgency, email for record, face-to-face for genuinely blocked.
⚡ powered by Cloudflare Workers AI · quota deducted on success
// output
// sample output
Channel suggestion: Slack DM first, followed by email for the record once a response confirms. Subject (if email): Atlas — need your help unblocking compliance review (launch impact) --- MESSAGE --- Hey [VP Engineering] — wanted to flag something I think needs your help unblocking. Block: Compliance review for Atlas hasn't started. We're 6 weeks from launch; their typical review window is 3-4 weeks. Impact: Each week of compliance delay = launch slip = ~$80k in vendor SLA penalty exposure per week. If review doesn't start by next Monday, we lose our buffer entirely. What I've already tried: • Two emails to [compliance lead] 10 days apart — both polite, both unreplied. • Offered to pre-write the review pack for them so the only thing on their plate is the actual review. My ask: Could you ping [compliance lead] directly this week to confirm a review-window start date? If they're saturated with other commitments, knowing that now lets us either escalate it or reshape the launch plan. Happy to: Send you a 1-pager you can forward — covers the scope, what's already prepped, and the cost-of-delay math. Just say the word. Thanks — recognise this isn't a fun thing to land in your inbox on a Tuesday. --- END --- Notes: • Send Slack first — read is faster than email and it's easier for them to ask a quick clarifying question. • If no response in 24h, gentle follow-up: "Hey, did this land OK?" — don't re-send the wall of text. • If still no response after 48h, escalate to a 5-min Zoom — sometimes the medium is the blocker, not the message.
// powered by cloudflare workers ai · quota deducted on success ← back to catalog