The pattern that verifies, immediately before send, whether the chosen channel is permitted for this customer in this moment: active subscription, current consent, regulatory coverage (BAA, age gating, jurisdictional rules), and any conditional contracts. Distinct from suppression and exclusion logic because eligibility is the affirmative gate at send time rather than the negative-list filter that runs earlier. Should be the last decision before the message leaves the queue.
The capability a stack needs to run this pattern, and the vendors that provide it, on Martech Stack Builder.
Warn the customer before the overage, the roaming charge, or the plan-mismatch cost lands on the bill, so the conversation is about what to do next rather than about why the bill is what it is
Recover the buy-online-pickup-in-store orders that the customer placed and never collected, with the cross-system identity and the in-store inventory signal that the recovery has to coordinate around
Follow up with shoppers who viewed products but never added to cart, filtering out the low-intent browsers so the sequence does not dilute itself
Recover the abandon that happened on the phone and the purchase that continues on the laptop, as one customer rather than two
Pick the cheapest channel that achieves the outcome (owned email before owned push before paid social) rather than firing every channel by default, and reserve the expensive channels for the moments they earn
Give the customer real control over what they receive on which channel, propagate the choice to every system that sends, and respect the jurisdictional defaults that say what each silence means
Stop sending the same offer through email, push, and SMS in the same hour, so the customer experiences one message about one thing rather than three timed competitions for their attention
Cap contact at the person, not per channel, so the customer stops getting hit five times a day by systems that do not talk to each other
Advance the onboarding sequence on what the user actually did in the product, not on a fixed timer that ignores their progress
A three-message email sequence triggered by abandonment, gated by consent and channel eligibility
A single consent record per user, mechanically propagated to every downstream system that activates against it