Rate watch: building a refinance nurture plan for past clients

Every loan officer has a past-client list. Few have a system that tells them, the week it matters, which of those clients might benefit from talking about a refinance. A rate-watch refinance nurture turns weekly market data into timely, compliant conversations. This guide shows how to build one: the data, the triggers, the messages and the guardrails.

What are mortgage rates doing right now?

Freddie Mac’s Primary Mortgage Market Survey (PMMS) is the most widely cited weekly benchmark. For the week of October 15, 2026 it reported an average 30-year fixed rate of 7.4% and a 15-year fixed rate of 6.71%. A year earlier (week of October 9, 2025) the 30-year averaged 6.3%, and over the past year the lowest weekly reading was 5.98% (week of February 26, 2026).

Weekly averages aren’t anyone’s actual rate; individual offers depend on credit, loan-to-value, loan type and the day of the lock. But the direction of the averages tells you when refinance conversations are likely to be worth having for some clients, and when they aren’t.

What is a rate-watch list?

How do you build the rate-watch automation?

1. Ask for opt-in. At closing and in annual check-ins: "Would you like us to tell you if refinancing might make sense for you?" Save consent.
2. Store a little data. Current rate (if shared), rough balance, goals (lower payment, shorter term, cash-out), and a review date.
3. Set an LO target. For example, a weekly survey average a set amount below the client’s rate. The LO, not the software, decides the threshold.
4. Check weekly. When the PMMS release meets the target, create a task for the LO with the client’s details.
5. LO reviews. The LO checks the file, runs a quick break-even estimate and decides whether to reach out.
6. Approved message. The LO sends a template your compliance contact approved, personalized but without unapproved rate or payment claims.

What should rate-watch messages say?

What else belongs in past-client nurture?

Rate watch is one of four touches that keep you the LO a past client calls next:

• Home anniversary on the closing date each year.
• Birthday message from the LO, no sales pitch.
• Annual check-in with an optional equity review.
• Rate watch alerts, LO-first.

How do you know it’s working?

Track: opt-in rate at closing, number of rate-watch alerts per month, LO follow-up rate on alerts, conversations started, and refinance applications from past clients. Keep the numbers by LO; the habit matters more than the software.

Mortgage Funnel Suite includes rate watch in its automation library, wired to the Past client stage of the mortgage pipeline.

An example rate-watch flow for one past client

Consider a fictional past client, Sam, who closed a purchase two years ago and opted in to rate watch at closing. Sam shared a rough current rate and said the goal would be a lower payment. Maya, the LO, set a review target in the CRM. Each Thursday after the Freddie Mac release, the suite compares the weekly 30-year average with Maya’s target for every client on her list.

For months nothing happens, which is the right outcome: no alert, no message, no noise. When the averages move toward Maya’s target, the CRM creates a task, not a text. Maya opens Sam’s record, sees the loan details and the goal, runs a quick break-even estimate and decides it is worth a conversation. She sends the approved template: "Hi Sam, rates have moved since you bought. Want me to check whether refinancing could make sense for you?" Sam replies yes, books a time, and the contact moves back into the pipeline as a new lead with source "rate watch".

If Maya decides it isn’t worth it, for example because Sam’s closing costs would not be recovered before a likely move, she dismisses the task with a note. The system learns nothing new, but Maya’s judgement stays in charge, which is exactly where it should be.

What are common rate-watch mistakes?

• Blasting every past client whenever rates dip.
• Putting specific rates or payments in unapproved messages.
• Storing more personal financial data than clients agreed to share.
• Forgetting clients who have already refinanced elsewhere; update records after each conversation.

Why use a public weekly benchmark?

A rate-watch program needs a consistent, public reference point so that alerts mean the same thing every week and can be explained to anyone. Freddie Mac’s PMMS fits: it is published every Thursday, has decades of history, and is mirrored on FRED, where anyone can download the series. It is an average across many lenders, not an offer, which is exactly why it works as a trigger for a conversation rather than as a quote.

Some groups also track their own pricing internally. That can make alerts more precise, but it also makes the messages more sensitive: an internal rate in a message is closer to an advertised rate and needs careful compliance handling. Many teams keep the public benchmark as the trigger and let the LO bring in real pricing once the conversation has started.

Whichever you choose, document it: which series, which day, what threshold, who receives the alert and which templates they may use. That documentation is what makes the program defensible and repeatable across branches.