Morning: the brief and the held-back sends
The illustrative day begins when the store's marketing lead opens the Today tab. The morning brief lists what is waiting: a proposed retiming of the replenishment flow for the store's best-selling consumable, and a new welcome-series draft. Below that, yesterday in one line: which flows sent, how many messages went out against the frequency cap, and how many were held back because a scheduled campaign collided with a flow for part of a segment. Spend against budget sits in the corner.
The lead reads the held-back count first. The brief explains it in a sentence: the contacts who received a post-purchase message yesterday were excluded from the campaign to keep them under the cap, and they will receive the campaign tomorrow if the cap allows. No one had to remember a setting.
Mid-morning: a retiming in Approvals
In Approvals, the replenishment proposal shows the current send interval beside what the order data says: the median gap between first and second orders of that product has shortened since the flow was built, so the reminder now lands after most repeat orders have already happened. The proposal moves the send earlier, shows the message exactly as it renders on a phone, shows the segment size with subscribers excluded, and confirms the cap and suppression list are applied.
The lead approves. A second proposal, the welcome series, comes back with one edit: the third message mentions a discount the lead does not want first-time buyers to expect, and the remit rule now says so. The Retention FTE will apply that rule to every future draft.
Midday: a signal, not an alarm
The brief carried a signal the lead returns to after lunch: the sending platform reported a small deliverability warning on one domain after yesterday's campaign. The Retention FTE has not raised it as an emergency. It has listed what it can see, the warning, the campaign it followed, the segment it went to, and what it cannot see, the mail provider's reasons, and it has proposed a cautious action: hold the next campaign to that domain's contacts for a day and watch the flows' placement.
The lead approves the hold. The alternative hypotheses stay attached to the signal with their evidence, not discarded and not asserted.
Afternoon: a segment change and a holdout
In the Segments tab the lead reviews a proposed change to the VIP definition. The Retention FTE has noticed from order data that a group of customers with fewer orders but far higher order value sits outside the current VIP tier, and it proposes widening the definition, showing how many customers would move and what messages they would begin to receive. It also proposes a holdout on the VIP flow itself, so that next quarter's review can say whether VIP treatment changes anything rather than assume it does.
The lead approves both. The holdout size appears beside the flow from now on, and the report will show it next to every VIP result.
Late afternoon: a diagnostic question
The lead asks a question in Missions: why did the second-order rate for last season's cohort fall? The Retention FTE returns ranked hypotheses with evidence rather than an answer: a post-purchase flow was paused for a fortnight during a platform migration; a product in that cohort's first orders had a delivery problem the help desk logged; the cohort skewed toward a discount-led acquisition campaign. Each hypothesis carries what the FTE can see and what it cannot.
The lead picks the paused flow to investigate first and asks for a proposal to prevent a pause from going unnoticed. The other hypotheses stay in the mission.
Evening: the log
At the end of the illustrative day the Performance tab shows what happened: the retiming approved, the welcome edit and its new remit rule, the domain hold, the VIP change, the holdout, and the mission opened, each with the person who decided and the evidence attached. Sends against the cap for the day are shown, with the held-back count and where those contacts go tomorrow.
Nothing in the day asked the lead to trust a system. It asked them to approve evidence, refuse one discount mention, and hold one domain for a day. The record exists already, which is what an audit trail means when it is built in.