Whether a given use case for any software is deemed feasible, depends on the economics of that use case. The project at hand will be considered viable if the software will achieve an adequate return on investment. This applies to chatbots as well.
In order to be economically viable, the cost of creating the chatbot must be less than the incremental profit it is expected to generate. While the cost is determined by the complexity of the use case and the efficiency of the chatbot development platform, the incremental profit is driven by the customer.
The customer has to complete many steps when completing a task. For example, if they want to use a new device, they will:
The chatbot (or any relevant software) could be introduced by a business as part of a service if it was possible to make any of the above steps easier for the customer (without adding excessive costs or introducing disadvantages).
The first condition is that it is possible to create a business service for an existing step that results in better customer experience than the current proses and secondly the chatbot needs to be the best model of technology for that service.
It is also important to consider that different customers may have different priorities. Some customers may be more price sensitive and therefore value a cheap price over convenience while others might value convenience over price.
A chatbot could be a good model for the customer who values convenience over price (for example when shopping for a present) as this customer wants a quick good enough outcome over shopping for exactly the right model and price combination. The person who values price or is searching for exact features is likely better off with a graphical interface where they can filter options with more granularity.
Of course all the chatbot business models above are brainstorming. There are likely to be many ideas for each step in the process. It is up to you to assess the value and feasibility of the ideas presented but hopefully, it gives you some idea as to what may be possible with chatbots.
A detailed comparison of Dialogflow ES, Dialogflow CX, and Botpress — with screenshots. Part two!