Trevor closes a loan on a Tuesday. Buyer’s happy, agent’s happy, everybody shakes hands. Then Trevor does what almost every loan officer does next: nothing. The file moves to funded, the CRM record goes quiet, and that client drops into the same fog as the other 600 people in his database. Eleven months later that buyer refinances with the LO who sent a birthday text. Trevor never knew the loan existed until he saw it on a rate sheet.
(Trevor is a composite, stitched together from the DFW LOs whose Jungo orgs I’ve opened. You’ll recognize the org.)
Most LOs have Jungo open eight hours a day and use four fields in it. Name. Phone. Loan status. Notes. Everything else sits empty. And empty fields are why your follow-up is a guess and your pipeline report is a fairytale.
Jungo runs on Salesforce, so every field is queryable, reportable, and automatable, as long as something actually puts data in it. The pattern in every shop I’ve opened is the same: 50-plus useful fields on the Contact and Opportunity objects, three of them populated. Here are the five most LOs ignore, then the one that quietly does more for repeat business than the other four combined.
Field 1: Last Contact Date
Object: Contact. This is the only honest answer to “when did I last talk to this person?” LOs answer that from memory, and memory lies the second a database crosses a few hundred names. Trevor would have sworn he “stays in touch.” The field would have shown 14 months of silence.
What to do: Auto-update it on any outbound email, logged call, or text. The standard Jungo integration already does this. It just isn’t turned on.
Field 2: Referral Source
Object: Contact and Opportunity. Without it you cannot answer the most expensive question in your business: where does my best business actually come from? I’ve watched LOs swear by “realtors” while the data said 60% of their closed loans came from one CPA and one financial advisor, and zero marketing energy was going to either.
Put a number on that miss. Say Trevor closes 80 loans a year and his average commission is $4,500, so about $360,000. If he’s spending his attention on the wrong sources and that costs him even 8 closings he could have kept warm, that’s $36,000 a year walking to whoever did know their numbers. Your numbers will be different. The size of the hole won’t be small.
What to do: Populate it on every new contact and Opportunity. Make it required. Build a report grouped by Referral Source, sorted by closed volume. Run it the first Monday of every month.
Without Referral Source populated, every “marketing strategy” talk is a guess. With it populated, the next move picks itself.
Field 3: Close Date Anniversary
Object: Opportunity. This is the trigger for the highest-ROI automation in mortgage: the closing-anniversary touch. A text or a card on the one-year mark pulls referrals at a rate I would not believe if I hadn’t built it and watched it run. This is the exact touch Trevor’s database never got, and the exact reason that refinance went somewhere else.
What to do: Confirm Close Date is populated on every closed Opportunity. Fire a touch on the anniversary: email, text, or a physical card through Postable or Handwrytten. Set it once, let it run forever.
Field 4: Loan Product / Loan Type Last Closed
Object: Contact (roll-up). When rates move or a product launches (HELOC, DSCR, non-QM), you want to filter the whole database in 30 seconds. “Show me every past client who closed an FHA in the last 18 months.” If Loan Product lives only on the old Opportunity and never rolls up to the Contact, that filter turns into a Sunday-afternoon project, which means it never happens.
What to do: Add a roll-up summary field on Contact that pulls Loan Type from the most recent closed Opportunity. Save the list view. You now have a one-click rate-change campaign instead of a wish.
Field 5: Preferred Communication Channel
Object: Contact. Some borrowers want texts. Some quietly hate them. Treating all 600 the same is the cheapest way to wear out a database, and you never see the damage because nobody unsubscribes from a relationship, they just stop answering.
What to do: Add a picklist: Email / Text / Phone / Mail. Capture it at application. Filter every outbound campaign by it.
The one that prints money: Last Touch by Type
Object: Contact (custom). Here’s where the fairytale pipeline finally breaks. Last Contact Date tells you when you last touched someone. Last Touch by Type tells you what the touch was: email, call, text, in-person, value-add (a market update, a gift, an event invite), or transactional (a doc chase).
A producing LO needs two facts about every past client, and one of them is the whole game.
When did I last touch them.
Was that last touch valuable, or was it me asking for their W-2?
If the last three touches with a past client were all “send me that document,” the relationship is on life support and you can’t feel it. If the last three were a market update and a birthday note, that client is going to refer. Trevor had thousands of touches logged. Not one of them was tagged, so he couldn’t tell the difference between a fan and a stranger, and he treated them all like strangers.
What to do: Add a picklist (Email / Call / Text / In-Person / Value-Add / Transactional) and auto-populate it from the activity type. Then build one report: contacts whose last three touches are all Transactional. That list is everyone about to forget you. Call them this week.
The honest answer to “who’s about to forget me” lives in this one field. Most LOs don’t have it because nobody ever told them to build it.
Why this never gets done
The Jungo admin who set the org up left two years ago. The fields exist. The automations that fill them were never switched on. This is a 4-to-6-hour fix in most shops, not a six-month consulting engagement, which is exactly why it keeps falling off the list. It’s never urgent until it’s the refinance you read about on a rate sheet.
This isn’t for you if you close under a dozen loans a year or you’re brand new and your database is your phone’s recent calls. At that size, manual follow-up still works. The fairytale pipeline is a problem you earn by getting busy enough to outgrow your own memory.
How HTS does this
A CRM audit is the first thing in every HTS engagement that touches a mortgage CRM. It’s built into the HTS Operating System tier and available as a standalone add-on. The deliverable is plain: the fields you have, the ones you should turn on, and the three automations that will populate them without changing how you work. We ran a version of this inside a recent HTS engagement and it produced a working report inside two weeks.
If your Jungo or Salesforce org looks like every other one I’ve opened, 50 fields and four of them filled, that’s fixable, and it’s faster than you think. Book a discovery call. We’ll spend it on your actual org, not a pitch. Bring up the one client you know you’ve gone quiet on. We’ll find the other 200 the system already knows about.
HTS does not provide loan advice, legal advice, or financial advice. Mortgage and finance professionals are responsible for their own regulatory compliance.