JP4628601B2 - Financial institution sales support system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a financial institution sales support system that can link, for example, registration of daily business reports, display of customer attributes, and display of important matters in transactions of financial products in order to support sales operations in financial institutions. It is.
[0002]
[Prior art]
In financial institutions such as securities companies that sell financial products such as investment trusts, systematization of daily business reports for registering contact details with customers, and systematization of customer attributes such as suitability of product transactions related to customers are being promoted. Yes.
[0003]
On the other hand, when financial institutions sell financial products, there are many cases where explanations about risks are not sufficiently given to customers, which causes troubles. Therefore, in accordance with the Financial Products Sales Act, which came into effect from April 2001, financial institutions are required to explain important matters in transactions of financial products such as characteristics and risks of financial products to customers when selling financial products. Mandatory.
[0004]
[Problems to be solved by the invention]
However, the current situation is that the registration of business daily reports and the display of customer attributes, including explanations of important matters in the transaction of financial products, are not well linked in operability. In addition, financial institutions need to explain important matters in the transaction of financial products depending on customers, but it is difficult to remember important matters without forgetting them.
[0005]
The present invention has been made in view of the above-mentioned problems, and by associating a daily business report with customer information, it becomes easy to link the registration of the daily business report and the display of customer attributes, thereby improving its operability. The purpose is to provide a financial institution sales support system.
[0006]
[Means for Solving the Problems]
In order to achieve the above-described object, the present invention is a financial institution sales support system that supports sales operations in a financial institution, and relates to a customer, a daily business report storage unit that stores contact details with a customer as a daily business report. Customer information storage means for storing predetermined information as customer information; data association means for associating the customer information stored in the customer information storage means with the business daily report stored in the business daily report storage means based on a customer; It is characterized by comprising.
[0007]
According to such a configuration, by associating the business daily report with the customer information, for example, it becomes easy to link the registration of the business daily report and the display of the customer attribute, and the operability can be improved. The data association means of the present invention can be configured to provide an identifier for identifying two or more related data, for example, or to associate predetermined storage areas in storage means such as a database with each other on an address. .
[0008]
The financial institution sales support system of the present invention further comprises customer information display means for displaying the customer information stored in the customer information storage means as a customer information display screen, and the customer information displayed by the customer information display means. The information display screen includes means for storing and registering the customer information in the customer information storage means.
[0009]
According to such a configuration, the display and registration of customer attributes can be linked, and the operability can be improved.
[0010]
Furthermore, in the financial institution sales support system of the present invention, the registration process by the means for registering is performed based on a process of displaying a predetermined item based on the customer information based on the customer information display screen. It is what.
[0011]
According to such a configuration, the creation of a daily business report, the display of customer information (attributes), and the display of predetermined items based on customer information such as important items of financial products can be linked. Information can be managed for each customer, and the sales employee can display the predetermined information (for example, explanation of important matters) based on the customer information (for example, customer attributes relating to necessity of explanation of important matters as customer information). It is possible to explain the predetermined matter (important matter) without forgetting it at the time of reception.
[0012]
In the embodiment of the present invention, there is provided a financial institution sales support system for supporting sales operations in a financial institution, which is information about customers and includes customer attributes including necessity of explanation of important matters in financial product transactions. And a database that stores and stores business daily reports that are contact details with the customer, customer attribute display means that displays the customer attributes, important matter display means that displays the important matters based on the customer attributes, There is disclosed a financial institution sales support system comprising business daily report registration means for registering business daily reports in the database.
[0013]
In the embodiment of the present invention, a financial institution sales support server for supporting business operations in a financial institution, which is information related to the customer and includes the necessity for explanation of important matters in transactions of financial products The business daily report that is the attribute and the contact details with the customer is stored in the database in association with each other, and the business daily report received from the financial institution sales support client for performing input from the user and output to the user is stored in the database. A financial institution sales support server is disclosed, which registers and transmits the customer attribute to the financial institution sales support client based on a request received from the financial institution sales support client.
[0014]
Further, in the embodiment of the present invention, the client is a financial institution sales support client that supports sales operations in a financial institution, creates a daily business report that is a content of contact with a customer, and the business daily report is used as the financial report described above. A request is transmitted to the financial institution sales support server in order to obtain customer attributes that are information related to the customer and include the necessity of explanation of important matters in the transaction of the financial product. A client for financial institution sales support is disclosed that displays the customer attributes received from the institution sales support server and displays the pre-registered important items based on the customer attributes. According to such a client, the display of the screen in accordance with the flow of contact with the actual customer is performed by linking the registration of the daily business report, the display of the customer attribute, and the display of the important items of the financial product. , Can reduce the burden of operating the sales staff. In addition, the sales staff can explain the important matters without forgetting when the customer responds based on the necessity of explaining the important matters in the customer attributes.
[0015]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. First, the configuration of a financial institution sales support system will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of a financial institution sales support system in the present embodiment. This financial institution sales support system includes a head office 100 and a branch office 200. The head office 100 includes a server 110 and a client 130 connected to the database 120. The branch 200 is composed of a client 130A. The client 130 and the client 130A perform the same operation. Further, there may be a plurality of clients 130 and clients 130A. The server 110 and the clients 130 and 130A are connected by an intranet 300.
[0016]
Note that the database 120 may be provided in the server 110, and the server 110 and the client 130 may be integrated, and is not limited to the form shown in FIG.
[0017]
Next, an outline of the operation of the financial institution sales support system will be described with reference to FIG. A salesperson at the head office 100 accesses the server 110 from the client 130 via the intranet 300. A sales employee in the branch 200 accesses the server 110 via the intranet 300 from the client 130A.
[0018]
The database 120 stores daily business reports, customer attributes, and the like in association with each other. Here, the business daily report is information in which the contents of one contact with a customer are stored. The customer attributes are basic information about the customer such as name, address and age, and information such as suitability of transactions including investment experience and necessity of explanation of important matters in transactions of financial products. Important matters in the transaction of financial products are information such as characteristics and risks of the financial products.
[0019]
The clients 130 and 130A display a business daily report registration screen that also serves as a business daily report display screen, a customer attribute display screen, and an important matter display screen, and accept input from the sales staff. Here, the business daily report registration screen is, for example, a “daily report save button” for registering a business daily report, customer code, date and time of contact with the customer, contact method with the customer, purpose of contact with the customer, proposed product, etc. This screen has an input function. The customer attribute display screen is a screen for displaying customer attributes, and includes, for example, an “important matter explanation button” for displaying an important matter display screen. The important matter display screen is a screen that displays an explanation of important matters in the financial product.
[0020]
In the present embodiment, the daily business report registration means is provided on the daily business report registration screen, and the customer attribute display means is provided on the customer attribute display screen.
[0021]
In response to the access from the clients 130 and 130A, the server 110 transmits the customer attributes and the like stored in the database 120 to the clients 130 and 130A. The server 110 registers the daily business report received from the clients 130 and 130A in the database 120.
[0022]
Here, all the operations in the server 110 and the clients 130 and 130A are realized by software. This software may be in the form of a Web application, for example.
[0023]
Next, details of the operation of the financial institution sales support system will be described with reference to FIGS. FIG. 2 is a flowchart showing an example of the operation of the financial institution sales support system in the present embodiment. Here, explanation will be given on the assumption that the salesperson of the head office 100 is in contact with the customer by telephone or face-to-face while browsing the screen displayed on the client 130 and performing input using the client 130. Note that the salesperson of the branch office 200 can perform the same operation using the client 130A.
[0024]
First, the client 130 displays a business daily report registration screen (S1). FIG. 3 is a diagram showing an example of the daily business report registration screen. Here, when the sales employee wishes to view the customer attribute in contact with the customer, for example, after inputting the customer code on the business daily report registration screen shown in FIG. Press the anchor 10 of the customer code.
[0025]
Here, the client 130 determines whether or not the salesperson desires to display the customer attribute display screen (S2). If the salesperson does not wish to display the customer attribute display screen (S2, N), the flow proceeds to processing S3.
[0026]
On the other hand, when the salesperson desires to display the customer attribute display screen (S2, Y), the client 130 transmits the customer code to the server 110 via the intranet 300. Receiving the customer code, the server 110 searches the database 120 for a customer attribute corresponding to the customer code, and transmits it to the client 130 via the intranet 300. The client 130 opens a new window and displays the customer attribute display screen (S11).
[0027]
FIG. 4 is a diagram illustrating an example of a customer attribute display screen. In the customer attribute display screen shown in FIG. 4, whether or not it is necessary to explain important matters in the transaction of the financial product is displayed in the column below the financial product name. The customer selects in advance whether or not it is necessary to explain important matters for each financial product, and the selected result is registered in advance in the customer attribute.
Here, the display of “necessary” indicating whether or not important matters need to be explained also serves as an “important matter explanation required button” for displaying an important matter display screen. When an important matter needs to be explained in contact with a customer, the sales employee presses an “important matter explanation button” corresponding to the financial product for which the important matter display screen is to be displayed. For example, when the sales employee desires to display the “stock” important item display screen, the sales representative presses the “important matter explanation button” 20 in the column under “stock” on the customer attribute display screen shown in FIG.
[0028]
Here, the client 130 determines whether or not the salesperson desires to display the important item display screen (S12). When the sales employee wants to display the important item display screen (S12, Y), the client 130 searches for an important item corresponding to the “important item explanation required button” pressed by the sales employee, and opens a new window. The item display screen is displayed (S21). Here, important matters in the transaction of each financial product are stored in the database 120 and may be transmitted from the server 110 to the client 130, or may be stored in the client 130.
[0029]
FIG. 5 is a diagram illustrating an example of an important matter display screen. Based on the important item display screen displayed on the client 130, the sales employee explains the important items of the financial product to the customer.
[0030]
When the explanation of the important matters in the transaction of the financial product is finished and the sales staff desires to end the important matter display screen, the sales staff instructs the end of the important matter display screen on the important matter display screen shown in FIG. In this case, by pressing the daily report registration button 40, the fact that the important matter has been explained as customer information is stored and registered. Here, the client 130 determines whether or not the salesperson desires to end the important item display screen (S22). If the salesperson does not wish to end the important matter display screen (S22, N), the flow returns to the process S22. On the other hand, when the sales employee desires to end the important item display screen (S22, Y), the client 130 closes the window and deletes the important item display screen (S23), and the flow returns to the process S13.
[0031]
If the salesperson does not want to display the important item display screen (S12, N), or after the important item display screen is deleted (S23), the client 130 determines whether the salesperson desires to end the customer attribute display screen. Is determined (S13). Here, when the sales employee desires to end the customer attribute display screen, the sales employee instructs the customer attribute display screen to end on the customer attribute display screen shown in FIG. If the salesperson does not wish to end the customer attribute display screen (S13, N), the flow returns to step S12. On the other hand, when the salesperson desires to end the customer attribute display screen (S13, Y), the client 130 closes the window and deletes the customer attribute display screen (S14), and the flow returns to the process S3.
[0032]
When the sales employee does not want to display the customer attribute display screen (S2, N), or after the customer attribute display screen is deleted (S14), the sales employee contacts the customer with the date and time of contact, the customer contact method, the customer Are input to the client 130 as a daily business report (S3).
[0033]
If the salesperson wishes to register the daily business report, he presses the “daily report save button” on the business daily report registration screen shown in FIG. Here, the client 130 determines whether or not the salesperson desires to register the daily business report (S4). If the salesperson does not wish to register the daily business report (S4, N), the flow proceeds to step S6. On the other hand, when the salesperson desires to register the daily business report (S4, Y), the client 130 transmits the daily business report to the server 110 via the intranet 300. The server 110 registers a daily business report in the database 120 (S5).
[0034]
If the salesperson wishes to end the business daily report registration screen, he or she instructs the business daily report registration screen to end on the business daily report registration screen shown in FIG. Here, the client 130 determines whether or not the salesperson wishes to end the business daily report registration screen (S6). If the salesperson does not wish to end the business daily report registration screen (S6, N), the flow returns to the process S2. On the other hand, if the salesperson wishes to end the business daily report registration screen (S6, Y), the client 130 closes the window, deletes the business daily report registration screen (S7), and ends this flow.
[0035]
As described in detail above, according to the embodiment of the present invention, the registration of the daily business report, the registration of customer attributes, and the display of important matters in the transaction of financial products are linked, thereby making it possible to The screen is displayed along the flow, and the operation burden on the sales staff can be reduced. In addition, by linking the display of customer attributes with the display of important matters in financial product transactions, sales representatives must remember when dealing with customers based on the necessity of explanation of important matters in customer attributes. Explain important matters.
[0036]
【The invention's effect】
As described above, according to the present invention, by associating the daily business report with the customer information, it becomes easy to link the registration of the daily business report and the display of the customer attribute, and the financial institution sales support improves the operability. The system can be provided.
[Brief description of the drawings]
FIG. 1 is a block diagram showing an example of the configuration of a financial institution sales support system in the present embodiment.
FIG. 2 is a flowchart showing an example of the operation of the financial institution sales support system in the present embodiment.
FIG. 3 is a diagram showing an example of a business daily report registration screen.
FIG. 4 is a diagram illustrating an example of a customer attribute display screen.
FIG. 5 is a diagram illustrating an example of an important matter display screen.
[Explanation of symbols]
100 head office, 110 server, 120 database, 130, 130A client, 200 branch offices, 300 intranet.

