The delivery question is 41% of your inbox

Before Porchlight had a name, we asked furniture brands to let us read their support inboxes. Not a sample, the whole thing: twelve months of email and chat from 212 brands, from a two-person sofa company in Asheville to a dining brand with its own fleet of trucks. We tagged every thread by hand for the first four thousand, then by rule for the rest.

One question beat every other one by a wide margin. Some version of where is my order made up 41% of all first messages. Damage claims were 14%. Returns, 11%. Product questions, the thing most chat widgets are built to answer, came in at 9%.

Why it is so hard to answer

On paper the delivery question is easy. You look up the order, you look up the shipment, you tell the customer. In furniture it is almost never that clean, for three reasons.

• The order and the shipment live in different systems. The storefront knows what was bought. The order system knows when it was built. The carrier knows where the truck is, and the white-glove carrier knows something different again: which crew, which day, which two-hour window.
• Freight scans are written for dispatchers. “Arrived at terminal, linehaul pending” is accurate. It is also useless to someone who wants to know whether to take Thursday afternoon off.
• The real answer is often a window, not a date. A sofa is not dropped at the door. Somebody has to be home, and the crew calls ahead. Customers are not asking where the box is; they are asking how to plan their week.

So agents do the translation by hand. In the inboxes we read, a good agent took four to six minutes per delivery question: open the order, find the shipment, open the carrier portal, read the scans, check the delivery policy, write the reply. Multiply by 41% of the inbox and you have most of a team’s week.

What a good answer contains

We pulled the 300 delivery replies that customers rated highest and looked for what they had in common. Every one of them did four things:

1. Answered yes or no first. “It is still coming Thursday.”
2. Said where the order is in words a person uses. “It left the Denver hub this morning.”
3. Gave the window and how they would be told. “The crew will text you 30 minutes before they arrive.”
4. Stopped. No tracking number, no link to the carrier, no “let us know if you have other questions.”

That last one surprised us. The replies that pasted a tracking link scored lower than the ones that did not, because the link sent the customer to the same dispatcher language the agent had just translated.

What we built from it

Porchlight reads your order system and your carriers’ feeds every five minutes, so when the question comes in, the answer already exists. It writes the reply in the four-part shape above, in your voice, and shows the agent (or the customer, once you trust it) exactly which records it came from.

When a carrier has gone quiet for longer than your policy allows, it does not guess. It shares the last confirmed scan, says so plainly, and hands the thread to a person with the gap already flagged.

What it frees up

At Loamwood, the first brand to run Porchlight on its whole inbox, the median first reply to a delivery question went from 19 hours to 38 seconds. That is the number people quote. The one their director of customer experience quotes is different: her team now spends Tuesday mornings on the eleven damage claims that came in over the weekend, instead of the two hundred “is it still coming” emails in front of them.

The delivery question will always be most of your inbox. It does not have to be most of your team’s day.