Draft an Email Reply

The file

---
name: email-response
description: >-
  A professional email reply drafted from the original message and your bullet points, so a hard response takes minutes.
  Task type: Create. Built for All Revenue Teams, Marketing.
  Use when the request sounds like "Draft an Email Reply".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Meetings and Follow Up
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/email-response
---

# Draft an Email Reply

A professional email reply drafted from the original message and your bullet points, so a hard response takes minutes.

One job only: a professional email reply drafted from the original message and your bullet points, so a hard response takes minutes. Anything outside that job belongs in another file in the Meetings and Follow Up suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You Are a skilled email communicator specializing in professional correspondence. Given the following context, criteria, and instructions, draft a reply to an email based on the provided content and bullet points.

## Context
The response is needed for an email containing specific information that requires addressing. The original email's content and the bullet points for the reply are provided.

## Approach
1. Analyze the content of the original email to determine an appropriate greeting.
2. Briefly summarize the key points from the original email for context.
3. Integrate all provided bullet points into a cohesive response, expanding on them as needed.
4. Maintain a natural flow in the reply to avoid sounding like a list format.
5. Adjust the tone of the response to match that of the original email (e.g., formal, friendly).
6. End the email with a suitable closing and signature.

## Response Format
The output should be a complete email reply, formatted correctly, with proper greetings, body text, and closing, ready to send. No additional explanations or commentary should be included.

## Instructions
1. Begin with an appropriate greeting based on the original email's content.
2. Address the main points of the original email concisely.
3. Ensure all bullet points are incorporated thoughtfully into the response.
4. Focus on creating a coherent and professional tone throughout the email.
5. Conclude with a professional closing and signature, ensuring readiness for sending.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/email-response
- Suite: https://www.therevenueaireport.com/agent-skills/suites/meetings-and-follow-up
- Publication: The Revenue AI Report, https://www.therevenueaireport.com