Use it when you are

  • Asking a busy colleague, manager or client for a decision or approval
  • Following up on an unanswered message without sounding impatient
  • Declining a request or delivering unwelcome news clearly and politely
  • Introducing yourself to someone you have not met with a specific request

Why this prompt works

The ask is found before the email is written

Most unclear emails are unclear because the writer has not decided what they want. Making the model state the ask as one actionable sentence, and showing it to you, catches that problem at the start. If the sentence is wrong, the email would have been wrong too, and you can correct it in a line.

It models the recipient, briefly

What the recipient already knows decides what to leave out; what is at stake for them decides how the request is framed. Those two notes are why a message to a client you met once comes out differently from one to a teammate, even with the same facts.

Purpose first, context second

People scan email and often act on the first lines alone. The instruction to put the reason and the ask in the first two sentences, with context limited to what the recipient needs, reverses the common habit of narrating the background before getting to the point.

Brackets instead of invented details

A model drafting an email will happily supply a meeting time or promise a delivery date. Requiring [square brackets] for anything missing, and forbidding commitments you did not mention, keeps the draft honest and gives you a visible list of blanks to fill before sending.

Hard messages get their own rule

Refusals and bad news are where drafts turn evasive. The prompt asks for the news early, a brief reason and what happens next, with one apology at most. That is the structure that respects the reader's time when the content is unwelcome.

How to use it

  1. Describe the recipient by role and relationship, including how well you know them.
  2. Write the goal as the outcome you want, with a date if there is one.
  3. Paste the facts and any earlier messages into the background. Leave out nothing the recipient would need in order to act.
  4. Check the ask sentence above the draft. If it is not what you want, correct it and ask for a new draft.
  5. Fill in every bracket and confirm each fact against your own records.
  6. Read it once as the recipient before sending, and adjust any phrase you would not say yourself.

AI model compatibility

ModelStatusNotes
ChatGPTExpected to workIf the draft comes back longer than you wanted, ask for the same email in half the words rather than editing line by line.
ClaudeExpected to workBackground is wrapped in XML-style tags, as Anthropic's guidance recommends for supplied context. Paste the earlier email thread inside them if you are replying.
GeminiExpected to workState the tone explicitly using the dropdown; clear, direct instructions about style are in line with Google's prompting guidance.

“Expected to work” means the prompt uses plain, model-independent structure and has been reviewed for that — not that it has been run on that model. A model is marked Tested only when a test record is published below.

Worked example

Scenario: A project manager at a small agency needs a client's finance lead to approve a revised quote. Illustrative inputs only.

Example: filled-in prompt
# Role
You are helping me write one professional email. Write it as I would send it: from me, in the first person, ready to paste.

# Situation
- Who I am writing to and how we know each other: Head of finance at a client company; we have met once on a kickoff call
- What I need to happen as a result of this email: She approves the revised quote by Friday so we can start work on the 12th
- Tone: Formal and respectful
- Must include or avoid: Mention the attached quote; do not bring up the earlier delay

<background>
We sent an original quote three weeks ago. The client's marketing lead then added two extra page templates to the scope. Revised quote reflects that and is attached. Marketing lead has agreed to the scope verbally. Our start date of the 12th depends on sign-off this week because the designer is booked afterwards.
</background>

# Before you write
Work these out and show them in two or three lines above the draft:
- The single ask or message, as one sentence the recipient could act on.
- What this recipient already knows, so the email does not explain it again, and what they need to be told in order to respond.
- What is at stake for them: why they would care, or what it costs them to do what I am asking.

# How to write it
- Subject line: says what the email is about and, if there is one, the action or date.
- First two sentences: the reason I am writing and the ask. Context comes after, and only as much as the recipient needs.
- One email, one main ask. If my background contains several requests, lead with the most important and tell me which ones you held back for a separate message.
- Make the next step easy. Say exactly what I need, from whom, by when, and offer a specific option where that helps: two time slots, a yes or no question, a document to approve.
- If the message is unwelcome news, a refusal or a complaint, state it plainly early on, give the reason briefly and say what happens next. Do not bury it under pleasantries or apologize more than once.
- Close with the next step. No stock opening or closing lines.

# Constraints
- Use only the facts in my background. Where a detail is missing, such as a date, a name, a figure or an attachment, put it in [square brackets] for me to fill in. Do not make commitments on my behalf that I did not mention.
- Match the tone to the relationship: no stiffness with a close colleague, no familiarity with someone I have not met.
- Keep it as short as the content allows. Aim for under 150 words and go longer only if the recipient needs the detail in order to act.

# Output format
1. The ask, what they know, what is at stake.
2. Subject line, plus one alternative.
3. The email.
4. Anything in brackets I need to fill in, and any assumption you made about the relationship or the tone.

What a good response should contain

  • An ask sentence along the lines of: approve the attached revised quote by Friday
  • A subject line that names the revised quote and the Friday deadline
  • An opening that states the request and the reason for the date within the first two sentences
  • A brief explanation of what changed in the scope, without retelling the project history
  • Brackets for details not supplied, such as the quote amount or the exact Friday date

This is an illustrative scenario showing how to fill in the prompt and what to look for. It is not a recorded model output. Recorded outputs will be published here once this prompt has a test record.

Testing and editorial review

Status: Untested. Reviewed for structure and clarity by the editorial team. No recorded model test yet.

No test record has been published for this prompt yet. When it is tested, this section will show the model and version, the date, the inputs, the actual output and notes against our seven-point rubric. We do not publish numerical scores.

Editorial record
AuthorTheBestPromptFor Editorial Team — The editorial team writes, reviews and maintains the prompts and guides on TheBestPromptFor. Prompts are drafted with AI assistance and reviewed against published editorial standards.
PublishedNovember 15, 2026
Last reviewedNovember 15, 2026
Last testedNot yet tested
Version history
  • v1.0 — November 15, 2026 · Initial version

Limitations and things to check

  • The model knows only what you tell it about the relationship and its history. Review the tone yourself for sensitive situations.
  • It cannot verify dates, amounts or what was agreed. Check every fact and fill every bracket before sending.
  • For legal, HR or contractual matters, have the right person review the wording; a well-phrased email is not advice.
  • Do not paste confidential or personal information into a tool your organization has not approved for it.

Alternative prompts

All Content Writing prompts →

Frequently asked questions

How long should a professional email be?

Long enough for the recipient to act without writing back to ask a question, and no longer. For most requests that is a few short paragraphs. If the email needs much more, the detail probably belongs in an attachment or a meeting, with the email carrying the ask and a pointer.

Can I use this to reply to an email thread?

Yes. Paste the thread into the background field and state what you want your reply to achieve. The prompt will treat what the other person wrote as things they already know, so the reply should not repeat their own points back to them.

What if I have several things to ask in one email?

The prompt leads with the most important ask and tells you which others it left out. Closely related questions on the same subject can stay together. Unrelated requests are more likely to get answered when each has its own message and subject line.

Sources and references

  1. Prompt engineering overview — Anthropic
  2. Prompt design strategies — Google AI for Developers

Was this prompt useful?

No account needed. Do not include personal information.