← Notes

Business hours are necessary and not sufficient

Declaring a window settles the expectation; keeping the promise inside it requires someone on call, and a lead response survey found that nearly one in five companies did not respond at all.

Declaring business hours is the most obvious correction for a channel that promises a human and does not deliver. It solves half the problem: it aligns the expectation of whoever arrives outside the window.

The other half is what happens inside the window. A lead response time survey found that "Nearly 1 in 5 companies didn't respond by email altogether" — it is not about being slow, it is about never replying, in organisations with a team. A declared window does not, on its own, produce the capacity to serve inside it.

Usability guidance completes the picture on the interface side: "Be honest about not understanding. Offer an escape hatch in the form of a real human, a phone number, or a link to a different interaction channel". Every recommended exit ends in someone who answers, which means the interface design is betting on an operation existing.

What remains as practical advice for anyone without someone on call is to invert the order of the design: start from the real capacity to reply and build the promise on top of it, instead of starting from the desirable promise. A narrow window that is kept is worth more than a wide one that is not, and an honest asynchronous path is worth more than a button suggesting immediacy.