CANDIDATE DECLARATION

I Hitesh Bansal hereby declare that I have made a software project in partial fulfilment of
requirements for the award of degree of B.tech (Computer Sciences & Engineering) at
SCHOOL OF ENGINEERING AND EMERGING TECHNOLOGY, BUEST, BADDI. The
work which is being presented in the training reports submitted to Department of Computer
Science & Technology, BUEST, BADDI is an authentic record of training work.

Signature of the Student

The software/industrial training/ Viva-Voice Examination has been held on 30th Dec 2020 and
accepted.

Signature of Internal Examiner

i
 ACKNOWLEDGEMENT

Behind every successful effort, there lie contributions from numerous sources irrespective of
their magnitude. Hard work and dedication is not the only thing required for the completion of
a Project, but equally important is proper guidance and inspiration. Our project is no exception
and we take this opportunity to thank all those who are lending a helping hand.
We take this opportunity to express our deep and sincere gratitude to most esteemed Head of
Department Mrs Renuka Rattan as who have been kind enough to spare their valuable time, on
which we have no claim. Their guidance and motivation conceived a direction in us, and are
helping us to make this project a grand success.

Last but not the least we shall remain thankful to all our classmates, at present as well as in
future who are cooperating with us in making this project happening.

Moreover we express our deep gratitude towards BADDI UNIVERSITY OF EMERGING

SCIENCES AND TECHNOLOGY, BADDI for providing us the different resources and
facility of Internet from where we took the references and completed our work on time

ii
 ABSTRACT

Conversational modelling is an important task in natural language processing as well as

machine learning. Like most important tasks, it’s not easy. Previously, conversational models
have been focused on specific domains, such as booking hotels or recommending restaurants.
They were built using hand-crafted rules, like ChatScript , a popular rule-based conversational
model. In 2014, the sequence to sequence model being used for translation opened the
possibility of phrasing dialogues as a translation problem: translating from an utterance to its
response. The systems built using this principle, while conversing fairly fluently, aren’t very
convincing because of their lack of personality and inconsistent persona . In this paper, we
experiment building open-domain response generator with personality and identity. We built
chatbots that imitate characters in popular TV shows: Barney from How I Met Your Mother,
Sheldon from The Big Bang Theory, Michael from The Office, and Joey from Friends. A
successful model of this kind can have a lot of applications, such as allowing people to speak
with their favorite celebrities, creating more life-like AI assistants, or creating virtual alter-egos
of ourselves. The model was trained end-to-end without any hand-crafted rules. The bots talk
reasonably fluently, have distinct personalities, and seem to have learned certain aspects of
their identity. The results of standard automated translation model evaluations yielded very low
scores. However, we designed an evaluation metric with a human judgment element, for which
the chatbots performed well. We are able to show that for a bot’s response, a human is more
than 50% likely to believe that the response actually came from the real character.

iii
 TABLE OF CONTENTS

Candidate Declaration i
Acknowledgement ii
Abstract iii
Table of Content iv
List of figures v

1. INTRODUCTION 1-6

1.1 INTRODUCTION TO PROJECT 1

1.2 DEFINING THE PROBLEM 1

1.3 EXISTING SYSTEM 2

1.4 PROPOSED SYSTEM 3

1.5 OBJECTIVES 3

1.6 FEASIBILITY STUDY 5-6

2. SYSTEM ANALYSIS & DESIGN 7-12

2.1 MODEL USED 7-8

2.2 SRS (SYSTEM REQUIREMENT SPECIFICATION): 9

2.3 DATA FLOW DIAGRAMS (DFDS): 10

2.4 E-R DIAGRAM: 11-12

3. WORKING OF PROJECT 13-17

3.1 INTRODUCTION TO PROJECT 13-14

3.2 TECHNOLOGY USED IN THE PROJECT 15-17

4. RESULTS & DISCUSSION 18

5. CONCLUSION & FUTURE SCOPE 19-20

5.1 CONCLUSION 19

5.2 FUTURE SCOPE 20

6. REFERENCE 21

iv
 LIST OF FIGURES

Figure Number Description Page Number

Fig. 2.1 SDLC Diagram 7
Fig. 2.2 Flow Diagram for Chatbot 11
Fig. 2.3 Class Diagram for Chatbot 12
Fig. 3.1 Splash Screen of Website 13
Fig. 3.2 Screenshot of Chatbot 14

