Chatbots are used in a variety of sectors and built for different purposes. There are retail bots designed to pick and order groceries, weather bots that give you weather forecast of the day or week, and simply friendly bots that just talk to people in need of a friend. The fintech sector also uses chatbots to make consumers’ inquiries and application for financial services easier. A small business lender in Montreal, Thinking Capital, uses a virtual assistant to provide customers with 24/7 assistance through the Facebook Messenger. A small business hoping to get a loan from the company need only answer key qualification questions asked by the bot in order to be deemed eligible to receive up to $300,000 in financing.
Users want to ask questions in their own language, and have bots help them. A statement that sounds as straight-forward as “My login isn’t working! I haven’t been able to log into your on-line billing system” might sound straight forward to us, but to a bot, there’s a lot it needs to understand. Watson Conversation Services has learned from Wikipedia, and along with its deep learning techniques, it’s able to work out what the user is asking.

This kind of thinking has lead me to develop a bot where the focus is as a medium for content rather than a subsitute for intelligence. So users create content much as conventional author, (but with text stored in spreadsheets rather than anywhere else). Very little is expected from the bot in terms of human behavious such as “learning”, “empathy”, “memory” and character”. Does it work?
Simple chatbots, or bots, are easy to build. In fact, many coders have automated bot-building processes and templates. The majority of these processes follow simple code formulas that the designer plans, and the bots provide the responses coded into it—and only those responses. Simplistic bots (built in five minutes or less) typically respond to one or two very specific commands.

Alternatively, think about the times you are chatting with a colleague over Slack. The need to find relevant information typically happens during conversations, and instead of having to go to a browser to start searching, you could simply summon your friendly Slack chatbot and get it to do the work for you. Think of it as your own personal podcast producer – pulling up documents, facts, and data at the drop of a hat. This concept can be translated into the virtual assistants we use on the daily. Think about an ambient assistant like Alexa or Google Home that could just be part of a group conversation. Or your trusted assistant taking notes and actions during a meeting.

In 1950, Alan Turing's famous article "Computing Machinery and Intelligence" was published,[7] 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: