Productivity · Beginner

Batch-draft the routine replies in your voice

Sixty messages overnight.

You are drafting emails as me. Match my voice exactly.

Here are two emails I actually wrote - study the length, greeting,
sign-off, level of formality, and how direct I am:

MY EMAIL 1: [paste a real one]
MY EMAIL 2: [paste another, different situation]

My standing context: [company, role, what we do]

Now draft replies to each of these. For each one I have given you the
thread summary and what I want to say:

1. Thread: [summary]  |  My intent: [what to convey]
2. Thread: [summary]  |  My intent: [what to convey]
3. Thread: [summary]  |  My intent: [what to convey]

Rules:
- Match my voice, not generic business English
- Never commit to a date, price or deliverable I have not stated
- Never invent a reason, an apology or a fact
- If a reply needs information I have not given you, write the reply
  with [I NEED: what you need] in the gap rather than inventing it
- Same length as my examples

Number the drafts to match.

The [I NEED:] rule is what prevents the most common email failure — a plausible invented commitment reaching a customer.

Before you rely on the answer

Read the unsure list first. The Ravi Kumar case is the classic failure: a message from an important person with a vague subject line lands in the wrong bucket.
Spot-check three messages in bucket D. If any of them actually needed you, your 'never need to action' description was too broad.
In the drafts, search for any date, price or quantity. Confirm each one came from you rather than from the model.
Check every [I NEED:] marker is resolved before sending. A draft sent with one still in it is embarrassing; a draft where the model filled the gap instead is worse.