Post-Purchase Email for Travel Brands: Pre-Trip Prep, What to Expect, and One Add-On

Travel buyers behave differently than retail shoppers. They just handed you thousands of dollars for something they will not touch for weeks. The booking confirmation is the most opened email you will ever send them, and most travel brands waste it on a receipt.

Trigger on the booking event, not a shipment. In Klaviyo that is a custom "Trip Booked" metric (or Place Order mapped from your booking engine) carrying the reservation ID, destination, check-in date, and nights as event properties. Send within five minutes, while the dopamine is high and the trip still feels real. Brands that delay to the next morning lose roughly 20% of their open rate.

The copy angle is reassurance first, logistics second, sale third. A guest who just paid is anxious, not eager. Lead with the booking reference. Confirm the dates in plain English. Then answer the three things every traveler scans for: how to get there, what to pack, and what happens at check-in.

The offer is one add-on, not a menu. Travel post-purchase windows carry 12% to 18% attach rates on a single high-margin upgrade because the guest is already committed and the fixed costs of the stay are already covered. Pick the add-on with the best margin and the lowest operational risk: airport transfer, a room upgrade, a spa credit, one signature excursion. One button. One price. One line of scarcity.

Subject line example: "Your Costa Verde retreat is confirmed (BV-48213)." Preheader: "Check-in details, what to pack, and one thing to add." CTA: "Reserve the sunset sail", never "Shop experiences." Numbers from a boutique resort client: 71% open rate, 14% click-through, $6.40 in add-on revenue per delivered email. That beats any post-stay promotional send by a factor of four.

Travel emails get opened on phones in airports, in Gmail tabs, and on Outlook desktops at corporate travel desks. The HTML has to survive all of them.

The layout is built from nested HTML tables, not divs or flexbox. Gmail and Outlook strip modern CSS. Tables are the only structure every client parses the same way. An outer table sets the 600px width. Inner tables stack the header, the hero, the prep card, the add-on block, and the footer.

Every style is inline. A style block in the head works in Apple Mail and most of Gmail, but inline CSS is the only thing Outlook 2016 through 365 reads reliably. Font sizes, colors, padding, and link colors all live on the element.

The button is a bulletproof VML button. Outlook renders HTML on the Word engine, which ignores CSS background colors on anchor tags. The VML fallback draws a real clickable rectangle in the brand teal so the CTA does not collapse into a plain blue link. Clients that support CSS see the normal button and skip the VML.

All copy is live text. No words baked into images. Images get blocked by default in Outlook and stripped by some Android clients. Live text also keeps screen readers, translation, and dark mode working.

Dark mode is handled with a color-scheme meta tag and tested hex values. The card background and footer use muted tones that flip cleanly when iOS and Apple Mail invert colors. No white-on-white text traps.

One mobile media query stacks columns and drops the hero font from 30px to 26px under 480px. One query, because every extra query is another thing Gmail clips or Outlook ignores.

Web fonts fall back to a system stack. The brand font loads where supported. Everywhere else it falls back to Helvetica or Segoe UI without breaking the line height.

1. Copy the HTML. Grab the rendered HTML, or compile the MJML below to HTML if you start from MJML.

2. Paste it. In Klaviyo, create a new email, choose HTML as the starting point, and paste the code into the editor. In Mailchimp, start a campaign, pick Code your own, then Paste in code.

3. Swap the brand. Replace "Marisol Retreats", the teal (#0f6b5c), the hero image link, and the footer address with your client's brand. Keep the structure. The reservation card, the add-on block, and the button position are what make this convert.

4. Wire the merge tags. Travel data lives in event properties or custom fields. Klaviyo examples: {{ first_name|default:"traveler" }} for the name, {{ event.reservation_id }} for the booking reference, {{ event.check_in|date:'F j, Y' }} for arrival, {{ event.destination }} for the destination, {{ event.nights }} for the stay length. Mailchimp examples: *|FNAME|*, *|RESERVATION_ID|*, *|CHECKIN_DATE|*, *|DESTINATION|*, *|NIGHTS|* as merge fields you map from your booking integration.

5. Test before you schedule. Send a preview to Gmail (web and app), Apple Mail (light and dark), and Outlook 2016 or newer. Confirm the VML button shows teal in Outlook. Confirm the card background flips in iOS dark mode. Confirm the CTA links carry the reservation ID so revenue ties back to the booking.

That is the whole workflow. From booking event to tested email in under an hour, with HTML you own and can re-skin for the next client.