Multichannel Cadences Across Holidays: Pause Without Losing the Next Step
TL;DR: Pause a multichannel cadence by preserving each prospect’s next action, owner and current state. Sales managers should configure local email exclusions, review manual call and LinkedIn tasks separately, and inspect the resumed queue. A holiday pause should change timing without erasing history, duplicating outreach or restarting a conversation that already moved forward.
What should a holiday pause preserve?
Preserve the relationship state and the next unfinished action. Before changing dates, identify who owns the account, what the prospect last received and what the rep is expected to do next. A calendar change should not quietly turn an active conversation back into a cold sequence.
Treat this as a proposed operating procedure for your team. The relevant holidays, working days and exceptions depend on the prospect population and your own coverage. Avoid a single global blackout period that assumes every region or account follows the same calendar.
Separate prospect availability from rep availability. A prospect can be working while the assigned rep is away, or the rep can be available during the prospect’s local holiday. Decide whether each case needs deferred outreach, an owner handoff or a relationship-specific follow-up.
| Channel or state | What to review | What to preserve |
|---|---|---|
| Automatic email | Send schedule, timezone and excluded dates | Unsent message and enrollment context |
| Phone-call task | Due date, assignee and local calling context | Call objective and pending outcome |
| LinkedIn or other manual action | Task instructions and whether the action already happened | Accurate completion state and next action |
| Active reply or meeting | Conversation owner and agreed follow-up | The prospect’s actual request |
| Paused enrollment | Pause reason and resumption owner | Completed steps and remaining sequence context |
How do Unify send schedules handle holidays?
Use send schedules to define when automatic emails can send. A schedule combines a timezone with permitted days and hours. You can skip the US holidays listed in the editor and add custom skip dates that apply once or repeat annually.
A ready email outside the permitted window waits for an eligible time. Mailbox sending limits still affect when it can actually send. Review the resulting schedule for the affected cohort instead of assuming that a holiday exclusion establishes the exact delivery time.
Changes to a schedule reschedule unsent emails for enrollments already in progress. If the schedule is shared, those edits affect the sequences and active enrollments using it. For a local exception, use a separate or duplicated schedule where appropriate rather than unintentionally changing unrelated outreach.
Keep a record of the intended cohort and why the schedule applies. A timezone is a timing setting, not proof of the prospect’s current location or holiday observance. Resolve uncertain geographic context before using it to make a specific local-calendar decision.
How should you handle calls and LinkedIn actions?
Review manual tasks independently from automatic email timing. A complete holiday plan needs the call queue and other action items to match the intended pause. Do not infer that an email skip date has changed every manual task or every rep’s worklist.
In Unify, phone-call and action-item sequence steps create manual work for the assigned rep. Completing or skipping a task advances the enrollment. Keep the task state accurate so rescheduling does not turn an unperformed action into completed work.
- Pending call: Preserve the reason for the call, assignee and appropriate next date
- Pending LinkedIn action: Check whether the rep already performed it before changing or completing the reminder
- Unassigned work: Resolve coverage before the team returns to a full queue
- Prospect response: Route the response to its owner and reassess the remaining cadence
- Promised follow-up: Honor the agreed conversation timing through a deliberate owner decision
A task can be administratively overdue without the rep being late to a valid prospect commitment. Keep the reason for the date change visible so a manager can distinguish planned holiday deferrals from missed follow-up. Do not clear the queue by marking unfinished tasks complete.
Use the team calling-task workflow to check assignment, due dates and the difference between recording activity and advancing the sequence. Holiday preparation is an application of that same ownership discipline.
When should you pause the sequence itself?
Pause the sequence when the intended hold applies to its active enrollments, and inspect the consequences before resuming. In Unify, sequence enrollment controls let you pause and resume the sequence while retaining enrollment context. Resumed work remains subject to schedules and sending limits.
Do not remove and recreate enrollments merely to express a temporary absence. First inspect the existing person, completed steps and next action. Rebuilding the workflow can make it harder to distinguish a resumed conversation from a new outreach motion.
If only part of the audience needs a pause, avoid a broad change until you understand its scope. Review which sequence or schedule is shared and which users are affected. Choose the narrowest supported control that represents the intended cohort, then verify that unaffected work retains its expected timing.
| Field | What to record |
|---|---|
| Affected cohort | The accounts or enrollments covered by the calendar decision |
| Reason | Prospect holiday, rep coverage or another explicit operational constraint |
| Control changed | The exact schedule or pause setting and its shared scope |
| Pending work | Unsent messages and open manual tasks requiring review |
| Operational owner | The person responsible for checking resumed execution |
| Relationship exceptions | Active conversations and promised follow-ups requiring owner decisions |
| Resumption evidence | Observed next dates, assigned tasks and unresolved blockers |
How do you resume without losing the next step?
Resume from the current relationship state, then inspect what the system and reps will do next. A pause ending on the calendar is not sufficient evidence that the right action is now queued. Review changes that happened while the cadence was paused.
- Inspect new context: Check replies, meetings, ownership changes and new exclusions for the held cohort
- Review pending messages: Confirm their relevance and the next allowed sending time
- Review manual tasks: Verify that each task still has a valid objective, assignee and due date
- Resolve blocked work: Investigate missing personalization, mailbox or other enrollment issues before increasing intake
- Confirm actual resumption: Inspect the intended next actions and retain unresolved cases for review
Avoid treating every overdue task as equally urgent. Preserve actual commitments first, then order the remaining work according to your team’s prospecting priorities. A task that no longer matches the account’s state should be revised or resolved deliberately instead of completed mechanically.
Check the manager’s view and the rep’s view. A schedule can look correct while a rep returns to an unowned or unclear manual queue. Have the operational owner confirm that the assignee can identify the next action without reconstructing the entire holiday decision.
How should the process differ by team?
Assign the holiday decision to the team that controls the affected workflow. Keep local knowledge close to the accounts while giving RevOps a clear view of shared configurations.
- Regional sales teams: Validate relevant local dates and account context before choosing schedules
- Central RevOps: Review shared schedules and the scope of any configuration change
- SDR managers: Resolve the manual-task backlog and make return-to-work priorities clear
- Account owners: Handle active conversations, promised follow-ups and exceptions to the standard cadence
If a holiday delay exposes missing qualification evidence, use an owned qualification review queue instead of releasing the account solely because the pause has ended. Timing and qualification are separate release conditions.
When should resumption be held?
Hold resumed work when the next action is ambiguous or the configuration affects the wrong audience. Give the owner a concrete resolution condition so a temporary pause does not become an invisible backlog.
| Condition | Hold decision | Release condition |
|---|---|---|
| Shared schedule affects unintended regions | Do not apply the broad change | The affected sequences and cohorts match the intended scope |
| Prospect replied during the pause | Review the conversation | Relationship owner sets the appropriate next action |
| Manual task marked complete without an action | Correct the record and inspect progression | Task and enrollment states reflect what actually happened |
| No rep owns the next task | Keep work assigned for resolution | A named assignee accepts the next action |
| Email is blocked after resumption | Investigate the enrollment | The blocking condition is resolved and next timing is inspected |
What should the team avoid?
Keep the holiday workflow understandable to the person who resumes it. Clear state and ownership matter more than making the task count look tidy.
- Do not assume a US holiday setting represents every local calendar
- Do not assume automatic email schedules control manual call or LinkedIn tasks
- Do not edit a shared schedule without checking its other sequences
- Do not mark unperformed actions complete to remove overdue work
- Do not restart an enrollment before reviewing its existing history and next step
To coordinate sequence timing and the work around it, sign up for Unify. Review the relevant schedule and manual queue together before the next holiday interruption.
Frequently asked questions
Can Unify skip holidays in an email sequence?
Yes. Send schedules support skipping the listed US holidays and adding custom skip dates that apply once or repeat annually. Configure the relevant schedule and verify the resulting unsent email dates for the affected enrollments.
Does an email send schedule also reschedule call and LinkedIn tasks?
Do not assume that. Unify send schedules govern automatic emails. Review phone-call and action-item tasks separately, including their owner, due date and completion state, before considering the entire multichannel cadence paused.
Should I remove and reenroll prospects after a holiday?
Use the appropriate pause or schedule control for a temporary interruption. Removing a person and creating another enrollment changes the workflow context and can conflict with reenrollment controls. Inspect the existing enrollment and next step before deciding that a new enrollment is necessary.
What if different regions observe different holidays?
Use region-appropriate schedules or deliberately scoped custom dates, and verify the prospect context used to select them. Avoid changing a shared schedule for a local exception without checking every sequence and active enrollment that uses it.
Does resuming a sequence send all overdue emails immediately?
Do not promise an immediate send. In Unify, the send schedule and mailbox limits still govern timing. Inspect the next scheduled messages and manual task backlog after resuming so the team knows what is actually due.
Who should own the return from a holiday pause?
Assign an operational owner for the affected cohort and preserve each relationship owner. The operational owner verifies schedule and task state; the relationship owner decides whether a reply, meeting or changed account context requires a different next action.
Glossary
- Send schedule: The timezone and permitted windows governing automatic email timing
- Skip date: A configured date on which automatic emails should not send
- Enrollment: A person’s progress through a sequence
- Manual action item: Assigned work that requires the rep to perform and resolve the task
- Resumption owner: The person responsible for checking that paused work returns to the correct next action
