Win-back email for fintech: bring dormant account holders back

Fintech dormancy is not ecommerce cart abandonment. The user already gave you money. Your product is holding it. That flips the win-back logic: you are not recovering a lost sale, you are reminding someone their balance still exists, still earns, and still belongs to them.

Trigger. Fire this email at 75 to 90 days of no login AND no transaction. Earlier than 60 days feels like surveillance. Later than 120 days and you run into two fintech-specific problems. First, the escheatment clock. In several US states, balances inactive past a threshold (often three years) must be turned over as unclaimed property. Keeping the account visibly active protects the user from that path. Second, stale accounts trip fraud and abuse rules. A user who signs in after a year of silence may get blocked by step-up authentication or a frozen-card flow, and that kills the re-engagement you just paid for.

The offer. Resist the cash bonus. In US fintech, incentives above small thresholds can trigger 1099-INT reporting and bonus abuse, and thin disclosure invites regulator attention. The cleaner offer is the value the user already earned but cannot see from the inbox: interest accrued since last login, round-up totals, goal progress. That is true, already owned by the user, and compliance-clean.

Copy angle. Lead with a real number. "You earned $42.18 in interest" outperforms "We miss you" in every test. Specificity also keeps you honest, because a number is either accurate or it is not, which forces the disclaimer discipline fintech requires. State the APY, mark it variable, date it, and name the partner bank and the FDIC line. Never use "guaranteed," "risk-free," or "free money." Those phrases are how marketing copy becomes a compliance finding.

CTA. One action. "Sign in to see your balance." Not "claim your reward" (implies a bonus you are not paying). Not "update your account" (implies something is wrong and scares the user). The user should feel they are checking on money that is already theirs, not completing a chore for you.

Email clients still render like it is 2009. This template is engineered for that reality.

The layout uses nested HTML tables, not divs or flexbox. Gmail strips flexbox. Outlook ignores CSS positioning. Tables are the one structure every client parses the same way, so the two-column stat block and the hero hold their shape in Apple Mail, Gmail web, and the Gmail Android app alike.

Every style rule is inline. Gmail keeps only the inline styles on the body of a message plus a single style block in the head. Anything you rely on from an external stylesheet never arrives. Inline CSS means the email looks right even after the client strips the rest.

The button is a bulletproof VML button. Outlook 2007 through 2021 use Microsoft Word to render HTML, and Word cannot draw CSS button backgrounds or border-radius. A VML fallback draws the button as a vector shape, so Outlook users see a real colored button with padding, not a flat text link.

The body copy is live text, not text baked into an image. Live text scales for the reader and loads with no network round trip. It also stays legible when images are blocked, which is the default state in many Outlook and enterprise installs.

Dark mode is handled with a color-scheme meta tag in the head. Apple Mail and Outlook dark modes invert dark backgrounds if the email does not declare its scheme. Declaring color-scheme: light dark tells the client the email is aware of dark mode, which prevents surprise inversions that turn your navy hero into a washed-out grey.

There is one mobile media query, scoped to a 480px breakpoint. It drops the hero headline size and lets the two-column stat block stack. A single media query is enough; more queries just mean more clients that ignore them anyway.

Web fonts load with a full system fallback chain. Inter is requested from Google Fonts, and if the client blocks remote fonts (which Gmail does), the stack falls back to the system UI font. No missing-font boxes.

1. Copy the compiled HTML. Use the export button on the preview to copy the rendered HTML, not the MJML source. ESPs send HTML.

2. In Klaviyo, open your campaign or flow email, add an HTML block, and paste. For a full-document import, click the source icon in a text block and paste the entire HTML document.

3. In Mailchimp, choose Campaigns, start a campaign, and under Content select Code your own, then Paste in code. Paste the full HTML and let Mailchimp inline any remaining styles.

4. Swap the brand. Replace "Haven" and the logo text, swap the navy #0B2545 and teal #1B998B for your client's palette, and update the two URLs.

5. Wire the merge tags. This is where fintech differs from retail. You want the interest, balance, and APY to come from live data, not be hardcoded. - Klaviyo: {{ person|lookup:'first_name'|default:'there' }} for the greeting. For the earned-interest figure, sync the value as a custom profile property and reference it as {{ person|lookup:'interest_earned'|default:'$0.00' }}. The APY, partner-bank name, and FDIC line should be hardcoded once, approved by compliance, and reused across every send. - Mailchimp: *|FNAME|* for the name, and custom merge fields like *|INTEREST_EARNED|* and *|BALANCE|* for the figures. Define these merge fields in Audience settings before you send.

6. Trigger on dormancy. In Klaviyo, build a segment of profiles where Last Login (or your custom Last Activity date) is older than 75 days, and drop them into a flow with this email. In Mailchimp, tag dormant contacts and send to that tag.

7. Test before you send. Send a proof to Gmail web, the Apple Mail app, and Outlook desktop. Toggle dark mode on each. Confirm the interest number pulled through the merge tag and that the FDIC disclaimer is intact and readable at small size.