Skip to content
Moosewave
Demo

MarketingNewsletter & editorial

Reader question answered email template

An issue built around a question from the audience.

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.

Reader question answeredIllustrative preview
Reader question answered email template preview

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

A reviewed browser rendition of the reader question answered 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 reader asked why one particular field floods when the ones either side do not. The answer turned out to be an enclosure-era drainage scheme and a culvert nobody maintains.

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
Fernhill Review
Subject
A reader asked why the field floods, and the answer is 1847
Preheader
A drainage decision made 178 years ago.

You asked

Why one field floods, and the answer is a decision from 1847

A reader asked why one particular field floods when the ones either side do not. The answer turned out to be an enclosure-era drainage scheme and a culvert nobody maintains.

The question

Why the field north of the lane floods every winter while the two beside it, on the same soil and the same contour, never do.

What I found

An 1847 drainage plan in the record office showing a culvert that was diverted in the enclosure. It still exists and it is blocked.

What it means

About four hours with a rod would probably fix a problem that has persisted for a century. Somebody is now finding out who owns it.

Read the full pieceAsk a question
Reader questions make about a third of what I write. You can send one by replying to this message.

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