How to Automate Stale Pre-Approval Follow-Up With Dynamic Groups in BNTouch
Written by Yuri Polukeev, CEO, BNTouch
Updated August 13, 2026
Short answer: A stale pre-approval follow-up workflow should begin with a record review, not a fixed number of days. Confirm the current record state, last verified context, accountable owner, next action, and a condition that pauses or removes the record before any re-engagement is considered.
Teams define pre-approval validity, communication approvals, review timing, and record ownership differently. This guide provides an evaluation method and a source-backed BNTouch example. It does not prescribe a universal timeline or communication process.
What makes a record ready for a stale-preapproval review?
| Review question | Evidence to check | Decision to document |
|---|---|---|
| What is the current record state? | Latest verified status and the source responsible for it. | Keep, pause, correct, or route for further review. |
| What is known about the relationship? | Prior activity, stated request, and relevant record context. | Whether there is a useful, approved reason to follow up. |
| Who owns the next decision? | Named person and a review date. | A clear next action rather than a generic reminder. |
| What should stop the workflow? | Removal, exclusion, or manual-review condition. | How an exception is corrected and who can make that change. |
| What evidence supports the setup? | Record sample, workflow definition, and source video. | Launch, revise, pause, or gather more evidence. |
Use a five-record check before relying on a workflow
- Review one record that clearly fits the stated condition and one that clearly does not.
- Check a record with incomplete context or a missing next owner.
- Follow the entry and exit logic through a record that should be paused or corrected.
- Confirm that the person reviewing the record can see enough history to make a responsible decision.
- Write down the outcome and the next workflow change, if any.
This makes the operating logic visible. It also keeps a team from turning one elapsed-time label into a substitute for record context or human review.
What the BNTouch walkthrough demonstrates
BNTouch's Stale Preapproval Recapture Campaign walkthrough shows one example of a stale-preapproval group and follow-up workflow. The timing and configuration shown are illustrative. The video does not establish a default configuration, a universal review interval, an approval standard, a communication requirement, or a result for another organization.
Use the mortgage lead-management workflow to define record ownership after a response. For broader outreach review, use the mortgage relationship communication framework.
Questions to ask in a CRM demonstration
- Can the team show a representative record entering, leaving, pausing, and being corrected in the workflow?
- Can the assigned owner see record context and a meaningful next action before follow-up?
- What can be configured, and who is responsible for reviewing exceptions?
- Can the product team demonstrate the exact workflow using the organization's own definitions and records?
Next step: Bring one record that should be reviewed, one that should be excluded, and one with missing context to a BNTouch demo. Ask for a record-level walkthrough of the workflow definition, stop condition, ownership, and correction path.
