How are contacts automatically removed from Unify sequences?

Context

When managing email sequences in Unify, it's important to understand all the ways contacts can be automatically removed from sequences to ensure compliance with recipient preferences, maintain good email practices, and avoid unexpected sequence interruptions.

Answer

Unify automatically removes contacts from sequences in several scenarios. Understanding these removal triggers helps you manage your sequences effectively and troubleshoot unexpected unenrollments.

Critical Sequence Settings for Proper Opt-Out Enforcement

Before configuring opt-outs, ensure exclusions are properly enabled in your sequence settings:

• Enable exclusions toggle: Navigate to your sequence's advanced settings and verify that the exclusions toggle is enabled. This setting must be turned on for the exclusions list to prevent enrollments of contacts already on your exclusion list.

• Enable automatic unenrollment: Also in sequence settings, ensure the "Enable this to exclude and unenroll People from Sequences" toggle is turned on. When enabled, contacts will be automatically removed from sequences if they meet exclusion criteria during an active sequence (e.g., if they become a customer or opportunity while enrolled).

Important: If the exclusions toggle is disabled, contacts may be enrolled in sequences even if they're on your exclusions list or have previously opted out. If automatic unenrollment is disabled, contacts enrolled before meeting exclusion criteria will continue receiving emails even after they should be excluded. Review these settings for all active sequences to ensure proper opt-out enforcement.

Navigate to Settings > Features > Sequences > Rulesets tab to configure your unsubscribe link settings. You can create different rulesets with distinct opt‑out configurations, allowing you to customize the unsubscribe link text and behavior for different sequences.

• Customize unsubscribe link text for different sequence types

• Apply different opt‑out behaviors based on sequence purpose

• Maintain consistent branding across your unsubscribe experience

• Configure sequence‑specific opt‑out settings rather than using a one‑size‑fits‑all approach

Critical Configuration Gap

Contacts may continue receiving emails even if they meet exclusion criteria (like becoming a customer) if they were enrolled before meeting those criteria and the automatic unenrollment toggle is disabled. This is a common configuration oversight that can result in inappropriate continued outreach to customers or other excluded contacts.

• Ensure mapping is correctly mapped in your Hubspot or Salesforce mapping to ensure opt out information is written back

CRM Field Mapping Clarification for Salesforce

When configuring your Salesforce integration, it's important to understand the distinction between commonly confused opt‑out fields:

• Email Opt Out – Standard Salesforce field on Lead/Contact, typically treated as a global “do not email this person” flag

• Do Not Email – Often a custom/marketing‑specific field (e.g., from Marketing Cloud/Pardot) used for certain types of campaigns rather than blocking all emails completely

Map whichever field your team treats as the master/global email suppression field. For most organizations, this will be the standard “Email Opt Out” field.

Email Opt-Out

• Ensure email opt out link is clearly visible at the bottom of each email in your Sequence on your Sequence settings page

Other Automatic Removal Triggers

Contacts are also automatically removed from sequences when:

Three-Tier Exclusion Toggle Hierarchy

Exclusions have a complex three-tier toggle hierarchy that controls how they affect sequences. Understanding this hierarchy is critical for proper configuration:

• Global "Exclude from Sequences" toggle (on the exclusion itself at Settings → Organization → Exclusions): This is the master switch. When enabled, the exclusion will block contacts from enrolling in sequences regardless of other settings. This toggle takes precedence over Ruleset-level settings.

• Ruleset-level sequence toggle (at Settings → Features → Sequences → Rulesets): Controls whether the exclusion applies to sequences within that specific Ruleset. However, this toggle is overridden by the global "Exclude from Sequences" setting - if the global toggle is ON, contacts will be excluded even if the Ruleset toggle is OFF.

• Audience-level toggle: Controls whether the exclusion filters contacts at the audience level before they reach sequence nodes in a play.

Important interaction: An exclusion can be toggled OFF at both the audience level and the Ruleset level, but contacts will still be excluded from sequences if the global "Exclude from Sequences" toggle is enabled on the exclusion itself. To truly bypass an exclusion for a specific play, you must disable the global "Exclude from Sequences" toggle, wait ~30 minutes for the change to propagate, then re-run the play.

