Sending after a long pause: revalidate the mailbox and the audience

Define the decision

During a pause, tokens can expire, employees can change roles and queued steps can become stale. A campaign that was sensible months ago may now send an outdated offer or an unexpected follow-up.

Work through the procedure

1. Retest sending and receiving access before resuming.
2. Review the age and relevance of each intended cohort.
3. Inspect queued sequence steps, dates and references to earlier conversations.
4. Verify suppression and capacity, then restart a small reviewed segment with active monitoring.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Paused sequence says: "following up on next week’s event"
Event is now past
Correct action: review or replace the sequence before resuming
Separate check: the mailbox still receives a controlled reply

Read the result

The stale-message check is independent of connection health. A perfectly connected mailbox can still send inappropriate follow-ups if the content and schedule are not reviewed.

Check before moving on

1. Confirm no old enrollment becomes immediately eligible unexpectedly.
2. Reassign reply ownership if team members changed.

Limits and next action

Do not erase prior opt-outs or negative responses during the restart. Mailbox age and previous performance do not guarantee that the current audience or provider conditions are unchanged.

Source: Zintara sequence restart context