Closing, and the next loan

The file you have been carrying since application now has a date on it. Closing week is where every open item either gets closed out on paper or becomes the thing that delays the signing table. The day after is where a borrower's first real questions land, usually about who they pay and when. And the months after that are where a desk either builds a referral business or starts every year from zero. This chapter walks all three, plus the review ask, the partner ask, and the cadence a database runs on without turning into spam.

Closing week

By the time a file reaches this stage, most of the regulatory clock has already run: the Closing Disclosure (CD) had to reach the borrower at least three business days before consummation, and only three specific changes (an APR that moves outside tolerance, a change in loan product, or an added prepayment penalty) restart that three-day wait. verified [1] Closing week is where the LO confirms every one of those pieces landed, and shows up, in person or by phone, for the parts a borrower should not do alone.

Every row on that table has an owner who is not the LO, and that is the point: the LO's job in closing week is confirmation, not execution. But the LO shows up or calls on closing day regardless of who is doing the signing appointment. A buyer's agent working new construction put it plainly from the other side of the table: the superintendent runs the final walkthrough and the punch list, title runs the signing and sends the wiring instructions, and the lender's job through that whole stretch is to fund the loan and be reachable if something moves. operator [2] The same posture holds on a resale closing. A borrower who cannot reach their loan officer during closing week remembers it, and it shows up later in exactly the review platforms covered below.

The day after

Three things a borrower needs in plain words within a day or two of funding, none of them a sales pitch.

1. A thank-you. Short, specific to their loan and their closing, not a template that reads like it went to everyone who closed that month.
2. What happens to their loan now, in plain words. Most loans are sold or transferred for servicing after closing; that is normal and does not change the loan's terms. If a transfer happens, the borrower gets it in writing from the new servicer before the transfer takes effect, and the closing package explains where to find that notice if it comes. Point the borrower to their own closing disclosure and servicing disclosure for the exact language and timing that applies to their file rather than reciting a number from memory; those documents are the loan's actual terms, this paragraph is not. operator
3. The first payment date and the escrow explanation, as facts. The first payment due date is printed on the closing documents; state it as printed, not as an estimate. If the loan has an escrow account for taxes and insurance, explain in plain words that the servicer collects a portion of the annual tax and insurance bill with every monthly payment, holds it, and pays the bill when it is due; the first year's escrow amount can adjust once the actual tax and insurance bills are known. State this as how escrow works, not as a promise about what the borrower's payment will do.

The annual review

An annual review is a scheduled, factual check-in on a closed loan: current rate versus today's market, current estimated equity, and whether the borrower's situation has changed enough to be worth a conversation. Industry practice cited across past-client marketing guidance runs the review on a recurring schedule after closing, commonly at year one, three, five, and seven. report [4] Tools built for this specifically, such as Homebot, generate an automated equity and market report a past client receives on its own cadence; third-party pricing puts a Homebot-class subscription at roughly $125 to $300 a month, dated 2026-09-04, not published by the vendor itself. report [5]

What Claude drafts for an annual review: a factual note built from the desk file (loan amount, rate, closing date) and the current numbers the LO types in (today's estimated value, today's published rate range, payoff balance). What compliance reviews before anything goes out: that the note contains no rate quote, no payment estimate, no comparison that favors refinancing, and no statement that reads as advice rather than information. The workflow block later in this chapter walks the full trigger and check sequence.

Equity and rate alerts

An equity or rate alert is a factual notice, not a recommendation. The honest version states one fact the borrower did not have a moment ago (their estimated equity moved, or a published rate index moved) and invites a conversation. It never says "you should refinance," and it never states a specific new payment or rate the borrower would get, because neither of those is known until an actual application and pricing run happens.

The facts worth watching for a past client, sometimes called refi triggers, are the same handful every time: a published rate meaningfully below the borrower's note rate, an estimated equity gain large enough to remove mortgage insurance or open a cash-out option, a program change the borrower did not have at closing (a rate buydown expiring into a fixed rate, a new down payment assistance program, an ARM approaching its first adjustment), or a life-event the borrower tells you about themselves (a second income, a move, a debt paid off). Each of those is a reason to reach out and ask if it is worth running the numbers together, not a reason to state a conclusion in the alert itself.

A refi break-even is a calculation the borrower runs with the LO, together, using that day's actual quoted numbers: closing costs divided by the monthly payment savings equals the number of months to break even. It is arithmetic on the day's real numbers, not a promise printed in a mailer. Present it as a worksheet the borrower can question line by line, not a conclusion handed to them.

The review ask

