Skip to content
allanninal.dev/build
Collaborate

Part 4 of 7 · Feedback follow-up router series ~5 min read

How the context gets attached

The ninety-second reply is only possible because everything somebody would have gone looking for is already on the screen. This post is about what those things are, and the surprising one is not the order.

Key takeaways

  • Five things: the order, what actually happened to it, open tickets, their history, and value.
  • What happened to the delivery matters more than the order itself.
  • Whether they have complained before changes what somebody writes, and it should.
  • Never show a customer lifetime value figure to the person replying.
  • Missing context is stated rather than left blank, so nothing is assumed.

The five

How context is gathered before a survey response reaches a personA vertical chain of five steps entered by a box labelled A routed response, with an order token. Step one fetches the order: what they bought and when, from the commerce system in one lookup. Step two fetches what happened to it: tracking, delays, and what we told them. Step three fetches open tickets, asking whether we are already talking to them, from the helpdesk by customer. Step four fetches their history: orders and prior scores. Step five presents one screen with nothing left to look up. A note says the second box is the one that most often contains the answer to the complaint.AWS ACCOUNTA routed responsewith an order tokenThe orderwhat they bought, whenCommerceone lookupWhat happened to ittracking, delays,what we told themOpen ticketsare we already talking?Helpdeskby customerTheir historyorders, and prior scoresOne screennothing to look upThe second box is the one that most often contains the answer to the complaint.
Fig 1. The five lookups that run before a person sees the response. The delivery history is the one that most often turns a complaint into an obvious apology.
  • Database
  • Analytics
  • Front-end & mobile
  • Outside AWS

What happened, not what was ordered

The order tells you what they bought. What happened to it — the carrier scans, the delay, whether a notification was sent — tells you whether their complaint is justified, and it usually is.

That distinction is what lets somebody write “you are right, it was two days late and we should have told you” in ninety seconds instead of writing something noncommittal because they do not know. And a noncommittal reply to a specific complaint is close to useless.

Are we already talking to them

The open-ticket check prevents the specific embarrassment of somebody sending a fresh “sorry to hear that, what happened?” to a customer who is already three messages into a conversation with a colleague about exactly this.

Where a ticket is open, the response is routed to whoever is handling it rather than to the rota, and it appears as an addition to that conversation rather than as a new one. That is a small piece of plumbing that prevents a genuinely annoying customer experience.

The context that is deliberately absent

The one piece of customer context deliberately not shownA horizontal row of five boxes. Order count: shown. Prior scores: shown. Open tickets: shown. Lifetime value: not shown. Why: it changes the reply. A note says showing a value figure produces better replies to richer customers, visibly.ONE THING THAT IS NOT ON THE SCREENOrder countshownPrior scoresshownOpen ticketsshownLifetime valuenot shownWhyit changes the replyShowing a value figure produces better replies to richer customers, visibly.
Fig 2. The context deliberately withheld from the person replying. Order count conveys loyalty without conveying a number that changes how somebody treats an individual.
  • Security & identity
  • Analytics
  • Front-end & mobile
  • People

This is a deliberate choice and it is worth defending. A person who can see that this customer has spent four thousand pounds and that one has spent forty will, entirely unconsciously, write a warmer reply to the first. Customers notice that over time, and the ones who notice are the ones who spent forty.

Order count conveys most of what is useful — a fourth-time customer is different from a first-time one — without attaching a figure that invites triage. It is a small restraint with a compounding effect.

Stating what is missing

Where a lookup fails or a system has nothing, the screen says so rather than showing a blank. “No tracking data available for this order” is different from an empty tracking section, and somebody writing a reply in ninety seconds will read an empty section as nothing happened.

Next: themes, and whether any of this changes anything.

All posts