Workflow

Stuck on: Draft a permission-aware outreach or follow-up email grounded in verified recipient context and approved proof.

Sales Email Drafting Workflow

One-to-one business development, partnership outreach, and service inquiry follow-up with a valid contact basis.

Follow the sequence

Steps

  1. 1

    Verify the recipient, current context, contact basis, channel rules, and do-not-contact status before drafting.

  2. 2

    State a relevant, observable context; do not infer private needs or invent a pain point.

  3. 3

    Match one approved offer and proof point to that context, including material exclusions or uncertainty.

  4. 4

    Draft concise subject options and a body with sender identity, factual personalization, and one low-friction CTA.

  5. 5

    Prepare at most one policy-compliant follow-up with an opt-out path; do not automate sending from this workflow.

  6. 6

    Require human approval of recipient list, claims, links, tone, and send decision; stop if identity, basis, or evidence is unclear.

Output contract

What you should get

  • Verified context and contact-basis log
  • Subject options and email draft
  • Single follow-up and opt-out wording
  • Human send-approval checklist or stop decision
Copy and adapt

Prompt

Run the Sales Email Drafting Workflow for the goal below.

Goal: Draft a permission-aware outreach or follow-up email grounded in verified recipient context and approved proof.

Inputs (replace each placeholder with verified information):
- Verified recipient identity, role, and organization: {{add verified input}}
- Current context sources and dates: {{add verified input}}
- Contact basis, channel rules, and opt-out requirements: {{add verified input}}
- Offer, exclusions, and approved proof: {{add verified input}}
- Desired action, tone, and sender identity: {{add verified input}}
- Do-not-contact or consent status: {{add verified input}}

Method:
1. Verify the recipient, current context, contact basis, channel rules, and do-not-contact status before drafting.
2. State a relevant, observable context; do not infer private needs or invent a pain point.
3. Match one approved offer and proof point to that context, including material exclusions or uncertainty.
4. Draft concise subject options and a body with sender identity, factual personalization, and one low-friction CTA.
5. Prepare at most one policy-compliant follow-up with an opt-out path; do not automate sending from this workflow.
6. Require human approval of recipient list, claims, links, tone, and send decision; stop if identity, basis, or evidence is unclear.

Return exactly these reviewable outputs:
- Verified context and contact-basis log
- Subject options and email draft
- Single follow-up and opt-out wording
- Human send-approval checklist or stop decision

Human review boundary: Never invent recipient pain, private facts, endorsements, or results. Follow applicable consent and channel rules; an approved draft is not authorization for bulk or automated sending.
Human review boundaryNever invent recipient pain, private facts, endorsements, or results. Follow applicable consent and channel rules; an approved draft is not authorization for bulk or automated sending.