Ask for a review after the day-after thank-you lands, once the borrower has had a moment to feel the relief of being done, not mid-closing-week stress. Three platforms come up repeatedly for loan officers specifically: Zillow, which lets a consumer filter mortgage lenders by distance and star rating and shows review counts on the LO's own profile report [6]; Google, the general-purpose default most borrowers already trust; and purpose-built post-closing survey tools such as Experience.com, which connects to the loan origination system to auto-send a satisfaction survey after closing and can route a positive response to Google, Zillow, or LendingTree, and Birdeye, which is marketed as an all-in-one dashboard for collecting reviews and tracking individual loan-officer performance across many review sites. report [7] [8] Both are vendor-described features, dated 2026-09-04; verify current functionality and pricing directly with each vendor before subscribing.

A short script for the ask, sent as a personal message, not a template blast:

"[Name], congratulations again on closing. If you have two minutes,
a short review on [Google / Zillow] helps other buyers find someone
who will actually walk them through this the way we just did.
Here's the link: [link]. Either way, thank you for trusting me
with this."

The referral ask cadence

Two different asks, on two different clocks. For borrowers: the ask sits naturally inside the day-after thank-you and the annual review, never as a separate cold ask; a borrower who had a good experience refers people when asked at a moment they are already thinking well of you, not out of the blue six months later. For referral partners (agents and builder reps): the ask is baked into the same weekly or milestone-based status updates already going out on the file, plus a direct, periodic check-in outside of any live file, since a partner relationship that only exists file-by-file has nothing holding it together between transactions. No single authoritative cadence number for partner check-ins was confirmed in the research behind this guide; treat "at least monthly, more often for your top few partners" as a working default, not a benchmark. inference [9]

What earns that check-in a repeat referral is largely the same thing that earned the first one: an Inman survey relayed by a secondary source found speed to be the top factor determining whether an agent recommends a lender, with 59% of respondents citing it as most important, ahead of price or program breadth. That figure is two steps removed from Inman's own publication in the research behind this guide, so treat it as directional rather than a precise benchmark to quote to a partner. report [13] The closing-week checklist above and a fast reply on the next file are the referral ask, in practice, more than any script is.

The database cadence

Whatever cadence a desk runs, it has to survive the same deliverability rules as any other marketing list: a dedicated sending subdomain kept separate from personal or transactional email, sends restricted to an engaged segment rather than the full historical list, and every unsubscribe honored immediately, not queued for later. operator [10]

The pipeline metrics an LO reviews monthly

Three numbers worth a standing monthly look, defined the same way every month so trend lines mean something: fundings by referral source (past client, agent partner, builder, direct/self-generated), so the desk can see which relationships are actually converting, not just generating conversation report [11]; the pull-through rate, defined as loans closed and funded divided by loan applications formally submitted in the same period, times 100, which is the most defensible formula in the industry evidence behind this guide and should be used exactly as defined rather than a looser in-house version report [12]; and the review count and rating trend across whichever platforms the desk actually uses, tracked monthly rather than checked only when a manager asks.

Claude workflow blocks

Closing-week checklist

Trigger: a file gets a firm closing date.

Claude prepares: the per-file version of the closing-week checklist table above, built from the stage notes already in the file (CD delivery date, funds-to-close figure the borrower confirmed, closing appointment details, any flags like power of attorney or remote notarization), with each row's done-when condition filled in from the actual file rather than left generic.

Human checks and does: confirms every row against the actual file and the actual CD, delivers the wire fraud warning personally, shows up or calls on closing day, and confirms funding, recording, and key release themselves.

Never automated: the wire fraud warning delivered as a form field instead of a real conversation, and any confirmation of funds movement; those are calls the human makes, every time.

Annual review and rate-alert draft

Trigger: a file reaches its year-one, three, five, or seven anniversary, or a real, documented market or valuation move crosses a threshold the LO sets.

Claude prepares: a factual note from the compliance-approved template, using the desk file's loan facts (closing date, original loan amount, program) and the loan facts the LO types in that day (current payoff balance, today's published rate range with source and date, an estimated value range if one is available), with no rate quote, no payment estimate, and no comparison that favors refinancing.

Human checks and does: reads the draft against the compliance-approved template line by line, confirms every figure is dated and sourced, gets compliance or manager review before send where the company requires it, and sends it themselves.

Never automated: stating a specific new rate, payment, or savings figure, or any language that reads as "you should refinance"; that judgment and any actual quote come only from a live application and pricing run with the borrower.

Review request and referral ask

Trigger: a file closes and the day-after thank-you window opens, or an annual review touch is going out.

Claude prepares: a short, personalized review-request message using the script pattern above, addressed to this specific borrower's closing, plus a separate short partner check-in draft for the file's referring agent or builder rep summarizing how the file closed.

Human checks and does: reads both drafts for tone and accuracy, confirms the review-platform link is correct and current, and sends them personally rather than through a bulk-blast tool.

Never automated: a mass, unpersonalized review-request blast sent without a human reading each message first, and any message that implies the review is required or incentivized beyond what the review platform's own terms allow.