The one-minute review
Read every draft for these five, in this order. The first three are where the expensive mistakes hide. Every vendor warns its AI may suggest inaccurate information, so the review is not optional.
| Check | Look for | Why |
|---|---|---|
| Facts | Order numbers, names, what happened | Gaps get filled with plausible guesses |
| Promises | "We will refund", "by Friday" | You are bound by what you send |
| Prices and dates | Every number | Old prices, wrong year or timezone |
| Recipients | To, Cc, reply-all | A supplier on the thread |
| Tone | Too stiff, cheerful or long | Matters least, easiest to fix |
How to draft email replies with AI, step by step
Step 1: Choose which emails get drafts
Questions from customers to support@, or all mail from people (not newsletters) to you. Narrow is better.
Step 2: Drafts only, never auto-send
Drafts in the thread, or a card to approve.
Watch out. Turn off any auto-send setting before the first run, and check it again after every update to the tool.
Step 3: Load your facts and examples
Three real replies you liked, your exact greeting and sign-off, and the facts it will be asked about: prices, hours, policies, links. Update facts the day they change.
Do this step in 50agents
Set up an AI agent that reads new support emails, drafts a reply from what you know about my business, and asks me before sending
Build itCaptain builds an AI agent that drafts replies from your business's memory, which you can read and correct. Every reply waits for you to approve, change or decline. See the ready-made version.
Step 4: Say what it must never offer
Refunds by email, discounts, legal opinions. Give the reason, so it applies the rule sensibly.
Step 5: Tell it what to do when unsure
"If the answer is not in what you know, do not draft. Tell me what is missing." A gap you see beats a guess you send.
Step 6: Review for two weeks, then decide
Count drafts sent unchanged, edited and thrown away. Fix the facts behind the thrown-away ones.
Tip. When you change a draft, tell the tool why in words, such as "we never offer refunds by email, offer a call".
What can go wrong
A promise you did not make
The draft offered a refund or a deadline. Keep policies in the AI's facts and list what it may never offer.
Stale prices
Last year's price sits in its memory. Update facts the day they change.
Reply-all to the wrong people
A thread with a supplier on Cc. Check recipients every time; it takes a second.
Everything sounds the same
Generic drafts come from having no examples. Paste in three of your own replies.
Questions people ask
Can AI reply to my emails for me?
It can draft them well. Sending should stay with you, at least for anything that reaches a customer.
How do I make AI emails sound like me?
Give it three replies you wrote and liked, your exact greeting and sign-off, and correct it in words when it misses.
Should I tell people a reply was drafted by AI?
If you read and approve it, it is your reply. If something goes out unreviewed, say so, or better, do not let it.
How long should checking a draft take?
About a minute. Read for facts, promises, prices and dates, recipients, then tone, in that order. The first three are where the expensive mistakes hide.
What should the AI never offer in a reply?
Refunds by email, discounts and legal opinions are the usual list. Write the reason beside each rule, so it applies them sensibly to cases you did not foresee.
When can I let it send on its own?
Count drafts sent unchanged, edited and thrown away for two weeks. Even then, keep anything with a promise, a price or a refund behind your approval.