Return Confirmation Email Template — Refund on the Way
A return-received notice that answers the only two questions that matter: how much is coming back, and when. Deliberately plain, with an outlined secondary CTA.
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 XEokrT65DjZH32tR3PZQI and rebrand. For the
full model, point an MCP agent at get_concept — email-structure,
layouts-vs-emails, design-recipes.
A customer who has just posted a parcel back to you is mildly anxious and has exactly two questions: how much am I getting, and when. This email answers both above the fold, states plainly that nothing further is required from them, and sets the refund expectation wide enough that the bank can’t make you a liar. Warm greys, one teal accent, and an outlined button — a return confirmation should not look like a campaign.
Snapshot
- Goal: close the loop on a return so the customer stops worrying and doesn’t open a support ticket.
- Audience & tone: someone mid-refund. Factual, calm, slightly apologetic in structure but not in words — over-apologising reads as a company that returns things badly and often.
- Palette: page
#e8e7e6· container#faf9f8· text#1c1917/#6d6a69(muted) · accent#0f766e - Font:
Arial, Helvetica, sans-serif - Artwork: none — fully native blocks.
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] Logo — logo. Brand mark, left-aligned.
- [native] Kicker 1 — text. “Return received”, fontSize: 14, color
#0f766e, left, uppercase. - [native] Story title — text. “We’ve got it — nothing else needed”, fontSize: 20, color
#1c1917, left. - [native] Body copy 1 — text. “Your return arrived March 10 and passed inspection — you do not need to reply, call, or follow up.”, fontSize: 16, color
#1c1917, left. - [native] Rule 1 — divider. full-measure rule, 1px, color
#e9e9e9. - [native] Kicker 2 — text. “What you sent back”, fontSize: 14, color
#0f766e, left, uppercase. - [native] Body copy 2 — text. “Fieldstone Wool Overshirt — Oatmeal, size M, quantity 1, $68.00. Reason given: too large.”, fontSize: 16, color
#1c1917, left. - [native] Rule 2 — divider. full-measure rule, 1px, color
#e9e9e9. - [native] Kicker 3 — text. “Your refund”, fontSize: 14, color
#0f766e, left, uppercase. - [native] Headline — text. “$68.00”, fontSize: 28, color
#1c1917, left. - [native] Body copy 3 — text. “Refunded to the card used at checkout, arriving in 3 to 5 business days — occasionally up to ten. It shows on your statement as FIELDSTONE RETURN.”, fontSize: 16, color
#6d6a69, left. - [native] Secondary CTA — button. Label “View the details”, fill
transparent, color#1c1917, shapeStyle: ‘0_1’, left. - [native] Body copy 4 — text. “If the refund has not arrived after ten business days, reply to this email and we will look into it.”, fontSize: 16, color
#6d6a69, left. - [native] Fine print — text. “This is a required service notice — manage preferences or unsubscribe anytime.”, fontSize: 12, color
#6d6a69, left. - [native] Footer rule — divider. short (96px) rule, 1px, color
#e9e9e9. - [native] Footer social — social. Icon row, social.color
#6d6a69, style circle-outline, center. - [native] Footer address — address. Postal address + unsubscribe, address.color
#6d6a69, address.fontFamilyArial, Helvetica, sans-serif, center.
Make it yours
- Set the refund window to your genuine worst case, not your average. Every day you promise and miss costs a support ticket; every day you under-promise and beat is free goodwill.
- Put your real statement descriptor in step 11, in the exact casing the bank shows it.
- Keep the button outlined and resist adding product recommendations. The moment a return confirmation starts cross-selling, it stops being trusted — and this is one of the highest-open emails you will ever send.
About transactional email templates
Transactional email gets the highest open rates of any category, because recipients expect and want it — an order confirmation or shipping update gets read almost every time it lands. That makes it a branding opportunity most teams under-invest in relative to promotional email.
See all transactional templates →Why bother designing a transactional email — isn't the information all that matters?
Transactional emails have the highest open rates of any email you send, because recipients expect and want them — that makes them a real branding opportunity most teams under-invest in relative to promotional email.
What information has to be in an order confirmation email?
Order number, itemized contents, total charged, and expected delivery or next steps at minimum — the order-summary template below leads with those before anything promotional.
Can I add an upsell or review request to a transactional template?
Yes, but keep it secondary — the templates below place the transactional information first and any cross-sell or review ask below the fold, so it never competes with the confirmation itself.
Do these transactional templates work for both order and account-related events?
Yes — the collection below covers order confirmations and shipping updates as well as payment receipts and return confirmations, so both commerce- and account-triggered sends are covered.