Other Automatic Removal Triggers

Contacts are also automatically removed from sequences when:

• Exclusions are triggered: When a contact matches an active exclusion with the Sequences toggle enabled (at either people or company level), they are removed from all active sequences. You can check which exclusions apply to a specific contact by viewing their person record in Unify under the exclusions tab.

• Company-level exclusions: When a company-level exclusion is triggered (e.g., CRM condition at the account level), all associated contacts are removed from sequences. Important: When you create a company-level exclusion, the “Excluded Count” shown includes ALL people associated with those companies, not just the number of companies. This is why you may see much higher excluded counts than expected—if you exclude 86 companies, but those companies have 1,368 total contacts in your database, the excluded count will show 1,368 people.

• Choosing between company-level and people-level exclusions: Use company-level exclusions when you want to exclude everyone at specific companies. Use people-level exclusions when you only want to exclude specific contacts at those companies while keeping other contacts from the same company eligible for sequences.

• Domain-based exclusions formatting: When configuring domain-based exclusions (such as competitor domains), enter multiple domains in the same field separated by commas. Use only the root domain without http:// or www prefixes (e.g., competitor1.com, competitor2.com, competitor3.io).

• HubSpot lists limitation: HubSpot lists are not supported as exclusion criteria in Unify. You must configure exclusions using individual field-based conditions or use CSV uploads as an alternative.

• Exclusion toggle settings: Each exclusion has multiple toggle levels that interact in a hierarchy (see "Three-Tier Exclusion Toggle Hierarchy" above). Understanding how these interact is important:

  • Toggle ON at sequence level: Removes contacts from active sequences immediately when they meet exclusion criteria (e.g., if a deal is created, all contacts from that company are removed from ongoing sequences)

  • Toggle OFF at sequence level: Only prevents new contacts from enrolling in sequences, but does not remove contacts already enrolled in active sequences

  • Important: The global "Exclude from Sequences" toggle on the exclusion itself takes precedence over Ruleset-level and audience-level settings. An exclusion can be toggled OFF at the audience level but still toggled ON at the global or Ruleset level, which will exclude contacts when they reach a sequence node in a play.

• CRM-driven exclusion criteria: When CRM-based conditions are met (e.g., opportunity created, Salesforce field updates) and exclusions are configured to affect sequences

• Built-in open opportunities exclusion: Unify includes a built-in "open opportunities" exclusion that automatically removes contacts from sequences when a deal/opportunity is created for their company (when the toggle is enabled). Important: This exclusion relies on matching specific deal/opportunity stage names in your CRM. If you change stage names in HubSpot or Salesforce, you must update the exclusion configuration to reflect the new stage names, otherwise the exclusion will stop working and contacts with active deals may continue receiving sequence emails.

• Deal‑based exclusion limitation: Unify's native HubSpot deal‑based exclusions operate only at the company level, removing every contact at that company when a deal is created. To target individual contacts, create a custom contact‑level field in HubSpot (e.g., “Has associated deal in stage X”), populate it via a HubSpot workflow, sync the field to Unify, and then build a people‑level exclusion on that field.

• Mailbox ownership changes: When the ownership of the sender's mailbox used to enroll the contact changes

Note: Exclusions are evaluated continuously, and CRM-based updates typically propagate on a short cadence, which can remove contacts mid-sequence. After removing a contact from an exclusion list or updating CRM fields that trigger exclusions, there may be a delay before the contact can be re‑enrolled in sequences.

Beyond opt-out links, contacts can also be automatically removed through exclusions, CRM triggers, and mailbox ownership changes as described above.

• Allow 15-45 minutes for exclusion changes to propagate before expecting new enrollments

• Global exclusions must be disabled or no longer matched for re‑enrollment to occur, even if the contact no longer meets other exclusion criteria

When a contact clicks the unsubscribe link or replies to opt out, only that individual contact is removed from the sequence; other contacts at the same company remain enrolled unless you configure a company‑level or domain‑level exclusion with proactive unenrollment enabled. To automatically unenroll all contacts at a company, set up the appropriate exclusion and enable proactive unenrollment in your exclusions settings. Learn more.

