Treat every AI drafted sales email as a set of claims to check. Review its facts, personalization, tone, and assumptions separately, then trace each material detail to the page or record it came from. AI can produce emails that appear personalized while being fake.1 Before polishing a sentence, ask whether it belongs. Send only when you can explain why each specific detail is in the email.
Set the standard
Before editing wording, decide what must be true for the email to go out. Match the depth of the check to the consequences of being wrong.
The right verification strategy depends on the task and the risk you can tolerate.2 Mark every sentence that makes a factual claim, names a customer problem, describes a company event, or assumes something about the recipient. Check those sentences before polishing the prose.
Check each sentence for four things:
- Is the statement accurate?
- Is it relevant to this recipient?
- Does the tone fit the message and the relationship?
- Has the draft included an assumption that nobody has supported?
This is your send standard. Good prose can still fail one of these checks.
Trace claims to the page they came from
Start with claims that would make the email embarrassing if they were wrong. Treat every citation, link, and research note as a lead until you open it and compare the wording yourself.
In AI summaries, it can be hard to tell whether a number came from a dependable source, a random site, or was made up.3 An AI tool can also misrepresent what a source says.4
For each material statement:
- Copy the exact sentence from the email into your review notes.
- Open the page behind the citation or link.
- Find the passage that supports the sentence.
- Compare the email's wording with the passage, including who did what, when it happened, and what the source actually claims.
- If the page supports only part of the sentence, cut the unsupported part or remove the sentence.
Verify the links and the content you find through AI.5 Compare the information with other sources when the statement affects the recipient's business or your reason for contacting them.6 The check is complete when you can point to the exact support, explain any qualification the email leaves out, and tell whether the claim belongs in this message.
Check personalization and freshness
Give personalization its own pass. A detail can sound specific without having a reliable connection to the person receiving the email. Read every personal reference as if the recipient will know immediately whether it is true.
Ask what record supports the company detail, the contact detail, the role, and the reason for reaching out. Check whether the wording still fits the account and the person you are contacting. AI can flag malformed variables and claims that lack support.7
Look for blank fields, mismatched fields, awkward substitutions, and details that could describe many companies. Then ask whether the recipient would recognize each detail as current, whether you can show where it came from, and whether it changes the reason for the email or is only decoration. Delete any detail you cannot answer for.
Read for relevance and tone
After the factual checks, read the email as the recipient would. This catches messages that are accurate in isolation but still feel strange, presumptuous, or unrelated to the person's situation.
A person should check the output for accuracy, relevance, tone, and unsupported assumptions.8 Read the opening, the personalized sentence, and the call to action without the research notes beside you. Listen for claims that assume a problem, urgency, interest, or knowledge the recipient has never shown. Remove language that makes the reader work out why the detail matters.
Ask whether the email sounds written for this person, whether the reason for contacting them is clear, and whether the requested next step follows from what the email says. If the answer depends on an unverified assumption, send the draft back to the claim check.
Use AI detection only as a side check
Authorship detection answers a limited question. It can show whether text resembles patterns found in AI output, while the verification process establishes whether the email is true and suitable to send.
AI detectors scan text for signs that AI was used.9 They return a probability percentage indicating that text is AI generated.10 Use that result, if you use it at all, as a prompt to inspect the writing more closely. It cannot replace opening the source, checking the personal detail, or reading for relevance.
Run a detector after the factual review. If it flags the message, look for vague claims, repeated phrasing, and sentences that sound detached from the recipient. Make the decision from the email's support and fit, not from the score.
Make the send decision
Finish the review with one of three decisions: send, rewrite, or stop. The draft should leave your queue as a sendable email, a rewrite with specific changes, or a message that stops because its support cannot be established.
AI can help with research. An inside salesperson should always validate the information.11 The representative should use AI to draft and research, then identify where the draft was wrong.12
Send when the factual statements have support, the personal details are current, and the tone fits. Rewrite when the source is sound but the sentence overstates it, or when a supported detail does not help the recipient. Stop when a claim has no source, a personal detail cannot be confirmed, or the draft depends on a contradiction you cannot resolve.
Keep the review notes short. Record the claim, the supporting page, and the change you made. That gives you a reason for the final wording when someone asks why the email was sent.
What not to do
These failure points deserve a hard stop during review.
- Use an AI summary to find material you can inspect. Do not treat it as a reliable account of what the whole web says.13
- Do not quote AI output without verification because it could be wrong.14
- Do not send outreach built on outdated contact information, incorrect job titles, or stale company data. Those details can make the message irrelevant or embarrassing.15
- Do not treat polished wording as proof of accuracy. AI generated research and messages can look polished while being wrong.16
- Do not treat a detector result as a factual verdict. Detector results are often inaccurate and can mislead.17
- Do not assume a positive detector result proves that someone used AI. False positives are common when AI has refined or polished text.18
- Do not use detector results to judge people who are not native English speakers without serious caution. Studies have found unpredictable results and bias against them.19