A rapidly growing, benign, form of internet bot is the chatbot. From 2016, when Facebook Messenger allowed developers to place chatbots on their platform, there has been an exponential growth of their use on that forum alone. 30,000 bots were created for Messenger in the first six months, rising to 100,000 by September 2017.[8] Avi Ben Ezra, CTO of SnatchBot, told Forbes that evidence from the use of their chatbot building platform pointed to a near future saving of millions of hours of human labour as 'live chat' on websites was replaced with bots.[9]
Through Amazon’s developer platform for the Echo (called Alexa Skills), developers can develop “skills” for Alexa which enable her to carry out new types of tasks. Examples of skills include playing music from your Spotify library, adding events to your Google Calendar, or querying your credit card balance with Capital One — you can even ask Alexa to “open Dominoes and place my Easy Order” and have pizza delivered without even picking up your smartphone. Now that’s conversational commerce in action.

Artificial Intelligence is currently being deployed in customer service to both augment and replace human agents - with the primary goals of improving the customer experience and reducing human customer service costs. While the technology is not yet able to perform all the tasks a human customer service representative could, many consumer requests are very simple ask that sometimes be handled by current AI technologies without human input.
Great explanation, Matthew. We just launched bot for booking appointment with doctors from our healthcare platform kivihealth.com . 2nd extension coming in next 2 weeks where patients will get first level consultation based on answers which doctors gave based on similar complaints and than use it as a funnel strategy to get more appointments to doctor. We provide emr for doctors so have rich data there. I feel facebook needs to do more on integration of messenger with website from design basis. Different tab is pretty ugly, it should be modal with background active. So that person can discuss alongside working.
You can structure these modules to flow in any way you like, ranging from free form to sequential. The Bot Framework SDK provides several libraries that allows you to construct any conversational flow your bot needs. For example, the prompts library allows you to ask users for input, the waterfall library allows you to define a sequence of question/answer pair, the dialog control library allows you to modularized your conversational flow logic, etc. All of these libraries are tied together through a dialogs object. Let's take a closer look at how modules are implemented as dialogs to design and manage conversation flows and see how that flow is similar to the traditional application flow.
Interface designers have come to appreciate that humans' readiness to interpret computer output as genuinely conversational—even when it is actually based on rather simple pattern-matching—can be exploited for useful purposes. Most people prefer to engage with programs that are human-like, and this gives chatbot-style techniques a potentially useful role in interactive systems that need to elicit information from users, as long as that information is relatively straightforward and falls into predictable categories. Thus, for example, online help systems can usefully employ chatbot techniques to identify the area of help that users require, potentially providing a "friendlier" interface than a more formal search or menu system. This sort of usage holds the prospect of moving chatbot technology from Weizenbaum's "shelf ... reserved for curios" to that marked "genuinely useful computational methods".