A pipeline name is not permission to text.
Pipeline automation needs an explicit decision about each stage. Moving a record, replying to an inquiry and starting a new conversation are separate actions with different boundaries.
Review behavior across the whole pipeline
Start with the stages your officer actually uses, not only the stages an analyzer flags for attention. Review ownership, existing conversations and the intended role of the assistant. A stage named “Follow Up” can still contain records that should not receive automated contact.
LoanWick supports stage-specific behavior through its Bonzo setup. The useful question is what the assistant may do in a stage, not whether a stage name sounds sales-friendly. Confirm the available controls in your workspace before relying on an automatic transition.
Separate the permissions
| Behavior | Purpose | Review point |
|---|---|---|
| Proactive outreach | May begin permitted follow-up | Check eligibility, timing, assignment and holds |
| Inbound response | May answer an eligible new inquiry | Do not infer proactive permission from reply permission |
| Pipeline-only behavior | Stage work without assistant texting | Do not mistake a stage update for a sent reply |
| Excluded or paused | No assistant outreach within that boundary | Verify how the hold is applied and reviewed |
Test a fictional stage boundary
Use synthetic records for boundary tests. A successful stage update does not prove a conversation was handled, and a generated reply does not prove it was delivered. Where a transition is unsupported or ambiguous, keep a manual review step rather than expanding permissions to make the test pass.
ScenarioA fictional inquiry is in a stage that should retain records but receive no assistant texts.
Expected reviewConfirm its configured behavior rather than trusting its name.
Test casesCheck an inbound inquiry, a scheduled follow-up and a proposed stage transition separately.
Keep the stage decision maintainable
Record the reason
Explain why each stage is proactive, reactive, pipeline-only or excluded.
Review changed stages
A renamed or newly added stage deserves inspection before inheriting contact behavior.
Inspect human overlap
Check whether an officer is already handling the thread before assistant activity continues.
Audit exceptions
Separate permission-based skips from processing failures in your reports.