Reschedule Logic

4 min read

Also known as: Smart Scheduling, Adaptive Cadence, Send-Time Optimization

Rules that automatically delay or shift sequence steps based on conditions like OOO replies, recipient time zones, or business-hour preferences.

Definition

Reschedule logic is the set of rules in a sequence platform that automatically adjusts when steps fire based on external conditions — out-of-office replies (pause until return), recipient time zones (deliver during recipient business hours), declared blackout dates (avoid weekends, holidays, specific dates), or contact-level preferences ('contact prefers morning delivery').

The goal is to deliver each step at the moment most likely to produce engagement, not at the moment most convenient for the sender. A perfectly-timed Step 3 that lands in the recipient's inbox at 9 AM their local time on a workday outperforms a Step 3 that lands at 3 AM their time on a Saturday — even if the content is identical.

Reschedule logic operates at multiple levels: platform-wide defaults (no sends on Saturdays/Sundays), sequence-level rules (this sequence skips holidays), step-level overrides (this specific step always sends at 9 AM recipient time), and contact-level adjustments (this contact's time zone is Asia/Tokyo).

Why It Matters

Smart reschedule logic can lift response rates 30-50% with no content changes. The difference between delivering at the right time versus the wrong time is enormous — recipients ignore (or worse, mark as spam) emails that arrive at clearly-bad moments. Reschedule logic ensures the platform respects recipient context.

The biggest mistake is treating sequence cadence as fixed — Day 1, Day 3, Day 5 regardless of who or when. Recipients in different time zones, different industries, and different roles have different optimal send times. Reschedule logic adapts cadence to context.

Examples in Practice

A SaaS team's reschedule logic delivers all sequence emails between 9 AM and 11 AM in the recipient's local time zone. A contact in Tokyo receives Step 2 at 9 AM JST on Tuesday; a contact in LA receives the same step at 9 AM PST on Tuesday. Same sequence, different absolute times, optimal engagement for each.

An outbound team configures reschedule logic to skip US federal holidays. The sequence pauses on Memorial Day, Independence Day, Thanksgiving, and Christmas. Steps scheduled for those dates shift to the next business day. The simple rule prevents tone-deaf send-during-holiday awkwardness.

A B2B agency builds advanced reschedule logic that pauses sequences during the contact's known vacation period (extracted from previous OOO replies). When a contact returns from vacation, the sequence resumes with a tailored 'welcome back' opener. Reply rate on the welcome-back step is 4x higher than the same step sent without context.

Frequently Asked Questions

What is reschedule logic?

Rules that automatically delay or shift sequence steps based on conditions — OOO replies, recipient time zones, blackout dates, contact preferences. The goal is to deliver each step at the moment most likely to produce engagement.

What conditions trigger rescheduling?

Common triggers: OOO replies (pause until return), recipient time zone (deliver during business hours), holidays/weekends (skip non-business days), declared blackout dates, contact-level preferences, and platform-detected high-engagement windows.

How much lift can smart scheduling produce?

30-50% lift in response rates is typical for sequences moving from fixed cadence to time-zone-aware, OOO-respecting scheduling. The exact lift depends on how scattered your audience is geographically and how often recipients are away.

Should I send only during business hours?

For B2B email, typically yes — 9 AM to 11 AM in recipient time zone is the sweet spot. For B2C, send-time depends on category; consumer subscription apps often see best engagement evenings and weekends. Test for your category.

How does reschedule logic handle missing time-zone data?

Falls back to platform defaults — usually the sender's time zone or a configured default. Best practice is to enrich contact records with time-zone data from third-party providers or from IP-based inference at signup, so the fallback is rarely needed.

Can reschedule logic differ per sequence?

Yes — most platforms allow per-sequence configuration. A high-velocity outbound cadence might allow weekend sends; a thoughtful nurture sequence might skip weekends and holidays. Match the rules to the sequence intent.

What happens if reschedule logic conflicts with cadence timing?

Reschedule wins — the step delays until the conditions allow delivery. This can stretch a 'Day 1, Day 3, Day 5' sequence into 'Day 1, Day 4 (Day 3 was a holiday), Day 7' if conditions delay each step. Most platforms maintain the relative spacing while shifting absolute dates.

Does reschedule logic respect contact-level preferences?

Mature platforms support contact-level overrides: a contact who's told you they prefer morning delivery gets morning delivery regardless of platform defaults. A contact who's marked unavailable until a specific date gets paused until then. Preferences should override defaults when set.

The AMW Suite