Layer 2: Broadcast Calendar (Time-based, cap-gated)
Broadcasts sit on TOP of the always-on automation layer, so these frequency-cap rules exist to prevent contact stacking. See section 2 for full rules.
Scheduled Broadcasts - Jul 25 to Aug 2, 2026
Sun 26
SMS send
Clicked, high-intent, SMS opt-in. Exclude: Customers, first-7d leads.
Tue 28
Email broadcast
Hook: "Beat the end-of-season rush." Engaged leads + potentials. Exclude: Customers, active-quote, new leads (created less than 10d).
Thu 30
SMS follow-up
Clicked Tue email + SMS opt-in + not converted. Exclude: Customers, first-7d leads. 48h gap from Tue.
Frequency-Cap Rules (Mandatory for All Broadcasts)
1
Max 1 marketing email per 48h per contact. A broadcast may not go to anyone who received a lifecycle email (welcome, nurture, rep follow-up) in the prior 48h.
2
Max 1 marketing SMS per 24h; never two SMS same day. Broadcast SMS excludes any lead inside their first 7 days (welcome and drip window active).
3
New-lead quiet window: first 10 days. No broadcast to a contact created within 10 days; they are mid welcome/nurture. Let the automation own them first.
4
Hard suppression (always): unsubscribed, hard-bounced, opt-out ledger. Plus, until gate-fixes ship: Customers and active-quote leads excluded from broadcasts.
5
Transactional exempt (shipped, reconversion). Email and SMS for the SAME event on one day is fine (different channels, one message).
6
48h between any two broadcast touches to the same contact, across email and SMS combined.
Broadcast content hook (approved): "Beat the end-of-season rush." Late summer is peak dock-use and the last window before fall install lead-times stretch. Personalization by Type_of_Watercraft and Type_of_Dock shows relevant product per contact.
Gate fixes required before widening broadcast audience: Two staged improvements (welcome-suppression-fix and cold-SMS-suppress-quote) must ship before broadcasts can reach customers or active-quote leads. Until then, cap rule 4 excludes them. Maps in the journey show these rules are baked in; the broadcast schedule is safe as-is.
PivotPlanit