Home C7 - Triggers & Automation 7.4 Trigger best practices

7.4 Trigger best practices

Last updated on Nov 13, 2026

The rules

10 triggers

  1. Leave the safety defaults on. The replied / opted-out / bounced / auto-replies triggers exist so you never send a follow-up to someone who answered, unsubscribed, or has a dead mailbox. Removing them is how teams get spam-flagged and annoyed replies.
  2. Add alerts before you add actions. The most valuable trigger change for most teams is "notify a human faster", not "automate more". A reply alert beats an elaborate auto-branch every time.
  3. One change at a time. Triggers run account-wide. Change one, observe, then change the next.
  4. Tag, don't destroy. When a trigger condition is ambiguous (unrelated replies), tag the prospect for human review rather than automatically removing or resuming them.
  5. Review triggers quarterly. As your team and campaigns change, old automation outlives its purpose. Check each trigger still reflects what you want.
  6. Watch the interaction with sending windows. A trigger that resumes campaigns interacts with windows and Daily Prospect Start — verify timing behavior after edits.

Debugging a misfire

When a trigger does something unexpected: check the prospect's timeline for the exact event that fired it, confirm the condition actually matched (an "unrelated reply" classification is judgment-based), and check whether a recent trigger edit is the cause. Revert recent trigger changes first — it's usually the last edit.