Skip to content
EmailCampaigns.io

Mortgage Brokers / new lead intake

Mortgage Preapproval Follow-Up Sequence

Help borrowers finish preapproval documents and understand the next decision.

2 emails · Immediate, Day 2, Day 5 · 3 platform options

Bottom line

Borrower starts preapproval or requests rate guidance.

Best for

Borrowers who intentionally requested preapproval and have exact status, assumptions, secure access, and licensed ownership.

Use when

Use the documented timing (Immediate, Day 2, Day 5) only while the recipient still needs this follow-up.

Watch for

Rate-only inquiries, purchased leads, denied/withdrawn/closed files, or records in active adverse-action or complaint workflows.

Disclosure

Some platform links on this page are paid links. If you choose a platform through one of them, EmailCampaigns.io may earn a commission. That does not change our recommendations. We include best for and not best for notes so you can decide based on fit, not payout.

Best for

  • Borrowers who intentionally requested preapproval and have exact status, assumptions, secure access, and licensed ownership.
  • Teams that separate inquiry, application, preapproval, credit decision, notices, approval, and lock states.

Not best for

  • Rate-only inquiries, purchased leads, denied/withdrawn/closed files, or records in active adverse-action or complaint workflows.
  • Systems that cannot securely collect documents or distinguish marketing status from governed application status.

How the Sequence Works

  1. Step 1 · Immediately after the verified entry event

    Mortgage Preapproval Follow-Up Email

    Job: A borrower intentionally requested mortgage preapproval and the licensed owner has verified the exact request status, assumptions, and one next step.

    Recipient state: A borrower intentionally requested mortgage preapproval and the licensed owner has verified the exact request status, assumptions, and one next step.

    Issue addressed: The borrower is unsure whether they are actually preapproved, what remains conditional, what to provide, and whether continuing commits them to the lender.

    Primary action: Review the secure preapproval status and complete the one documented next step or close the request.

    Why it earns its place: Orient and make the first useful request

    SubjectNext step for your mortgage request

    speed to leadnew lead
  2. Step 2 · Relative to completion or non-completion of step 1

    Mortgage Secure Document Request Email

    Job: An active mortgage request has a licensed-team-approved set of outstanding borrower documents and a verified secure portal.

    Recipient state: An active mortgage request has a licensed-team-approved set of outstanding borrower documents and a verified secure portal.

    Issue addressed: The borrower may be overwhelmed, unsure what applies, or concerned about sending sensitive records and what submission means for approval.

    Primary action: Upload the requested available documents securely or identify an unavailable or inaccurate request.

    Why it earns its place: Close the loop or route the unresolved case

    SubjectDocuments needed for {{application_reference}}

    document collectionnew lead

How to Automate It

Begin only after licensed verification of the exact request state and next step. Request only approved outstanding items through the secure portal. Completion, reply, withdrawal, closure, adverse action, status change, complaint, opt-out, or licensed-owner contact stops automation; required notices remain separate.

B2B organizations aligning marketing, sales, and service around shared CRM data

Watch for: packaging, contacts, seats, and onboarding complicate total cost

View HubSpot

small businesses connecting leads, pipeline activity, appointments, and follow-up

Watch for: account logic can become difficult to govern

View Keap

Stops, Branches, and Handoffs

Stop the sequence when

  • Stop when the goal-completion event is recorded.
  • Stop automation when the recipient replies or a human begins active handling.
  • Stop on unsubscribe, complaint, or hard bounce.
  • Suppress when required data is stale or conflicting.
  • Route safety, dispute, or regulated-review signals to a qualified human.

Branch when

  • The recipient replies or a human begins active handling. → assign human
  • The goal is complete, the recipient unsubscribes or complains, or a hard bounce occurs. → stop
  • Required data is stale, conflicting, unsafe, disputed, or needs regulated review. → assign human

Human handoff: Assign the current record and full message history to a named owner; suppress further automated steps until the owner resolves or re-enrolls it.

Make this sequence yours: No more than one sequence message in 24 hours; coordinate with other active campaigns.

When to end it: End at the final step or sooner on any stop condition; do not restart without a new verified event.

Primary outcome: Verified completion of the sequence goal

Guardrails: reply-to-human latency; unsubscribe and complaint rate; hard-bounce rate; suppression accuracy

Channel fit: Email for durable context and links; Human call or secure channel for urgent, sensitive, disputed, or complex cases