What happens when automation conditions overlap?

Overlapping conditions create automation conflicts:

The problem: Customer action qualifies for multiple automations. Without coordination, all automations trigger. Recipient receives multiple, potentially conflicting messages.

Example: Customer browses products and adds to cart. Browse abandonment triggers because they viewed products. Cart abandonment triggers because they left items in cart. Both emails send within hours.

Consequences: Recipient overwhelmed with similar messages. Messages may have different offers, causing confusion. Engagement diluted across messages. Appears disorganized and spammy.

Solutions: Priority rules: Higher-intent automation wins. Mutual exclusion: If in Flow A, cannot enter Flow B. Consolidation: Single message combining triggers. Frequency caps: Limit total messages regardless of triggers.

Overlaps are inevitable in complex programs. Deliberate rules must govern which automation takes precedence.