← Back to portfolioGREG MAYS
Journey Builder · Case study

Pre-Approval Nurture Journey

The problem
A lead who fills out the website pre-approval form is at peak intent — and then has to wait for a human. Unattended, that intent decays by the hour.
The build
A 5-day Journey Builder flow with a 4-way loan-type split, so a VA refinance lead and a first-time buyer never see the same message.
My role
Journey architecture, entry and exit logic, decision splits, all email copy and builds, and the website content each path links to.
Journey BuilderSalesforce data entry event4-way decision splitDynamic merge fieldsRound-robin LO handoffPer-step exit criteria

How it works

The journey enters on a Salesforce data event the moment the Lead record is created, confirms receipt immediately, then splits four ways by loan type. Each path gets the same cadence — options, calculator, education, handoff — but different content, all of it linking back to UMortgage web pages and blogs written for exactly that loan type.

The last send is the handoff: dynamic merge fields introduce the lead’s round-robin-assigned Loan Originator and reroute replies to them directly, so the first human touch feels like a continuation instead of a cold start.

Journey flow · 10 steps · 4 content paths
Entry source · Salesforce data event

Lead created: website pre-approval form

Fires when a Lead is created with Forms_Filled_Out__c = “Website Pre-Approval” and a referral status that is neither Accepted nor Declined — the window where marketing, not an LO, owns the relationship.

Step 2 · Decision split · 4 ways

Branch by loan type

Everything downstream is tailored to the path:

Standard PurchaseVA PurchaseStandard RefinanceVA Refinance
Wait · 1 day
Wait · 1 day
Wait · 1 day
Wait · 1 day
Exit

Lead handed off

The relationship continues 1-to-1 with the assigned Loan Originator.

After every step: exit criteria remove any lead whose Referral_Lead_Status__c = Declined — nobody keeps getting nurture email after they’ve said no.