Draft a reply to the email below. I am [SENDER ROLE] at [COMPANY], writing to [RECIPIENT AND RELATIONSHIP]. The original email is: [INBOUND EMAIL]. My verified facts, approved terms, and constraints are: [FACTS AND CONSTRAINTS]. My preferred outcome for this reply is: [NEXT STEP]. Use this tone: [TONE]. First, identify the recipient's explicit questions, implied concern, decision stage, and any commitment they are requesting. Then write the email in 120-220 words with: a subject line only if the thread needs one; a direct acknowledgement of their main point; concise answers in the same order they asked; one relevant proof point or example only if supported by [FACTS AND CONSTRAINTS]; and one specific next step with a proposed action, owner, and timing when known.
Do not introduce a new offer, discount, deadline, legal term, product capability, security claim, customer name, or implementation promise that is not in [FACTS AND CONSTRAINTS]. Do not use fake urgency, vague “just checking in” language, or several competing CTAs. If I cannot answer a question, say what I will verify and when I can return with an answer; do not guess. After the draft, add a short “Commitments to confirm” list containing every promise, date, price, scope item, or attachment mentioned. Before answering, check that the reply answers each material question and that its CTA matches [NEXT STEP]. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [SENDER ROLE] | State your role and authority in the sales conversation. | Account executive with authority to schedule a product demo, not approve discounts. |
| [COMPANY] | Enter your company name and, if useful, the product or service involved. | Northline Workflow, a project intake tool for creative agencies. |
| [RECIPIENT AND RELATIONSHIP] | Identify the recipient's role, company, and current relationship to you. | Priya Shah, operations director at Morrow Design; attended a discovery call last week. |
| [INBOUND EMAIL] | Paste the email or thread excerpt you need to answer. | Can you confirm whether we can use SSO, how onboarding works, and what the annual price would be for 42 users? |
| [FACTS AND CONSTRAINTS] | Provide approved pricing, scope, timing, capabilities, policies, and facts you can stand behind. | SSO is available on Enterprise; onboarding includes kickoff and two admin sessions; Enterprise pricing requires a formal quote. |
| [NEXT STEP] | State the one desired next action, such as book a technical call or confirm requirements. | Schedule a 30-minute technical fit call with Priya and her IT lead. |
| [TONE] | Describe the tone, such as direct and consultative or warm and brief. | Clear, helpful, and commercially direct. |
How to use
- Paste enough thread context to show what has already been promised and what the recipient actually asked.
- Give the prompt your approved facts; leave unknown pricing, legal, or technical details explicitly unknown.
- Read the commitments list before sending and remove or verify anything you cannot deliver.
- Follow up with: “Make this 90 words and offer two specific meeting times without adding any new commitments.”
Variations
Pricing reply
Use this when a prospect asks about price or commercial terms.
Reply to this pricing email: [EMAIL]. I can accurately state these plans, prices, and terms: [APPROVED COMMERCIAL FACTS]. The buyer is [BUYER CONTEXT], and the next step is [NEXT STEP]. Write 100-180 words that answers direct pricing questions, distinguishes confirmed pricing from quote-dependent items, and gives one next action. Do not offer discounts, custom terms, or savings claims that are not approved. End with commitments to confirm.
Objection reply
Use this when a buyer raises a specific concern.
Draft a reply to [OBJECTION EMAIL] from [RECIPIENT]. Use only these verified facts and proof: [EVIDENCE]. Address the concern directly, acknowledge any valid trade-off, explain the relevant capability or process, and propose [NEXT STEP]. Keep it under [WORD COUNT] words. Do not dismiss the concern, invent customer results, or promise integrations, timelines, or outcomes not documented.
Post-demo follow-up
Use this after a sales demo or discovery call.
Write a post-demo follow-up to [RECIPIENT] using these meeting notes: [NOTES]. My approved follow-up materials are [MATERIALS], and the desired next step is [NEXT STEP]. Return a concise email with their stated priorities, agreed facts, linked or named materials, open questions, and one CTA. Separate what they said from what I am proposing. Do not claim agreement on scope, pricing, or timing unless the notes show it.
Tips
- Answer questions in the recipient's order; it makes the email feel responsive and exposes anything you still need to verify.
- Keep commercial and operational promises in your source notes, then use the commitment list as a pre-send control.
- One meeting request is clearer than an email that asks the recipient to review, reply, schedule, and introduce someone at once.
- If a buyer's concern is valid, name the trade-off plainly before explaining fit; evasive replies usually extend the sales cycle.
FAQ
Can AI reply to a customer email automatically?
It can draft the reply, but a person should verify commitments, pricing, legal terms, and sensitive customer details before sending.
How long should a sales email reply be?
Match the question's complexity. A simple scheduling reply can be brief; a technical or commercial answer should be structured enough to avoid ambiguity.
Should I include a calendar link?
Include one when booking is the single next step and the recipient is ready. Otherwise offer a specific action that fits the stage of the conversation.