Skip to content
Moosewave
Demo

MarketingNewsletter & editorial

A re-run email template

An old piece republished with the reasoning given.

Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.

Responsive design preview

See the message before you make it yours.

Compare the desktop and mobile compositions, or unfold the full design. The complete starting copy remains readable below.

A re-runIllustrative preview
A re-run email template preview

Auto follows your screen width. Scroll inside the frame to inspect the complete email.

A reviewed browser rendition of the a re-run structure. It is not a send receipt or an inbox-placement claim.

Want to change the copy and style?

Try one of the editable browser templates.

This page is a read-only reference. The five hands-on studios let you edit a local preview, compare desktop and mobile, and review every change before continuing.

See editable templates

Message anatomy

A useful starting point, with the important parts named.

Republishing old work is usually filler. This one is being run again because the application it describes has been resubmitted almost unchanged.

What you can change

  • Brand name
  • Subject line
  • Preheader
  • Eyebrow
  • Headline
  • Supporting copy
  • Primary action label
  • Primary action URL

What to keep clear

  1. Campaign context
  2. Headline and editorial premise
  3. Three skimmable sections
  4. Primary and secondary action
  5. Preference and unsubscribe footer

Complete starting copy

Read it as text, not only as a picture.

Sample details are fictional. Replace them with reviewed customer and event data before use.
From
Coppice Lane Chronicle
Subject
Running a piece from 2019 again, and why
Preheader
It is about to become relevant. Read it before it does.

From the archive

Six years old and about to matter again

Republishing old work is usually filler. This one is being run again because the application it describes has been resubmitted almost unchanged.

The piece

From March 2019, about the drainage implications of the site. Nothing in it has been edited and one figure in it is now known to be wrong.

Why now

Because the application has been resubmitted with essentially the same drainage strategy and the consultation closes in three weeks.

The wrong figure

The run-off calculation in paragraph nine, which I got wrong and which a reader corrected in April 2019. The correction is attached.

Read the pieceSee the new application
Archive pieces are never edited. Corrections attach to them and stay attached.

Moosewave MCP

Give an agent the structure, the job, and a stopping point.

A compatible MCP app can inspect this reference and create a separate workspace draft when it has permission. The brief cannot send.

The brief asks for a new draft and stops before send.

Read the complete brief

Connected work

Take the design beyond the canvas.

AutomationsPlace this message inside a journey with a clear trigger and exit.AudiencesChoose who should receive it, and who should be left out.AnalyticsMeasure the response that matters after the send.MCP for agentsAdapt the structure through a compatible assistant with limited workspace access.