v
 CHAPTER 1
INTRODUCTION

1.1 Introduction to Project:

Chatbot is a machine that interact with the human and it provides answer to the several
problem of human in its domain.
We can safely say that we are in or at least entering the era of the chatbot. The big
players, Google, Facebook, Microsoft and others, are all busy developing and
improving this innovative user experience technology. Messaging applications are now
more widely used than social networks, which is good news for the chatbot as they are
such messaging applications!

The most natural definition of a chatbot is – a developed a program that can have a
discussion/conversation with a human. For example, any user could ask the bot an
inquiry or a statement, and the bot will respond or perform an activity as appropriate.

A chatbot interacts on a format similar to instant messaging. By artificially replicating

the patterns of human interactions in machine learning allows computers to learn by
themselves without programming natural language processing. The most natural
definition of a chatbot is – a developed a program that can have a
discussion/conversation with a human. For example, any user could ask the bot an
inquiry or a statement, and the bot will respond or perform an activity as appropriate.
For example, if you’ve asked Amazon’s Alexa, Apple Siri, or Microsoft’s Cortana,
“What’s the weather?”, it would respond according to the latest weather reports it has
access to. The complexity of a chatbot is determined by the sophistication of its
underlying software and the data it can access. Every enterprise has expanded IT
infrastructure. From different fields, on-premise to cloud, companies with different
supply providers, run on many different, internal and characterized built applications,
as well as ERP, encompass applications. There are other core applications like CRM
and customer portals, which are the backbone of ERP. 11 Currently, many e-commerce
companies are looking at various ways to used to improve their customer experiences.
Whether for shopping, booking tickets or simply for customer service. The next time
you hear about a chatbot, especially in business and travel, remember to look beyond
the fancy term. And ask about how it really adds value to your travel program

1.2 Defining The Problem

The creation and implementation of chatbots is still a developing area, heavily related
to artificial intelligence and machine learning so the provided solutions, while
possessing obvious advantages, have some important limitations in terms of
functionalities and use cases. However this is changing over time.

1
The most common ones are listed below.

• As the database, used for output generation, is fixed and limited, chatbots can
fail while dealing with an unsaved query.
• Chatbot's efficiency highly depends on language processing and is limited
because of irregularities, such as accents and mistakes that can create an
important barrier for international and multicultural organisations .
• Chatbots are unable to deal with multiple questions at the same time and so
conversation opportunities are limited.
• As it happens usually with technology-led changes in existing services, some
consumers, more often than not from the old generation, are uncomfortable with
chatbots due to their limited understanding, making it obvious that their requests
are being dealt machines.
• It is often considered that chatbots are complicated and need a lot of time to
understand what you want in customer. Sometimes, it can also annoy the client
about their slowness, or their difficulty in filtering responses.
• Fixed chatbots can get stuck easily. If a query doesn’t relate to something
you’ve previously “taught” it, you won’t understand it. This can lead to a
frustrated customer and the loss of the sale. Other times they do understand you,
but they need double (or triple) as many messages as one person, which spoils
the user experience.
• Chatbots are installed with the aim of speeding up responses and improving
customer interaction. However, due to the limited availability of data and the
time needed for self updating, this process can be slow and costly. Therefore,
there are times when instead of serving several customers at once, chatbots may
become confused and not serve the customer well.

1.3 Existing System:

As a chatbot developer, you can make your bot by scratch by utilizing these
platforms’ API or SDK :
• Facebook messenger
• Slack
• Kik
• Telegram
• Whatsapp

However, for some businesses that need to rapidly produce an MVP product to
validate your idea via chatbots, using existing chatbot builders is obviously a better
choice for you. Check out the following services that provide opportunities for those
without any programming background to your own chatbots:
• Api.ai
• Motion.ai 17

2
 • converse.ai
• stamplay

1.4 Proposed System:

Chat bot project is built using selenium tool using amazon aws that analyzes user’s
queries and understand user’s message and revert back to give answers

This System is a web application which provides answer to the query of the student.
Students just have to query through the bot which is used for chatting.

Students can chat using any format there is no specific format the user has to follow.

The answers are appropriate what the user queries. If the answer found to invalid, user
just need to select the invalid answer button which will notify the admin about the
incorrect answer.

