← Notes

The escape hatch is part of the design, not an admission of defeat

Usability guidance for chatbots includes offering an explicit path to a human; what it does not resolve is what happens when that path is taken and nobody is on the other side.

The Nielsen Norman Group guidance on chatbots is direct about the exit: "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".

Two things follow. The first is that offering the button is a design success, not a confession that the bot is bad — the exit exists precisely so the bot's limits do not become a prison for the visitor. The second, less discussed, is that the recommendation describes three forms of exit: a person, a phone number and a different channel. All three share an implicit promise that someone answers.

That is where the pattern touches the operation. A talk-to-an-agent button is a promise made on behalf of a human capacity that has to exist at the moment the button is pressed. When it does not, the usability pattern is still followed on screen and broken in the experience: the visitor did exactly what the interface suggested and was left waiting.

The useful reading, then, is that the escape hatch is not an interface decision alone. It is the interface of an operational commitment, and the design is only complete when both sides exist — including in the form of honestly saying nobody is available right now, which is the grown-up version of the same advice.