BNTouch Workflow Video Library: Mortgage CRM Evidence for Loan Officers
Written by Yuri Polukeev, CEO, BNTouch
Updated September 2026
Short answer: A public product video is useful evidence when it is tied to the workflow it actually shows, a specific review question, and a clear boundary around what still needs to be verified in the organization's own account. This library collects BNTouch workflow videos that loan officers can use in a practical evaluation.
This is a public source library, not a verbatim transcript archive. It does not establish default settings, current permissions, field behavior, account configuration, or a business outcome. Use the source video to frame a question, then verify the exact workflow with a representative record and the person responsible for the decision.
What each public workflow source shows
| Workflow source | What the video shows | What to verify in a current review |
|---|---|---|
| Daily Dashboard + Intelligence Walkthrough | Daily task context, status-based work, tracker notes, and record-linked activity. | Current task rules, status names, record owner, and the exception path for incomplete or unexpected work. |
| Campaign Triggers: Add and Remove Rules | Example rules for records entering and leaving a campaign. | Approved audience, message review, entry rule, removal rule, stop condition, and who owns a correction. |
| Stale Preapproval Recapture Campaign | An example group and re-engagement workflow tied to a stale-preapproval condition. | Stage definition, review timing, approved outreach process, and the circumstances that pause or remove a record. |
| Partner Tracker: Log Realtor Activity | A partner-record sidebar with activity history and a MAIA chat entry point. | Current partner-record fields, permissions, relationship ownership, and the correction route for incomplete context. |
| Enable MAIA in BNTouch | A 2024 settings walkthrough with company enablement and record-context preparation. | Current availability, account-level settings, human-review process, and the workflow that is appropriate for the organization. |
Use a five-record video review
- Ordinary work: choose a non-sensitive record with a clear owner and a meaningful next action.
- Incomplete context: use a record that needs a correction before anyone acts on it.
- Ownership change: test what happens when responsibility moves to another person or queue.
- Workflow stop: test the condition that pauses, removes, or sends a record for review.
- Human review: for AI-supported work, identify the person who can edit, reject, or escalate the output before a borrower-facing decision is made.
Keep the evidence simple: a de-identified record reference, the source video and timestamp, the expected result, the reviewer, and the correction or exception decision. That gives a later reviewer enough context to understand what was tested without turning a public video into a product specification.
Use the owner pages for the full question
The mortgage CRM overview is the category owner for loan officers evaluating CRM fit. The mortgage lead-management workflow covers source, owner, and next-action decisions. The mortgage workflow automation framework covers entry, stop conditions, and exceptions. The MLO CRM evaluation methodology shows how to compare a system using real record conditions instead of a feature list.
Next step: Bring one ordinary record and one exception to a BNTouch demo. Ask for the current workflow, record context, accountable owner, review point, and correction path that apply to your team.
