Written by Yuri Polukeev, CEO, BNTouch Published September 7, 2026
A useful mortgage CRM note records the reason for the conversation, what the person actually asked, what was confirmed, and who will do what next. “Called, left voicemail” records an attempt. It does not explain the work a colleague needs to continue.
Why this interaction happened, not just the channel used.
Request
The borrower’s or partner’s stated question or preference.
Confirmed
Facts checked or information actually communicated.
Open
What still needs an answer and who can provide it.
Next action
Person, action, and agreed date or event.
These are example labels for a note, not a claim that your account has five dedicated fields with these names.
Borrower note: before and after
Weak: Called. Client confused. Follow up.
Useful, illustrative version: Borrower asked who can confirm whether the latest uploaded item has been reviewed. Confirmed only that it was received, not that it was accepted. Assigned processor will check the source record. Loan officer owns the next borrower update at the agreed check-in time. If the processor is unavailable, route through the branch’s coverage process.
The stronger note separates receipt from review. It gives the next team member a real question to answer and avoids presenting an unknown loan-file status as fact.
Referral partner note: before and after
Weak: Good Realtor meeting. Send stuff.
Useful, illustrative version: Partner asked for a clearer introduction process when a prospective borrower wants to speak with the team. Discussed who receives the introduction and who confirms receipt. Relationship owner will prepare a process outline for internal approval before the next meeting. No borrower-specific information included in this partner note.
A partner relationship record is not the place to copy an entire borrower’s financial history. Keep the business conversation distinct from information that belongs in a restricted loan record.
Choose the right place for each kind of information
A relationship note should help the next authorized person understand a conversation. A task identifies work to complete. A structured status supports a defined workflow. A document belongs in the organization’s approved storage location. Decide which job you need before putting the same information into several places.
For example, a note can explain that a borrower asked whether an upload arrived. The task assigns the check. The authorized source record establishes receipt and review status. Pasting the document into the note creates another copy to control without answering the borrower’s question any better.
Information
Useful treatment
Common mistake
A preference stated during a call
Record the preference and update the designated preference record through the approved process.
Leaving the instruction only in an old narrative note that the next sender will not see.
An unresolved document question
Summarize the question and assign a source check to the responsible person.
Using the note to imply a document-review decision.
A promised callback
Record the commitment and create the next action in the team’s working queue.
Typing a date into a note without assigning anyone to act.
A partner’s process concern
Record the business issue and the agreed follow-up in the partner history.
Copying private borrower information into a broadly accessible partner record.
Adapt the note to the conversation
An early inquiry with unanswered questions
At the inquiry stage, the useful note may be short: what the person wants to discuss, the correct contact, and the next agreed conversation. Avoid making qualification conclusions from an incomplete conversation. Where a person describes a financial situation, follow your company’s rules for what to record and where to record it.
Fictional example: Prospective borrower asked which team member can explain the application process. No loan option or eligibility determination discussed. Assigned loan officer will contact the person through the approved channel at the agreed time. Open item: confirm the correct introduction and contact details.
A returning borrower asking about a new situation
Separate the new request from the previous transaction. A historical record may help an authorized team member understand the relationship, but it does not establish that old facts, preferences, or permissions remain current. Identify the new question and the facts that still need review.
Fictional example: Past client requested a conversation about a possible future move. Historical loan record exists; current circumstances have not been reviewed. Relationship owner will arrange the requested discussion. Do not treat the old file as a completed application for the new inquiry.
A partner meeting about introductions
Write down the process issue the partner raised and the action your team agreed to take. A useful note lets a colleague prepare for the next meeting without having to guess what “touch base” meant. Where the discussion raises compensation or co-marketing arrangements, use the organization’s review process rather than recording an informal promise as an approved program.
Correct a note without obscuring what happened
If someone records the wrong callback date or confuses receipt with review, follow the company’s correction procedure. Identify the corrected fact and the source used to verify it. Avoid silently changing a material statement in a way that makes the original interaction impossible to reconstruct.
The appropriate correction method depends on the system and your recordkeeping requirements. Ask the administrator how edits, access, and retention work in the current environment. Do not infer an audit-history feature from the presence of an edit button, and do not promise one based on this article.
Give a reviewer a concrete note-quality test
Reconstruct the request. Can someone who missed the call state what the borrower or partner asked?
Separate fact from uncertainty. Does the note show what the writer checked and what remains open?
Find the next owner. Can the reader identify who will act and when the work should be checked?
Check appropriate detail. Is the note missing needed context or copying information that belongs elsewhere?
Check follow-through. Does the work queue contain the action the note promises?
Use anonymized samples from several interaction types, not only the team’s best notes. Review a new inquiry, a handoff, and a partner meeting. Keep the feedback specific: “The callback owner is missing” is more useful than “Write better notes.” A longer note fails the test if a colleague still cannot identify the next step.
Keep reusable templates flexible
Give writers prompts for purpose, request, facts, and next action, then allow them to omit sections that do not apply. Avoid copying a previous borrower’s narrative to start a new note. That shortcut can carry forward the wrong person, request, or promise. A blank template with clear labels is a safer starting point for accurate work.
How the BNTouch Partner Tracker records activity
The BNTouch Partner Tracker tutorial opens a partner from the Partnerships tab and shows the record’s activity tracker. Around 4:00, the walkthrough demonstrates adding an event. This is a concrete place to evaluate how a partner meeting is recorded.
Check the current options and permissions in your own account. The note format above is an editorial example, not a transcript of an actual customer’s conversation or a claim about an automatic note-generation feature.
What should stay out of a relationship note?
Speculation about a person’s motives or character.
Unnecessary sensitive financial details or copied identity documents.
An approval, rate, qualification, or timing conclusion that has not been verified by the responsible person.
Statements that hide uncertainty, such as “all done,” when a review is still open.
Follow your company’s rules for access, retention, corrections, and communication preferences. A note template is not a compliance certification.
Can AI draft CRM notes?
When an organization permits an AI tool for this purpose, a person should compare the draft with the actual conversation before saving it as a working record. Check names, amounts, dates, questions, and commitments. Do not let a plausible summary become evidence of something that was never said.
A useful quality check
Give a recent anonymized note to a colleague who was not on the call. Ask what they would do next. If the answer differs from the writer’s intended next step, revise that line. Measure whether notes support handoffs, not how many words people type.
