Cross-Team Request Email · High-Response Template
Turn cross-team requests into a 3-paragraph high-response email; less ignored.
Pain addressed · Pain #1 · Almost-right: AI-written emails read fluently but 80% of the time fail to nail 'what I want from you' and 'why this matters'.
Cross-Team Request Email · High-Response Template
You are an operations lead skilled at cross-team comms. Convert the request below into a sendable email.
# What I'm asking for
{the_ask}
# Context
- My team: {my_team}
- Their team: {their_team}
- Recipient: {recipient_name}, role {recipient_role}
- Urgency: {urgency} (P0/P1/P2)
- Relationship: {relationship}
# Output: 3-paragraph email
## Subject (≤ 20 chars)
Action verb + core ask + deadline. e.g. "[P1·May 30] Need eval on batch-export feature"
## Body 3 paragraphs
### Paragraph 1: Context anchor (≤ 60 words)
- Skip pleasantries. Why this matters, with a verifiable number/event.
### Paragraph 2: The ask (≤ 100 words, bullets)
- Bullet 1: what I want (verb-led)
- Bullet 2: by when (date)
- Bullet 3: what I'll provide to lower your cost of starting
### Paragraph 3: Easy reply (≤ 40 words)
- Two options to choose from, not open question.
## Sign-off: one line
# Hard rules
- No over-formal "sorry to trouble you"
- No "ASAP"/"soon" — use a date
- "Why" comes first, not last
- Cap email at 300 wordsOpen directly on your favourite AI
One click copies the prompt and opens the platform in a new tab — just paste (⌘/Ctrl + V). Recommended platforms are ordered by content fit.
Workflow · 5 steps
- 1
Lock down four things before opening the model: who, what they need to do, by when, and why they should care. Vague on any one — fix that first.
- 2
Replace the six placeholders and run the prompt.
- 3
On the first draft, do three edits: cut every 'sorry to bother you' line, swap any 'ASAP' for a real date, and only propose meeting times you actually have free on your calendar.
- 4
Before sending, reread the subject line. If you got this in your inbox, would you open it first? If not, rewrite it.
- 5
Wait 24 hours. No reply? Send a 2-line follow-up with two fresh time options — don't pile on.
Verify before you ship
AI's "almost right" is the #1 pain. Tick these off so reviewers can't find the obvious holes. (Checkbox state stays local — we don't track it.)
Why this prompt works
This prompt isn't a generic “write me a Email & Comms Templates”. It folds in the concrete context a Operations & Content actually faces (target reader, info density, deliverable format). LLMs deliver an order-of-magnitude better answer when they get role × scenario × constraints together — they can make the right tradeoffs about what to spotlight and what to cut.
When to use
Best moment: you know roughly that you need to do a Email & Comms Templates, but you're stuck on “how do I even ask the AI?” Muscle memory has no template. Copy this card, tweak 2-3 fields per the workflow, and get a first revisable draft in 30 seconds.
Common pitfalls
- Send without tweaking placeholders · the draft reads as default-GPT and your reviewer spots it in 3 seconds.
- Skip the verify checklist · “almost right” failures usually hide in a thing you assumed the model handled but it didn't.
- Stop after the first answer · a single follow-up like “make section X tighter / more formal” usually pushes a 70 → 90.
Variants & extensions
Want to use this card more aggressively? Three extensions:
- Swap languages: both EN/ZH prompts ship in the card — use the EN version when shipping to a Western audience.
- Swap platforms: the same prompt has slightly different taste on ChatGPT / Claude / Kimi. The recommended-platform pill marks the best fit.
- Stack the checklist: paste the verify checklist back into the chat and ask the AI to self-audit — error rate drops sharply.
Want 25 more prompts like this one?
Get the full 50-card Pro deck — multi-step chains, vertical variants, lifetime updates.
- 50 prompts · 25 free + 25 advanced multi-step chains
- PDF printable + Notion template
- Lifetime updates · ~5 new prompts a month, auto-synced
- Dual-language · EN/CN + 5 China-exclusive scenarios