The User can search and our algorithm will run in background to find the best
possible answers for his question.

The system answers to the query as if it is answered by the person. With the help of
google search, the system answers the query asked by the students.

The system replies on the same chat screen.

The user can query about the college related activities through online with the help of
this web application.

1.5 Objective:
The aim of a chatbot is to conduct conversation which allows people access to
information via a lightweight messaging application. There are currently two distinct
types of chatbot:

• Rule-based chatbot: These essentially work as an interactive FAQ. They’re

programmed to recognize certain terms and patterns from which they can
respond with pre-set answers.
• AI chatbot: These act as an artificial brain, using sophisticated cognitive and
natural language processing capabilities. It not only understands requests but
also context, intent, emotion and it continuously gets smarter as it learns from
conversations it has with users.

3
Chatbots are being made to ease the pain that the industries are facing today. The
purpose of chat bots is to support and scale business teams in their relations with
customers. It could live in any major chat applications like Facebook Messenger, Slack,
Telegram, Text Messages, etc.

Chatbots may sound like a futuristic notion, but according to Global Web Index
statistics, it is said that 75% of internet users are adopting one or more messenger
platforms. Although research shows us that each user makes use of an average of 24
apps a month, wherein 80% of the time would be in just 5 apps. Undoubtedly among
them are Facebook Messenger, Snapchat, Whatsapp, WeChat etc. This means you can
hardly shoot ahead with an app, but you still have high chances to integrate your chatbot
with one of these platforms.

Wouldn’t it be great if someone could ease your pain by helping you out 24*7 making
your work easier and less hectic. Chatbots can do just that!!

Chatbots are being made to ease the pain that the industries are facing today. The
purpose of chat bots is to support and scale business teams in their relations with
customers. It could live in any major chat applications like Facebook Messenger, Slack,
Telegram, Text Messages, etc.

Chatbots may sound like a futuristic notion, but according to Global Web Index
statistics, it is said that 75% of internet users are adopting one or more messenger
platforms. Although research shows us that each user makes use of an average of 24
apps a month, wherein 80% of the time would be in just 5 apps. Undoubtedly among
them are Facebook Messenger, Snapchat, Whatsapp, WeChat etc. This means you can
hardly shoot ahead with an app, but you still have high chances to integrate your chatbot
with one of these platforms.

Wouldn’t it be great if someone could ease your pain by helping you out 24*7 making
your work easier and less hectic. Chatbots can do just that!!

Hiring a human for a job is never a cheap affair, and it will be expensive if your revenue
are not high or sales targets are not met and would create havoc in the business. Due to
the boundaries of human beings, a single human can only handle one or two people at
the same time. More than that would be extremely tough for the employee.

chatbot could help solve this age-old problem. As one chatbot is equal to loads of
employees, it can easily communicate with thousands of customers at the same time.
We would only need a handful of people to jump into conversations sometimes when
necessary. Hence, it would drastically bring down the expenses and bring about a steep
rise in revenue and customer satisfaction.

4
1.6 Feasibility Study:
1.6.1 Economical Feasibility

Bearing the findings from the prototype phase in mind, we develop a minimum viable
product (MVP). An MVP is a product with basic functional features, a light version of
the ultimate solution that already works with actual data.

The MVP is exposed to a small group of end users in order to gather vital feedback. It
is way less expensive to modify the system at this stage, than when it is fully
developed.

The cost for a chatbot-related MVP ranges between $10,000 – $20,000, depending on
the total project size and complexity.

This makes sense given the impact automation technology could have on cutting labor
costs. Although complete automation of the customer service workforce is not
feasible, automating customer management and sales positions in the any organization
would result in considerable savings.

Twenty-nine percent of customer service positions could be automated through

chatbots and other tech, according to Public Tableau.

We estimate this translates to $23 billion in savings from annual salaries, which does
not even factor in additional workforce costs like health insurance.

1.6.2 Operational Feasibility

Chatbots are revolutionising the B2E and B2B scenarios along with the B2C
space.Almost 85% of global executives believe that AI will allow their companies to
obtain or sustain a competitive advantage .A chatbot architecture should deploy
intelligent chatbots, identify and engage with right technology, and should have a
multiple channel support among other requirements.
Artificial intelligence & Machine learning — The two words that are on the tip of
every technophile tongue. It is fair to say that AI and ML, over the years, have
successfully transformed almost every aspect of our personal and more importantly,
our professional lives.

