Abandoned Mortgage Applications: Catch the Ones You Never See

A borrower starts your application, hits a document they don't have on hand, and closes the tab. The half-finished 1003 sits in your point-of-sale system. Your follow-up lives in your CRM. Neither one tells the other, so that borrower is now a dead record nobody will ever work, and you probably don't even know it happened.

Quick answer: An abandoned mortgage application is a loan application a borrower started but never submitted, usually because they hit a document or question they weren't ready for. It goes invisible because the half-finished record sits in the point-of-sale (POS) system while follow-up runs out of the CRM, and no single system watches the gap between them. To catch it, you have to make "started but not submitted" a dated follow-up task owned by a real person, triggered off the POS status and worked in the CRM.

This is a different leak from the document-chasing you already do on a live file. Once a loan file exists, someone owns the pay-stub reminders. The abandoned application never gets that far. There's no file, no loan number, nobody assigned, which is exactly why it disappears.

Why an abandoned application is invisible when it's started but not submitted

The abandoned application is invisible because the two systems that could catch it don't share the record. Your POS holds the application experience, where the borrower fills out the 1003. Your CRM holds the relationship and the follow-up. Setshape's mortgage automation breakdown names this exact leak: the half-finished record sits in the POS while follow-up lives in the CRM, so an abandoned application is invisible to the system that would otherwise turn it into a task (setshape.com).

The scale is not small. A majority of lenders told Ellie Mae that on average half of their online applications were started but never completed, and one in five borrowers who abandoned an online application went on to pick a different lender (Ellie Mae survey, via BusinessWire). The MortgagePoint puts online loan application abandonment around 68%, usually tied to poor interactions during the process (themortgagepoint.com). Fintactix notes mortgages run even higher than the 70%+ general rate because the process is document-heavy (fintactix.com).

The MBA has a name for the number that measures this: Application-Start to Application-Submission. It's a real ratio most teams never track, and the MBA's point is blunt. Borrowers lost at this stage never reach the pipeline, so they're never locked and never funded (MBA Newslink). You can't lose a deal you never knew you had, which is precisely the problem.

Abandoned application vs. document chasing on a live file

Document chasing happens after a file exists; abandonment happens before it does. That one difference is why abandonment slips past the systems that already handle the chase. When a loan is in your LOS and the processor needs a missing bank statement, there's a file, an owner, and a task. The nudge gets made, late or on time, because somebody is assigned to it.

The abandoned application has none of that infrastructure. The two situations look completely different in your own stack:

Your LOS can't help you here. The loan origination system is the system of record for a loan file, but the abandoned application never became a file. A POS like Blend pushes data into the LOS at submission; the LOS doesn't write back to the POS, so a pre-submission drop-off is never captured as a loan file anywhere (Lender Toolkit). That means the system you'd normally check for stalled files has nothing to show you.

How to turn a half-finished 1003 into a dated follow-up task

Catch an abandoned application by making "started but not submitted" a status your CRM can see and assign, the same way you'd handle any other stalled deal. The mechanics are not complicated; they just require that someone decides to watch the gap.

1. Find out what status your POS exposes

Most point-of-sale tools track where a borrower is in the application, including "started" and "submitted." Check whether yours can mark a record as started-but-not-submitted, and for how long. That status is the trigger for everything else. If your POS can't surface it at all, that's your first finding, and it tells you the gap is wider than you thought.

2. Get that status into the CRM where follow-up runs

The half-finished record has to become visible in the tool that runs your follow-up, usually Follow Up Boss or whatever CRM your team lives in. The clean way to do this is a sync that lets the CRM see POS status without the POS and CRM fighting over who's in charge of the borrower's data. Techyorker's integration guidance frames it right: the LOS and POS stay the systems of record for the file and the application, while the CRM is the working record for relationship and follow-up, with a sync making each visible in the other (techyorker.com). The abandoned record shows up in the CRM as a task, not a competing source of truth.

3. Assign an owner and a clock

An abandoned application with no owner is still invisible even if the CRM can see it. Decide who works these, and set a time window. AGC Studio's broker tracking guide uses a concrete example: a 72-hour nudge when a pay stub is outstanding (agcstudio.ai). Pick a similar window for a stalled start, 24 to 72 hours, and name the person who reaches out.

4. Nudge in your team's voice, about the specific thing that stalled them

Most borrowers who need multiple sessions aren't quitting; they're gathering a document they didn't anticipate when they started, according to MPA's reporting (mpamag.com). So the nudge should sound like a helpful person, not a drip. "Saw you got partway through the application, that part where it asks for two years of W-2s trips a lot of people up, want me to walk you through it?" beats a generic reminder every time.

The part no single system owns, and where it breaks

The whole thing breaks at step 2, the sync, because that's the one piece no off-the-shelf tool does for you when your POS and CRM are different vendors. Most LOS and POS platforms don't natively push status events to your follow-up channel, so someone has to manually trigger the message or update the CRM, and that only happens when that person has time (US Tech Automations). "When that person has time" is the whole leak. The vendor pages that cover this problem solve it by assuming you buy their POS and their CRM as one bundle. That's not your situation if you run a separate POS and Follow Up Boss.

This is the specific gap SalesOS is built to close: it watches for the stall across the two systems that don't talk, and when an application sits started-but-not-submitted past your window, it surfaces that record as a follow-up task and nudges the borrower in your team's own voice and templates, with escalation when the clock runs out. It doesn't replace your CRM or your POS. It watches the gap between them that neither one owns, the same way SalesOS handles stalled deals and the handoff leak elsewhere in your pipeline. You can see how AI Cofounder works if you want the fuller picture of how it reads your systems.

Common pitfalls when you go to catch these

The usual mistake is treating abandonment as a form-design problem and stopping there. Smoother forms help, but they don't recover the borrower who already left, and they don't make the drop-off visible to the person who should follow up. These are the traps worth naming before you build anything.

You can audit your own version of this in an afternoon without buying anything: pull a month of started applications from your POS, pull submitted ones, and count the difference. Every record in that gap is a borrower who raised their hand and then vanished. If your team ran any follow-up on them at all, it was because somebody remembered.

FAQ

What is an abandoned mortgage application?

An abandoned mortgage application is one a borrower started in your point-of-sale system but never submitted, typically because they hit a document or a question they weren't ready to answer in that session. It's distinct from a completed application that's missing a document later, because the abandoned one never became a loan file in your LOS.

Why can't my LOS tell me about abandoned applications?

Your LOS only holds loans that reached submission, so an application a borrower quit before submitting never becomes a file there to track. A POS like Blend pushes data into the LOS at submission and the LOS doesn't write back, so a pre-submission drop-off isn't captured as a loan file anywhere in your stack.

How common is loan application abandonment?

Loan application abandonment is common and expensive: a majority of lenders reported that on average half of their online applications were started but never completed, per an Ellie Mae survey, and one in five borrowers who abandoned went to a different lender. Mortgage abandonment tends to run higher than other loan types because the process requires more documents.

How is this different from the document chasing I already do?

Document chasing happens on a live loan file that already has an owner and a task; abandonment happens before any file exists, so nobody is assigned to it by default. The fix for abandonment is making "started but not submitted" a dated, owned task, which your current document-chasing process never sees.

If you run a separate POS and a CRM like Follow Up Boss and you suspect that gap is costing you borrowers, the fastest way to know is to watch it work on your own systems. Book a demo and we'll walk your start-to-submission gap and show you what catching it would take.