Outbound Segmentation
+ Suppression
Built reusable contact segments for community-bank and credit-union outreach, with shared customer exclusions and consistent follow-up tracking.
Problem & approach
Situation
The simulated outreach scenario needed reusable audiences and shared exclusion rules, rather than independently maintained contact lists.
Goal
Make eligible community-bank and credit-union contacts easy to find while consistently excluding customers from outbound targeting.
Solution
Configured an eligible pool, master suppression logic, and persona and institution segments, supported by shared tracking fields.
How the framework works
Contacts move through shared rules before becoming targeted audiences.
- ContactsSource records
- Eligibility rulesEmail + outbound eligibility
- Suppression logicExclude Customer lifecycle stage
- Audience segmentsPersona + institution type
- Tracking & reportingStatus + last-touch fields
See the setup
Open any screenshot to inspect the full-size view.
Key design decisions
Eligibility layer
Start with a shared pool requiring a known email, outbound eligibility, and a non-Customer lifecycle stage. Reuse that baseline across targeting views.
Suppression layer
Use a master exclusion rule for customers so persona and institution views follow the same contact policy.
Tracking layer
Use defined outbound statuses and last-touch dates to support follow-up queues and consistent attempted, connected, and meeting-set reporting.
What the setup delivers
- Standardized audience creation using shared eligibility criteria.
- Centralized customer-exclusion logic across targeting views.
- A reusable segmentation framework for personas and institution types.
- A documented alternative to creating one-off lists.
- Consistent fields and naming to make ongoing maintenance easier.