Skip to content
Moosewave
Demo

MarketingNewsletter & editorial

A response to criticism email template

A public criticism answered directly rather than ignored.

See the full preview Use it with MCP

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 response to criticismIllustrative preview
A response to criticism email template preview

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

A reviewed browser rendition of the a response to criticism 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.

A published criticism of this letter appeared last week. It is linked at the top rather than characterised by me, and my response follows it.

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
Dunstanburgh Digest
Subject
Somebody has written that this is nostalgic, and they have a point
Preheader
Their piece is linked. My answer is below it.

A response

Their criticism is linked first, and about half of it lands

A published criticism of this letter appeared last week. It is linked at the top rather than characterised by me, and my response follows it.

What they argue

That this consistently frames change as loss and does not distinguish between things worth mourning and things worth being glad about.

Where they are right

On the framing, entirely. Reading back, about two thirds of pieces use the vocabulary of loss without examining whether it applies.

Where I disagree

On the conclusion, that this makes it useless. Recording what went is worth doing even when the going was an improvement.

Read their piece firstRead my response
Their piece is linked in full and unedited. It is worth reading whether or not you read the response.

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.

Keep exploring

Browse all 1405