Hacker News Reader

Comment by nitrogen | Hacker News Reader

I absolutely detest most chat-based support. 60 seconds is way too long for an interactive medium. I'd rather be waiting for a sound from a phonecall than waiting for a browser tab. If I'm going to be using a keyboard, don't make me wait there by my computer or on my phone browser. Just let me send an email.

View on HN

To note, this is for the first response. It is significantly faster once we have the context of the conversation.

Edit: pulled some stats for another commenter - currently 51s first response, ~40s subsequent, 2.7 responses in total to resolution.

This sounds like an opportunity for an audio in a chat feed where between lines the computer spits out typing sounds and a virtual agent saying please hold on while I look into that.

Of course a better fix would be a combination of the two. Have some agent read your original email sent through some secure internal site and build and classify a case in the system with email attached and then reply to let you know there is a secure reply with a chat link to the complete case detail with time frames reserved for high responsiveness.

I am fine with it when the chat happens on a platform I am already using. I often use Facebook Messenger to contact companies as I have realised a lot of them actually have chat support there, even though it is not listed anywhere and their website only mentions calling (and they usually answer way faster than email!).

But if I am having to stay on your website and use your chat widget I expect a faster reply!

It’s intended for people who are in meetings or doing work to have a disjointed brief conversation that may span a half hour or more - eg, feature support.

Reply on news.ycombinator.com