How to properly exclude contacts from sequences when meetings are scheduled

When contacts book meetings or advance in your sales process, you may want to exclude their entire company from ongoing sequences. However, a common issue occurs when only the meeting booker gets updated in your CRM while their teammates remain eligible for sequences.

Understanding Company-Level Exclusion Limitations

Company-level exclusions in sequences only apply to contacts that match the specific criteria you set. For example, if you create an exclusion for companies where "lifecycle stage = opportunity," it will only exclude contacts who are also marked as "opportunity" stage - not contacts from the same company who are still in "lead" stage.

This creates a problem when only the person who books a meeting gets updated to "Opportunity" lifecycle stage, while other contacts at the same company continue to be eligible for sequences.

Recommended Solution: Configure CRM Automation

The best approach is to set up your CRM to automatically update the lifecycle stage or opportunity status for ALL contacts associated with a company when ANY contact from that company books a meeting or becomes an opportunity.

For example, in HubSpot, you should configure workflows to:

• Trigger when one contact books a meeting or reaches a specific stage

• Update all contacts within the same company/domain to the same lifecycle stage

• Ensure company-wide exclusions work as expected

This prevents scenarios where sequences continue targeting other team members at companies that have already engaged with your sales team.

Alternative Solutions

Use Company-Level Fields

Instead of relying on contact-level lifecycle stages, use company-level fields for your exclusions. This ensures that when one contact advances, the entire company is properly excluded.

Custom Field Exclusions

If your CRM has custom fields like "Discovery Call Scheduled" that get populated across all company contacts, create exclusions based on these fields instead of lifecycle stages.

Troubleshooting Tips

Temporary Domain-Based Exclusions: As a quick fix while resolving CRM configuration issues, you can temporarily add specific company domains to your exclusions to prevent unwanted outreach to companies that have already engaged.

This approach helps you maintain professional communication while you work on implementing the proper CRM automation described above.