An automation rule in Aviary's (Hello's) email system stops sending email sequences the moment a lead is converted to an opportunity. Because the client (Aaron) converts nearly every inbound lead to an opportunity, this rule is effectively halting all outbound email campaigns. As of the March 17 weekly call, the email pipeline had sent only 41 emails the prior day and 5 on the day of the call — far below expected volume.
This is a critical blocker for a [1] due to flat performance across all channels.
The suppression rule was likely put in place to avoid emailing contacts who had already entered an active sales conversation. The assumption was that only a subset of leads would convert to opportunities quickly. In Aviary's case, however, Aaron converts virtually all leads to opportunities immediately, which means the suppression rule fires on nearly every contact and drains the active send list.
The fix requires a client decision before any technical change is made:
This bug surfaces a common misconfiguration risk in CRM-linked email automation: suppression rules that make sense for typical pipelines can break entirely when a client's sales behavior is atypical (e.g., converting all leads immediately). When setting up lifecycle-based suppression rules, it's worth confirming the client's actual conversion rate and workflow before assuming a "standard" threshold applies.