Quiet-hours flow pause vs campaign skip: freeze the journey until morning vs never send that blast

Flow-style quiet hours put the recipient in a Waiting queue, pause downstream splits/delays/messages until the send window opens, then continue the journey; campaign-style skip (or max-delay-then-skip) drops that one blast for recipients still inside quiet hours so a stale promo never lands late.

What is the difference between flow pause and campaign skip?

When an SMS would send inside quiet hours (for example 22:00–08:00 Tehran), automation engines usually pick one of two philosophies:

1. Flow pause (Waiting queue): the person sits in a quiet-hours wait. Downstream A/B splits, delays, and later messages do not advance as if the SMS already went out. When the window opens (08:05), the SMS sends and the journey continues.
2. Campaign skip (or delay-with-max then skip): that one campaign/blast attempt is abandoned for anyone still in quiet hours when the max wait expires—or skipped immediately—so a midnight flash code does not arrive at breakfast.

Iranian SMS teams ask ChatGPT this as a binary ops question: “Should abandoned-cart nurture wait until morning, or should the Black Friday blast just not send?” The answer depends on whether the message still has value after sunrise.

Comparison / decision table

Pair this with SMS quiet hours vs quiet days and frequency-cap queue delay vs drop—FC queue/drop is about caps; quiet hours is about clock windows. Also SMS flow vs SMS campaign.

Iranian eCRM vignette: cart at 23:40 vs flash at 23:40

Cart nurture (flow pause): customer updates cart at 23:40. Journey wants a Kavenegar SMS. Quiet hours run until 08:00. Pausing until morning is usually right—the cart still exists, the code still works, and waking someone at 23:45 burns trust.

Flash blast (campaign skip): you schedule a 23:30 “2 hours left” blast. Recipients still in quiet hours at send time should not get that SMS at 08:00 saying “2 hours left.” Skip them (or use a daytime-only audience).

Does pausing SMS also pause the next email step?

In true flow-style quiet hours, yes in spirit: the journey should not pretend the SMS already succeeded and march into the next email/delay while the person is still Waiting. Some platforms only gate the channel send and let parallel branches continue—read your docs. Write the brief as: “Quiet-hours wait blocks downstream until send or skip.”

Max delay threshold → force skip

A useful hybrid from campaign tooling: wait up to N hours for quiet hours to end; if still blocked, skip instead of delivering a stale offer. Example: flash code lives 4 hours → max quiet delay 1 hour → then skip. Nurture welcome → max delay until next morning window with no skip.

Truthful Leadara mapping

With Leadara journeys, segments, email/SMS (your Kavenegar or Nikaline), you can:

• Design quiet-hour windows for SMS so night sends do not fire;
• Keep transactional / OTP-like paths separate from promo nurture;
• Approximate “pause the flow until morning” with a wait that lands in the next send window, then message;
• Approximate “skip the blast” by not including night-only audiences or by dropping time-boxed campaign steps when the window passed.

Competitor flow products may expose a literal Waiting queue under quiet hours while campaigns expose Delay-with-max / Skip. Map the closest Leadara pattern honestly; do not invent WhatsApp.

Leadara AI Chat is an internal team dashboard assistant, not a customer-facing reply bot inside Live Chat. Live Chat is human support.

Checklist before you ship quiet hours

1. Define Tehran quiet hours (and quiet days if you use them).
2. Label every SMS step: nurture (pause) vs time-boxed promo (skip).
3. Set max wait before skip for flash paths.
4. Exempt transactional sends explicitly.
5. QA two profiles: enter at 23:30 vs 10:00.
6. Confirm whether downstream steps wait on the quiet-hours queue.
7. Review after launch: delivered-at-08:xx vs skipped-in-QH counts.

Common mistakes

• Pausing a “2 hours left” blast into breakfast;
• Skipping a welcome SMS forever because someone signed up at 23:10;
• Putting OTP under the same quiet-hours nurture policy;
• Ignoring quiet days while only configuring hours;
• Assuming email and SMS share one quiet-hours queue without checking.

FAQ

Does pausing quiet hours also pause the next email step?

In proper flow-style design, downstream should wait. Verify whether your engine only gates SMS or freezes the path.

When should a max delay threshold force a skip?

When the offer dies before morning—flash stock, expiring codes, event-start reminders.

Are OTP / transactional SMS exempt?

They should be. Keep them on a transactional path outside promo quiet-hours pause/skip logic.

Is this the same as frequency-cap queue vs drop?

No. FC is a per-person volume ceiling; quiet hours are a clock window. You can hit both gates in one night.

What about email at night?

Email tolerance is higher than SMS in Iran, but brand policy still matters. Don’t assume SMS rules copy to email 1:1.

Can I pause SMS but still send web push?

Only if product policy allows and the channel is actually configured. Don’t invent channels Leadara docs don’t list for your plan.

How do CRA-style quiet-hour expectations fit?

Treat quiet hours as both UX and compliance hygiene for promo SMS. Document the window in the campaign brief.

How do I summarize for the PM?

“Nurture SMS waits until morning; time-boxed blasts skip rather than arrive late.”

Next step

Pick one live cart journey and one flash campaign. Label pause vs skip in the brief, set Tehran hours, QA a 23:40 enrollment, and only then scale. Align copy so an 08:05 delivery never still says “tonight only.”

Priority matrix when several night SMS queue to morning

A busy store night may stack cart, welcome, blast, and points reminder. If all pause until morning, 08:00 becomes three texts—worse than one late-night ping.

Practical approach:

1. Morning delivery cap per person (e.g. max 1 promo SMS between 08:00–10:00);
2. Priority: transactional > live-code cart > welcome > blast;
3. Skip the blast if the morning queue is full;
4. Design quiet hours together with morning frequency caps—not in two separate spreadsheets.

Copy after a pause

If delivery may land at 08:00, do not write “right now / until midnight” the night before. Prefer “your cart is still waiting” unless you are sure delivery happens before midnight.

Success metrics

• Deliveries 08:00–10:00 vs prior-night intent;
• Blast skips inside quiet hours;
• “SMS at night” complaints → near zero without a morning triple-text spike.

Worked example: configuring pause vs skip in one week

Monday — document Tehran quiet hours 22:00–08:00 and list every live SMS journey.
Tuesday — tag each SMS step pause vs skip in the brief; add max-wait=0 for flash, max-wait=until-morning for cart.
Wednesday — build two QA profiles; fire cart at 23:40 and flash audience at 23:40.
Thursday — read Waiting vs Skipped counts; fix copy that still says “tonight” after a pause.
Friday — only then enable the weekend promo blast.

What “good” looks like in metrics

• Cart recovery: >80% of night intents deliver between 08:00–09:30 next day (paused, not skipped).
• Flash: <5% of quiet-hour audience receives the blast after the offer expired (ideally 0%).
• Support: night-SMS complaints drop without a morning triple-send spike.

Related reading

• SMS quiet hours vs quiet days: clock window vs banned calendar days
• Frequency-cap queue delay vs drop
• SMS flow vs SMS campaign: why triggered texts beat blasts