Use AI for sales emails by supplying the reason for contact, the offer facts and one next action. Ask for a draft, then replace vague praise and guessed buyer problems with details you can support.

Pick the job of the email

Situation What the message should do A fitting next action
A person requested information Answer the request Ask which detail they need next
A discovery call just ended Confirm what you heard Check the recap or agreed action
A prospect has a proposal Explain the relevant scope Ask about one unresolved decision
You are making first contact Explain why the offer may be relevant Ask whether they want the specific resource

A meeting request is useful when a conversation is the agreed next step. If someone asks for a checklist, send the checklist; adding a scheduling demand creates a new task for them.

Write from a filled-in brief

Use this fictional example to practice. It describes a requested reply, not permission to contact a real person.

RECIPIENT: Lena at Maple Studio.
REASON FOR CONTACT: She requested our client-handoff checklist in a demo form.
HER MESSAGE: "We are moving from shared folders to a client portal.
Please send the handoff checklist before we decide whether to book a demo."
OFFER: StudioFlow provides a client portal with a file-request checklist.
RESOURCE: A one-page checklist exists and is ready to attach.
NOT ESTABLISHED: Her budget, deadline, team size or current error rate.
EMAIL JOB: Deliver the requested resource.
NEXT ACTION: Ask whether she wants the demo to cover file requests.
SENDER: Sam.

Paste the brief into your writing tool with this prompt:

Write a subject line and an email body under 100 words using only this brief.
Answer the request in the first sentence.
Use one closing question. Do not ask for a meeting yet.
Do not add savings claims, compliments, urgency or product features.
Return the body without inventing an address, signature details or links.

An example result:

Subject: The client-handoff checklist you requested

Hi Lena,

I've attached the one-page checklist you requested. It covers the
client-handoff steps to review while moving files into a client portal.

You mentioned wanting to read it before deciding about a demo.
Would you want that demo to focus on requesting files from clients?

Sam

This is a teaching example, not a captured tool response. Attach the actual checklist before using a sentence that says it is attached. The sample shows the message body; your sending system must supply the correct sender details and any required commercial-email footer.

Repair personalization that goes beyond the evidence

Suppose the first draft instead says, “I love how your fast-growing team is transforming design. StudioFlow will cut your admin time in half, so let’s book 30 minutes this week.”

Every persuasive detail in that sentence has a problem:

Wording What is wrong Better wording for this brief
“Your fast-growing team” No growth or team-size evidence “You mentioned moving from shared folders.”
“I love how…” Invented personal reaction Remove it.
“Cut your admin time in half” No supporting result Name the file-request checklist instead.
“Book 30 minutes this week” Ignores the request to read first Ask whether file requests should be the demo focus.

Ask for a focused revision: “Remove every claim absent from the brief. Keep the request for the checklist and Lena’s preference to read before booking.” Then reread the result yourself. A second model pass can still miss the same assumption.

Public company information needs the same distinction. A job listing for an operations manager establishes that the company posted a role. It does not establish that its current process is broken or that it is looking for your software. Personalization should explain relevance without claiming to know the buyer’s situation.

Adapt the message after a call

Change the brief when the relationship changes. In this second fictional situation, Lena has attended a demo and supplied these notes:

Lena wants a checklist for two client handoffs.
Sam agreed to send the checklist.
Lena will review it with Jordan before deciding on a trial.
No trial date or discount was discussed.

A useful follow-up is:

Subject: Checklist for the two client handoffs

Hi Lena,

As agreed, I've attached the checklist for the two client handoffs
we discussed.

You'll review it with Jordan before deciding on a trial.
Is there anything else you need for that review?

Sam

The change is in the next action: support the internal review. “Your trial starts Monday” would invent a commitment. “Can you introduce me to Jordan?” would introduce a different request; use it only if that is what you actually need to ask, not as an automatic extra line.

If the call notes are messy, the ChatGPT for sales guide shows how to separate confirmed facts from unanswered questions before drafting.

Choose between subject lines and calls to action

Compare two candidates against the actual email body. “The checklist you requested” fits a requested resource. “Quick question” hides the subject, while “Re: our conversation” is misleading if no conversation happened. A shorter subject is not automatically a better one.

Match the closing question to the recipient’s work:

  • When they need information, ask which missing detail would help.
  • When a decision is waiting on a specific concern, ask about that concern.
  • When they agreed to schedule, offer actual availability.
  • When no next action is justified, close without forcing a question.

For a first-contact practice draft, ask AI to write two versions: one offering a relevant resource and one asking about a relevant process. Compare whether each explains why you chose this company. Do not treat the more confident version as the more accurate one.

Check the message and the sending setup

Read the draft once for meaning and once for mechanics. Verify names, attachments, offer details and the requested next action. Remove placeholder links and check that the subject accurately describes the body.

For US commercial messages, the FTC’s CAN-SPAM guide covers accurate sender information, nondeceptive subjects, ad identification, a valid postal address and a clear opt-out method. It also explains that business-to-business email has no blanket exception. Follow your organization’s suppression and review process; these writing examples are not a complete compliance checklist or authorization to send.

Measure useful replies without promising a reply rate

Define the result before comparing drafts. A reply that supplies the missing information or confirms the next action matters differently from a rejection. Track those outcomes separately. If you test two versions, keep the audience and offer comparable so you do not mistake a different recipient group for better writing. A small test can suggest a revision; it does not establish a universal winning template.

Questions about AI for sales emails

What should I do when the email sounds generic?

Look at the brief first. Add the actual request, a relevant observation or a detail from the conversation. Asking for a more personal tone without adding facts often produces unsupported compliments.

How long should a sales email be?

Long enough to explain the reason for contact and the next action. The 100-word limit in this exercise is an editing constraint, not a proven optimum. A proposal explanation may need more room than a checklist delivery.

Can I reuse the same prompt for different prospects?

Yes, but replace the brief and verify each output. Check that a name, offer or commitment from the previous example has not carried over. Reuse the structure, not another account’s facts.

Should AI send the finished draft?

This workflow keeps sending in your approved email or sales system. Review the recipient, content, attachments and applicable sending requirements there before sending.

Use the sales follow-up workflow to turn your next set of call notes into a reviewed message.