Preference Centre Email Template — A Form Set as a Ledger
A preference email drawn as a ledger of three checkbox rows, each with a label and a line of detail and the first already ticked, with no fills and no button in the artwork.
Preview unavailable — view the prompt below.
The prompt
Two ways to build this email in plain language. The fastest is Temway's in-editor assistant — open the chat drawer in the email editor and paste the recipe below. Or connect Claude or ChatGPT via Temway's MCP and paste it there; the agent builds the email step by step. Either way, adapt the copy and colors to your brand.
- An email is a top-to-bottom stack of blocks — the recipe follows that order.
- A
[layout]step becomes a single image (great for heroes); everything else stays live text and links. - Theme the footer to match — the recipe's last step does exactly that.
Want this exact email? Click Use this template below to clone
it into your workspace, then ask the in-editor assistant to rebrand it. Over MCP, tell
your agent to clone the Temway share fszYscVG7FnHwsCxHrFqo and rebrand. For the
full model, point an MCP agent at get_concept — email-structure,
layouts-vs-emails, design-recipes.
The email you send instead of losing a reader. It is a form, so it is drawn as one: three checkbox rows, each with a label and a line of detail, the first already ticked to show the state. There are no fills and no button in the artwork, because the destination is a settings page and pretending otherwise wastes the trip.
Snapshot
- Goal: move a reader who is close to unsubscribing onto a frequency they will actually tolerate.
- Audience & tone: subscribers whose engagement has dropped. Matter-of-fact, respectful, zero persuasion — this is a menu, not a pitch.
- Palette: page
#ededed· container#ffffff· text#18181b/#707072(muted) · accent#0c4a6e - Font:
Helvetica, Arial, sans-serif - Artwork: one
preference-ledgerlayout hero (a single rasterized image), 600×440 — A preference form as three repeated cells: a checkbox and a one-line label per row, with the first row already ticked. No fills and no buttons — the destination is a settings page, and pretending otherwise wastes the recipient a trip. Everything below it is native, selectable, clickable.
Build recipe
Each step is one block in the flat stack, top to bottom.
[native]= a real email block.[layout]= a free-form layout embedded as a single image.
- [native] Standfirst — text. “You get three emails a week from us right now — you can change that in one click.”, fontSize: 20, color
#18181b, left. - [layout] Layout hero —
preference-ledger— apply thepreference-ledgerlayout template (600×440). A preference form as three repeated cells: a checkbox and a one-line label per row, with the first row already ticked. No fills and no buttons — the destination is a settings page, and pretending otherwise wastes the recipient a trip. Alt text: “Choose what you hear about: product news (selected), tips and walkthroughs, offers and events”. - [native] Body copy 1 — text. “Product news — roughly monthly, what shipped and what is next. Choose this”, fontSize: 16, color
#18181b, left. - [native] Body copy 2 — text. “Tips and walkthroughs — occasional, how other teams use the editor. Choose this”, fontSize: 16, color
#18181b, left. - [native] Body copy 3 — text. “Offers and events — sales, launches, research invitations. Choose this”, fontSize: 16, color
#18181b, left. - [native] Primary CTA — button. Label “Update my preferences”, fill
#0c4a6e, color#ffffff, shapeStyle: ‘0_1’, left. - [native] Rule — divider. full-measure rule, 1px, color
#e9e9e9. - [native] Body copy 4 — text. “Not the right month? Pause everything for 90 days and we will pick it back up after.”, fontSize: 16, color
#18181b, left. - [native] Body copy 5 — text. “Or leave the list entirely — one click, and we will not email to ask why.”, fontSize: 14, color
#707072, left. - [native] Footer rule — divider. short (96px) rule, 1px, color
#e9e9e9. - [native] Footer social — social. Icon row, social.color
#0c4a6e, style circle-outline, center. - [native] Footer address — address. Postal address + unsubscribe, address.color
#707072, address.fontFamilyHelvetica, Arial, sans-serif, center.
Make it yours
- Make each native option a real one-click link, not a trip to a settings page with a login wall. The artwork is a picture of the choice; the links are the choice.
- State honest frequencies. “Occasional” that turns out to mean twice a week is the specific betrayal that generates spam complaints.
- Keep the pause option. A 90-day pause saves subscribers that a binary stay-or-leave email loses outright.
About re-engagement email templates
A re-engagement email targets one specific, identifiable moment: someone stopped opening. The job is to re-earn attention with a real incentive or a clean exit — not to guilt-trip a subscriber back with vague "we miss you" copy that never says why it's being sent now.
See all re-engagement templates →How long should someone be inactive before sending a re-engagement email?
Most teams trigger a win-back after 30-90 days of no opens or logins — long enough to be a genuine lapse, not so long that the incentive has to be unreasonably large to work.
What makes a re-engagement email different from a regular promotional send?
It has to acknowledge the gap directly — "it's been a while" — rather than pretending nothing changed. The templates below open with that acknowledgment before the offer.
Should a win-back email always include a discount?
Not necessarily — the templates below pair an incentive for commerce win-backs, but the nonprofit volunteer and donor comeback template leans on reconnection and impact instead of a discount.
What should happen if someone doesn't respond to a re-engagement email?
Plan a follow-up suppression or list-cleanup step outside the email itself — a re-engagement template's job is the ask, not the list hygiene that follows it.