Quiet hours first, then Smart Sending recheck: delay overnight can still skip at sunrise

Quiet hours are evaluated before Smart Sending / frequency windows at actual send time: a message delayed overnight is re-checked when the quiet window ends; if another SMS landed inside the Smart Sending window during the wait, the delayed message is skipped—not automatically rescheduled again.

What does “quiet hours first, then Smart Sending recheck” mean?

Marketers often model a single gate: “If it’s night, wait until 8am, then send.” Real engines (Klaviyo-style) stack two gates in order:

1. Quiet hours first: at intended send time, if the contact is inside the quiet window, delay until the window opens (flow Waiting behavior).
2. Smart Sending / frequency recheck at the new send time: when 8am arrives, the platform checks again whether another SMS (or the channel’s smart-sending window) already messaged this person recently. If yes, the delayed SMS is skipped—it does not get a second overnight delay.

That is why teams see “why was my delayed SMS skipped at 8am?” in dashboards after a busy night of parallel journeys.

Ordered sequence (memorize this)

1. Journey reaches an SMS step at 23:20.
2. Quiet hours block → contact enters Waiting until 08:00.
3. Meanwhile at 07:10 another campaign/flow SMS delivers (promo, blast, or even another nurture).
4. At 08:00 quiet hours clear → Smart Sending / FC window is evaluated now.
5. If still inside the smart-sending/FC cool-down → skip the delayed SMS.
6. Skips from Smart Sending are typically not auto-rescheduled; the step is lost unless the journey has another path.

Compare with smart-sending window vs flow frequency filter and frequency-cap queue delay vs drop. Quiet hours alone: quiet hours vs quiet days.

Iranian vignette: abandoned cart at 23:00 + morning campaign

Store setup:

• Quiet hours SMS: 22:00–08:00 Tehran;
• Smart Sending / recent-SMS window: 16 hours;
• Flow A: cart updated 23:05 → wants recovery SMS → delayed to 08:00;
• Campaign B: morning promo blast scheduled 07:30 to a wide segment that includes the same user.

Result under two-gate semantics: Campaign B delivers at 07:30; at 08:00 Flow A rechecks, finds a recent SMS, skips the cart recovery. The marketer expected “wait until morning then always send.” The engine did something stricter—and usually healthier for inbox trust.

Why this surprises people

• They diagram only quiet hours, not the second gate;
• They assume a skip will retry tomorrow;
• They run overlapping blasts and flows on the same night;
• They change the Smart Sending window after the delay started and expect retroactive leniency (usually it uses the rule at send time).

Email vs SMS windows

Smart Sending / frequency windows are often per channel. An email at 07:00 does not always suppress an SMS at 08:00—or it might, if you configured a cross-channel policy. Write the brief per channel. Do not assume one global cool-down without reading the product.

Truthful Leadara mapping

With Leadara journeys, segments, email/SMS (Kavenegar/Nikaline):

• Configure quiet-hour windows so night SMS does not fire;
• Apply frequency / spacing rules so morning delivery still respects recent sends;
• Expect the practical interaction: a wait for morning does not guarantee send if another SMS landed during the wait—design overlapping journeys accordingly;
• Prefer queue-with-TTL or explicit retry branches if a skipped recovery SMS must get a second chance (see FC queue vs drop).

If a competitor documents the exact order “quiet hours before Smart Sending; SS skips not rescheduled,” say Leadara teams should implement the same mental model with quiet windows + frequency filters even when the UI labels differ.

Leadara AI Chat is an internal team assistant—not a customer-facing live-chat bot. Live Chat is human support. No invented WhatsApp.

Design rules that prevent 8am surprises

Practical steps

1. Draw the two-gate sequence on the campaign brief.
2. List every SMS that can fire between 22:00 and 09:00 for the same segment.
3. Set Tehran quiet hours and the frequency/smart window in writing.
4. QA: Profile hits cart at 23:00; force a second SMS at 07:30; observe 08:00 skip vs send.
5. Decide: protect cart SMS (suppress morning blast) or accept skip.
6. If skip is unacceptable, add a next-day branch—not a silent hope.
7. Review weekly counts of QH-delay then SS-skip.

Common mistakes

• Modeling only quiet hours;
• Assuming skipped-after-delay messages reschedule themselves;
• Wide 07:30 blasts that poison in-flight cart flows;
• Changing SS windows mid-flight without retesting;
• Mixing email cool-downs into SMS mental models blindly.

FAQ

Why was my delayed SMS skipped at 8am?

Another message likely landed inside the Smart Sending / frequency window while quiet hours held the first SMS. Recheck at send time failed.

Does changing the Smart Sending window apply retroactively?

Usually the rule at actual send time matters. Don’t rely on retroactive forgiveness—retest.

Are email and SMS Smart Sending windows independent?

Often yes (per channel). Confirm in your product; cross-channel caps are a separate policy.

Is this the same as FC queue vs drop?

Related but different act in the play. After QH releases you, FC/SS may still drop/skip. Queue-delay would try again inside a TTL; classic SS skip does not.

Should cart recovery or the morning blast win?

Product choice. Many stores suppress morning promo for people in an active cart journey.

Do quiet days recheck the same way?

If a day ban delays send into the next allowed day, run the same mental model: re-evaluate frequency at the new send time.

Can AI Chat fix overlapping journeys for me?

Leadara AI Chat helps the team inside the dashboard; it is not a customer bot and does not magically dedupe live sends without your design.

How do I summarize for the PM?

“Quiet hours delay to morning; at morning we recheck frequency—and we may still skip.”

Next step

Reproduce the dual-trigger night on two QA profiles (QH-only vs QH+morning blast). Decide which SMS wins, document the two-gate order, then adjust audiences or add an explicit retry branch before the next big promo night.

Protecting recovery SMS from morning skips

To reduce 8am skips on cart flows:

1. Morning blast segment: NOT in active_cart_journey;
2. Or move the blast to 11:00 so delayed flows at 08:00 get first chance;
3. Do not casually Ignore Smart Sending on cart flows without a written policy—unscoped ignore creates spam;
4. If skipped, add an explicit “next day 10:00 if cart still open” branch.

Two separate dashboards

• Dashboard A: count Waiting because of quiet hours;
• Dashboard B: count skips after QH release because of SS/FC.

A single “not sent” metric hides which gate failed.

War-room drill before a big campaign

Night before Black Friday, on staging: one profile QH-only, one QH+07:30 blast, one control. Sign the outcome table with the team.

Worked example: dual-gate night drill

1. Set quiet hours 22:00–08:00 and a 16-hour SMS smart/frequency window.
2. Profile A: cart at 23:00 only → expect deliver ~08:00.
3. Profile B: cart at 23:00 + promo SMS at 07:30 → expect cart SMS skip at 08:00.
4. Profile C: promo only at 07:30 → expect promo deliver, no cart.
5. Write the winner policy: suppress promo for in-cart journeys, or accept skip + next-day retry.
6. Ship only after the three profiles match the signed table.

Copy and analytics hygiene

• Never promise “you will get a cart SMS in the morning” in on-site UI if SS can still skip.
• Export reason codes: qh_delayed, ss_skipped_after_qh, delivered_after_qh.
• Review them the morning after every major blast.

Related reading

• Smart-sending window vs flow frequency filter: account-wide recent-send skip vs per-flow rules
• SMS quiet hours vs quiet days: clock window vs banned calendar days
• Frequency-cap queue delay vs drop