Skip to content
Moosewave
Demo

TransactionalReview & approval

Consultation response acknowledged email template

A public consultation response received and its influence explained.

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.

Consultation response acknowledgedIllustrative preview
Consultation response acknowledged email template preview

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

A reviewed browser rendition of the consultation response acknowledged 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.

Responses are not tallied by machine. Each is read, themes are drawn out, and representative comments are quoted anonymously in the report.

What you can change

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

What to keep clear

  1. State or event context
  2. Plain-language explanation
  3. Three labelled facts
  4. Primary and secondary action
  5. Support or privacy 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
Newton St Loe Consultations
Subject
Your response is in, and here is how it will be used
Preheader
Read by a person. Counted, and quoted if useful.

Response received

Every response is read by a person

Responses are not tallied by machine. Each is read, themes are drawn out, and representative comments are quoted anonymously in the report.

Consultation closes

31 October

Report published

January

Your response

Read and themed

See the consultationAmend your response
You can amend or withdraw your response until the closing date. After that it forms part of the record.

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.

Transactional email APIConnect the message to a real product event and keep its outcome visible.IntegrationsCarry the right customer and event context into the draft.SecurityKeep account, access, and recovery boundaries explicit.MCP for agentsAdapt presentation without quietly changing the event being explained.