Mortgage Rate-Watch Workflow: Review Before Refinance Outreach
Written by Yuri Polukeev, CEO, BNTouch
Last reviewed: August 2026
Loan officers often hear “rate watch” and jump straight to a message sequence. The better first move is a record review. A past borrower may have changed circumstances, incomplete information, a different relationship context, or a reason that the team should pause and evaluate before communicating. A workable process puts a person in charge of that decision and keeps the reason for it visible on the record.
What the public tutorial demonstrates
In a public BNTouch Groups webinar, the presenter discusses a group labeled “Rate Watch” and later shows an example in which a group condition can add a record to a campaign. View the source video at 20:43. This is useful visual context for a group-and-campaign review; it is not a specification of current data sources, calculations, timing, coverage, account configuration, or a recommended borrower action.
Run a five-record rate-watch review
| Record to inspect | What the reviewer checks | Decision to document |
|---|---|---|
| Complete past-borrower record | Relationship history, current owner, loan context available to the team, and the reason the record appears in the review queue. | Whether a person should review further, the next task, and the owner. |
| Record with incomplete loan context | What is missing, who can verify it, and whether a workflow should pause until the context is understood. | Escalation owner and the condition for resuming review. |
| Record with recent contact history | Prior conversations, record notes, and whether another touch would match the current relationship. | Next action, later review date, or no-action decision. |
| Record with a changed relationship owner | Who is accountable now and whether the new owner can see the relevant history. | Handoff note and current task owner. |
| Record that should not move forward | The visible reason for stopping, pausing, or seeking additional review. | Stop condition, reviewer, and follow-up rule for the exception. |
Define what belongs on the review record
Before a team uses a group or campaign, document the inputs that make the record useful to a person. The point is not to create a longer checklist. It is to make sure a future reviewer can understand why the record appeared and what happened next.
| Record element | Question for the team | Human responsibility |
|---|---|---|
| Relationship context | Can the user see why this borrower is known to the organization and what has happened previously? | The loan officer or assigned reviewer confirms that the context supports a useful conversation. |
| Observed signal | What specifically caused the record to be reviewed, and when was it observed? | The workflow owner documents the source and confirms that it is not treated as a conclusion. |
| Current record state | Does the record contain enough current detail to decide whether a next step is appropriate? | The assigned reviewer pauses or escalates when the answer is unclear. |
| Next action | What will the responsible person do, and what is the reason for that action? | The owner records the action or no-action decision so another user can review it. |
| Exception path | Who resolves a conflicting, incomplete, or unexpected record? | The team names the escalation role before relying on the workflow. |
Separate a review workflow from borrower guidance
A review queue helps a team organize internal work. It does not replace the care required when a loan officer speaks with a borrower. The Consumer Financial Protection Bureau’s Your Home Loan Toolkit is a useful primary reference for the home-loan questions consumers may consider. It does not replace an organization’s current policies, disclosures, or professional review process.
Method and source trail
This page is a workflow-review guide for mortgage professionals. It is not a loan recommendation, legal opinion, product specification, or performance promise. Confirm the current workflow, account setup, data context, and review roles in a live demonstration before relying on a process.
