1. Define the goals. What should your chatbot do? Clearly indicate the list of functions your chatbot needs to perform. 2. Choose a channel to interact with your customers. Be where your clients prefer to communicate — your website, mobile app, Facebook Messenger, WhatsApp or other messaging platform. 3. Choose the way of creation. There are two of them: using readymade chat bot software or building a custom bot from scratch. 4. Create, customize and launch. Describe the algorithm of its actions, develop a database of answers and test the work of the chatbot. Double check everything before showing your creation to potential customers.
Kunze recognises that chatbots are the vogue subject right now, saying: “We are in a hype cycle, and rising tides from entrants like Microsoft and Facebook have raised all ships. Pandorabots typically adds up to 2,000 developers monthly. In the past few weeks, we've seen a 275 percent spike in sign-ups, and an influx of interest from big, big brands.”
In sales, chatbots are being used to assist consumers shopping online, either by answering noncomplex product questions or providing helpful information that the consumer could later search for, including shipping price and availability. Chatbots are also used in service departments, assisting service agents in answering repetitive requests. Once a conversation gets too complex for a chatbot, it will be transferred to a human service agent .
Malicious chatbots are frequently used to fill chat rooms with spam and advertisements, by mimicking human behavior and conversations or to entice people into revealing personal information, such as bank account numbers. They are commonly found on Yahoo! Messenger, Windows Live Messenger, AOL Instant Messenger and other instant messaging protocols. There has also been a published report of a chatbot used in a fake personal ad on a dating service's website.
For designing a chatbot conversation, you can refer this blog — “How to design a conversation for chatbots.” Chatbot interactions are segmented into structured and unstructured interactions. As the name suggests, the structured type is more about the logical flow of information, including menus, choices, and forms into account. The unstructured conversation flow includes freestyle plain text. Conversations with family, colleagues, friends and other acquaintances fall into this segment. Developing scripts for these messages will follow suit. While developing the script for messages, it is important to keep the conversation topics close to the purpose served by the chatbot. For the designer, interpreting user answers is important to develop scripts for a conversational user interface. The designer also turns their attention to close-ended conversations that are easy to handle and open-ended conversations that allow customers to communicate naturally.
2010 SIRI: Though Siri is considered colloquially to be a virtual assistant rather than a conversational bot, it was built off the same technologies and paved the way for all later AI bots and PAs. Siri is an intelligent personal assistant with a natural language UI to respond to questions and perform web-based service requests. Siri was part of apples IOS.
If AI struggles with fourth-grade science question answering, should AI be expected to hold an adult-level, open-ended chit-chat about politics, entertainment, and weather? It is thus encouraging to see that Microsoft’s Satya Nadella did not give up on Tay after its debacle, and Amazon’s Jeff Bezos is sponsoring an Alexa social chatbot competition. I love this below quote from Jeff:
Furthermore, major banks today are facing increasing pressure to remain competitive as challenger banks and fintech startups crowd the industry. As a result, these banks should consider implementing chatbots wherever human employees are performing basic and time-consuming tasks. This would cut down on salary and benefit costs, improve back-office efficiency, and deliver better customer care.
To envision the future of chatbots/virtual assistants, we need to take a quick trip down memory lane. Remember Clippy? Love him or hate him, he’s ingrained in our memory as the little assistant who couldn’t (sorry, Clippy.). But someday, this paper clip could be the chosen one. Imagine with me if you will a support agent speaking with a customer over the phone, or even chat support. Clippy could be listening in, reviewing the questions the customer is posing, and proactively providing relevant content to the support agent. Instead of digging around from system to system, good ‘ole Clippy would have their back, saving them the trouble of hunting down relevant information needed for the task at hand.
Logging. Log user conversations with the bot, including the underlying performance metrics and any errors. These logs will prove invaluable for debugging issues, understanding user interactions, and improving the system. Different data stores might be appropriate for different types of logs. For example, consider Application Insights for web logs, Cosmos DB for conversations, and Azure Storage for large payloads. See Write directly to Azure Storage.
Earlier, I made a rather lazy joke with a reference to the Terminator movie franchise, in which an artificial intelligence system known as Skynet becomes self-aware and identifies the human race as the greatest threat to its own survival, triggering a global nuclear war by preemptively launching the missiles under its command at cities around the world. (If by some miracle you haven’t seen any of the Terminator movies, the first two are excellent but I’d strongly advise steering clear of later entries in the franchise.)
Developed to assist Nigerian students preparing for their secondary school exam, the University Tertiary Matriculation Examination (UTME), SimbiBot is a chatbot that uses past exam questions to help students prepare for a variety of subjects. It offers multiple choice quizzes to help students test their knowledge, shows them where they went wrong, and even offers tips and advice based on how well the student is progressing.
Simple chatbots work based on pre-written keywords that they understand. Each of these commands must be written by the developer separately using regular expressions or other forms of string analysis. If the user has asked a question without using a single keyword, the robot can not understand it and, as a rule, responds with messages like “sorry, I did not understand”.
It may be tempting to assume that users will navigate across dialogs, creating a dialog stack, and at some point will navigate back in the direction they came from, unstacking the dialogs one by one in a neat and orderly way. For example, the user will start at root dialog, invoke the new order dialog from there, and then invoke the product search dialog. Then the user will select a product and confirm, exiting the product search dialog, complete the order, exiting the new order dialog, and arrive back at the root dialog.
The front-end app you develop will interact with an AI application. That AI application—usually a hosted service—is the component that interprets user data, directs the flow of the conversation and gathers the information needed for responses. You can then implement the business logic and any other components needed to enable conversations and deliver results.
Previous generations of chatbots were present on company websites, e.g. Ask Jenn from Alaska Airlines which debuted in 2008 or Expedia's virtual customer service agent which launched in 2011. The newer generation of chatbots includes IBM Watson-powered "Rocky", introduced in February 2017 by the New York City-based e-commerce company Rare Carat to provide information to prospective diamond buyers.