1.6.3 Technical Feasibility

• Identify the right use case and the right scope with your client : sometime
projects are not feasible technically, not really useful, or even too expensive.
Don’t hesitate to start small and scale up !
• Design the conversation flows (you can use real time board a great
collaborative mind mapping tool, or Bot mock)

5
 • Choose the most appropriate tech stack
• Develop in agile methodology using sprints, test with beta-users, improve the
bot flow, the knowledge base, the bot personality...
• Scale up, follow analytics/KPI and compare to objectives you want to achieve.

The foremost question you should be asking is “Where are your users? “ which is
actually which platforms are being used by your users for the end interaction with the
bot. Whether they use voice, chat, web or a normal messenger, you need to figure out
what works best for your users. This also includes the mode the bot uses to
communicate with its customers.

For instance,

Facebook Messenger, Kiko, Telegram, Line are used as a platform when there is a
large audience to cater to. As per Statista, As of the last reported period of April 2014
to April 2017, the mobile messenger had 1.2 billion monthly active users worldwide,
ranking second among mobile chat apps worldwide.Slack could be considered while
focusing on startups and developers.

Smart assistants like Google Assistant, Cortana and Amazon Echo could be used
when for audience prefers voice-enabled services. .

6
 CHAPTER 2
SYSTEM ANALYSIS & DESIGN

2.1 Model Used

SDLC Model

Software Development Life Cycle (SDLC) is a process used by the software industry
to design, develop and test high quality softwares. The SDLC aims to produce a high
quality software that meets or exceeds customer expectations, reaches completion
within

times and cost estimates.

• SDLC is the acronym of Software Development Life Cycle. • It is also called as
Software Development Process.

• SDLC is a framework defining tasks performed at each step in the software

development process. It aims to be the standard that defines all the tasks required for
developing and maintaining software.

Figure-:2.1 SDLC Diagram

There are various software development life cycle models defined and designed which
are followed during the software development process. These models are also referred

7
 as Software Development Process Models". Each process model follows a Series of
steps unique to its type to ensure success in the process of software development.

Following are the most important and popular SDLC models followed in the industry:-

• Waterfall Model
• Iterative Model
• Spiral Model
• V-Model
• Big Bang Model

Other related methodologies are Agile Model, RAD Model, Rapid Development and
Prototyping Models.

Application

Every software developed is different and requires a suitable SDLC approach to be

followed based on the internal and external factors. In this project we have used
waterfall model for representing our SDLC. Some situations where the use of
Waterfall model is most appropriate are −
• Requirements are very well documented, clear and fixed. • Product definition is
stable.

• Technology is understood and is not dynamic.

• There are no ambiguous requirements.

• Ample resources with required expertise are available to support the product.

The Prototyping Model is a systems development method (SDM) in which a prototype

(an early approximation of a final system or product) is built, tested, and then reworked
as necessary until an acceptable prototype is finally achieved from which the complete
system or product can now be developed. This model works best in scenarios where
not all of the project requirements are known in detail ahead of time. It is an iterative,
trial- and-error process that takes place between the developers and the users.

There are several steps in the Prototyping Model:

• The new system requirements are defined in as much detail as possible. This usually
involves interviewing a number of users representing all the departments or aspects of
the existing system.
• A preliminary design is created for the new system.
• A first prototype of the new system is constructed from the preliminary design. This is
usually a scaled-down system, and represents an approximation of the characteristics
of the final product.

8
• The users thoroughly evaluate the first prototype, noting its strengths and weaknesses,
what needs to be added, and what should to be removed. The developer collects and
analyses the remarks from the users.
• The first prototype is modified, based on the comments supplied by the users, and a
second prototype of the new system is constructed.
• The second prototype is evaluated in the same manner as was the first prototype.
• The preceding steps are iterated as many times as necessary, until the users are satisfied
that the prototype represents the final product desired.
• The final system is constructed, based on the final prototype.
• The final system is thoroughly evaluated and tested. Routine maintenance is carried out
on a continuing basis to prevent large-scale failures and to minimize downtime.

2.2 System Requirement Specification (SRS)

This software requirement specification (SRS) report expresses complete description

about the project. This document includes all the functions and specifications with
their explanations to solve related problems to the project.

