← All articlesAutomations

Email automation timing: choose delays that fit the customer

4 min read

Email automation timing begins with the event that starts the clock. A reminder one day after signup means something different from one day after fulfillment or the previous message. Choose delays around the customer's decision, then check for purchases, opt-outs, or other changes during the wait. A schedule copied from another store is only a hypothesis.

Start with the decision being made

A simple refill may require little consideration, while a high-value purchase may involve measurements, consultation, or budgeting. Use support conversations and purchase patterns to estimate how long the decision usually takes.

Choose a starting delay for the Sendvio automation and write down why it seems reasonable. This turns timing into a testable hypothesis. Avoid presenting the first setting as a proven best practice when you have not observed your own audience yet.

Identify exactly when the clock starts

A delay measured from order creation is different from one measured from fulfilment or a later qualifying event. Before choosing a number of hours or days, write down the event the automation actually uses. A good delay attached to the wrong event still produces a poorly timed message.

For a care guide, an order-based delay should allow for the fact that the item may not have arrived. For checkout recovery, allow for ordinary completion before assuming a reminder is needed. For replenishment, the relevant interval depends on the product and quantity. These are different clocks, so copying one delay across all journeys is unlikely to preserve the intended meaning.

Also inspect re-entry behaviour and recent events. If a customer qualifies again, determine whether the existing wait continues, another journey begins, or a condition prevents duplication. Test the supported configuration rather than relying on the visual position of a delay block to explain the whole timing model.

Check what can happen while they wait

A customer may purchase, unsubscribe, or become ineligible during the delay. Review the conditions before the next message rather than assuming the initial state remains true. Also inspect whether a campaign or another automation may reach them first.

For a checkout reminder, a later follow-up should add useful information, not merely repeat the original message with louder urgency. If there is nothing new to say, a longer delay or one fewer message may improve the experience more than another subject-line variation.

Compare timing with equal opportunity to act

Suppose you compare an earlier reminder with a later one. If you stop measurement at the same short deadline after entry, the earlier group may have had more time after the message to purchase. Choose an observation period that gives both approaches a fair opportunity while still matching the business question.

Keep the audience selection, offer, content, and channel treatment comparable. Record orders per eligible entrant and negative responses over the full journey. If the earlier group buys sooner but both groups eventually purchase at a similar rate, you may have changed timing rather than the total number of buyers. That distinction matters when deciding whether another interruption is justified.

Compare timing fairly

Keep the offer, creative, and audience criteria comparable when evaluating a timing change. Review orders per eligible entrant, negative feedback, and the full sequence rather than one message's open rate.

Allow enough time for the buying cycle to play out. A faster click is not always a better purchase outcome. Save the result and revisit timing when the product mix, delivery expectations, or audience changes. A useful delay reflects the customer's situation, not a permanent number inherited from a template.

Do not let a delay hide an expired promise. A customer can wait past a sale's end, a shipping cutoff, or a product sellout. Check time-sensitive conditions before the send step and ensure the content remains accurate when the message actually leaves, not only when the person entered the automation.

Document the reason for the chosen delay next to the rule. “Enough time to use the guide before a follow-up” is a useful rationale; “the template had three days” is not. Revisit it when fulfilment times, product usage, or buying behaviour changes. Timing becomes manageable when every wait has a customer purpose and a clear way to tell whether that purpose is being met.

Put it into practice

Explore automation timing