LOS + CRM Integration for Mortgage Pre-Qualification: A Practical Guide

Reference Architecture

1. 01

   Lead capture

   Form or landing page collects intake + consent, fires a webhook to the CRM.
2. 02

   CRM triggers pre-qual API

   CRM automation posts the intake payload to the pre-qualification endpoint.
3. 03

   Decision returns

   Pre-qual API returns { decision, tier, dti_estimate, program, reason_code, artifact_id } in under a second.
4. 04

   CRM routes + LOS writes

   CRM updates lead status and routes; a background job writes the decision + artifact ID into the LOS loan file.
5. 05

   LO acts

   LO opens a Qualified file with the decision, program, and consent already attached.

At Lead Capture

The capture surface — landing page form, dialer intake, or third-party lead feed — is where the consent artifact is created. Display the FCRA + TCPA language inline, store the exact text shown along with a timestamp and IP, and pass the artifact ID with every downstream API call. This is the compliance backbone; skip it and nothing else in the stack saves you.

Into the LOS

Every major LOS supports the pattern:

• Encompass: Partner API + custom fields for tier, DTI estimate, and matched program.
• Empower: Web Services + LOAssistant to write the decision object to the loan file.
• Byte Software: Custom-field write via web services.
• MeridianLink Mortgage: API-based custom field updates on loan creation.

The rule is the same in every LOS: only create the loan file for Qualified leads. DNQ files stay in the CRM until (and unless) a manual review promotes them.

Into the CRM

On the CRM side, the pre-qual decision drives three automations:

• Routing: Qualified files route to the LO whose program specialty matches the returned program.
• Nurture: DNQ files enter a nurture flow appropriate to the reason code (credit-repair path, retry-in-90-days path, cross-sell to a partner lender).
• Reporting: Decision and reason code become filterable dimensions on every LO scorecard and pipeline report.

Two-Week Rollout

Frequently Asked Questions

• Do we need to modify our LOS to integrate a pre-qualification API?

  No. Modern pre-qual layers integrate at the CRM or lead-capture layer and push the resulting decision into the LOS via existing webhook or API paths (Encompass Partner API, Empower Web Services, etc.).

• How long does a typical integration take?

  For a CRM-first integration (HubSpot, Salesforce, Velocify), 3–5 business days is normal. Full LOS write-back adds another week.

• Does the pre-qual result need to live on the loan file?

  Yes — for both compliance (audit trail) and productivity (LO sees the reason code). Store the decision, credit tier, matched program, and consent artifact on the loan record.

• Which CRMs are best supported for mortgage pre-qual?

  Any CRM with webhook + custom-field support works. In mortgage specifically, Velocify, Surefire, HubSpot, and Salesforce Financial Services Cloud are the most common patterns.

• What about lender-portal integrations for wholesale?

  The same API pattern works — the pre-qual runs when a broker submits a scenario, and the decision returns to the broker portal in real time.

• Do we need PII to leave our environment?

  Modern pre-qual APIs accept minimum-necessary fields (name, phone, email, address for mortgage) and return a decision. No SSN, no bank data, no docs. PII exposure is minimal and lives under a signed DPA.

• How do we handle DNQ leads in the LOS?

  Best practice is to hold DNQ files in the CRM only — never open a loan file in the LOS for a DNQ. This keeps your LOS pipeline clean and your reporting honest.

• Can we A/B test pre-qualification without a full rollout?

  Yes. Most teams route 25–50% of new leads through the pre-qual pipeline for the first two weeks, measure LO-level app and fund rates against the control cohort, then expand to 100% once the lift is proven.