Five hands are already raised.
Most email calendars get built from the wrong question. The team sits down, asks “what can we send this week?”, and works forward from a blank page. That’s how you end up with a promo cadence nobody asked for and open rates that sag a little more each month.
The better question is the one a good teacher asks a classroom: whose hand is already up?
Because your customers are raising hands constantly. They ask when a product comes back. They check date labels. They reorder on a rhythm you could set a clock to. They email when something’s wrong and wait to see what you do. Every one of those is a hand in the air, and every one maps to an email that answers it. Here are the five I build first in almost every account, before any campaign calendar exists.
1. The back-in-stock alert
The raised hand: “When is this coming back?” In any active product community, this is the most common unanswered question. People describe checking a site daily for a restock. That’s purchase intent with nowhere to go.
The email: the moment it’s back, tell exactly the people who asked. Nothing else. No persuasion is needed because the persuasion happened before you sent anything.
The mechanics: in Klaviyo, the native back-in-stock trigger fires on the Subscribed to Back in Stock event from your storefront’s notify-me button. For product launches and drops rather than restocks, a “notify me” signup property plus a targeted campaign does the same job. In the accounts I run, this is routinely the best-performing email in the entire program, and it’s usually the one that didn’t exist before the audit.
2. Batch and freshness transparency
The raised hand: customers photograph date labels. Roast dates on coffee, batch codes on supplements, packaged-on dates in other categories I work in — buyers track details the brand never mentions, and they compare notes on which batches were best.
The email: put the detail in first. A post-purchase message that says what batch this was, when it was made, and what to expect reads as confidence. The brand that names its dates is the brand with nothing to hide, and customers in date-conscious categories reward it disproportionately.
The mechanics: custom catalog fields or order-item properties carry the data; the post-purchase flow renders it. If your fulfilment system knows the batch, Klaviyo can say it. Most brands already have this data and ship it in silence.
3. Service recovery
The raised hand: the quietest one, and the most expensive to miss. The customer whose order arrived wrong emails you once. What happens next decides whether the story they tell in public is “they made it right” or a screenshot of your auto-reply. I covered the two branches of that fork in the room piece; the short version is that the defect is identical in both branches, and the outcome is decided entirely by response speed.
The email: a plain-text note after delivery — “did everything arrive the way it should?” — sent from a real reply-to that a human reads. Its job is to catch the problem while it’s still a private conversation.
The mechanics: trigger on the delivery event from your shipping integration, delay a day, send plain text. Route replies somewhere with an owner and a same-day expectation. This flow’s revenue never shows in attribution, which is why nobody builds it. It shows up in the reviews you didn’t get.
4. Replenishment on their rhythm
The raised hand: it’s in your order history. Consumable products get rebought on personal cycles — some customers every three weeks, some every two months. The rhythm is real and measurable, and a calendar blast ignores it completely.
The email: arrive just before they’d reorder anyway. Not “it’s Friday, here’s 15% off” — rather “you’re probably running low.” One reads as marketing. The other reads as memory.
The mechanics: Klaviyo’s predictive analytics gives you expected date of next order on every profile with enough history; a flow triggered off it, or time-since-last-order splits for thinner data, covers the rest. The win isn’t the send. It’s that the send lands inside the window where reordering was already the plan.
5. Winback without a discount
The raised hand: lapsed customers had a reason. The product changed, something disappointed, they found an alternative, life moved. A percentage off answers none of those. Leading your winback with a discount also teaches the lesson you least want to teach: leaving is how you get a better price.
The email: say what’s changed since they left. New products, a fixed problem, a restock of the thing they actually used to buy. Or simply ask — one plain question to a written-off segment once brought back 266 replies in an account I run, from people everyone assumed were gone.
The mechanics: a winback flow with conditional splits on what they used to buy, informational sends first, the discount held back as the last card in the sequence rather than the first. If the discount is doing all the work, the flow isn’t a winback, it’s a markdown.
Why these five come before the campaign calendar
Campaigns interrupt. These five answer. That’s the entire difference, and it’s why they behave differently in every metric that matters: they get opened because the recipient was waiting, they don’t burn list goodwill, and they keep working every week without anyone writing new copy.
They also compound. The back-in-stock alert grows the list of people who tell you what they want. The delivery check-in catches problems that would have become churn. The replenishment flow quietly becomes the biggest line in flow revenue. And none of them trained your list to shop only on discount weekends.
The take
Before the next brainstorm about what to send, count the hands already up in your account: the notify-me clicks with no flow behind them, the batch data shipping in silence, the support emails answered in two days, the reorder rhythms nobody measured, the lapsed segment that only ever hears “15% off.” Build the five answers first. The calendar can have whatever’s left.