Skip to content
Moosewave
Demo

MarketingNewsletter & editorial

The final issue email template

A publication ending, with everything settled.

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.

The final issueIllustrative preview
The final issue email template preview

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

A reviewed browser rendition of the the final issue 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.

This ends because I have said what I have to say about this parish, not because of any difficulty. Everything that needed arranging has been arranged.

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
Embleton Envoi
Subject
This is the last one, and everything is arranged
Preheader
Archive deposited, list deleted, domain paid for ten years.

The last issue

The hundred and sixty-second, and the last

This ends because I have said what I have to say about this parish, not because of any difficulty. Everything that needed arranging has been arranged.

Why

Because the last four issues have been written from habit rather than from having something to say, and that is the right moment to stop.

What happens to the archive

Deposited with the record office, free and permanent. The domain is paid to 2036 and redirects to their copy.

What happens to this list

Deleted next week. Nothing is transferred, sold, or handed on, and nobody will write to you claiming to continue this.

See the deposited archiveRead the first issue
Thank you. Nine hundred people read this and about a hundred wrote to me, and the second number is the one that mattered.

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.