Get email copy approved word by word.

The steps

1. Put the emails on one review page. One page for the whole campaign, each email under its own heading, with its subject line and preview text written out at the top as ordinary text. An AI assistant connected to Stacktree can build the page and publish it for you.
2. Turn on comments and send the link. Switch on "Let them comment on the page" and send the private link. The client opens it in any browser with no account. Add a passcode or a company-email check if the campaign is under wraps.
3. The client suggests new wording. They select the words they want changed, choose "Suggest an edit", type what it should say and press Suggest. For anything that is not a wording change, such as an image or the offer itself, they leave a comment.
4. Accept or dismiss each suggestion. On the page's screen, under What came back, each suggestion shows the old words struck through and the new ones beside them. Accept swaps the new wording in on the same link and keeps the previous version. The client sees "Applied as suggested."
5. Ask for sign-off, then paste the copy into your email platform. Turn on sign-off and the client approves each email, with every answer recorded against the version they read. Then copy the approved subject, preview text and body into Klaviyo, Mailchimp or whichever platform sends it.

Why copy approval drags

Email copy usually gets approved in a document. The client reads it as a block of text in a shared doc, without the layout, the button or the subject line beside the preview, and suggests changes there. Then someone retypes the agreed words into the email template, and the next round of feedback arrives as a reply about the build: "the subject got cut off on my phone", "this isn't what we agreed in the doc".

Two things fix most of it. The client reads the email the way it will be read, on their own phone if they like. And a change they ask for is the exact wording, in the exact place, so nobody has to interpret "make the opening punchier" or copy a phrase from one tool to another.

Set the review page up for editing

A few layout choices decide whether the client can change everything they will want to change:

• Subject and preview as text. Write "Subject:" and "Preview:" at the top of each email. The subject line is the most edited line in most campaigns, and a client can only select what is on the page.
• One heading per email. "Email 2: Reminder" as its own heading lets the client approve the campaign email by email instead of all at once.
• Buttons as styled text. Dragging across a live link drags the link rather than selecting its words, so draw the button with its label and leave the link for the real build.
• Go easy on bold mid-sentence. A suggestion that runs across bold or a link cannot be swapped in one click. Bold a whole line, or none of it, in the lines the client is likely to rewrite.

If an AI assistant builds the page, it does this for you. Ask Claude, ChatGPT or Codex, connected to Stacktree, for something like:

Put these three emails on one review page for Juniper. Show the subject line
and preview text as text at the top of each email, give each email its own
heading, and draw the buttons as styled text. Publish it to Stacktree with
comments on, for people at juniper.com only.

What comes back to you

You get one email a few minutes after the client finishes, listing every suggestion as "Suggested wording" with their note. On the page's screen, What came back shows each one with the old words struck through and the new words beside them.

Accept puts the new wording in place of the old, as plain text, in the paragraph, cell or button the client left it on. The page is saved as a version first, the link stays the same, and the client sees "Applied as suggested." next to their suggestion. Dismiss tells them "Kept the original wording."

When a suggestion cannot be swapped in one click, it says why, and you get Resolve instead, with a line for the client about what you did. Your assistant can make those changes by hand: it reads every suggestion as the exact words to replace and the wording to put in.

From edits to a yes

Accepted suggestions are not approval. Once the wording has settled, switch on sign-off on the page's screen and ask for it by name. The client approves the whole campaign or goes email by email, Approve or Request changes, with a note. Each answer is recorded against the words they read, so a later edit to email 3 does not undo their yes on email 1. It is a record of who approved what and when, not a legal e-signature. We wrote more on why the two are different in feedback is not approval.

Then the approved copy goes into the platform that sends it. Copy it from the page, or ask your assistant for the final subject, preview text and body of each email in a form you can paste straight into Klaviyo, Mailchimp or HubSpot.

Compared with a shared doc, a PDF proof or reply-all

• Suggesting mode in a shared doc is good at tracked word changes, and it is the right place for a first draft that several people are still arguing about. But the client reads the copy without the email around it, usually needs an account with the doc's provider, and the agreed wording still has to be copied into the template by hand.
• A PDF or screenshot proof shows the layout, but a change comes back as a sticky note that someone has to read, interpret and retype.
• Reply-all is where copy approval goes to get lost: three people, three versions of the subject line, and nobody sure which one won.

The review page keeps the layout and the exact wording together, and the wording that gets accepted is already in the page.

Honest scope

• It changes words. Links, images, colors and layout get a comment instead, and you or your assistant make the change.
• One suggestion stays within one paragraph, cell or button. A selection across two paragraphs offers a comment, not a suggestion.
• It does not send test emails or check how the email renders in Gmail, Outlook or dark mode. Use an email testing tool on the final build for that.
• The page is a review copy. Your email platform still holds the email that gets sent, so the approved wording has to make it there.
• Suggestions do not work on pages encrypted end to end, because the server cannot read those pages to change them.