The message that never got a reply

A customer asks a pre-purchase question on WhatsApp — sizing, stock, delivery timing — and doesn't hear back for six hours. Most of the time, they don't wait. They buy somewhere else, and nothing in your dashboard ever records that as a lost sale.

Why response time is a revenue metric, not a vanity one

Support teams often track response time as a service-quality number. On a channel like WhatsApp, where a meaningful share of messages are pre-purchase questions, it's closer to a conversion metric — every hour of delay is measurable drop-off, not just a slower support experience.

The compounding cost of being slow

The cost isn't linear. A reply within a minute catches someone still in a buying mindset; a reply six hours later catches them after they've already decided, one way or another. The value of a fast reply decays fast, which is exactly why automation on the first response matters more than automation anywhere else.

What to track instead of gut feel

Three numbers tell you most of what you need: median first-response time, percentage of conversations answered within your target window, and conversion rate by response-time bucket. That last one is usually the one that changes minds internally.