Short answer: Mortgage lead distribution software should be evaluated by following a record from source context through assignment, a visible next action, a fallback owner, and a correction path. A feature name or a recorded example does not establish current account behavior. Verify the written scope and the workflow your team will actually use.
Written by Yuri Polukeev, CEO, BNTouch. Updated August 2026.
Separate assignment rules from the work that follows
An assignment rule answers who should review a record first. It does not replace source context, a useful task, or a way to handle an unavailable user, duplicate, or disputed assignment. A practical evaluation makes each of those decisions inspectable.
| Review point | What to inspect | Question for the team |
|---|---|---|
| Source context | Where the record came from, when it arrived, and what information arrived with it. | Can the assigned person understand the source before acting? |
| Assignment rule | The documented condition that routes the record to a person or queue. | What determines the first owner? |
| Fallback | What happens when the intended owner is unavailable, no longer appropriate, or cannot review the record. | Who becomes responsible and how is that decision visible? |
| Next action | The task, review, or handoff a person sees after assignment. | Does the record state a meaningful next action? |
| Exception path | A duplicate, missing-context, disputed, or reassigned record. | Who can correct the record and leave a usable trail? |
Use a five-record workflow review
- Review one ordinary record with clear source context.
- Review a record that needs a fallback owner.
- Review a duplicate or incomplete record.
- Review a reassignment and the reason it occurred.
- Review one record that should pause for a person to decide the next step.
The point is not to declare one assignment method universally correct. It is to let the team inspect ownership, exception handling, and the next action before relying on a workflow.
Video evidence: historical users-and-filters example
Options Tab: Automated Lead Distribution – Users & Filters was published in September 2020. It shows an example of users, filters, schedules, and reassignment settings in a BNTouch tutorial. Treat it as historical visual evidence only. It does not establish the current product configuration, permissions, data behavior, or a suitable workflow for another organization.
Source: Options Tab: Automated Lead Distribution – Users & Filters.
Related evaluation paths
For platform and system-level questions, use the mortgage lead distribution platform review. For the record after it is assigned, use the mortgage lead management guide. For broader software evaluation, use the mortgage CRM evaluation method.
Next step: Bring one ordinary record and one exception record to a live workflow review. Ask to see source context, assignment, fallback ownership, next action, and correction.
Scope
This is an operational evaluation guide, not legal advice or a statement that a particular configuration is appropriate for every organization. Use current written information and the organization's own approved process when evaluating a workflow.
