The forwarded-email problem
The most common escalation in ecommerce is an email chain forwarded upward with the words "can you take a look at this". It fails for a specific reason: the person receiving it now has to reconstruct the situation before they can make a decision, and reconstruction is the expensive part.
A good escalation is not a longer message. It is a message that contains the four things a decision needs.
1. The decision you are asking for
Lead with it. "I want to approve a refund outside our window" is an escalation. "This customer is upset" is a status update wearing an escalation's clothes.
If you do not know what decision you want, you are not escalating, you are sharing, and that belongs in the channel, not in someone's direct notifications.
2. What you already tried
Two lines. This prevents the single most demoralising response in support, which is being told to do the thing you did an hour ago. It also tells the decider how much runway is left.
3. The context that changes the answer
Not all of it. The parts that would change the decision:
- How much this customer has spent, and how often. A first-time buyer and a fourteen-order regular are not the same question.
- Whether this has happened to them before.
- Whether it is happening to other people right now, which turns one refund into a pattern worth investigating.
- What it costs to say yes.
4. Your recommendation
This is the one people leave out, usually out of politeness. Say what you would do. The person above you is nearly always going to agree, and when they do not, the disagreement is where the useful conversation is.
An escalation without a recommendation asks someone else to do your thinking. An escalation with one asks them to check it.
The shape it ends up being
"Asking to approve a $178 refund four days outside our window. I offered store credit, they declined. Six prior orders, no returns, first complaint. Cost to say yes is $178 and about ten minutes; cost to say no is probably the customer. I would approve it."
Four sentences. The decision takes about fifteen seconds, which is the entire point.
Why the tool matters here
All four of these are easier when the order, the customer history, and the previous threads are already attached to the conversation instead of living in three systems. That is most of what we built Store Huddle to do: not to make people write better escalations, but to make the context free so they can.