Written by Yuri Polukeev, CEO, BNTouch Published September 7, 2026
A mortgage borrower communication map names the person responsible for each update, the event that triggers it, and what the borrower should understand afterward. It is separate from a loan-status list: a file can move forward while the borrower is still waiting for an answer.
Use the map below as a team discussion template. The role assignments are examples, not a required staffing model or a substitute for disclosure deadlines and company procedures.
Who will respond, what the person asked, and the agreed next conversation.
Application handoff
Loan officer introduces the receiving processor
Who handles document questions, who handles loan questions, and how to reach each person.
Requested item received
Team member responsible for reviewing the item
Whether the item arrived and whether review is still pending. Receipt is not approval.
Additional information needed
Authorized request owner
What is needed, where to provide it securely, and whom to ask about the request.
Expected update delayed
Person who made the commitment, or named backup
What is known, what is still being checked, and when the next update will happen.
Closing and subsequent questions
Designated closing or relationship contact
The correct contact for the question. Do not imply the originating LO is also the loan servicer.
A delay example: update the borrower before the answer is ready
Illustrative situation: A borrower was promised an update this afternoon. The processor is still waiting for a status confirmation.
Internal record: Processor checks the authoritative loan record. The loan officer owns today’s borrower update. The backup is the branch’s designated coverage person. If the status is still unconfirmed at the agreed check-in, the update says that the review remains open and establishes the next contact time.
Do not substitute: A generic milestone message that suggests approval, completion, or a closing date that has not been confirmed.
The next contact time is a communication commitment the team can control. It is not a promise that underwriting or another party will finish by that time.
Keep the internal note and the borrower update separate
The internal note records the source checked, unanswered question, responsible person, and next action. The borrower update explains what matters to the recipient without copying internal commentary or exposing another person’s information.
Use the organization’s approved secure channel for documents and sensitive information.
Check the current recipient and communication preferences before sending.
Record the substance of the update, not just an activity count.
Do not send a status to a referral partner simply because the partner appears on the relationship record. Confirm the appropriate audience and permissions.
Build the communication map around the borrower’s question
Start with the points where a borrower has to make a decision, supply information, or wait for someone else. A pipeline label such as “processing” is too broad to explain those moments. Within that stage, the borrower may need to confirm receipt of an upload, understand a new request, or find out whether a prior question reached the right person. Give each moment its own communication rule.
For each row, have the loan officer and processor agree on the source they will check before speaking. Record who owns the loan fact separately from who delivers the update. A loan officer may own the relationship while a processor checks an item in the approved loan system. That arrangement works only when both people know who is expected to call the borrower.
Identify the question. Write it in plain language: “Did my document arrive?” or “Who answers this request?”
Name the source. Point the team to the authoritative record or authorized person. Avoid copying a status from a second system without checking its meaning.
Assign the sender. Choose one accountable contact and a coverage role for an absence.
Define the event. Specify whether the update follows a verified change, a borrower question, or an agreed check-in.
Define completion. Record what was communicated, any delivery issue, and the next open commitment. A task checkmark alone may not explain the result.
Separate process updates from required notices
This map organizes service conversations. Your company should continue to manage required disclosures, formal notices, and applicable deadlines through its approved procedures. Adding a friendly status message to a CRM does not replace those procedures. When a question concerns a regulated notice or a time-sensitive decision, the sender needs the appropriate authorized reviewer.
Keep the map small enough that an employee covering an absence can use it. References to approved procedures are more maintainable than pasting their full text into each row. Assign someone to review the references when the company changes a process, rather than relying on every loan officer to discover the change.
Decide what changes when the normal plan breaks
Situation
Working response
What to record
The usual sender is absent.
The coverage owner accepts the next update before the original task is reassigned.
New contact, outstanding question, and the existing commitment.
The borrower cannot use the proposed channel.
Confirm an approved alternative with the borrower and the responsible team.
Channel preference and how the next update will reach the person.
The loan officer and processor have different information.
The authorized source owner resolves the discrepancy before anyone repeats it as fact.
Which source was checked, by whom, and which question remains open.
A partner requests a borrower update.
Check the appropriate audience and permissions before sharing information.
The request and the approved response, separate from the borrower’s private record.
Run a coverage rehearsal before using the map
Use a fictional borrower record and an ordinary staff-absence scenario. Ask a colleague who did not write the map to find the next promised update. They should be able to identify the sender, locate the source of the answer, and explain what happens if the answer is still unavailable. If they need a private message to the original loan officer, record the missing context.
Repeat the exercise with a changed situation: the borrower uploads another item after the original task was created. Check whether the old task still makes sense, who reviews the new information, and whether the borrower is expecting a response. This tests the map’s treatment of new work without assuming a particular software automation.
Review communication quality with a defined sample
Choose a period and review the commitments that became due within it. Count kept commitments, missed commitments, and commitments that the team changed with the borrower. Keep an unanswered loan question separate from a missed communication: a person can provide the promised update while an outside review remains open.
For example, in a fictional review of 12 due updates, nine occurred as agreed, two were missed, and one changed with the borrower. Record all three results and the sample size. Do not describe the result as a benchmark or assume that fewer phone calls means better service. Read the missed cases to find the next process change: missing coverage, an unclear source, or a commitment nobody recorded.
What the BNTouch tutorial actually shows
The BNTouch Daily Dashboard walkthrough shows task and campaign work, followed by status-trigger and removal examples around 2:56 and 3:20. These are useful building blocks to review when deciding how an update becomes a task.
The staffing map above is an editorial example. The video does not establish your organization’s disclosure workflow, LOS sync behavior, or a guaranteed borrower-notification configuration.
Check the map on one real handoff
Find the last update promised to the borrower.
Ask the receiving person who owns it now.
Check whether that person can find the confirmed status and open question.
Confirm the backup knows when to take over.
After the update, verify that the next contact commitment is recorded.
How often should loan officers update borrowers?
Agree on an update expectation with the borrower and add contact when a meaningful event, question, or delay requires it. A generic weekly cadence does not replace a promised callback or the team’s applicable legal and operational requirements.
Evaluating a CRM for your team? Bring an anonymized borrower-update example and ask to see the task, relationship history, and next responsible person.
