A bot is software that is designed to automate the kinds of tasks you would usually do on your own, like making a dinner reservation, adding an appointment to your calendar or fetching and displaying information. The increasingly common form of bots, chatbots, simulate conversation. They often live inside messaging apps — or are at least designed to look that way — and it should feel like you’re chatting back and forth as you would with a human.
The process of building a chatbot can be divided into two main tasks: understanding the user's intent and producing the correct answer. The first task involves understanding the user input. In order to properly understand a user input in a free text form, a Natural Language Processing Engine can be used. The second task may involve different approaches depending on the type of the response that the chatbot will generate.
Conversational bots “live” online and give customers a familiar experience, similar to engaging an employee or a live agent, and they can offer that experience in higher volumes. Conversational bots offer scaling—or the capability to perform equally well under an expanding workload—in ways that human can’t, assisting businesses to reach customers in a way they couldn’t before. For one, businesses have created 24/7/365 online presence through conversational bots.
The fact that you can now run ads directly to Messenger is an enormous opportunity for any business. This skips the convoluted and leaky process of trying to acquire someone's email address to nurture them outside of Facebook's platform. Instead, you can retain the connection with someone inside Facebook and improve the overall conversion rates to receiving an engagement.
Because chatbots are predominantly found on social media messaging platforms, they're able to reach a virtually limitless audience. They can reach a new customer base for your brand by tapping into new demographics, and they can be integrated across multiple messaging applications, thus making you more readily available to help your customers. This, in turn, opens new opportunities for you to increase sales.
Canadian and US insurers have a lot on their plates this year. They’re not just grappling with extreme weather, substantial underwriting losses from all those motor vehicle claims, but also rising customer expectations and an onslaught of fintech disruptors. These disruptors are spurring lots of activity in insurance digital labs, insurance venture capital arms, and […]
According to this study by Petter Bae Brandtzaeg, “the real buzz about this technology did not start before the spring of 2016. Two reasons for the sudden and renewed interest in chatbots were [number one] massive advances in artificial intelligence (AI) and a major usage shift from online social networksto mobile messaging applications such as Facebook Messenger, Telegram, Slack, Kik, and Viber.”
Die Herausforderung bei der Programmierung eines Chatbots liegt in der sinnvollen Zusammenstellung der Erkennungen. Präzise Erkennungen für spezielle Fragen werden dabei ergänzt durch globale Erkennungen, die sich nur auf ein Wort beziehen und als Fallback dienen können (der Bot erkennt grob das Thema, aber nicht die genaue Frage). Manche Chatbot-Programme unterstützen die Entwicklung dabei über Priorisierungsränge, die einzelnen Antworten zuzuordnen sind. Zur Programmierung eines Chatbots werden meist Entwicklungsumgebungen verwendet, die es erlauben, Fragen zu kategorisieren, Antworten zu priorisieren und Erkennungen zu verwalten. Dabei lassen manche auch die Gestaltung eines Gesprächskontexts zu, der auf Erkennungen und möglichen Folgeerkennungen basiert („Möchten Sie mehr darüber erfahren?“). Ist die Wissensbasis aufgebaut, wird der Bot in möglichst vielen Trainingsgesprächen mit Nutzern der Zielgruppe optimiert. Fehlerhafte Erkennungen, Erkennungslücken und fehlende Antworten lassen sich so erkennen. Meist bietet die Entwicklungsumgebung Analysewerkzeuge, um die Gesprächsprotokolle effizient auswerten zu können. Ein guter Chatbot erreicht auf diese Weise eine mittlere Erkennungsrate von mehr als 70 % der Fragen. Er wird damit von den meisten Nutzern als unterhaltsamer Gegenpart akzeptiert.
Another option is to integrate your own custom AI service. This approach is more complex, but gives you complete flexibility in terms of the machine learning algorithm, training, and model. For example, you could implement your own topic modeling and use algorithm such as LDA to find similar or relevant documents. A good approach is to expose your custom AI solution as a web service endpoint, and call the endpoint from the core bot logic. The web service could be hosted in App Service or in a cluster of VMs. Azure Machine Learning provides a number of services and libraries to assist you in training and deploying your models.
At this year’s I/O, Google announced its own Facebook Messenger competitor called Allo. Apart from some neat features around privacy and self-expression, the really interesting part of Allo is @google, the app’s AI digital assistant. Google’s assistant is interesting because the company has about a decades-long head start in machine learning applied to search, so its likely that Allo’s chatbot will be very useful. In fact, you could see Allo becoming the primary interface for interacting with Google search over time. This interaction model would more closely resemble Larry Page’s long-term vision for search, which goes far beyond the clumsy search query + results page model of today:
Not integrated. This goes hand-in-hand with the contextual knowledge, but chatbots often suffer from “death by data silo” where their access to data is limited. If a chatbot is “chatting with” a customer, they not only need to access the contextual data of their customer but also have access to every place where the answer to the customer’s question may reside. Product documentation site, customer community, different websites are all places where that answer can be.
Chatbots and virtual assistants (VAs) may be built on artificial intelligence and create customer experiences through digital personas, but the success you realize from them will depend in large part on your ability to account for the real and human aspects of their deployment, intra-organizational impact, and customer orientation. Start by treating your bots and […]
In 1950, Alan Turing's famous article "Computing Machinery and Intelligence" was published, which proposed what is now called the Turing test as a criterion of intelligence. This criterion depends on the ability of a computer program to impersonate a human in a real-time written conversation with a human judge, sufficiently well that the judge is unable to distinguish reliably—on the basis of the conversational content alone—between the program and a real human. The notoriety of Turing's proposed test stimulated great interest in Joseph Weizenbaum's program ELIZA, published in 1966, which seemed to be able to fool users into believing that they were conversing with a real human. However Weizenbaum himself did not claim that ELIZA was genuinely intelligent, and the introduction to his paper presented it more as a debunking exercise: