The email problem I remember best was silence. This was PingPong, the cross-border payments company where I worked from 2021 to 2025, and this ran in my first role there, Marketing Manager, Ads and Lifecycle, 2021–2023. Our average KYC completion time was 140 hours, and a user could sit in verification limbo that entire time without a single email firing, because nothing in the system was keyed to her state. Nobody noticed until she churned. Submission rate: roughly 10%. That's the backdrop for everything below. One welcome flow is a writing exercise. A full lifecycle across onboarding, KYC, activation, and renewal is a systems problem. Four stakeholders pull in different directions: marketing wants engagement signal, sales wants to know who's warm, support wants fewer tickets. Compliance wants nothing sent that shouldn't be.
Timing beats copy
I built the first KYC cadence on timers (day 2, day 5, day 9) because that's what every onboarding template does. Then I traced real users through it on paper. One would have gotten a “stuck?” nudge while her documents were already in review; another would have been congratulated on progress he hadn't made. A timer is a guess about where somebody is; the account record already knows. I threw that version out before it sent a single email.
The cadences I rebuilt triggered on account status: KYC submission went from roughly 10% to 35–40%, and completion time collapsed from 140 hours to 24–48. The copy stayed the same. Only the trigger changed. That compares the eight weeks before with the eight weeks after, with no holdout, against a monthly registration base in the low thousands, and the 35 to 40 percent is month to month variation.
A user who just registered doesn't care about product announcements. Someone stuck during KYC doesn't want a discount.
If a message can't answer “what state is this user in, and what do they need next,” it doesn't ship. That one rule kills bad sends.
The system underneath the sends
Plumbing enforces that rule. Ours was HubSpot, and the native Salesforce sync is why it fit. I ran the evaluation and recommended it, my manager approved the spend, and everything I built afterwards ran inside that contract. Compliance owned updating KYC status on the Salesforce account record; I built the sync mapping that field to a contact property, and each cadence enrolled on the property change. When the logic keys off state (registered, verifying, verified, activated, stalled), volume drops on its own, because the system stops sending things the user's state has already made irrelevant.
The rest of the fix was people. Email, onboarding, CRM, compliance and support have to define user state the same way. Most “email problems” I've debugged were alignment problems wearing an email costume, and the 140-hour limbo came from five teams with five views of where a user stood.
Writing for a fintech inbox
I write like a colleague giving advice. The early draft of our verification email opened with the product story, what the platform makes possible and why global payments matter. Nobody mid-KYC cares. The version I shipped says: your documents are in review, here are the document issues that most often stall a review, and here's where to reply if compliance asks a clarifying question.
Testing that compounds
I tested mechanically: I ranked every recurring email by open and click-through rate, and the bottom of the ranking became the standing A/B queue, so nobody had to argue every month about what “underperforming” means. I tested subject lines first, because they're the cheapest change with the fastest read; content and CTA placement after. Not everything belongs in the queue. A compliance notice has one job, to be correct and on time, and no version of it wins. Nothing I tested moved a number by double digits either. On an email that goes out every day, it doesn't have to.
Where the returns show up
Fixing KYC completion moved three other things, and I have no numbers for any of them. Support tickets dropped, because users stopped writing in to ask what was happening. Account managers read the funnel off the contact record and stopped asking me for list pulls. Sales conversations got smoother, because users arrived already oriented.
What I'd do Monday morning
Don't open the templates. Ask four questions first: who owns the instance, is there a gate on contact volume, does email live inside the revenue workflow, and can account state trigger a message. If the answer to the last one is no, that's the whole project, map one status field from your CRM to your ESP and hang one cadence off it before you write a single line of copy. The copy is the easy part.