Short answer: The public BNTouch Campaign Triggers video shows add and remove rules for campaign enrollment. Before a team relies on a rule, it should test the applicable records, inspect the resulting audience, identify the person who owns an exception, and confirm the current account behavior in context.
This page explains how to review the recorded source. It does not establish a required process, a record field, a permission, a message policy, or behavior in a particular account.
Recorded campaign-trigger source
Published October 13, 2025, the tutorial demonstrates a campaign editor with rules intended to add records to or remove records from a campaign. It also shows a candidate-review step before a rule is saved. Use the recording to frame a current product review rather than as a substitute for one.
Source: BNTouch Campaign Triggers: Add and Remove Rules.
Questions to use while reviewing the recording
| Review point | What to inspect | Human-owned decision |
|---|---|---|
| Entry rule | The record condition, relationship context, and the audience expected to match it. | Whether the record belongs in the campaign at all. |
| Removal rule | The changed condition that makes the path no longer appropriate. | Whether the record should pause, leave, or be handled another way. |
| Candidate review | A representative group of expected, unexpected, and incomplete records before the rule is used. | How a mismatch is corrected and documented. |
| Exception ownership | The named owner and visible route when a record does not fit the usual path. | What next action serves the relationship responsibly. |
Use five representative records
- Expected match: a record that should be eligible under the written rule.
- Expected removal: a record whose changed context should take it out of the path.
- Unexpected match: a record that reveals an overly broad rule or incomplete context.
- Incomplete record: a record that needs a person to decide before it is treated as normal.
- Ownership change: a record whose next action must remain clear after a handoff.
Record the expected state, the actual state, the reviewer, and the correction route. A rule is easier to assess when a team can explain those items for ordinary and exceptional records alike.
What the recording does not establish
The tutorial is one public training example. It does not establish present availability, account setup, permissions, record fields, approval policy, communication eligibility, configuration, legal status, commercial terms, or a particular result. Confirm the current workflow in a live review using the records and responsible owners relevant to the organization.
Related owner pages
Use the mortgage CRM campaign-control review for the broader campaign evaluation method. Use the mortgage marketing automation review for a separate workflow-level assessment. Keeping the source tutorial and the operating evaluation on separate owner pages makes each question easier to verify.
Scope: This is a source-review guide, not lending, legal, privacy, disclosure, communication, technology, or compliance advice. Use the organization's approved process and responsible reviewers for decisions involving records, communications, borrowers, or workflow changes.
Review a representative campaign rule with BNTouch
Bring one expected match and one exception to a BNTouch demo, then ask to see the current review points that apply to your team.
