Sample BRD - AI Driven Chat
Sample BRD - AI Driven Chat
VERSION1.0 –COMPLETED
NETHRA A
Page 1 of 14
Contents
Version Control............................................................................................................. 2
1.0. Project Overview....................................................................................................3
2.0. Project Goals & Objectives....................................................................................3
2.1. Goals................................................................................................................... 3
2.2. Objectives...........................................................................................................3
3.0. Scope...................................................................................................................... 3
3.1. In-Scope..............................................................................................................3
3.2. Out-of-Scope......................................................................................................3
4.0. Assumptions & Dependencies................................................................................3
4.1. Assumptions.......................................................................................................3
4.2. Dependencies......................................................................................................3
5.0. Business Processes.................................................................................................3
5.1. As-Is...................................................................................................................3
5.2. To-Be..................................................................................................................3
6.0. Business Requirements..........................................................................................3
6.1. Module 01...........................................................................................................3
6.2. Module 02...........................................................................................................3
6.3. Module 03...........................................................................................................3
6.4. Module 04...........................................................................................................3
6.5. Module 05...........................................................................................................3
6.6. Module 06...........................................................................................................3
7.0. Reporting Requirements.........................................................................................4
8.0. Annexures..............................................................................................................4
8.1. Annexure A.........................................................................................................4
8.2. Annexure B.........................................................................................................4
Page 2 of 14
Version Control
Page 3 of 14
1.0. Project Overview
This project deals with implementation of chat bot named ZEN for BOFA to manage
its customers who are warming to its AI-driven virtual financial assistant which is
expected to surpassed 6 million users and to complete more than 35 million client
requests.
The proactive insights of this ZEN include, Daily client engagement, helps users to
host a simple transaction like money transfers, balance inquiries, digital banking
capabilities and to provide clients relevant timely guidance, help manage their
finances easier.
The milestones of ZEN in user engagement coincides with the introduction of a series
of new features which includes insights that offer clients personalized and proactive
guidance to help them stay on top of their finances say, increase in recurring charges,
including regular subscriptions, reward notifications, enrolment guidance and bill
payment remainders.
In addition to this, Zen should offer their clients with more flexibility and security on
daily spending through new functionality in the app which allows clients to set,
manage and control how much they spend on purchases or withdraw from ATM each
day.
Page 4 of 14
2.0. Project Goals & Objectives
2.1. Goals
2.1.1. To act as a virtual financial assistant -This enables personalised,
proactive, predictive financial insights to the customer.
2.1.2. Schedule day to day payments.
2.1.3. Helps to view changes in FICO credit score.
2.1.4. Every day banking – Manage your financial life with ease.
Page 5 of 14
3.0. Scope
3.1. In-Scope
The in-scope items of zen implementation comprise below:
3.1.1 Problem organization needs to solve:
BOFA is in seek of personalized proactive insights and guidance in order to
enhance the customer needs towards their financial insights to be addressed most
efficiently and effectively there by creating a win – win situation for both the
bank and customers.
3.1.2. Restrictions need to be considered:
Functionalities which are not - listed under goals and objectives are to
considered as restrictions.
3.1.3. Worthwhile of time and money invested in this solution:
This will be justified when ZEN achieves to surpassed 6 million users and to
complete more than 35 million client requests.
3.2. Out-of-Scope:
3.2.1Any requirements which are not discussed or specified as a part of this
requirement document are considered to be OUT SCOPE items.
4.2. Dependencies:
ZEN is meant to establish a vital integration between all banking modules like
transaction, saving account, checking account etc.
Page 6 of 14
5.0. Business Processes
5.1. As-Is
Considering the current situation BOFA doesn’t have an AI platform as a chat
bot to act as virtual financial assistant.
5.2. To-Be
Rolling out ZEN in BOFA's, which drives customers to the AI - driven virtual
financial assistant platform to accomplish the functionalities mentioned in the
goals and objectives.
Page 7 of 14
Process Flow diagram:
Page 8 of 14
6.1.7 How logic adaptors work:
A typical logic adapter designed to return a response to an input statement will use
two main steps to do this. The first step involves searching the database for a known
statement that matches or closely matches the input statement. Once a match is
selected, the second step involves selecting a known response to the selected match.
Frequently, there will be a number of existing statements that are responses to the
known match.
To help with the selection of the response, several methods are built into Chatterbot
for selecting a response from the available options.
Input statement – A statement, that closely matches an input to the chat bot.
Page 9 of 14
To get random response:
Attend the inbound calls from clients about inquiries, transactions and
customer support
Make an update on transactions to the client via email / SMS etc. through an
automated API service.
Personal Assistance
Professional Support
Page 10 of 14
Technical Support
Interaction with another VAs to build a strong and effective virtual team
Date rolling - Rule used to adjust the payment date if the schedule date is not
a Business Day
End Date - Also known as the Maturity date. The date of the last payment
Customized schedule:
The schedule consists of a series of dates that define exactly when payments will be
made.
The payment schedule can also be linked to achievement or fulfillment of certain
predefined tasks or events or even stages against which payments are required to be
made by one party to another
Page 11 of 14
Module 3: Every day banking
Monitor recurring charges – To monitor and intimate the customer on the increase /
decrease in their recurring bills / charges.
Card Assistance – To get a list of where your card information may be stored.
7.0. Annexures
7.1. Annexure A
7.2. Annexure B
Page 12 of 14