Chatbot technology has hit the market recently. This new piece of software enabled
brands with a very intuitive way to communicate with their customers —
conversation. This triggered a range of new ideas coming to creative minds.
However, it takes a lot of work to turn a chatbot idea into a project. In fact, it requires
a complete step-by-step chatbot strategy starting from goal definition to publishing
and maintenance. One of the most important steps in this strategy — documenting
product requirements — is focused precisely on shaping a chatbot idea into a working
project. Apparently, the most intuitive way of communication is not that intuitive
when it comes to documentation. It seems much easier to sketch a mobile app or a
website layout than to explain a dialog. Therefore, a new technology brings a new
challenge.

2.2.1 Hardware Requirements

There will be no hardware requirement to build a chatbot. Chatbot is scripted unless it

is an AI based chatbot. For software, there are many other platforms on which you
can build chatbot, but mostly people use Python to build efficient chatbot. Python is
prefered most because it is easy to code in python and it give efficient output. Script
or code to develop chatbot in python is easy available on github and stack overflow
etc.

2.2.2 Software Requirements

There are many platforms available for creating a chatbot.

9
Or if we are for sure to create a chatbot from scratch then we would recommend
python as the language of choice.

More detailed thought process would be required to think about hardware. All will
depend upon the chatbot use case. Number of users who will use, core purpose of the
chatbot etc.

We have recently created a chatbot framework that allows one to use and try many
platforms and technologies for various purposes like entity extraction, intent
identification and content management.

2.3 Data Flow Diagrams DFDS:

A data flow diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modeling its process aspects. A DFD is often used as a
preliminary step to create an overview of the system without going into great detail,
which can later be elaborated. DFDs can also be used for the visualization of data
processing (structured design).

A DFD shows what kind of information will be input to and output from the system,
how the data will advance through the system, and where the data will be stored. It
does not show information about process timing or whether processes will operate in
sequence or in parallel, unlike a traditional structured flowchart which focuses on
control flow, or a UML activity workflow diagram, which presents both control and
data, flows as a unified model.

Obviously this is the most complex part, but I never give any step forward without
knowing the previous ones. Once that I got all that information is time to start
designing how the chatbot will behave in every possible scenario in its interaction
with every user.

I always use X mind for designing the flows from scratch. It’s easy to use and really
fast if you want to make any changes. The first thing I need to do is create a color
legend with every possible item I will include on the chatbot.
Because at this point the scope has been set, I need to take users to the functionalities
that I cover. In the e-commerce chatbot I was able to give pictures, opinions, details
and prices for technological products. Because the best way to set the scope is making
it clear in the welcome message, that is the first thing I write down in X mind. Right
after, I point out every possible scenario the bot will need to deal with it.

10
 Figure 2.2 : Flow Diagram For Chatbot

2.4 E-R Diagram:

An entity-relationship diagram (ERD) is a graphical representation of an information

system. An ERD is a data modeling technique that can help define business processes
and can be used as the foundation for a relational database.

• The entity relationship diagram describes the relationship between entities,

cardinality and their attributes.

• The object relationship pair can be graphically represented by diagram called entity
relationship diagram (ERD).

• The ERD is mainly used in database applications but now it is more commonly used
in data design.

• The ERD was originally proposed by Peter Chen for design of relational database
systems. • The primary purpose of ERD is to represent the relationship between data
objects.

There are five main components of an ERD:-

11
Entities, which are represented by rectangles. An entity is an object or concept about
which you want to store information. A weak entity is an entity that must defined by a
foreign key relationship with another entity as it cannot be uniquely identified by its
own attributes alone.

Actions, which are represented by diamond shapes, show how two entities share
information in the database. In some cases, entities can be self-linked.

Attributes, which are represented by ovals. A key attribute is the unique, entity

A multivalued attribute can have more than one value. For example, an employee
entity can have multiple skill values. A derived attribute is based on another attribute.
For example, an employee's monthly salary is based on the employee's annual salary.

Connecting lines, solid lines that connect attributes to show the relationships of
entities in the diagram.

Figure 2.3 : Class Diagram for chatbot

12
 CHAPTER 3
WORKING OF PROJECT

3.1 Introduction to project

Figure 3.1 : Screen Shot Of Website

