Skip to main content
Email exclusions help you prevent AI-generated drafts for automated emails that accidentally end up in your CRM. This reduces noise and keeps your drafts focused on real customer conversations that require human attention.

​
The Problem: Automated Emails in Your CRM

Modern CRMs often contain automated emails from various SaaS tools due to:
  • Integration syncing that captures all emails
  • Email tracking catching system notifications
  • Manual data entry mistakes
  • Broad email capture rules
Common automated email sources include marketing platforms, support systems, developer tools, and communication apps.

​
How Email Exclusions Work

Fabius checks every incoming email against your exclusion rules before generating drafts. If an email matches an exclusion, no draft is created. Note: Exclusions are evaluated before the “reply needed?” step, so excluded senders/domains never proceed to drafting.

Email Exclusions

Block specific email addresses like [email protected]Best for: Known automated senders with consistent addresses

Domain Exclusions

Block all emails from a domain like slack.comBest for: Services that use multiple sender addresses
Enter only the domain name (e.g., slack.com), not a full email address

​
Managing Exclusions

​
Creating an Exclusion

  1. Open Emails Settings: https://app.fabius.io/interactions/emails/settings
  2. Go to Exclusions: https://app.fabius.io/interactions/emails/settings/exclusions
  3. Click Add Exclusion and choose your scope:
    • Personal: Only affects your draft generation
    • Company: Prevents drafts for all team members (admin only)
  4. Select the exclusion type:
    • Email: For specific addresses
    • Domain: For entire domains
  5. Enter the email address or domain
  6. Add a reason (e.g., “GitHub automated notifications”)
  7. Click Save
Company exclusions require admin permissions and affect all users immediately.

​
Common Automated Emails to Exclude

​
Viewing and Managing Existing Exclusions

The exclusions page shows all active rules organized by:
  • Company Exclusions: Applied to all team members
  • Personal Exclusions: Your custom rules
For each exclusion, you can:
  • Toggle active/inactive status
  • Edit the reason
  • Delete the exclusion
  • See who created it and when

​
Best Practices

​
Identifying Automated Emails

Look for these common patterns:
  • Email addresses containing “noreply”, “no-reply”, or “donotreply”
  • Addresses with “notifications”, “automated”, or “system”
  • Consistent templated subject lines
  • Machine-generated content patterns

​
When to Use Company vs Personal Exclusions

Company Exclusions (Admin only)
  • Widely-used services (GitHub, Slack, HubSpot)
  • Known automated senders affecting multiple team members
  • Standard SaaS tools used across the organization
Personal Exclusions
  • Role-specific tools only you use
  • Testing or development emails
  • Personal app notifications

​
Regular Maintenance

Review your exclusions quarterly to:
  • Add newly identified automated sources
  • Remove exclusions for discontinued services
  • Share useful exclusions with your team
  • Check draft logs for patterns

​
Monitoring Effectiveness

Track the impact of your exclusions:
  1. Review Draft History: Check which emails are generating drafts
  2. Identify Patterns: Look for automated emails still creating drafts
  3. Add New Exclusions: Block newly discovered automated sources
  4. Share with Team: Recommend useful exclusions to admins

​
Troubleshooting

​
Draft Still Generated for Automated Email

  1. Verify the exclusion is active - Check the toggle in settings
  2. Match exactly - Email addresses must match precisely
  3. Check scope - Ensure it’s company-wide if needed
  4. Look for variations - Some services use multiple sender addresses

​
Not Sure What to Exclude?

  1. Review your recent draft history
  2. Look for obvious automated patterns
  3. Check email headers for system indicators
  4. Start with domain exclusions for broader coverage
Exclusions take effect immediately. Test with personal exclusions first if you’re unsure about the impact.

​
Quick Setup Guide

For new users, we recommend starting with these common exclusions: 
Domain Exclusions:
- github.com (development notifications)
- slack.com (team notifications)
- hubspot.com (marketing automation)
- zendesk.com (support tickets)

Common Email Exclusions:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Fabius does not support wildcard patterns. You must specify exact email addresses or exact domain names. For broader coverage, use domain exclusions (e.g., github.com) to block all emails from that domain.
This will prevent the most common automated emails from generating unnecessary drafts while you fine-tune your exclusion list based on your specific tools and workflows.