Understanding why contacts are excluded from sequences
Last updated: May 5, 2026
When contacts aren't enrolling in your sequences as expected, understanding the exclusion hierarchy and enrollment rules can help you identify and resolve the issue. This guide explains how to diagnose exclusion problems and troubleshoot enrollment issues.
Understanding Exclusion Hierarchy
Exclusions work at multiple levels, and it's important to understand which takes precedence:
Sequence-level exclusions apply globally across the entire sequence
Audience-level exclusions allow different exclusion rules for different audience segments within the same sequence
When audience-level exclusions are disabled but sequence-level exclusions remain enabled, contacts can enter the audience but will still be prevented from enrolling in the sequence.
Important: Advanced settings exclusions in your company exclusion configuration act as additional guardrails that can prevent enrollment even when audience-level exclusions are disabled. To successfully enroll contacts that match exclusion criteria, you must disable both the relevant audience-level exclusions AND any corresponding advanced settings exclusions in Settings > Exclusions.
Important: Manual enrollment via the extension cannot bypass active exclusions. All exclusions (company-level, sequence-level, and audience-level) apply to both automated and manual enrollments. To manually enroll contacts that match exclusion criteria, you must temporarily disable the relevant exclusions globally, which will affect all sequences.
Diagnosing Enrollment Issues
To understand exactly why contacts were not enrolled:
Navigate to Play Builder > Metrics > Enrollments tab
Review the detailed enrollment failure reasons
Important: When exclusion rules are disabled (unchecked), contacts may still appear in the exclusion criteria lists in your metrics, but they will not actually be excluded from the sequence. The presence of a contact in an exclusion category does not necessarily mean that exclusion rule caused their non-enrollment.
Note: Exclusions are evaluated based on contact attributes at the time of exclusion. When investigating historical exclusions in your metrics, understand that records were excluded based on the combination of exclusion filters and the attributes contacts had at that exact moment. A contact that was excluded in the past may no longer meet the exclusion criteria if their attributes have changed since then.
Systematic Troubleshooting Approach
Follow these steps to identify enrollment issues:
Check company-level exclusions first - Review your company-level exclusion settings, particularly "Any Associated Deal" exclusions and advanced settings exclusions which commonly cause enrollment failures. Advanced settings exclusions can prevent enrollment even when audience-level exclusions are turned off.
Verify sequence-level settings - Confirm whether exclusions are enabled at the sequence level. Check the sequence ruleset configuration by navigating to Sequence → Settings → Ruleset to ensure exclusions are toggled on. If the ruleset is set to "default," verify that the default ruleset has exclusions enabled by going to Settings → Sequence → Ruleset. A ruleset with all exclusions toggled off will prevent any exclusion rules from being applied, regardless of other exclusion configurations.
Review audience-level exclusions - Check if specific audience segments have their own exclusion rules
Check persona routing configuration - Verify that all relevant personas are properly configured and tracked in the play's enrollment settings. Missing persona routing will prevent enrollment regardless of exclusion settings being correct. If you see "no valid routing target" in the play logs for a specific record, it means the contact's title didn't match any configured persona titles.
Test exclusion rules systematically - If the exclusion reason isn't clear from the metrics, create a test audience containing only the affected contact and toggle individual exclusion rules on/off to identify which rule actually removes them from the audience
Temporarily disable exclusions for re‑enrollment - If you need to re‑enroll contacts that were previously excluded, follow this procedure:
Navigate to the Ruleset your sequence falls under (Settings > Features > Sequences > Rulesets tab)
Temporarily toggle off the specific exclusion that's blocking the contacts
Wait approximately 30 minutes for the exclusion change to take effect
Re‑add/re‑enroll the prospects from the list
Toggle the exclusion back on after successful re‑enrollment
Implementing Granular Exclusion Control
To achieve different exclusion rules for different audiences within the same sequence:
Configure audience-level exclusions - Set exclusions at the audience level for each specific audience segment when uploading
Disable sequence-level exclusions - Turn off exclusions at the sequence level to rely on audience-level settings
Re-enroll the audience - After changing exclusion settings, you must wait approximately 15-30 minutes for the exclusion changes to take effect before re‑enrollment attempts will work.If you've changed underlying CRM data (such as closing an opportunity or updating deal stages) rather than Unify exclusion settings, allow additional time for the CRM data to sync to Unify before the exclusion status updates. We recommend waiting ~1 hour before attempting to re‑enroll to ensure previously excluded contacts are now included. Note that plays cannot be rerun with a 0‑day interval (minimum is 1 day), so creating a new play with the same audience is the easiest way to immediately re‑enroll contacts.
This approach allows some audiences to exclude contacts with deals while others don't, all within the same sequence.
Proactive Company-Level Exclusion Setup
Navigate to Settings > Exclusions > New
Select Companies as the exclusion type
Set criteria using your CRM fields (e.g., company stage, industry)
Enable the Sequences toggle to proactively unenroll all contacts at matching companies from active sequences
Verify that universal exclusions haven't been disabled at the audience level, as audience-level settings can override these universal exclusions
Multiple Linked Company Records
When companies have multiple linked records in your CRM, enrollment qualification checks can produce unexpected results:
If qualification fields (such as employee count, funding amount, or custom criteria) exist on ANY linked company record that meets the criteria, the enrollment check will pass
This can result in contacts being enrolled even when their primary/visible company record does not meet the qualification criteria
The play pulls qualification data from whichever linked record satisfies the enrollment conditions, not necessarily the primary record
Diagnostic approach: If a contact was enrolled despite appearing unqualified, check the company's linked records in your CRM to see if an alternate record contains qualifying data. Navigate to the company record and review all linked/associated company records to identify which one provided the qualifying information.
Other Factors That Prevent Enrollment
Even when exclusions are disabled, several other factors can prevent enrollment:
Sequence Enrollment Limits
Sequences have a maximum enrollment limit (typically “Maximum enrollments per company”) that prevents additional contacts from enrolling once reached.
This limit is shared across all plays using the same sequence.
The per-company sequence enrollment limit is applied globally across your entire organization, not per individual play. If you set a maximum of 10 contacts per company in one play, and another play has already enrolled 8 contacts from that company, only 2 additional contacts from that company can be enrolled across all plays until the limit resets.
Other plays can consume your enrollment limit and block additional enrollments, even when your current play’s settings appear correct.
To check and adjust enrollment limits, navigate to Settings > Organization > Sequences > Rulesets.
Important: Increasing the enrollment limit does not automatically re‑enroll previously blocked contacts – you must manually re‑enroll them by re‑running the play or duplicating and launching it again.
Check the “Max enrollments reached” status in Play > Metrics to confirm if this limit is preventing enrollment.
To diagnose if global caps are causing low enrollment numbers, review the “Not Enrolled” breakdown in Metrics → Sequence node → View and check Execution Logs for “Max enrollments reached” messages.
Automatic Re-enrollment Prevention
Contacts cannot be re-enrolled in the same sequence
Re-enrolled contacts resume at their next step, not from the beginning - When you successfully re-enroll a contact into a sequence (after adjusting re‑enrollment settings to allow it), they will continue from where they left off in the sequence rather than restarting from step one.
Contacts cannot be re-enrolled in the same sequence
Re-enrolled contacts resume at their next step, not from the beginning - When you successfully re-enroll a contact into a sequence (after adjusting re‑enrollment settings to allow it), they will continue from where they left off in the sequence rather than restarting from step one.
Company-Level Sequence Exclusion Limitation
Important Limitation: Company-level exclusions based on sequence enrollment status are not currently available in Unify. You cannot directly exclude companies from plays based on whether any contact from that company is enrolled in a sequence.
Workaround: To achieve similar functionality, use a custom CRM field at the company level (such as a lifecycle stage or custom flag) that indicates “actively prospected” status, then create a company exclusion in Settings > Organization > Exclusions using that field.
Understanding "Completed: Excluded" Status
“Completed: Excluded” status appears when a contact’s sequence is terminated mid‑execution because they met an exclusion rule during the sequence. This differs from being excluded at enrollment time—it means the contact was initially enrolled but later matched an exclusion criterion while the sequence was running.
Manual Enrollment Limitations
Manual enrollment cannot bypass any active exclusion rules
To enroll contacts that match exclusion criteria (like "open opportunity exists"), you must disable the exclusion globally in Settings > Organization > Exclusions
Global exclusion changes affect all sequences, not just the target sequence
Changes to exclusion settings may take up to 30 minutes to take effect. If the exclusion is based on CRM data (like open opportunities), changes to that data in your CRM will require additional sync time before the exclusion status updates in Unify.
Changes to exclusion settings may take up to 30 minutes to take effect
Exclusions must remain disabled for the entire duration of multi-step sequences, not just during initial enrollment, as re‑enabling exclusions will block subsequent sequence steps
Manual Enrollment Exception Workaround
While manual enrollment cannot bypass exclusions, you can create targeted exceptions within exclusion rules by adding “AND” conditions with “is not equal to” operators. For company‑level exclusions, add domain is not equal to example.com to exempt a specific domain. For contact‑level exclusions, add email is not equal to user@example.com to exempt a particular contact. This provides a granular alternative to disabling the rule globally.
Note: Enhanced sequence-level exclusion configuration is planned for future release, which will provide more granular control over exclusions for individual sequences.
Preventing Post-Enrollment Exclusions: Critical Timing Considerations
A common issue occurs when exclusions are applied AFTER the first email is sent rather than before enrollment, which defeats the purpose of exclusions. This happens due to timing delays between CRM updates, exclusion processing, and email sends.
Strategic Exclusion Configuration to Prevent Post-Send Issues
To prevent exclusions from happening after the first email has already been sent:
Prefer company-level exclusions (e.g., domain-based) over person-level exclusions for new contacts to avoid caching delays that can miss pre‑send checks
Avoid activity-based exclusions (e.g., last contacted/activity) that can cause mid‑sequence removals due to CRM writeback, or disable “Exclude from Sequences” for those specific rules
Critical Combined Timing Window
CRM field updates: Approximately 15 minutes to sync before exclusion checks can properly evaluate them
Exclusion toggle changes: Up to 30 minutes to take effect system‑wide
Combined delay: Wait at least 45 minutes after CRM updates before running plays to ensure exclusions are properly applied before enrollment
This timing‑focused approach prevents the frustrating scenario where contacts receive emails despite meeting exclusion criteria, ensuring exclusions work as intended rather than as post‑send cleanup.
When the same contact appears in multiple audiences added to a single sequence, they will only be enrolled once
The system automatically deduplicates contacts across audiences within the same sequence
Total enrollment numbers may be less than the sum of all audience sizes due to this automatic deduplication
Contact-Level Exclusion Diagnostics
Individual Contact Exclusion Status Check
When you need to understand why a specific contact cannot be enrolled (especially when receiving exclusion notifications during manual enrollment attempts), navigate to Contacts, search for the contact by email, click their record, and review the Exclusion tab to see exactly which exclusion rule(s) apply to that contact.
Re‑enrollment Visibility by Enrollment Method
For Play‑based enrollments: the contact's activity log will show when they ran through the Play and display “not enrolled” with specific failure reasons like “already enrolled” or “recently enrolled.” However, if the Play itself is configured to not allow re‑runs (separate from sequence re‑enrollment settings), contacts won’t trigger a new Play run at all, and no new activity will be logged.
For manual enrollments: exclusion reasons due to re‑enrollment rules are not visible in the activity logs.
Play‑Level vs Sequence‑Level Re‑enrollment Controls
Play‑level re‑run settings are separate from sequence re‑enrollment rules. If a Play is configured to only run once per contact, the contact won’t trigger a new Play run regardless of sequence re‑enrollment settings, and no new activity will be logged in their activity tab.
Advanced Company‑Level Exclusion Behavior
Toggle ON: Proactively unenrolls all contacts at matching companies from active sequences. When a contact or company meets the exclusion criteria mid‑sequence, they are immediately removed and stop receiving any remaining sequence emails.
Toggle OFF: Prevents new enrollments only. Contacts already enrolled in sequences will continue receiving emails even if they meet the exclusion criteria mid‑sequence (for example, if an opportunity is opened for their account after enrollment). Only new enrollment attempts will be blocked.
When to use each setting: Enable the toggle when you want to immediately stop outreach when conditions change (e.g., when an opportunity is opened for an account). Keep the toggle disabled for exclusions like “last sales activity” where Unify itself triggers the activity – enabling it would cause contacts to be unenrolled as soon as Unify logs an activity, making the sequence ineffective.
Creating Custom Field‑Based Exclusions
Navigate to Settings > Exclusions > New
Select the appropriate exclusion type (Companies or Contacts)
Set criteria using any available CRM field (e.g., custom qualification status, call disposition fields)
Configure the Sequences toggle based on whether you want to remove already‑enrolled contacts or only prevent new enrollments
Save the exclusion rule
Common Reasons for Non-Enrollment
If contacts still aren't enrolling, check for these common issues:
Already enrolled in the current sequence
Currently enrolled in another active Unify sequence (automatically prevented) or excluded by HubSpot sequence rules
Persona Configuration Issues
Persona configuration can also cause enrollment issues:
Personas defined but not enabled for tracking in specific plays
Contact titles that don't match any configured persona (shown as "no valid routing target" in play logs)
Persona mapping disconnected after system updates
New personas created but not added to existing play configurations
Persona criteria too restrictive, causing contacts to fall outside defined parameters
Workaround: To ensure all contacts are enrolled regardless of persona matching, configure the sequence node to route "everyone else" to a default mailbox/sequence. This catches contacts whose titles don't match any defined persona criteria.
Excluded by company-level, sequence-level, or audience-level rules
Recently enrolled in another sequence within the cooldown period
Contact data issues or missing required fields
Free or educational email domain restrictions (check if the contact's email domain is flagged as a free email provider)
By understanding these enrollment behaviors and exclusion hierarchies, you can better control who gets enrolled in your sequences and troubleshoot issues when enrollment numbers don't match your expectations.
Dynamic Audience vs. Static Enrollment Records
When troubleshooting enrollment discrepancies, it's important to understand the fundamental difference between audience counts and enrollment records:
Audiences are dynamic - Contacts can move in and out of audiences as their data changes or as they meet/stop meeting the audience criteria
Play enrollment logs are static - Once a contact is enrolled in a sequence, that enrollment record remains in the play logs regardless of whether the contact still meets the original audience criteria
Count discrepancies are normal - The current audience count may be different from the total number of contacts enrolled from that audience because contacts may have moved out of the audience after enrollment
This means a smaller current audience size doesn't indicate an enrollment problem if the play logs show successful historical enrollments
This distinction helps explain why you might see fewer contacts in an audience today than were actually enrolled from that audience historically, which is expected behavior rather than a system issue.
Managing Sequence Enrollments: Reassignment and Re-enrollment Solutions
When you need to change the outbox for contacts already enrolled in a sequence (rather than re‑enrolling them), you can use the Email Backlog reassignment feature:
Navigate to Email Backlog > Reassign Sequence enrollments
Click Reassign Enrollments for your sequence
Select the new mailbox(es) and save
Important: This feature only works for queued enrollments that haven’t been sent yet.
To allow contacts to re‑enroll in sequences when troubleshooting enrollment issues, temporarily adjust the re‑enrollment settings:
Navigate to Settings > Features > Sequences > Rulesets tab
Set the re‑enrollment wait period to 0 days
Re‑enroll your contacts as needed
Remember to revert this setting after re‑enrollment if you don’t want this behavior to apply globally