Claims (2)

A financial institution sales support system for supporting sales operations in a financial institution,
Customer information, including customer attributes including the necessity of explanation of important matters in each of the transactions of multiple financial products registered for each customer, business daily reports that are the contents of contact with the customers, and importance in each of the financial products A financial institution sales support server having a database for storing explanations of matters,
A business daily report registration screen for accepting input of the business daily report from the user, a customer attribute display screen for displaying necessity of explanation of important matters included in the customer attributes for each transaction of a plurality of financial products, and the important matters A client for financial institution sales support having an important matter display screen for displaying an explanation of
The financial institution sales support client, when the business daily report is input from the user on the business daily report registration screen, transmits the input business daily report to the financial institution sales support server,
When receiving the customer code input from the user through the business daily report registration screen, the customer code is transmitted to the financial institution sales support server,
When the customer attribute is received from the financial institution sales support server, the necessity of explanation of important matters included in the customer attribute is displayed on the customer attribute display screen for each transaction of a plurality of financial products,
Upon receiving a request to display the explanation of the important matter from the user on the customer attribute display screen, the request is transmitted to the financial institution sales support server,
When the explanation of the important matter is received from the financial institution sales support server, the explanation of the important matter is displayed on the important matter display screen,
The financial institution sales support server receives the business daily report from the financial institution sales support client, registers the business daily report in the database,
When a customer code is received from the financial institution sales support client, the customer attribute corresponding to the customer code is retrieved from the database and transmitted to the financial institution sales support client,
Receiving a request for displaying the explanation of the important matter from the financial institution sales support client, searching for the explanation of the important matter corresponding to the request from the database, and transmitting to the client for financial institution sales support. A characteristic financial institution sales support system. A financial institution sales support system for supporting sales operations in a financial institution,
Finance having a database for storing customer attributes including information on necessity and explanation of important matters in each of a plurality of financial products registered for each customer and a daily business report that is a contact content with the customer. An institutional sales support server;
A business daily report registration screen for accepting input of the business daily report from the user, a customer attribute display screen for displaying necessity of explanation of important matters included in the customer attributes for each transaction of a plurality of financial products, and the important matters A client for financial institution sales support having an important matter display screen for displaying the explanation of and a storage unit for storing an explanation of important matters in each of the financial products,
The financial institution sales support client, when the business daily report is input from the user on the business daily report registration screen, transmits the input business daily report to the financial institution sales support server,
When receiving the customer code input from the user through the business daily report registration screen, the customer code is transmitted to the financial institution sales support server,
When the customer attribute is received from the financial institution sales support server, the necessity of explanation of important matters included in the customer attribute is displayed on the customer attribute display screen for each transaction of a plurality of financial products,
When receiving a request to display the explanation of the important matter from the user on the customer attribute display screen, search the explanation of the important matter corresponding to the request from the storage unit storing the explanation of the important matter in each of the financial products, An explanation of the retrieved important matter is displayed on the important matter display screen,
The financial institution sales support server receives the business daily report from the financial institution sales support client, registers the business daily report in the database,
When a customer code is received from the financial institution sales support client, the customer attribute corresponding to the customer code is retrieved from the database and transmitted to the financial institution sales support client. system.

Images