The blank compose window
Personal outreach at volume means a fresh draft for every contact, every time. Most signals get politely ignored because the writing is the bottleneck.
Wave · AI Email Writer
Wave writes the first draft. Grounded in what each person already read.
Generic AI writers know your brand and nothing about this buyer. Wave already knows what each person read, what they should see next, and how they like to hear from you, so the draft arrives grounded in their actual history, waiting for your approval.
People › Dana Kim
AI draft
Draft: recap email
Subject: Your ROI benchmarks, and the security recap you asked about
Thanks for spending time with the ROI benchmark report last week.
Since security certification is your next question, this recap pulls the three answers most finance leaders need.
Grounded in:ROI benchmark reportSecurity certification recap
Human approval requiredEdit draftApprove
Affinity
78
Promotional channel
LinkedIn paid
64
Engagement format
Whitepaper
Quick answer
The AI Email Writer produces two kinds of drafts. The per-person recap email summarizes what a contact recently read on your site and nudges them toward their best next item, subject line included. Per-audience content framing pitches one asset differently by the reader's role and buying stage. Every draft is grounded in real consumption history, is off by default, is enabled per tenant, and is a starting point a human reviews and approves. Wave never sends.
Key capabilities
- Per-person recap drafts built from actual reading history
- Subject line plus body, pointed at the best next asset
- Per-audience framing: one asset pitched by role and stage
- Drafts refresh when the person's best next item changes
- Accept, edit, or discard, with version history kept
- Off by default, enabled per tenant, never auto-sent
Last updated: July 2026
Why teams need this
The blank compose window is where your signals go to die.
Intent tools, scores, and recommendations all end the same way: a human has to sit down and write the message. That step is real work, per contact, every time, and it is why insights never become sends.
Tokens are not personalization
A first-name merge field dropped into one template reads like a mail merge because it is one. Buyers notice the difference between their name and their history.
Generic AI knows the brand, not the buyer
A prompt-driven writer produces plausible copy about your product. It cannot recap what this person read last week, because it has no idea.
How Wave does it
The homework is already done. The draft starts from it.
Wave's writer is the last link in a chain: committee mapping, consumption tracking, next-best-content, and channel and timing predictions all feed the draft.
- 01
The homework is already done
Before a word is written, Wave has mapped the buying committee, tracked what each person consumed, picked their best next asset, and read their channel and timing preferences.
- 02
The draft is assembled from facts
The recap draft draws on that person's recently read items and their recommended next item. The framing draft draws on one asset plus the audience's role and stage. Clean facts reach the model: titles, summaries, role, stage. Raw page contents never do.
- 03
A human approves every word
Accept, edit, or discard, with version history kept. Nothing is sent and nothing is pushed into your CRM or marketing platform. You keep the send button.
- 04
Drafts refresh themselves
When a person's recommended next item changes, the recap re-drafts, so the copy your marketer opens is always built on current reading history.
Where it fits
The last link in Wave's intelligence chain.
The words are only as good as the facts behind them. Wave's writer inherits every fact the platform has already established about each buyer.
Reading history
Wave
A reviewed draft
Committee mapping, content intelligence, next-best-content, and channel and cadence predictions all feed the writer, which is why its drafts read like a rep who did the homework and a bolt-on AI writer reads like a mail merge. Every call is spend-capped per tenant, logged with personal details scrubbed, and confined to your own tenant's data. The capability is off by default, enabled per tenant from the Wave console, and its drafts stay inside Wave until a person decides otherwise.
Works alongside Play Engine, Next Best Action Engine, Buying Group Intelligence.
Why Wave is different
AI writers know your brand. Wave knows this buyer.
Anyone can bolt on a text generator. The difference is what the writer knows before it writes: the committee, the reading history, the next-best pick, and the channel and timing fit.
Most tools
Wave
Generic AI writers need a prompt and know nothing about the recipient.
Wave's draft is already built from what this person read and who they are on the deal. No prompt to write.
Mail-merge fields drop the same template on everyone.
A different message per person and per buying stage, grounded in their actual consumption.
AI SDR tools write and send on their own.
Wave drafts only. A human reads, edits, and approves, and you keep the send button.
Signals and scores you still have to act on.
The finished words, ready to review, with the best next asset already chosen.
Bolt-on writers see your brand guide at best.
Wave's writer inherits the whole intelligence chain: committee role, reading history, next-best pick, and channel and timing fit.
FAQ
Questions buyers ask about the AI Email Writer.
What is the AI Email Writer?
A Wave capability that drafts email copy grounded in each person's real consumption history. It produces per-person recap drafts that summarize what a contact recently read and point to their best next item, and per-audience framing that pitches one asset differently by role and buying stage. A human approves every draft, and Wave never sends.
What are the two draft surfaces?
The per-person recap email: a subject line plus a short body recapping what that person recently read, with a nudge to their recommended next item. And per-audience content framing: a subject line plus a short blurb that pitches one content piece differently depending on the reader's role and stage.
What is a draft actually built from?
First-party behavior. The recap draws on that person's most recently read items and their recommended next item. The framing draws on the content piece plus the audience's role and buying stage. No generic templates and no guessing.
Does Wave send the emails?
No. Drafts are internal writing aids. Nothing is sent and nothing is pushed into your CRM or marketing platform. Your team reviews, edits, and approves every word, and you keep the send button.
What happens when a person's recommendation changes?
The recap draft refreshes itself so it never goes stale. What your marketer opens is always built against the person's current reading history and current best next item.
What does the AI actually see?
A few clean facts: titles, summaries, the person's role, and their stage. Raw page contents never reach the model. Every call is spend-capped per tenant, logged with personal details scrubbed, and confined to your own tenant's data.
Is the writer on by default?
No. It is off by default and enabled per tenant from the Wave console, so the capability arrives on your terms.
How do I see drafts for my own contacts?
Book a 20-minute walkthrough. We will open a real contact record and show the recap draft Wave writes from that person's actual reading history.
See it on your data
Open a contact. The email is already written.
Book a 20-minute walkthrough. We will open a real record and show the recap Wave drafts from that person's actual reading history.
Request a demo