SKSMart.co.in is an online food and grocery store. With over 2,000 products and over
a 1000 brands in our catalogue you will find everything you are looking for. Right
from fresh Rice and Dals, Spices and Seasonings to Packaged products, Beverages,
Personal care products, Meats – we have it all.

Choose from a wide range of options in every category, exclusively handpicked to

help you find the best quality available at the lowest prices. Select a time slot for
delivery and your order will be delivered right to your doorstep, anywhere in Baddi,
Barotiwala, Housing Board, Amravati, Shiwalik Nagar, Jharmajri, Sai Road HP. You
can pay using COD (Cash on delivery), Paytm, Gpay, PhonePay while delivery.

Sksmart.co.in allows you to walk away from the drudgery of grocery shopping and
welcome an easy relaxed way of browsing and shopping for groceries. Discover new
products and shop for all your food and grocery needs from the comfort of your home
or office. No more getting stuck in traffic jams, paying for parking, standing in long
queues and carrying heavy bags – get everything you need, when you need, right at

13
your doorstep. Food shopping online is now easy as every product on your monthly
shopping list, is now available online at sksmart.co.in .

Figure 3.2 : Screen Shot Of Chatbot

The aim of a chatbot is to conduct conversation which allows people access to

information via a lightweight messaging application. There are currently two distinct
types of chatbot:

• Rule-based chatbot: These essentially work as an interactive FAQ. They’re

programmed to recognize certain terms and patterns from which they can
respond with pre-set answers.
• AI chatbot: These act as an artificial brain, using sophisticated cognitive and
natural language processing capabilities. It not only understands requests but
also context, intent, emotion and it continuously gets smarter as it learns from
conversations it has with users.
• Hiring a human for a job is never a cheap affair, and it will be expensive if
your revenue are not high or sales targets are not met and would create havoc
in the business. Due to the boundaries of human beings, a single human can
only handle one or two people at the same time. More than that would be
extremely tough for the employee.
• chatbot could help solve this age-old problem. As one chatbot is equal to loads
of employees, it can easily communicate with thousands of customers at the

14
 same time. We would only need a handful of people to jump into
conversations sometimes when necessary. Hence, it would drastically bring
down the expenses and bring about a steep rise in revenue and customer
satisfaction.

3.2 Technologies Used In The Project

3.2.1 Amazon LEX

Amazon Lex is a service for building conversational interfaces into any application
using voice and text. Amazon Lex provides the advanced deep learning functionalities
of automatic speech recognition (ASR) for converting speech to text, and natural
language understanding (NLU) to recognize the intent of the text, to enable you to build
applications with highly engaging user experiences and lifelike conversational
interactions. With Amazon Lex, the same deep learning technologies that power
Amazon Alexa are now available to any developer, enabling you to quickly and easily
build sophisticated, natural language, conversational bots (“chatbots”).

With Amazon Lex, you can build bots to increase contact center productivity, automate
simple tasks, and drive operational efficiencies across the enterprise. As a fully
managed service, Amazon Lex scales automatically, so you don’t need to worry about
managing infrastructure.

High quality speech recognition and natural language understanding

Amazon Lex provides automatic speech recognition and natural language
understanding technologies to create a Speech Language Understanding system.
Amazon Lex uses the same proven technology that powers Alexa. Amazon Lex is able
to learn the many different ways someone could express their intent based on the sample
utterances provided by the developer. The speech language understanding system takes
natural language speech and text input, understands the intent behind the input, and
fulfills the user intent by invoking the appropriate response.

Multi-turn conversations
Amazon Lex bots provide the ability for multi-turn conversations. Once an intent has
been identified, users will be prompted for information that is required for the intent to
be fulfilled (for example, if “Book hotel” is the intent, the user is prompted for the
location, check-in date, number of nights, etc.). Amazon Lex gives you an easy way to
build multi-turn conversations for your chatbots. You simply list the slots/parameters
you want to collect from your bot users, as well as the corresponding prompts, and
Amazon Lex takes care of orchestrating the dialogue by prompting for the appropriate
slot.

Context Management

15
As the conversation develops, being able to classify utterances requires managing
context across multi-turn conversations. Amazon Lex supports context management
natively, so you can manage the context directly without the need for custom code. As
initial prerequisite intents are filled, you can create “contexts” to invoke related intents.
This simplifies bot design, and expedites the creation of conversational experiences.

