But not every use case is a chatbot use case, and I think that's the key point of the article.
The sudden viability of a conversational interface that is good enough at having a fluid conversation to revolutionize the experience of that conversation does not suddenly make this interface the best fit for all use cases.
I still find it far more pleasant to browse to a page and see a list of clearly displayed options that I can absorb at a glance and get on to what I really need to accomplish in the moment.
Even a perfect conversationalist can't remove the extra friction involved in disclosing information in an efficient way.
But still agree with the sentiment here. There are applications that I cannot imagine ever wanting to interact with via a bot.
Hybrid interfaces that combine visual cues and output and natural language input.
Asking what a user wants would be having a competent customer service representative, and would be simple, like asking me to drive home from work.
Voice prompts require me to intuit the customer support structure in order to guess where the path is to reach my category of issue. It's like asking me to walk home from work in the sewer system.