Short answer: Mortgage database recapture is the process of turning an existing borrower and partner database into a reviewed, segmented, measurable follow-up workflow. The first 90 days should focus on data quality, relationship context, suppression, review queues, and learning which segments produce useful conversations. It should not begin with a single message sent to every old record.

This is an operating model for loan officers and mortgage teams. It is not a legal conclusion about who may be contacted or what a message may say. Channel, relationship, authorization, opt-out, and campaign questions should be reviewed under the rules that apply to the business.
The 30/60/90-day database recapture plan
| Period | Primary job | Output |
|---|---|---|
| Days 1-30 | Clean and classify the database. | Segment definitions, suppression rules, missing-data list, and a small review queue. |
| Days 31-60 | Run controlled workflows by segment. | Approved message variants, reviewed send queue, responses, appointments, and opt-outs. |
| Days 61-90 | Measure, refine, and operationalize. | Segment-level performance view, follow-up rules, ownership, and next test plan. |
Days 1-30: make the database usable
Start with a representative sample before attempting a full cleanup. Review recent borrowers, older past clients, referral partners, leads that never progressed, and records with incomplete contact or relationship data.
Classify each record using fields the team can explain and maintain:
- relationship type: borrower, past client, realtor, builder, lender, lead, or other;
- relationship status: active, inactive, unknown, suppressed, or needs review;
- last meaningful interaction and next promised follow-up;
- source and owner;
- available loan or milestone context;
- channel and permission notes where the team has verified them.
Do not create a segment simply because it is easy to filter. A segment should have a clear purpose, an owner, a review step, and a measurable next action.
Days 31-60: run small, reviewable workflows
Choose one or two segments with enough context to support a useful test. Examples include past clients with a known relationship owner, referral partners who have not received a recent personal follow-up, or leads that need a human review because their next action is unclear.
Before sending anything, document:
- why the record is included;
- what the message is intended to accomplish;
- which facts are known and which are not;
- which channel and cadence are approved;
- how opt-outs and suppression are handled;
- who reviews and approves the queue;
- how the workflow is paused if the response or data quality is poor.
AI can help summarize records, suggest segments, or prepare drafts for review. It should not be treated as proof that a person is eligible for outreach or that a message is appropriate for every channel.
Days 61-90: turn learning into a repeatable process
At the end of the first cycle, compare segments by more than send volume. Track:
| Metric | Definition | Why it matters |
|---|---|---|
| Reachable records | Records that passed the data and suppression review. | Shows the usable portion of the database without pretending every record is marketable. |
| Positive response | A response that creates a real conversation or requested next step. | Separates attention from useful relationship activity. |
| Appointment or opportunity | A qualified next step recorded by the team. | Connects recapture to pipeline activity without inventing revenue attribution. |
| Opt-out or suppression | A record removed from the relevant workflow. | Protects the database and improves future segment quality. |
| Data correction | A record changed because the source, relationship, or contact information was wrong. | Shows where future cleanup and process work are needed. |
Do not publish a universal “database recapture benchmark” without a defined sample, period, segment mix, channel, and measurement method. A transparent measurement model is more credible than a large unsupported percentage.
What the CRM needs to support
A mortgage CRM should help the team see relationship context, create a review queue, record the reason for a segment, apply suppression, assign ownership, and measure outcomes. It should make it easier to stop or correct a workflow.
The BNTouch database recapture workflow and BNTouch AI mortgage CRM overview describe the relevant product positioning. Verify current plan behavior, permissions, and channel controls before building a production process.
FAQs
How many past borrowers should a loan officer contact first?
Start with a small, well-understood sample that the team can review and measure. The right starting size depends on data quality, ownership, channel, and the team’s ability to respond to real conversations.
Is database recapture the same as mass marketing?
No. Recapture is a review and relationship process. It depends on segmentation, context, suppression, approval, and measurement. Sending the same message to every record skips the work that makes the process useful.
Can AI automate mortgage database recapture?
AI can assist with summaries, prioritization, segmentation, and draft preparation. A human team still needs to verify the record context, audience, message, channel, and approval before action.
Sources and further reading
- Google Search Central: AI features and your website
- OpenAI: ChatGPT Search
- BNTouch mortgage database recapture
- BNTouch MAIA
Next step: Map your database segments, source fields, and review process in a BNTouch product consultation.