Utility Prompts
Amazon Lex provides two types of prompts: confirmation prompts that enable you to
confirm an action before fulfilling it; and error-handling prompts, that request the user
to repeat input for additional clarity. Confirmation prompts allow you to confirm the
intent of the user before executing back-end business logic (for example, "Would you
like to confirm your reservation now?"). Error-handling prompts address scenarios
where the user input is not understood, allowing for a graceful handling of error
scenarios. For example, if a user’s speech input is not clear or audible, or doesn’t map
to a known intent, you can configure Amazon Lex to prompt the user to repeat
information, for example, “Sorry I didn’t get that.” or “Can you please repeat that?”.
You can set the number of retries and also specify the goodbye message before your
app stops prompting the user.

Integration with AWS Lambda

Amazon Lex natively supports integration with AWS Lambda for data retrieval,
updates, and business logic execution. The serverless compute capacity allows
effortless execution of business logic at scale while you focus on developing bots. From
Lambda, you can access various AWS services, such as Amazon DynamoDB for
persisting conversation state and Amazon SNS for notifying end users.

Connect to Enterprise Systems

You can also use AWS Lambda to easily integrate with your existing enterprise
applications and databases. You just write your integration code and AWS Lambda
automatically runs your code when needed to send or retrieve data from any external
system.

One-click Deployment to Multiple Platforms

Amazon Lex allows you to easily publish your bot to chat services directly from the
Amazon Lex console, reducing multi-platform development efforts. Rich formatting
capabilities provide an intuitive user experience tailored to chat platforms like
Facebook Messenger, Slack, and Twilio SMS.

Powerful Lifecycle Management Capabilities

Amazon Lex lets you apply versioning to Intents, Slot Types, and Bots that you create.
Versioning enables you to easily maintain code as you test and deploy in a multi-
developer environment, including implementation of rollback mechanisms. You can
create multiple aliases for each Amazon Lex bot and associate different versions to each
- for example, “production”, “development” and “test”. This enables you to continue to

16
make improvements and changes to the bot and release new versions to associate them
with the same alias, rather than making changes to all clients whenever a new version
of the bot is deployed. Versioning and alias support together allow you to easily build
and manage a bot through its lifecycle.
Intent Chaining

3.2.2 BlahBox

Blahbox is a platform that allows you to quickly integrate AI chatbots into your
website or mobile application.
CHATBOTS ENGINES:
• Watson Assistant
• Dialogflow
• Amazon Lex
• QnA Maker

You can also extend your virtual assistants capabilities adding carousels, buttons,
cards, lists and much more component enhancing your users experience.

17
 CHAPTER-: 4
RESULTS & DISCUSSION

Chat bot project is built using selenium tool using Amazon Lex that analyses user’s
queries and understand user’s message and revert back to give answers

This System is a web application which provides answer to the query of the student.
Students just have to query through the bot which is used for chatting.

Students can chat using any format there is no specific format the user has to follow.

The answers are appropriate what the user queries. If the answer found to invalid, user
just need to select the invalid answer button which will notify the admin about the
incorrect answer.

The User can search and our algorithm will run in background to find the best
possible answers for his question.

The system answers to the query as if it is answered by the person. With the help of
google search, the system answers the query asked by the students.

The system relies on the same chat screen.

The user can query about the college related activities through online with the help of
this web application.

18
 CHAPTER -: 5
CONCLUSIONS & FUTURE SCOPE

5.1 Conclusions:
From my perspective, chatbots or smart assistants is dramatically changing businesses.
There is a wide range of chatbot building platforms and also wide range of chatbot types
that are available for various enterprises, such as e-commerce, retail, banking, leisure,
travel, healthcare, and so on but due to this apprich we want to make more user centric
chatbot which will help both user and business to handle huge customer base at a time.

Chatbots can reach out to a large audience on messaging apps and be more effective
than humans. They may develop into a capable information-gathering tool in the near
future.

These days, consumers expect to be able to find the information they’re looking for
online quickly and easily. And when a business can’t provide that type of experience,
they become frustrated. Chatbots are poised to ease these frustrations by providing the
real-time, on- demand approach that consumers are seeking out.

The top three potential benefits of chatbots that consumers reported in our survey:

1. 24-hour service (64%)

2. instant responses (55%)
3. answers to simple questions (55%)
4. Direct google search

And that’s true across all age groups. It’s not just Millennials who see the potential
benefits of chatbots. In fact, Baby Boomers were 24% more likely to to expect benefits
from chatbots in five of the nine categories we looked at compared to their Millennial
counterparts.

However, chatbots — like all technologies — aren’t without their limitations: 43% of
consumers said they prefer dealing with an actual person (that was the number one
potential barrier to using chatbots). That being said, 34% of consumers also predicted
that they would use chatbots for getting connected with a human. So it doesn’t have to
be either/or. As a business, you can use chatbots to supplement your human workforce
(not replace them). Compared to other business communication channels, chatbots
scored the second-highest when it came to consumers expecting instant responses, only
losing out to online chat. But by using chatbots in combination with online chat,
businesses can deliver a level of real-time service that they’d be unable to achieve using
either technology on its own.

19
And while chatbots can’t replace phone or email when it comes to providing in-depth
answers to technical questions (some things will always require a human touch), they
are poised to become the new apps. As you saw in the previous section, chatbots
outperformed apps in the following five benefits categories:

1. Quick answers to simple questions (Chatbots, 69% | Apps, 51%)

2. Getting 24-hour service (Chatbots, 62% | Apps, 54%)
3. Quick answers to complex questions (Chatbots, 38% | Apps, 28%)
4. Ability to easily register a complaint (Chatbots, 38% | Apps, 28%)
5. Getting detailed / expert answers (Chatbots, 28% | Apps, 27%)

There’s been a lot of hype around chatbots recently, and we hope this report has helped
to separate fact from fantasy. Ultimately, we see chatbots as a technology that can help
bridge the gaps between business communication channels, and that can help deliver a
better, speedier online experience to consumers.

5.2 Future Scope:

We can implement AI to give specific answers to users as per their question. We can
integrate real time chat and answer fetching directly from google using AI to be more
specific on user query.

SOFTWARE SCOPE:

Extensibility: This software is extendable in ways that its original developers may not
expect. The following principles enhances extensibility like hide data structure, avoid
traversing multiple links or methods, avoid case statements on object type and
distinguish public and private operations.

Reusability: Reusability is possible as and when require in this application. We can

update it next version. Reusable software reduces design, coding and testing cost by
amortizing effort over several designs. Reducing the amount of code also simplifies
understanding, which increases the likelihood that the code is correct. We follow up
both types of reusability: Sharing of newly written code with in a project and reuse of
previously written code on new projects.

Understandability: A method is understandable if someone other than the creator of

the method can understand the code (as well as the creator after a time lapse). We use
the method, which small and coherent helps to accomplish this.

20
 CHAPTER-: 6
REFRENCES

• Computer History Museum (2006), "Internet History—1970's", Exhibits, Computer

History Museum, archived from the original on 2008-02-21, retrieved 2008-03-05
• Güzeldere, Güven; Franchi, Stefano (1995-07-24), "Constructions of the Mind",
Stanford Humanities Review, SEHR, Stanford University, 4 (2), retrieved 2008-03-05
• Mauldin, Michael (1994), "ChatterBots, TinyMuds, and the Turing Test: Entering the
Loebner Prize Competition", Proceedings of the Eleventh National Conference on
Artificial Intelligence, AAAI Press, retrieved 2008-03-05 (abstract)
• Network Working Group (1973), "RFC 439, PARRY Encounters the DOCTOR",
Internet Engineering Task Force, Internet Society, retrieved 2008-03-05
• Sondheim, Alan J (1997), <nettime> Important Documents from the Early Internet
(1972), nettime.org, archived from the original on 2008-06-13, retrieved 2008-03-05
• Searle, John (1980), "Minds, Brains and Programs", Behavioral and Brain Sciences,
3 (3): 417–457, doi:10.1017/S0140525X00005756
• Shevat, Amir (2017). Designing bots: Creating conversational experiences (First
ed.). Sebastopol, CA: O'Reilly Media. ISBN 9781491974827. OCLC 962125282.
• Turing, Alan (1950), "Computing Machinery and Intelligence", Mind, 59 (236): 433–
60, doi:10.1093/mind/lix.236.433
• Weizenbaum, Joseph (January 1966), "ELIZA—A Computer Program For the Study
of Natural Language Communication Between Man And Machine", Communications
of the ACM, 9 (1): 36–45, doi:10.1145/365153.36516

21