Exclusion Timing and CRM Field Dependencies

When exclusions rely on CRM fields that are updated after a contact is enrolled, the first email step can be sent before the exclusion evaluates. This occurs because enrollment happens immediately based on the initial audience criteria, while CRM sync runs on ~15‑minute polling cycles. The contact is later unenrolled when the CRM data syncs and the exclusion triggers.

Re-enrollment Timing and Mechanics After Exclusion Changes

Setting NOT required: If a contact was never enrolled in a sequence before (only blocked by exclusions), they will enroll automatically once exclusions no longer apply and they meet audience criteria.

Setting IS required: Only when a contact was previously enrolled in that exact sequence and completed it, and you want them to enter the same sequence again.

Re‑enrollment settings are configured in your sequence rulesets. Navigate to Settings › Features › Sequences › Rulesets tab to access re‑enrollment restrictions.

• Days before re‑enrollment: Set the minimum number of days required before a contact can be enrolled in any sequence again (can be set to 0 days for immediate re‑enrollment).

• Allow re‑enrollment into the same sequence: Toggle this setting to permit contacts to re‑enroll into the exact same sequence they previously received. When disabled, contacts who have already been enrolled in a specific sequence cannot be added to that same sequence again, even if they were unenrolled.

Note: If you encounter a “prospect already sequenced” error when trying to re‑enroll a contact, check the ruleset applied to that sequence. You may need to enable “Allow re‑enrollment into the same sequence” or adjust the days before re‑enrollment setting. Admin permissions are required to modify ruleset settings.

Alternative to re‑enrollment: If you need to make updates to an active sequence, you can edit the sequence and then upgrade all enrollments (active and queued) to the new version rather than unenrolling and re‑enrolling contacts.

Max Enrollments Per Company

The “Max enrollments per company” setting limits the number of contacts from the same company that can be enrolled in sequences at the same time. It counts only active enrollments and does not consider CRM lifecycle stage, deal status, or conversation activity. To prevent enrolling additional contacts when a deal is active, use company‑level exclusions driven by CRM deal/opportunity fields rather than relying on this setting.

Advanced Sequence Removal Scenarios and Configuration Pitfalls

Activity-Based Exclusion Configuration Pitfall

When configuring activity-based exclusions (e.g., “Recent Manual Email” or “Last activity date within X days”), Unify’s email activity writeback can update these fields and trigger immediate unenrollment after the first email step.

Best Practice: Many teams keep the Sequences toggle OFF for activity‑based exclusions to prevent unintended mid‑sequence removals while still blocking new enrollments.

Out-of-Thread Reply Detection

Unify can detect when a contact has replied outside the sequence thread and may remove them from active sequences based on this detection.

Direct Email Impact Clarification

Sending a direct 1:1 email outside of Unify or CRM sequences does not automatically unenroll contacts, though it may indirectly trigger unenrollment if activity‑based exclusions that track manual email activity are enabled.

Troubleshooting Steps

1. Check CRM activity/history for field updates that occurred around the time the first email was sent.

2. Review exclusion criteria to see if they depend on fields that update post‑enrollment.

3. For company‑level exclusions, verify the domain in the exclusion matches the company’s primary domain in Unify.

4. Add a short delay node (15‑30 minutes) at the start of the play to give CRM data time to sync before exclusions are evaluated.

5. If using built‑in opportunity exclusions, ensure stage names in the exclusion configuration match the current CRM stage names.

Troubleshooting Unexpected Enrollment Numbers

If fewer contacts than expected enroll in a play, they are likely being caught by active exclusions. Currently, there is no easy self-serve way to see exactly why a specific person didn't go through a play. This is a recognized product gap that Unify is actively working to improve.

Available options for investigating enrollment issues:

• Person-level Exclusions tab: Navigate to an individual contact's profile in Unify and check the Exclusions tab to see which exclusions apply to them. This requires checking each person one by one.

• Settings → Exclusions: Review all active global and sequence-level exclusions at Settings → Features → Exclusions to identify which ones might be preventing enrollment.

To temporarily bypass exclusions for a specific play:

