Mortgage CRM Requirements by Lead Source: Realtor, Consumer Direct, Past Client, and Purchased Lead
Text-free editorial illustration of a loan officer comparing mortgage lead-source workflows for referral, consumer-direct, past-client, and purchased leads.
Short answer: A mortgage CRM should not treat every lead as the same. A useful setup preserves how the relationship began, assigns an accountable owner, records the next meaningful action, and makes exceptions visible. Realtor referrals, consumer-direct inquiries, past clients, and purchased leads each need different context and review rules.
Lead source is more than a reporting label. It changes what a loan officer needs to know before taking action. A referral may need relationship history and partner context. A consumer-direct inquiry may need a clean intake and duplicate check. A past client may need a record review before any outreach. A purchased lead needs a transparent source, ownership, and follow-up process.
Use lead source to define the operating requirement
Lead-source family
What the record should make clear
Review question
Realtor or partner referral
Relationship owner, referral context, and current borrower handoff.
Can another team member understand the relationship and next step?
Consumer-direct inquiry
Original source, consent or contact-status review, intake completeness, and duplicate risk.
Does the accountable loan officer have enough context to make a useful first response?
Past client or database contact
Prior relationship history, current record quality, and a reason for the review.
Is the information current enough for the intended conversation?
Purchased or third-party lead
Vendor/source detail, acquisition date, routing rule, and missing-information path.
Can the team trace the lead to its original source and correct a disputed record?
See this in a live workflow: Bring one a lead-source-specific CRM requirement to a BNTouch demo. Ask how your team could preserve relationship context, assign an accountable owner, and surface the required next action or exception. Confirm current configuration and plan scope in the demonstration.
Set the minimum fields before comparing platforms
Write the lead-source families the business actually uses. Avoid a long list of labels that no one can maintain.
For each family, define the source value, accountable owner, expected next action, and exception path.
Decide what information must be visible before a loan officer starts a new relationship or follow-up task.
Test a duplicate, an unavailable owner, and an incomplete record for each high-volume source.
Review a small sample every week to see whether the source and next-action fields are still useful.
Do not confuse a source tag with a workflow
A source tag identifies where a record entered. It does not decide who owns the relationship, whether information is complete, or what happens when the normal path fails. Those decisions belong in a documented operating model. Software can support that model only after the business has made the rules clear.
Next step: List your four most important lead sources and write one sentence for the owner, required context, next action, and exception path for each. Bring that worksheet to a BNTouch product consultation when you are evaluating how a mortgage CRM could be configured around your team’s workflow.
Questions loan officers ask
Why should CRM requirements change by mortgage lead source?
A referral, consumer-direct inquiry, past client, and purchased lead arrive with different relationship context and ownership needs. The CRM should preserve the information needed for the next responsible action.
What is the minimum record for a new mortgage lead?
Start with a source, timestamp, accountable owner, contact information provided, meaningful next action, and a path for incomplete or duplicate records. Add fields only when the team can explain the decision they support.
Prove the lead-source workflow with a record, not a feature list
Each lead source creates a different operating requirement. A referral-partner lead needs shared relationship context. A consumer-direct lead needs a reviewable response process. A past-client opportunity needs clean history and a human-approved outreach plan. A purchased lead needs clear source attribution and ownership from the moment it enters the CRM.
This walkthrough demonstrates a stage-triggered re-engagement workflow. Treat it as one workflow example: each team must define its own stage rules, timing, reviewer, and stop conditions.
