← Notes

Honesty about absence is an exit, not an excuse

The advice to own the failure and offer an escape hatch applies just as well when the limit is availability rather than comprehension — and there the exit has to be a path that does not depend on waiting.

Usability guidance for chatbots addresses the limit of comprehension. The Nielsen Norman Group recommends: "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". The principle carries over, with one adjustment, to the limit of availability.

The first half tends to be met already: saying the team will be paged and is not present right now is honesty about the limit. The second half is the one that goes missing, because the recommended exit — talk to a person — is exactly what is unavailable at that moment.

The exit, in that case, has to be something else: a concrete time when someone answers, a booking the visitor makes on their own, an asynchronous channel where the message is recorded, or a commitment to reply within a stated window. What these options share is giving the visitor something to do that is not waiting without a forecast.

There is a side benefit. A flow that offers booking instead of generic collection needs less data — a date, a time and a contact — and therefore suffers less from re-asking. The better exit is also the simpler one to implement correctly.