BUSINESS REQUIREMENT DOCUMENT
Functionality
Name: Branch Channel
Submitted by: Dolee Boruah
BRANCH CHANNEL
Contents
Version and Approvals ........................................................................................................................... 2
Project Details........................................................................................................................................ 2
1. Overview: ................................................................................................................................... 3
2. Process Flow: .............................................................................................................................. 3
3. Proposed process in SFDC: ........................................................................................................ 4
4. SFDC to Insurance Mart Flow: .................................................... Error! Bookmark not defined.
5. Report/Auto Mailer Requirement ............................................................................................. 14
6. API Integration requirement ..................................................................................................... 13
7. Impact Analysis: ....................................................................................................................... 14
8. Functional Test Scenarios ......................................................................................................... 14
9. Priority Calculator..................................................................................................................... 14
1|Page
BRANCH CHANNEL
Version and Approvals
VERSION HISTORY
Version # Date Author/Revised by Reason for change
0.1 05-12-2018 Dolee Boruah
0.2 23-02-2019 Dolee Boruah Revision done in process
Following approval of this document, requirement changes will be governed by the project’s change management
process, including impact analysis, appropriate reviews and approvals.
DOCUMENT APPROVALS
Approver Name Project Role Signature/Electronic Approval Date
Mayank Pandya Senior Manager - Insurance, FD &
Investments COE, IT, PMO & Digital
Initiatives
Aniket Gade National Manager - Insurance,
Telebinding
Pradeepta Morajkar National Manager - Insurance, FD
& Investments COE, Product &
Process Capabilities
PrinceAsir Prakash Senior Manager - Insurance, FD &
Investments COE, Product &
Process Capabilities
Project Details
Project Name Branch Channel
Project Type New business model set up
Project Start Date
Project End Date
Project Owner Rishikesh Mohite
Stakeholders
Project Manager Mayank Pandya
2|Page
BRANCH CHANNEL
1. Overview:
The objective of this BRD is to set up new business model in SFDC HTS.
A new business named as ‘Branch’ is launched for Semi Rural customer segment. Under this channel
Insurance partner’s sales agents based at BFL branches will be selling insurance products to branch
walk in customers and leads which will be allocated to sales agent in SFDC.
Customers targeted can be either existing BFL customers or new customers.
Tablets will be provided to each sales agent to complete data entry and sales process. Entire policy
journey will be processed through partner’s app. However, lead allocation to sales agent will be done in
BFL SFDC application.
Every sales agent will have individual access to BFL SFDC and partner’s applications.
2. Proposed Process Flow:
2.1. Scenario 1: Existing BFL Customer
For existing BFL customer, Sales Agent is required to fetch customer details in partner’s app with
BFL customer id. Below process is to be followed. KYC docs are not required for policy
processing of such customers.
Demographic details fields of customers to be kept editable in partner’s app, to capture revised
details, if any. If details are changed then KYC docs are required.
3|Page
BRANCH CHANNEL
2.2. Scenario 2: New Customer without BFL ID
For new customers whose BFL customer id is not available, below process flow is to be followed.
KYC docs to be collected by Sales Agent for policy processing of such customers.
2.3. Scenario 3: Manual Forms Journey
For customers where manual forms are collected, below process to be followed.
KYC docs to be collected by Sales Agent for policy processing of such customers.
Scenario 4: Cashier Leads (System configuration to be developed in development phase II)
Scenario 5: Marathon leads (System configuration to be developed in development phase II)
Scenario 6: Prospect leads (System configuration to be developed in development phase II)
4|Page
BRANCH CHANNEL
3. Proposed process in SFDC HTS
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 01
Business Requirement Description : - New Home Page creation and display of tiles
-----------------------------------------------------------------------------------------------------------------------------
A new homepage to be designed for ‘Branch’ model business named as ‘Branch’.
On Branch homepage, new page should open and below tiles/options should get displayed to
select.
1. New Lead – All fresh leads (existing BFL customers) allocated to FOS should reflect under this.
2. Lead List – All leads (existing BFL customers) allocated till date to FOS should reflect under this. In
the front end, below fields are required to be displayed.
Mobile 989XX-XXXXX
Customer id 334822XXXX
Customer name FirstName LastName
Customer segment e.g, Affluent/Mass Affluent etc
Wealth surplus Value to be populated from Income and Expense details
Pre-Approved Sum Assured Value to be populated from product section
Note: Above details of leads will also be shown in other sections for leads (New, Follow-up, Prospect Leads)
3. Follow up Lead – All leads where FOS has marked interaction with follow up disposition should
reflect under this.
4. Prospect Lead – All fresh leads allocated to FOS, where customer id is not available should reflect
under this. Mobile number is the unique identifier for such leads. (Tile to be developed in phase II)
5. New to Bajaj – A search high level search should be available, where user will search the Lead basis
the basic lead details.
Below are the fields which are required to search on the high level.
Fields Mandatory / Non-Mandatory
First Name Mandatory
Last Name Mandatory
Date of Birth Non-Mandatory
Mobile Number Mandatory
PAN Non-Mandatory
If lead is available then the FOS should be able add the interactions and should get tagged to the FOS.
6. Target - Product team should be able to set target to sales agents and track users achievement in
this tile. Dashboard should get displayed with number of leads allocated, sale closed, policies
issued, premium collected etc details, as provided below.
5|Page
BRANCH CHANNEL
i. Total Leads allocated (Today, This Month, Quarter).
ii. Lead conversion rate and count (Today, This Month, Quarter).
iii. Calling Details (Leads Called Day, week, month)
iv. Product wise sales count
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 02
Business Requirement Description : - Lead allocation
-----------------------------------------------------------------------------------------------------------------------------
Round robin lead allocation logic based on pin code currently available in Insurance Distribution
channel is required for Branch channel.
A Notification count should be shown to the user which will have a count of new leads which are
allocated. This notification should be available on the New-Lead Icon/section.
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 03
Business Requirement Description : - Calendar
-----------------------------------------------------------------------------------------------------------------------------
Calendar view is required.
FOS should be able to see appointment/Follow ups in Calendar.
Notifications should be pushed to the users which are scheduled for the day.
6|Page
BRANCH CHANNEL
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 04
Business Requirement Description : - Customer Profile
Customer Profile tab is required under every Lead sections (New, Follow-up, Prospect Leads) except
target tab.
Customer Profile will display the customer details (Demographic, Loan Info, Income/Expenses),
Interactions, Products.
Below sections are required under Customer Profile tab:
1. Customer Details
2. Interaction Details
3. Products
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 04
Functional Requirement ID :- FR01
Business Requirement Description : - Customer Details
-----------------------------------------------------------------------------------------------------------------------------
This section will display customer details containing the basic details. These details will be viewable
only and users won’t be allowed to update any details.
Section and fields required under customer details tab are provided below:
Customer Details
Section Fields
Customer Title
Customer First Name
Customer Middle Name
Customer Last Name
Customer's DOB
Place of birth
Demographic Details
Gender
Marital status
Email id
Mobile number
Occupation
Preferred language
Address Details
Address Line 1
Residence Address
Address Line 2
7|Page
BRANCH CHANNEL
Address Line 3
Area Locality/Landmark
City
State
Country
Pin Code
Address Line 1
Address Line 2
Address Line 3
Area Locality/Landmark
Office Address
City
State
Country
Pin Code
Cibil score
Bajaj Loan
Loans Information
Other Loans
Summarised view
Net Annual Income
Income and Expense Details
Current Savings/Wealth Surplus
Note: All fields are required to be kept configurable, so that additions/changes can be made
whenever required.
8|Page
BRANCH CHANNEL
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 04
Functional Requirement ID :- FR02
Business Requirement Description : - Interaction Details
-----------------------------------------------------------------------------------------------------------------------------
This section will be used by the FOS to enter interaction details.
Two sections are required under this – New interaction and Previous interaction.
User will always do new entry under new interaction tab, post interaction with customer. No
updates should be allowed to the previous interaction entries.
Interactions for which the FOS is marking the lead under Appointment/follow-up, those should
appear under ‘Follow-up Lead’ section available on home page.
Leads marked for appointment/Follow-up should be available in calendar.
Interaction details: Fields required under interaction details are provided below.
For below 5 dispositions, sub fields should be available for the users to update the interactions
carried out.
Appointment
Disposition Sub Disposition Channel
Date
Mandato
ry / Non Picklist Mandatory/N
Picklist value
Mandato value on-Mandatory
ry
Issuance pending Mandato NA Non-
Sale NA
Issued ry (Default) Mandatory
Mandato NA Non-
Appointment Meeting Date Field
ry (Default) Mandatory
Busy
Disconnected by Customer
Not Mandato NA Non-
Not reachable NA
Contactable ry (Default) Mandatory
Switched Off
Wrong number
Already have policy
Do not call
Financial problem
Not Insured by employer Mandato NA Non-
NA
Interested ry (Default) Mandatory
Interested in other product
Service issues with BFL
Service issues with insurance
partner
9|Page
BRANCH CHANNEL
Telephonic Mandato NA Non-
Follow Up Date Field
Meeting ry (Default) Mandatory
Sale disposition: below sub fields are required and all fields should be mandatory.
Disposition Insurance company Insurance product Sum Assured Premium Term Mode of payment
Sale
Insurance company and Insurance Product for selection should be as below.
Insurance Company Insurance Sub Category Insurance Product
Savings POS Goal Suraksha
ULIP Future Gain
BALIC Term iSecure
Term eTouch
Savings LifeLong Assure
New Assure Plus
Traditional
Traditional Assured Money Back Plan
Traditional
FUTURE GENERALI Big Income Multiplier
Traditional Assured Income Plan
ULIP Bima Advantage Plus
Traditional
Wealth Protect Plan
All the above details (Insurance Company, Insurance Sub Category and Insurance Product)
should be configurable and a provision where admin can active/deactivate the product if
required.
10 | P a g e
BRANCH CHANNEL
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 04
Functional Requirement ID :- FR03
Business Requirement Description : - Product Details
-----------------------------------------------------------------------------------------------------------------------------
1. Products: In this channel, FOS are from insurance partner (BALIC, HDFC Life, Future Generali
etc) and they will source only their own company products. So, it is required to display
insurance products of respective companies in SFDC ids of FOS.
Fields under product section are required to be kept configurable to allow addition/changes in
products whenever required.
Pre-approved sum assured will be provided against every lead by Ins COE to Branch team for uploading
in SFDC before lead allocation is done.
Insurance Insurance Insurance Sub Pre-Approved Sum
Insurance Product
Company Category Category Assured
Life Savings POS Goal Suraksha
Life ULIP Future Gain
BALIC Life Term iSecure
Life Term eTouch
Life Savings LifeLong Assure
New Assure Plus
Life Traditional
Life Traditional Assured Money Back Plan
FUTURE
Life Traditional Big Income Multiplier
GENERALI
Life Traditional Assured Income Plan
Life ULIP Bima Advantage Plus
Life ULIP Wealth Protect Plan
11 | P a g e
BRANCH CHANNEL
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 05
Business Requirement Description : - Insurance page/Wallet Record
-----------------------------------------------------------------------------------------------------------------------------
Insurance page/Wallet Record is required in SFDC for tracking of all policy details.
For every insurance record, insurance id should get generated. Policy data will be pushed from
insurance partner’s system, once application number/policy number gets generated in partner’s
system.
Data pushed from insurance partner’s end, should get captured in respective fields in insurance page.
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 06
Business Requirement Description : - New to Bajaj customer creation
-----------------------------------------------------------------------------------------------------------------------------
For new to Bajaj customers whose data is received in data push API without customer id,
customer id should get auto created based on details received from insurance partner.
This will also impact on the FOS sales count which will be displayed in the ‘Targets’ section
displayed on home page.
For new customers, auto dedupe/ auto linking to best match should happen, or auto creation
of customer should happen if no customer match is found in existing base.
Data inputs/Fields required for creation of new customers are provided in the attached sheet.
New customer id created should get tagged in customer id field in insurance page/ wallet page
against insurance id/ insurance wallet id.
12 | P a g e
BRANCH CHANNEL
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 07
Business Requirement Description : - Exotel – Click to Call
-----------------------------------------------------------------------------------------------------------------------------
Exotel – Click to Call functionality is required to be developed in same lines as PLCS business.
(System development to be taken up in phase II)
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 08
Business Requirement Description : - Flow of data from SFDC to Insurance Mart
-----------------------------------------------------------------------------------------------------------------------------
Insurance data captured in SFDC are required to auto flow to Insurance Mart. (System development to
be taken up in phase II)
5. API Integration requirement
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 01
Business Requirement Description : - Customer Search/fetch API
-----------------------------------------------------------------------------------------------------------------------------
Customer search API to be built between SFDC HTS and Partner’s App:
As per current process, customer fetch API is built between SFDC STS and BALIC INSTAB.
Need to extend existing customer fetch API services between SFDC HTS and all partner’s app.
Branch Model
Fetch API Spec Document [Link]
-----------------------------------------------------------------------------------------------------------------------------
Business Requirement ID :- 02
Business Requirement Description : - Data Push API
-----------------------------------------------------------------------------------------------------------------------------
Data Push API to be built between partner’s app and SFDC HTS:
i) Post policy processing journey in partner’s app (for existing and new BFL customers) and
partner’s core system (manual applications), data should be pushed to SFDC HTS for every
application. Frequency/stages of data push API to be confirmed with partners.
13 | P a g e
BRANCH CHANNEL
ii) Based on application number received from partner, insurance id and insurance page
should get created in SFDC to capture policy data.
iii) For applications where BFL customer id is not available, BFL customer id should get auto
created based on New to Bajaj customer creation functionality and get tagged to insurance
id for every application number.
Fields that needs to be stamped in SFDC HTS through Data Push API from insurance partner and vice
versa needs to be re-discussed with SFDC IT PO Team.
6. Report/Auto Mailer Requirement
a. Require system generated MIS from insurance partners to track issuance records.
b. Require system generated report from SFDC to track insurance business done.
7. Impact Analysis:
SYSTEM Yes No
SFDC-HTS ×
SFDC-STS ×
Integration Team X
Experia Web ×
Experia App ×
DataMart X
FinnOne X
ODM/Galaxie Portal ×
8. Functional Test Scenarios
Sr. Business Scenario Scenario Description Expected Result
No.
1 Insurance Page Data pushed from In insurance page, insurance
insurance partner should data pushed from insurance
get updated partner should get updated.
9. Priority Calculator
Priority
[Link]
14 | P a g e
