Late entry after a calendar wait: silent drop vs a Window-Miss alternate path

A late-entry drop removes anyone who arrives at a specific-date/time Wait after the deadline (no next message); a Window-Miss path routes those late arrivals to an alternate branch (follow-up, retry, or softer offer) instead of ending the trip with no design.

What is the difference between late-entry drop and Window-Miss?

A calendar Wait says “wait until Aug 8 at 18:00.” If someone reaches that step after 18:00 (queueing, FC, late enroll), what happens?

1. Silent late-entry drop: the engine removes them with no further Send. No “you’re late” message was designed—the path ends.
2. Window-Miss path: like WebEngage-style Wait for Date/Time Slots with On Window Miss—late arrivals go to follow-up, retry, or a post-sale soft offer.

Do not confuse this with past-dated calendar delay exit vs next occurrence: there the contact was already inside the delay when the slot passed; here they arrive late to the Wait step itself.

Related: wait until date property vs relative duration and delay-until-weekday vs fixed N-days. The practical question here: drop late arrivals or give them a designed miss path?

Comparison table

Iranian example: Black Friday / Yalda ends 18:00

Home-goods store:

1. Morning: “sale interested” segment enters;
2. Calendar Wait: today 18:00 “last chance before close”;
3. Kavenegar SMS with code valid until 18:30;
4. Someone hits the Wait at 18:45 because of queueing:

For Tehran flash sales, Drop or honest Window-Miss beats a blind next-slot.

Second example: late webinar signup

Online academy, webinar today 17:00:

• Someone enrolls at 17:20 and reaches Wait “until 17:00”;
• Drop: no live reminder (correct—session started);
• Window-Miss: recording link + next cohort invite—worth designing;
• Blind next Tuesday: only OK if the Wait was intentionally weekly DoW, not “this session.”

How to design a Window-Miss path (steps)

1. Brief: what exact hour is the slot (Tehran)?
2. Define three outcomes: On-time → main message; Late → Window-Miss; Never entered → outside this journey.
3. Miss copy must be honest: “window closed,” not “you still have 20%” on a dead code.
4. Separate success metric for Miss (CTR on alternate offer, not flash conversion).
5. QA: on-time 17:50; late 18:10; very late next day.
6. Sync with inventory: if stock is zero at 18:00, Miss must not sell the same SKU.
7. Treat quiet hours separately—Miss at 23:00 may need morning send with rewritten copy.

Truthful Leadara mapping

With Leadara journeys, waits, branches/conditions, segments, and email/SMS you can:

• Wait until a specific date/time for flash paths;
• Approximate Drop by gating entry with “still before window end”;
• Approximate Window-Miss with a time/timeout branch plus alternate SMS/email;
• Use weekday-oriented delays for weekly series—not one-shot exact dates.

If a competitor labels “On Window Miss” and Leadara does not, stay honest: combine time conditions + branch + alternate copy.

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

When to Drop vs Window-Miss

Common mistakes

• Treating past-dated exit (already in Wait) as late-entry drop (arriving late to Wait);
• Next-slot on a one-shot flash;
• Window-Miss reusing “last chance” copy after the window died;
• No QA for 18:10 arrivals;
• Mixing quiet hours with sale-window logic.

FAQ

What’s the difference between past-dated exit and late entry to a calendar wait?

Past-dated: you were already inside the delay when the date passed. Late entry: you reach the Wait step after the deadline. Both are “late,” different entry points.

Should flash-sale journeys drop late arrivals or send “sale ended”?

If you have an honest alternate → Window-Miss. If there’s nothing to say → Drop. Never send a burned code.

How do I design a Window-Miss path?

Time/timeout check → alternate branch → honest copy → separate metric → late-arrival QA. Product label aside, that’s the logic.

Is next occurrence the same as Window-Miss?

No. Next occurrence waits for the next slot; Window-Miss deliberately takes another path without promising the same slot.

Timezone?

Lock Tehran for Iran campaigns. UTC drift causes false drops.

What if enrollment happens after the whole sale ended?

They should never enter the “last chance” journey—close the entry segment.

Does Leadara Live Chat explain this?

Live Chat is human support; AI Chat is an internal dashboard assistant.

PM one-liner?

“Late to a calendar Wait: either silent Drop or an honest Window-Miss branch—no blind next-slot for flash.”

Next step

For your next sale or Yalda window, lock the end hour in the brief, build a profile 10 minutes late, and decide Drop vs Miss with alternate copy. Then align with inventory.

Sale-window checklist

1. What is the end hour in Tehran time?
2. How long is the code/stock alive?
3. What should late arrivals receive (or nothing)?
4. Is Miss success metric separate?
5. Did on-time / late / next-day QA pass?
6. Does entry segment close after the window?

Align with media

If Instagram ads run until 19:00 but Wait ends at 18:00, either cut the ads or make Window-Miss match media reality.

Success metrics

• Late-entry / total entrants;
• Miss sends vs Drop rate;
• “Code didn’t work” tickets after end hour (near zero).

Yalda scenario with two windows

Many stores run two slots: “sale starts 20:00” and “special stock ends 24:00.” Decide per calendar Wait:

1. Late to the start reminder → often Window-Miss with “sale already live, code still valid” if the code is alive;
2. Late to the end reminder → Drop or Miss with a non-special offer;
3. Never put a weekly next-slot on a Yalda stock-end.

That two-line brief prevents contradictory copy.

Acceptance test with three timed profiles

If all three profiles behave the same, you do not have a real Window-Miss—only one path.

Related reading

• Past-dated calendar delay exit vs wait for next occurrence: leave the journey vs hold until the next valid slot
• Wait until a date property vs relative duration: birthday/renewal day vs 'wait 3 days'
• Delay-until-weekday vs fixed N-days: send only Mon/Wed/Fri vs always wait exactly 2×24h