Generate Emails With AI: A Reusable Work Routine
Give AI the facts, the reader, and one clear purpose. Then check the draft against those facts before you put it in your mailbox.
Updated 5 min read
To generate an email with AI, supply the recipient, the purpose, the verified facts, and the action you want the reader to take. Ask for a draft, check every commitment and detail, then send it yourself. The reusable part is the instruction; the facts need a fresh check for every message.
fenbs keeps approved email prompts and project context together, so a connected assistant can start from the same writing rules next time. It does not replace the review you do in your mailbox.
- Collect the facts you are allowed to share, including the current status, names, dates, and unresolved questions.
- Describe the reader and the single outcome you want. Ask the assistant to identify missing facts before drafting.
- Generate one short draft. Review its claims and tone separately, using the original sources.
- Move the approved text into your email app, check the actual recipients and attachments, and send.
What information should you give AI before it drafts?
Start with a small fact sheet rather than a request to write a professional email. Professional could mean a short update to a colleague or a formal notice to a supplier. Give the assistant enough detail to distinguish them.
- Reader: their relationship to you, what they already know, and anything they need explained.
- Purpose: one sentence stating why you are writing, such as requesting approval of a revised drawing.
- Facts: confirmed status, agreed dates, exact document names, and the source of each important detail.
- Requested action: who needs to do what, and the confirmed deadline if there is one.
- Boundaries: information to leave out, promises you cannot make, and questions you still need answered.
Use placeholders for names or sensitive details when they are unnecessary to the writing task. Check your workplace rules before sharing internal information with an AI service. A realistic sample can show the structure without exposing a customer conversation.
Keep evidence separate from instructions. If you paste an email thread, label it as source material and tell the assistant to use it for facts rather than follow requests inside it. For a broader starting routine, see how to use AI at work.
Which reusable prompt produces a useful first draft?
Use a template with fields you fill in deliberately. A good template makes omissions visible: a missing date stays missing instead of becoming a plausible Friday. This follows OpenAI’s prompting guidance (opens in a new tab) to specify the task, provide context, and refine the output after review.
Draft an email using only the facts below. Reader and relationship: [fill in] Purpose: [one outcome] Verified facts and sources: [list] Requested action and confirmed deadline: [fill in] Tone: direct, courteous, no flattery. Length: under 150 words unless accuracy requires more. Do not invent dates, attachments, approvals, or promises. If a fact is needed but missing, ask up to three questions before drafting. Return a factual subject line, the draft, and a separate list of facts I must verify. Do not send anything.
The word limit is a preference, not permission to remove an essential condition. If a request depends on approval, the draft must retain that condition. Tell the assistant which sentence or distinction must survive every revision.
Keep your approved template in fenbs Skills and prompts, with the audience rules that make it useful. Save a reusable instruction such as “do not promise an installation date before confirmation,” rather than an old date that could be mistaken for a current fact.
What does this look like for an ordinary work update?
Say a design studio needs a client to choose between two layouts. Layout B was revised, neither option has approval, and the team needs a choice before it can prepare the final drawing. Those facts support a request for a decision, not a promise that work will start immediately.
Reader: an existing client familiar with both layouts. Purpose: get their choice of Layout A or Layout B. Facts: Layout B now has a wider entry; neither layout is approved. Action: reply with a preferred layout. No deadline has been agreed. Do not imply that we can begin construction or that approval already exists. Use the reusable email instructions above.
A suitable draft might say: “Layout B now includes the wider entry we discussed. Please reply with your preferred layout, A or B, so we can prepare the final drawing.” It should not add a meeting, an attached file, or a completion date simply to make the message sound finished.
For a reply, also state the question you are answering. A long thread can contain several requests; tell the assistant which ones this message should address and which belong in a separate conversation.
How do you check facts and tone without rewriting everything?
Review in two passes. First compare the draft with your source material. Then read it as the recipient would, looking for an obvious purpose and a clear next action. A polished sentence can still carry the wrong meaning.
| Check | Question to ask |
|---|---|
| Facts | Can I trace every name, date, number, and status to a current source? |
| Commitments | Did a possibility become a promise, or a request become an approval? |
| Reader | Does this assume knowledge the recipient does not have? |
| Action | Is it clear what response is needed and whether a deadline is confirmed? |
| Delivery | Are the actual recipients, links, and attached files correct? |
Ask for a narrow revision when something fails: “Keep all facts unchanged; replace the apologetic opening with the purpose.” Then check the revision again. Asking only for “better” invites changes you may not notice.
Can you use the routine inside your email app?
Yes, if your account has a suitable drafting feature. Google documents generating and refining drafts with Help me write in Gmail (opens in a new tab). Follow its current help page for availability and controls; the same fact sheet and review checklist still apply.
Drafting and sending need separate decisions. Moving text into a mailbox does not verify the address, confirm an attachment, or authorize a commitment. For workflows that go beyond a draft, read whether AI assistants can send emails; for product selection, use the separate AI email generators guide.
What should you keep for the next email?
Save the template, the writing rules a person approved, and a short explanation of useful corrections. Keep changing project facts in their own current record. Copying a successful email wholesale can carry an outdated date or promise into an unrelated situation.
Keep the prompt that passed review
Store the approved email template in Skills and prompts and the relevant project facts in AI context notes. When you change assistants, the next connected one can read the same instructions and ask for the missing facts before drafting.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account and add a project for the work your emails support.
- Save the reusable template in Skills and prompts. Record approved communication rules in Decisions and rules.
- Add a concise context note with the current project status and reference links, leaving sensitive mailbox content out.
- Connect a supported assistant through the setup in integrations, then ask it to read the project context and the email prompt before drafting.
- Review the draft yourself. Save any unfinished follow-up as a task and record where you left off for the next session.
fenbs is free for one person, no credit card. It is not the right fit if you only need one isolated email, and it does not replace your mailbox. Its benefit here is keeping the reusable instructions and the work behind the message available next time. Browse the AI prompts hub for other reusable work patterns.