In dormant-user sequences, the send-time window often explains more of the difference in reactivation than the subject line or offer. That is counterintuitive because copy is the most visible part of a campaign, and it is usually the first thing we test. But a well-written message sent while a customer is unlikely to check email still has a narrow chance of doing its job.
Re-engagement is partly a message problem and partly a timing problem. For small DTC and SaaS teams, the timing question is often easier to improve than the copy. Before rewriting a subject line for the fourth time, look at when each dormant customer has historically opened, clicked, logged in, or purchased. Those signals can tell you when a send is more likely to be noticed.
Set the dormancy threshold before choosing the send
A re-engagement flow should start with a clear definition of dormancy. “Inactive” is not a useful segment on its own. A customer who has not opened an email in 30 days may still be visiting your store every week. A SaaS user who has not logged in for 21 days may be genuinely at risk, while an annual-plan customer may have a naturally lower usage frequency.
Choose a threshold that reflects the product’s normal behavior and the signal you are trying to recover. For example:
- A DTC brand might enter customers into a re-engagement audience after 60 days without a purchase, provided they have not browsed or added to cart recently.
- A SaaS company might use 30 or 45 days without a login for monthly active users, while excluding accounts with a pending renewal or an open support issue.
- A subscription business might define dormancy through a combination of skipped sessions, unopened messages, and declining product usage.
The threshold should also prevent unnecessary contact. If someone is still active through another channel, an email that says “we miss you” can feel inaccurate. Build the audience from behavioral events, not just from the absence of an email open.
Find the individual send-time window
Once a user qualifies, the next question is not simply whether Tuesday performs better than Friday. It is when this particular person tends to engage. Some customers open messages during a morning commute. Others respond after work, or on a weekend when they have more time to shop or explore a product.
For each person, examine recent engagement signals and look for a repeatable window. Useful inputs include email opens and clicks, site sessions, app activity, purchases, product usage, and the time zone associated with the customer. You do not need a perfect prediction. A practical window, such as Tuesday between 8:00 and 10:00 local time, is more useful than a universal send at 9:00 for everyone.
Day-of-week effects still matter. A B2B product may see stronger weekday engagement, while a consumer brand may see more browsing on Saturday or Sunday. But the average for the segment can hide meaningful individual differences. Treat day of week as one input, not as the final answer.
In Braze or Klaviyo, the flow can hold a qualified user until the next suitable window, subject to a maximum delay. That cap matters. A campaign should not wait six days for a theoretically perfect moment if the customer’s intent is already fading. Set a reasonable delivery range, then use the person’s history to select the best available time inside it.
A synthetic example: a 60-day lapsed SaaS user
Consider a fictional project-management SaaS with a large base of monthly users. The team defines dormancy as 60 days without a login, while excluding users who have canceled, opened a support case, or changed billing status.
The first message in the flow reminds the user what they had been doing in the product and offers a direct path back to their workspace. Instead of sending it immediately when the user reaches day 60, the team checks the user’s prior activity. One customer historically logged in between 7:00 and 9:00 on weekday mornings. Another tended to use the product after 18:00 on Tuesdays and Thursdays.
Both users receive the same campaign family, but at different times. The first customer gets the message on the next weekday morning. The second receives it on Thursday evening. If neither engages, the flow waits several days before sending a second message, again using the available behavioral window rather than a single campaign-wide schedule.
The team also creates a control group that receives the same messages at a fixed time. This is important. Without a control, a lift in reactivation could come from a stronger offer, a seasonal change, or simple variation in the audience. Compare reactivation, not just opens, and keep the test long enough to account for delayed logins.
Where subject lines fit
Subject line optimization is not wasted. It matters more after timing is sorted. If a message reaches the customer during a likely engagement window, the subject line can determine whether they open it. Clarity, specificity, and a credible reason to return still matter.
For a dormant SaaS user, “Your workspace is waiting” may be less useful than “Pick up your project where you left off.” For a DTC customer, a concrete reminder of a product category or replenishment need may outperform a vague “We miss you.” Test one meaningful difference at a time, such as the benefit, the degree of urgency, or the level of personalization.
Do not judge subject lines only by open rate. Privacy changes and inconsistent tracking can make opens noisy. Track clicks, sessions, completed purchases, renewed subscriptions, or meaningful product actions. A subject line that produces more opens but fewer downstream actions is not necessarily the winner.
Timing is a layer, not the whole strategy
Timing alone is not sufficient. A customer may receive a message at exactly the right moment and still ignore it because the content is irrelevant, the offer is weak, or the return path is confusing. Timing buys you the open, but the content has to close.
Keep the re-engagement path focused. Explain why the customer is receiving the message, show a relevant next action, and make the destination work well on the device where the customer is likely to respond. Suppress people who have converted through another channel, and stop the sequence when the customer returns to an active state.
For a small team, the practical order of operations is straightforward: define a sensible dormancy threshold, exclude people who are still active, identify each customer’s likely engagement window, and compare personalized timing with a fixed schedule. After that baseline is working, test subject lines, offers, creative, and sequence length.
Zalera adds a per-person decision layer on top of Braze and Klaviyo, selecting the message variant and send time for each customer from their behavioral signals. The useful starting point is not the cleverest subject line. It is the moment when the right customer is most likely to pay attention.