At PingPong I replaced a 30-day calendar drip with five account-state triggers: application started, KYC pending, KYC approved, first funding, first payment. The journey now advances on what the account just did.
Every onboarding system I've inherited made the same bet: that day 3 means the same thing for every new user. It never does. One account is stuck on verification, another already moved money, and both get the same “here's a tip” email because the calendar said so.
At PingPong I rebuilt the onboarding email system around real-time account state instead of a 30-day calendar drip. I threw out the sequence and built five account-state triggers in its place: application started, KYC pending, KYC approved, first funding, first payment. Each one fires because the account changed, and I gave each one a single job, which is moving the user to the next state.
The results made the argument for me. KYC submissions went from roughly 10% of registrations to 35–40%, and average KYC completion time fell from 140 hours to 24–48 hours. Same product, same audience. The only thing that changed was what the emails listened to. The industry moved the same direction: API-triggered campaigns grew ~33% on Braze in 2025 while time-based sends fell ~19%, and calendar blasts to stuck accounts burn the 0.3% spam budget that onboarding depends on.
Activation is the first meaningful action the account takes. For a payments product that was the first payment, and everything upstream of it, application, KYC, first funding, was a state on the way there. I name the target action first, then work backwards to the states that gate it.
A trigger is only as good as the field it watches. The KYC-approved cadence runs on one field mapping: enrollment fires when kyc_status flips to Approved, and the journey exits the moment first_funding_date is set, once per lifetime. I spent most of the build getting that mapping right.
I built three journeys: orientation at signup, KYC-progress support during verification, and activation after compliance approval. I measured every send. Between state changes I kept the pacing deliberate, three sends carry the unfunded wait after approval, then the system goes quiet until the account moves again.
Behavioral systems fail silently. A compliance-driven change to state flips once broke enrollment without erroring, and I only caught it because the KYC-pending segment quietly dropped to zero. I turned the fix into standing practice across the workflow layer I built: I put a count alert on every trigger segment that flags zero enrollments. If a trigger stops firing, I want a page the moment it happens.
The old system sent 30 days of scheduled emails to every registration, whether the account was stuck at KYC or already funding. I replaced it with five account-state triggers and gave each cadence one measurable job. KYC submissions climbed from roughly 10% of registrations to 35–40%, and average completion time collapsed from 140 hours to 24–48 hours.
This activation engine sat inside a larger machine. At PingPong I owned the marketing for the cross-border payments line end to end as it scaled from $2M to $76M in year one and past $250M+ in year two. Sales carried the deal conversations and finance ran the payment rails; the activation programs timed to usage signals instead of calendar guesses were mine.
KYC submissions 10% → 35–40% · completion 140h → 24–48hHe is intelligent, willing to learn, and is a hard-working performer amongst his peers at Tolocal. Finally, he does what he says he will do because his word is guaranteed. This is a unique and powerful combination of skills and experience.
Victor KaoVP of BD, Reward Networks
Define the meaningful action, watch for the signal that says it happened, and stop guessing on a calendar.