Frequency caps & quiet hours

The fastest way to burn a list is to over-message it. WeZend's sending policy is a platform-level guard: however many campaigns, journeys and API calls target a contact, the policy decides what actually goes out.

What you can cap

Under Settings → Sending policy:

• Global marketing cap — e.g. max 4 marketing messages per contact per week, across all channels.
• Per-channel caps — e.g. max 2 SMS per week (SMS fatigue is real and expensive), max 5 emails.
• Per-category caps — using the same categories as the preference center: max 1 "offers" message per day even if three different campaigns fire.
• Quiet hours — a nightly window (e.g. 21:00–09:00) where marketing messages are held, not dropped: they queue and go out when the window opens, in the contact's timezone when known, falling back to your account timezone.

What is exempt

Transactional messages — OTPs, receipts, delivery notices, password resets — bypass caps and quiet hours by design. A 3 a.m. login code must arrive at 3 a.m. The transactional/marketing flag is set per send ("category": "transactional") and per journey step.

How conflicts resolve

When a contact hits a cap, further marketing sends that period are suppressed and recorded as such (visible in message history with the suppression reason — never a silent drop). Journeys handle it gracefully: a suppressed step is skipped or retried after the window depending on the step's setting.

Why bother

Beyond politeness: complaint rates are the deadliest deliverability signal there is, and complaints spike when people feel bombarded. A cap costs you a few sends today and buys you inbox placement for quarters.