1. Identify which exclusions are catching the contacts you want to enroll

2. Go to Settings → Organization → Exclusions and toggle OFF "Exclude from Sequences" for those specific exclusions

3. Wait ~30 minutes for the change to propagate through the system

4. Duplicate the play and re-run it

5. Immediately re-enable "Exclude from Sequences" on those exclusions after the play completes

Important: Simply turning off exclusions at the Ruleset level is not sufficient if the global "Exclude from Sequences" toggle is enabled on the exclusion itself. The global setting takes precedence over Ruleset-level settings.

Manual Opt-Out Process for Email Replies

When contacts request to opt out by replying to your sequence emails (rather than clicking the unsubscribe link), you need to manually process their request. Here's the step-by-step procedure:

1. Navigate to the contact's profile in Unify

2. Click the “opt-out” button at the top right of the page

Critical Distinction: Opt-Out vs. Unenrollment

Opting Out a Contact:

• Prevents them from receiving ALL future Unify emails across all sequences

• This is a permanent action that affects all current and future communications

• Use this when contacts explicitly request to stop receiving all emails from you

Unenrolling from a Single Sequence:

• Removes them only from that specific sequence/play

• Keeps them available for future Unify sequences

• Use this when you need to remove someone from one campaign but want to maintain the ability to contact them in future sequences

When to Use Each Option

• Use Opt-Out: When contacts explicitly request to stop receiving all emails, express frustration, or indicate they don't want any future communications

• Use Unenrollment: When you need to remove someone from a current sequence due to timing, relevance, or strategic reasons, but want to preserve the ability to include them in future appropriate sequences

Reversing an Accidental Opt-Out

If you accidentally opt out a contact when you meant to unenroll them from a single sequence, the opt-out can be reversed with proper authorization:

• Opt-outs are intended to be permanent and should only be reversed if you have the lead's explicit permission to resume outreach

• Currently, reversing an opt-out requires contacting Unify support to clear the opt-out record from the database

• Once the opt-out is cleared, you can re-enroll the contact into sequences as needed

Important: Before requesting an opt-out reversal, ensure you have documented permission from the contact to resume communications. Reversing opt-outs without proper consent can damage your sender reputation and violate email best practices.

Advanced Troubleshooting for Sequence Enrollment Issues

Understanding Queued Contacts and Exclusion Timing

Contacts matching exclusion criteria may still appear as “queued” in your sequence. This is expected behavior—exclusions are evaluated at send time, not when contacts are queued. Contacts matching active exclusions will be automatically skipped when the sequence attempts to send, even if they appear in the queue.

Queued Message Handling During Unenrollment

When you unenroll contacts from sequences, it's important to understand what happens to messages that are already scheduled but not yet sent:

• Immediate Cancellation of Queued Messages: Unenrolling a contact cancels all remaining steps for that contact immediately, including any queued messages scheduled to send.

• Bulk unenrollment runs in batches and completes shortly after you trigger it. Queued messages for the unenrolled contacts will be canceled.

Alternative: Pausing Sequences for Campaign-Wide Stops

If you need to stop an entire campaign rather than removing specific contacts, pause the sequence or play. This will prevent all queued emails in that sequence from sending to any enrolled contacts while preserving enrollments.

Strategic Considerations

• Use pausing when you need to temporarily halt a campaign due to timing, content updates, or external factors.

• Use unenrollment when you want to permanently remove specific contacts while keeping the campaign active for others.

• Remember that pausing preserves all enrollment data and allows you to resume exactly where you left off.

Workaround for Allowing Specific Contacts Through Exclusions

If you need to enroll a specific contact who is caught by an exclusion, you can add a filter to that exclusion rule. Navigate to the exclusion settings and add a condition such as “Email is not [contact’s email]” to exclude that individual from the exclusion rule. This allows you to keep the broader exclusion active while making exceptions for specific contacts.

Exclusions and Static Lists vs. Play Triggers

Exclusions do not apply to static lists uploaded to Unify, but they do apply to play triggers. If you’re using a list as a trigger in a play and contacts aren’t enrolling as expected, check whether exclusions are blocking them at the trigger evaluation stage.