Morning: escalations first
The illustrative day begins when the store's support lead opens the Today tab. The morning brief puts escalations at the top: a delivered-but-not-received claim above the goodwill limit, and a customer whose message mentions a chargeback. Each escalation carries the thread, the order, the carrier's delivery scan, the policy excerpt that applies, the Order Support FTE's one-paragraph summary of what the customer wants, and a suggested resolution. Below the escalations, yesterday in one line: tickets resolved inside policy, exchanges chosen versus refunds, and no limits crossed.
The lead reads the chargeback case first, because the always-escalate list put it there. With everything in front of them, the decision takes a few minutes, and the mark they leave, correctly escalated, feeds the month's escalation accuracy.
Mid-morning: routine replies from the carrier scan
In the Queue tab, the overnight where-is-my-order tickets are already answered, because routine order-status replies earned autonomy last month. The lead spot-checks a few. Each states the carrier, the last scan with its time and place, the delivery estimate, and the store's late-parcel rule for the cases where the estimate has passed, with the tracking link. None says the parcel is on its way and nothing else. Each reply has the order and the scan attached in the ticket history, so anyone taking over sees what the FTE saw.
Two tickets were not answered: their tracking showed no scan at all since the label printed. The FTE escalated those to the fulfillment team with a note, because a missing first scan is a warehouse question, not a customer reply.
Midday: an exchange before a refund
In Approvals, a return request waits, because returns are still gated. The customer wants a refund on a jacket that does not fit. The Order Support FTE has checked the delivery date against the window, confirmed the category allows exchanges, and drafted a reply that offers the next size with the replacement shipping now, states plainly that a refund is available instead if they prefer, and gives the return label either way. The draft uses the returns wording from the policy page verbatim, which was a remit rule from a send-back weeks ago.
The lead approves. Whatever the customer chooses will be logged on the ticket, and the exchanges-versus-refunds number in the review will be a count, not a guess.
Afternoon: a claim above the limit
The delivered-but-not-received claim from the brief is next. The order value exceeds the goodwill limit the owner set, and the FTE has not resolved it; it has assembled the case. The carrier scan shows delivered at the front door with a photo; the customer says nothing arrived; the address has no previous claims; the store's rule for this case asks the customer to check with neighbours and the carrier for two days before a replacement. The suggested resolution follows the rule. The lead accepts it, and the FTE sends the reply the lead approved.
Nothing about the case asked the lead to reconstruct anything. The rule, the evidence and the suggestion were on one screen because the limit made it a person's decision.
Late afternoon: a spike, tagged
The brief had also flagged a signal: damaged-item claims on one product rose sharply over the last two days, all from orders shipped through one carrier lane. The Order Support FTE has not explained it away and has not declared a cause. It has tagged the claims, shown the product and the lane they share, listed what it can see, the claims and photos, and what it cannot, the warehouse's packaging change log, and proposed two actions: hold the product's shipments on that lane pending a packaging check, and pre-approve replacements for the claims already open, since each is inside the limit.
The lead approves both and forwards the packaging question to operations. The tag will show in the monthly review whether the spike ended when the packaging changed.
Evening: the log
At the end of the illustrative day the Performance tab shows what happened: the two escalations decided and marked, the routine replies sent under the autonomy the lead granted, the two warehouse escalations, the exchange offered, the claim resolved by the lead's decision, the spike and its two actions, each with the person who decided and the evidence attached. First-reply time for the day sits against the target.
Nothing in the day asked the lead to trust a system. It asked them to decide two cases with everything in front of them, approve one exchange, and approve two actions on a spike. The record exists already, which is what an audit trail means when it is built in.