Awesome Claude Prompts Unofficial

Reply to an email

Draft a reply that addresses each question in an email, aims at your goal in the tone you choose, and flags what you still need to decide.

Task: Reply to an email · Other tasks

Fill in the details

Remove personal details you do not want to share, such as phone numbers or account numbers.

Optional. Dates, numbers or decisions the reply should use. The prompt asks Claude to mark missing answers with placeholders; check the draft before sending.

Copy your prompt

This site doesn't run Claude or show model output. Results depend on your input and the model you use.

2 required fields are empty.

What you type is kept in this tab's session storage so a reload doesn't lose it. Use "Clear this task" to remove it. Browsers can restore session data when they reopen tabs, so closing a tab isn't a guaranteed way to erase it.

When to use this template

  • You know what you want to say but the reply is taking too long to write, or you keep rewriting the first sentence.
  • The email asks several questions and you want to make sure the reply answers all of them.
  • The situation needs a particular tone, such as saying no politely or following up firmly, and you want a draft to start from.

When not to use it

  • The reply commits you to legal, financial or contractual terms. Draft it with this template if you like, but have it checked by the right person before sending.
  • You do not yet know what you want to happen. Decide the goal first; the compare-options template can help.
  • The thread contains confidential information you are not allowed to paste into another service.

Why this structure

  • The incoming email sits first inside <email> tags, which helps Claude tell the other person's words apart from your instructions.
  • Your goal is required because a reply without a goal tends to be polite but vague; stating it gives Claude a clear test for a good draft.
  • The optional facts block appears only when used. The guidelines tell Claude to use only commitments, dates and numbers supplied in your goal or facts.
  • Placeholders in square brackets show exactly where your input is still needed instead of hiding guesses in fluent text.
  • The closing list of placeholders and uncovered points works as a short checklist before you press send.

Example input (fictional)

The email you are replying to
Hi Sam, could we move Friday's review of the Oakfield garden plans (fictional) to next week? Also, do you still need the updated cost sheet, or is the March version fine? Thanks, Priya
What you want the reply to achieve
Agree to move the review to Tuesday afternoon and ask for the updated cost sheet.
Tone
Warm and friendly
Facts the reply should include
I am free Tuesday after 2 pm. The March cost sheet is missing the fencing quote.

Follow-ups to send Claude

  • Make it shorter: three sentences at most, keeping the answer to both questions.
  • Write a second version that declines the request politely.
  • What could the reader misunderstand in this reply?

Common mistakes

  • Pasting only the latest message when earlier ones in the thread hold the context. Include what the reader will remember.
  • Leaving out the facts and then trusting the draft. Fill every placeholder and check every date before sending.
  • Sending without reading it aloud once. A quick read catches tone that sounds different from how you talk.
  • Edit a draft for clarity: Make a draft clearer for a named reader while keeping your meaning and voice, with a short list of what changed and why.
  • Turn meeting notes into action items: Turn rough meeting notes into a clear list of action items with owners and due dates, plus decisions made and questions left open.

See all templates

Sources