AI can help you get past the blank page. It should not invent a deadline, promise a result, or send a client message without your review. This workflow keeps the useful part—organizing a draft—separate from the decisions that belong to you.
Start with a short, non-sensitive brief
Write down the purpose of the message, who will read it, the one action you want them to take, and the facts that must be correct. Remove private client details, account numbers, unpublished plans, and anything you are not allowed to share with the service you use.
If you cannot explain the task in two or three sentences, clarify it before prompting. A fuzzy request usually produces a polished but fuzzy draft.
Purpose: send a project update. Reader: a client who prefers concise notes. Include: the draft is ready for review, feedback is due Friday, and the next milestone begins after approval. Do not add new commitments.
Ask for structure, not authority
Give the tool a role as a drafting assistant, not as the person making business decisions. Ask it to use only the facts you provide, keep unknown details as questions, and return a subject line plus a short email. If you need a particular tone, describe it with observable qualities such as warm, direct, and brief.
- Say what the reader should understand or do.
- List the confirmed facts and any details that must stay out.
- Ask the model to flag missing information instead of guessing.
- Request a first draft that you can edit—not a message to send automatically.
Check every consequential detail
Compare names, dates, prices, scope, and promises against the original brief. Read the message as the client would: is the request clear, does the tone fit the relationship, and could any sentence be interpreted as a commitment you did not intend? Correct unsupported claims and remove filler.
For sensitive or regulated communications, follow your organization’s review process. A language model is not a substitute for legal, financial, medical, or security expertise.
- Confirm facts against your source notes.
- Check that the call to action is specific and easy to answer.
- Remove confidential material and any detail the recipient does not need.
- Send only after a human has approved the final text.
Save the repeatable part
When the workflow works, keep a reusable prompt with placeholders for purpose, reader, confirmed facts, tone, and next step. Do not save client data inside a shared prompt library. Revisit the template when the tool changes or you notice the same error appearing more than once.
The short version
Use AI to organize and phrase information you already understand. Keep private data out, verify every material detail, and make the send decision yourself.
Editorial note: This guide is general information. Check current provider documentation and local requirements before acting on sensitive matters.
Use tools to support a clear process. Verify important details, keep private data protected, and make consequential decisions yourself.
Editorial note: This guide is general information. Check current provider documentation and local requirements before acting on sensitive matters.
Read how we create and correct guides ↗