JP2021022164A - Business support system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a sales support system capable of easily migrating from a CRM server to an information providing server in cooperation with a CRM server and an information providing server, particularly for a market event. SOLUTION: A brand matching the conditions of a market event is extracted from the market information imported by a CRM server 1, a customer holding the extracted brand is extracted, a brand corresponding to the customer, a type of a condition of a market event, etc. Event information is generated, and a list of event information is generated as a market event list. When the type of market event condition is selected from the list, the company information of the related brand on the information providing server 7 is displayed. It is a sales support system. [Selection diagram] Fig. 1

Description

The present invention relates to a sales support system, and more particularly to a sales support system capable of easily linking a CRM (Customer Relationship Management) server and an information providing server.

[Conventional technology]
The conventional sales support system is provided with a CRM server that manages customers, and is a device different from the information providing server that provides information such as stock prices, and it is necessary to operate to access each server.

[Related technology]
As a related prior art, there is Japanese Patent Application Laid-Open No. 2019-101607 “Sales Support System for Structured Bonds” (Patent Document 1).
Patent Document 1 shows a sales support system that allows a salesperson to easily grasp the conditions of structured bonds by displaying stock information on complicated structured bonds on a customer's deposit details and transaction details. There is.

JP-A-2019-101607

However, in the above-mentioned conventional sales support system, the CRM server and the information providing server are not linked, and there is a problem that it is inconvenient especially when it is desired to go back and forth between the two servers for a market event.

It should be noted that Patent Document 1 does not describe the cooperation between the CRM server and the information providing server.

The present invention has been made in view of the above circumstances, and it is intended to cooperate with the CRM server and the information providing server, and to provide a sales support system capable of easily migrating from the CRM server to the information providing server, particularly for market events. The purpose.

The present invention for solving the problems of the above-mentioned conventional example is a sales support system having a sales support server linked with an information providing server, in which the sales support server inputs market information from the information providing server and markets. The stocks that match the event conditions are extracted, the customers who hold the extracted stocks are extracted, the stocks corresponding to the customers, the event information of the type of market event conditions are generated, and the list of event information is displayed in the market event. It is characterized in that it is generated as a list and the related information of the brand related to the event information is acquired from the information providing server.

In the above-mentioned sales support system, the sales support server displays a list of market events on the terminal device to which the sales support server is connected, and when a specific market event condition type is selected from the market event list, the information providing server It is characterized by displaying the action information of the company of the brand related to the event information on the terminal device.

According to the present invention, in the above-mentioned sales support system, when a customer is selected from a list of holding customers of a brand provided by an information providing server in the terminal device, the sales support server displays a customer attribute screen on the terminal device. It is a feature.

In the above-mentioned sales support system, when a link button provided for each issue is selected on the detail screen of the issue entrusted by the customer on the terminal device, the sales support server displays the stock price provided by the information providing server. The feature is that the screen is displayed on the terminal device.

The present invention relates to the above-mentioned sales support system when the sales support server shifts to the screen provided by the information providing server, or when the screen provided by the information providing server shifts to the screen of the sales support server. It is characterized by performing login authentication at the migration destination.

According to the present invention, the sales support server inputs market information from the information providing server, extracts stocks that match the conditions of the market event, extracts customers who hold the extracted stocks, and responds to the customers. Since it is a sales support system that generates event information of the type of brand and market event condition, further generates a list of event information as a market event list, and acquires related information of the brand related to the event information from the information providing server. , Event information can be easily transferred to related information of related issues, and there is an effect that sales support for customers can be easily performed.

It is a schematic diagram of this system. It is a figure which shows the market event generation / display processing flow. It is a figure which shows the display processing flow of the information providing server from a cooperation button. It is a figure which shows the customer attribute screen display processing flow of CRM from the possession customer list screen of an information providing server. It is a figure which shows the company information display processing flow of the information providing server from a CRM market event. It is a figure which shows the transition of the market event display screen. It is a figure which shows the transition from the CRM deposit detail screen to the stock price display screen of an information providing server. It is a figure which shows the transition from the possession customer screen of an information providing server to the customer attribute screen of CRM. It is a figure which shows the transition from the CRM market event search screen to the corporate action screen of an information providing server.

Embodiments of the present invention will be described with reference to the drawings.
[Outline of Embodiment]
The sales support system (this system) according to the embodiment of the present invention extracts a brand that matches the conditions of the market event from the market information imported by the CRM server, extracts the customer who holds the extracted brand, and the customer. Generates event information such as the brand corresponding to, the type of market event condition, and further generates a list of event information, and when the type of market event condition is selected from the list, the related brand on the information providing server. It displays the company information, etc. of the customer, can easily shift from the CRM market event to the related company information, etc., and can easily provide sales support to the customer.

[This system: Fig. 1]
This system will be described with reference to FIG. FIG. 1 is a schematic view of this system.
As shown in FIG. 1, this system includes an AP (Application) server 1, a CRM database (DB) 2, a data acquisition server 3, a terminal device 4, an internal network 5, an external network 6, and information. It is provided with a providing server 7.
The AP server 1, CRMDB2, data acquisition server 3, and terminal device 4 are connected to the in-house network 5, and the data acquisition server 3 and information providing server 7 are connected to the external network 6.
The AP server 1 may be referred to as "CRM server 1".

[Each part of this system]
Next, each part of this system will be described.
[AP server 1 (CRM server 1]
The AP server 1 is a computer processing device, and includes a control unit, a storage unit, and an interface unit connected to the in-house network 5.
Then, the AP server 1 accesses the customer information of the CRMDB2, provides the customer information to the terminal device 4, and stores the sales activity information input from the terminal device 4 in the CRMDB2.
Further, the AP server 1 is a CRM server that operates the CRM application stored in the storage unit in the control unit and realizes the processing described later.

[CRMDB2]
The CRMDB2 is a storage device that stores data, and includes a control unit, a storage unit, and an interface unit that connects to the in-house network 5.
Then, CRMDB2 stores information such as sales person information, customer information, and securities owned by the customer.

[Data acquisition server 3]
The data acquisition server 3 is a computer processing device, and includes a control unit, a storage unit, and an interface unit that connects to the internal network 5 and the external network 6.
Then, the data acquisition server 3 connects to the external network 6, acquires information from the outside, and provides it to the internal network 5.

[Terminal device 4]
The terminal device 4 is a computer device, includes a control unit, a storage unit, an interface unit, a display unit, and an input unit, and is connected to the in-house network 5.
Then, the terminal device 4 accesses the AP server 1 via the in-house network 5 and displays CRM-related information and information from the information providing server 7. A display example on the terminal device 4 will be described later.

[Internal network 5, External network 6]
The in-house network 5 is realized by using a LAN (Local Area Network) or the like.
The external network 6 assumes the Internet or the like.

[Information provision server 7]
The information providing server 7 is a computer processing device, and includes a control unit, a storage unit, and an interface unit that connects to an external network 6.
Then, the information providing server 7 constantly provides stock information such as stock prices, stock-related news, corporate information, and the like to a computer device or the like connected to the external network 6.
The cooperation processing of the information providing server 7 with the AP server 1 will be described later.

[Outline processing in this system]
The outline of the processing in this system will be described.
The data acquisition server 3 acquires market information from the information providing server 7 and stores it in the CRMDB2.
The types of conditions for market events are the plunge rate of foreign stocks, the plunge rate of investment trust distributions, the plunge rate of investment trust base prices, earnings revision data (sales, ordinary profit, etc.), public offering / sale information, etc.
In addition, the conditions of the market event show an index of the market (market) trend.

The CRM server (AP server) 1 generates a market event based on a preset market trend index (market event conditions) from the captured market information, and market event list information according to an instruction from the terminal device 4. Is displayed. Market events are generated on a regular basis, once or multiple times a day.
Specifically, the types of conditions for market events are "public offering / sale", "decrease in investment trust base price", "reduction in investment trust distribution", "decrease of foreign stocks (foreign stocks) by more than 000% from the previous day", and "review / revision of business performance". , Etc., the presence or absence of these becomes a judgment criterion.

Specifically, the CRM server 1 extracts stocks that match the conditions of the market event.
Stocks that meet the conditions are stocks whose crash rate of foreign stocks is a predetermined value, stocks whose investment trust distribution is reduced, stocks whose base price has fallen to a predetermined value for investment trusts held for three months, and earnings revision data. The stocks that are occurring and the stocks that have been publicly offered or sold.

Then, the CRM server 1 generates event information corresponding to the customer (generation of market event).
Specifically, the CRM server 1 collates the customer attributes and deposit balance imported from the accounting system (CRMDB2) with the information of the extracted brand, extracts the customer who owns the extracted brand, and responds to the customer. Information (event information) such as a brand, a type of condition of a market event, and an occurrence date is generated, and further, a list of the event information (market event list) information is created.

Then, when the type of market event condition is selected from the market event list information displayed on the terminal device 4, the CRM server 1 provides information on parameters (for example, brand code) related to the selected market event condition type. Output to the providing server 7, the information providing server 7 acquires related information (for example, stock price information, etc.) according to the parameter and sends it to the CRM server 1, and the CRM server 1 displays the related information on the terminal device 4. ..
Related information includes stock price information corresponding to a stock, transfer information of a company (corporate) corresponding to a stock, company stock information, action information such as public regulation, and the like.

[Specific processing in this system]
Next, specific processing in the CRM server 1, the terminal device 4, and the information providing server 7 in this system will be described.
Specific processing includes market event (event information) generation / display processing, information provision server 7 display processing from the link button, CRM customer attribute screen display processing from the owned customer list screen of the information provision server 7, and CRM market. There is a company information display process of the information providing server 7 from the event.

[Market event generation / display processing: Fig. 2]
Next, the market event generation / display processing on the CRM server 1 in this system will be described with reference to FIG. FIG. 2 is a diagram showing a market event generation / display processing flow.
As shown in FIG. 2, the CRM server 1 performs a process of fetching market information from the data fetching server 3 from the information providing server 7 (S11).

The CRM server 1 extracts stocks and customers that meet the predetermined judgment conditions based on the imported market information, and lists information (event information) such as stocks, market events, and occurrence dates corresponding to the customers (market event list). ) Is generated (market event generation process) (S12).
Then, it is determined whether or not there is a market event display instruction from the terminal device 4 (S13), and if there is a display instruction (in the case of Yes), the customer information is read from CRMDB2 and the market event list screen is displayed on the terminal device 4. (S14). The market event list screen will be described later with reference to FIG. If there is no market event display instruction (if No), the process proceeds to the determination process S15.

Next, the CRM server 1 determines whether or not it is the time when the market event is generated (S15). This is to generate a market event at a predetermined time.
If it is the time of market event generation (in the case of Yes), the process returns to process S11, and if it is not the time of market event generation (in the case of No), then it is determined whether or not today's market event generation is finished. (S16) If it is not finished (in the case of No), the process returns to the determination process S15, and if it is finished (in the case of Yes), the process is finished.

[Transition of market event display screen: Fig. 6]
The transition of the market event display screen in the terminal device 4 will be described with reference to FIG. FIG. 6 is a diagram showing a transition of the market event display screen.
In the terminal device 4, a salesperson (CRM person in charge) accesses CRMBD2 and displays the screen of the CRM person in charge (FIG. 6A).
On the CRM staff screen, "event" is displayed in the category column and "market event" is displayed in the notification content column. When "market event" is selected, the market event search screen is displayed (Fig. 6). (B)).

On the market event search screen, as a list of input items for the market event, one of the handler code, the handler name, the customer code, the customer name, the brand code, the brand name, the market event, and the correspondence status is input to perform the search. Here, the type of the market event is specified and can be selected from the pull-down menu, and the response status is to select whether or not the event has been supported by the pull-down menu.

When a market event is searched from the market event search screen, a market event list display screen is displayed on the terminal device 4 (FIG. 6 (c)).
On the market event list display screen, the handler code / handler name, customer code / customer name, brand code / brand name, market event, and occurrence date are displayed as search results.

[Display processing of information providing server from link button: Fig. 3]
Next, when the CRM server 1 of this system causes the terminal device 4 to display the customer's deposit details, the display process of the information providing server from the cooperation button displayed on the deposit details screen will be described with reference to FIG. To do. FIG. 3 is a diagram showing a display processing flow of the information providing server from the cooperation button.
As shown in FIG. 3, the CRM server 1 determines whether or not the information providing server 7 can be used when the terminal device 4 displays the customer's deposit details (S21). Specifically, the CRM server 1 stores an authenticated login ID and password for using the information providing server 7 in advance, and determines whether or not the ID and password exist.

If the information providing server 7 can be used (in the case of Yes), a link button is displayed on the stock deposit statement screen (S22). If it is not used (in the case of No), the link button is not displayed on the deposit details screen (S23).
Then, when the cooperation button displayed on the deposit details screen is selected, the process shifts to the information providing server 7 and displays information such as the stock price of the corresponding issue (S24). When migrating to the information providing server 7, the stored ID and password are output to the information providing server 7, login authentication is performed, and the related stock price and the like are displayed. After that, the process ends when the screen display ends.

[Transition from CRM deposit details screen to stock price display screen: Fig. 7]
Next, the transition from the CRM deposit details screen to the stock price display screen of the information providing server will be described with reference to FIG. 7. FIG. 7 is a diagram showing a transition from the CRM deposit details screen to the stock price display screen of the information providing server.
As shown in FIG. 7, the CRM server 1 determines whether or not an ID and a password for logging in to the information providing server 7 exist when displaying the CRM deposit details screen, and if so, a link button (cooperation). The CRM deposit details screen on which the button) is displayed is displayed (FIG. 7 (a)).

On the CRM deposit details screen, the customer code and the customer name are displayed, and the link button "LB" is displayed according to the brand code and the brand name.
Then, when this link button is selected, the information providing server 7 is logged in with the stored ID and password, and when login (login authentication) is performed, the stock price display screen of the information providing server 7 is displayed (FIG. 7). (B)).

[Customer attribute screen display processing from owned customer list screen: Fig. 4]
Next, the customer attribute screen display process of CRM from the owned customer list screen of the information providing server 7 will be described with reference to FIG. FIG. 4 is a diagram showing a customer attribute screen display processing flow of CRM from the owned customer list screen of the information providing server.
As shown in FIG. 4, the terminal device 4 requests the CRM server 1 to display the customer attribute from the state where the owned customer list screen of the information providing server 7 is displayed (S31), and makes a CRM login determination (S31). S32).

When the terminal device 4 makes a request to the CRM server 1, the determination process S32 outputs an ID and password for logging in to the CRM server 1 to the CRM server 1, and the CRM server 1 determines whether the ID and password are appropriate. If it is appropriate and login is possible (in the case of Yes), the customer attribute screen of CRM is displayed (S33).

In the determination process S32, if the login is rejected (No), an error response indicating that the CRM customer attribute screen cannot be displayed on the terminal device 4 is performed (S34), and the screen returns to the owned customer list screen of the information providing server 7. (S35). Then, the process ends when the screen display ends.

[Transition from owned customer list screen to customer attribute screen: Fig. 8]
Next, the transition from the owned customer screen displayed on the information providing server 7 to the customer attribute screen of CRM will be described with reference to FIG. FIG. 8 is a diagram showing a transition from the owned customer screen of the information providing server to the customer attribute screen of CRM.
First, in the terminal device 4, the information providing server 7 displays a list screen of owned customers for a specific brand (FIG. 8A). On the owned customer list screen, "handler code / handling name", "customer code / customer name", "deposit classification", and "quantity" are displayed.

When a specific "customer code / customer name" is selected on the owned customer list screen, if the CRM server 1 can be logged in, the CRM server 1 accesses CRMDB2 and displays the CRM customer attribute screen ( FIG. 8 (b). On the customer attribute screen, the customer name, address, etc. are displayed.
The owned customer screen provided by the information providing server 7 can be easily switched to the CRM customer attribute screen provided by the CRM server 1.

[Transition from market event search screen to corporate action screen: Fig. 9]
Next, the transition from the CRM market event search screen provided by the CRM server 1 to the corporate action screen provided by the information providing server 7 will be described with reference to FIG. FIG. 9 is a diagram showing the transition from the market event search screen to the corporate action screen.

The CRM server 1 displays the market event search screen on the terminal device 4 (FIG. 9 (a)), and when the market event is searched, the market event list display screen is displayed (FIG. 9 (b)). Therefore, when the market event of "public offering / sale" is selected, the corporate action screen provided by the information providing server 7 is displayed on the terminal device 4 regarding the actions of the company related to the public offering / sale.
On the corporate action screen, movement information of the company (brand name), company stock, public regulations, etc. are displayed.
In this way, the transition from the market event search screen to the corporate action screen can be easily performed.

[Effect of Embodiment]
According to this system, stocks that match the conditions of the market event are extracted from the market information imported by the CRM server 1, customers who hold the extracted stocks are extracted, and the stocks corresponding to the customers and the conditions of the market event are met. Event information such as type is generated, and a list of event information is generated as a market event list. When the type of market event condition is selected from the list, the company information of the related brand on the information providing server 7 is displayed. It is displayed, and there is an effect that it is possible to easily shift from a CRM market event to related company information and the like, and it is possible to easily provide sales support to customers.

The present invention is suitable for a sales support system in which a CRM server and an information providing server are linked, and in particular, a market event can be easily migrated from the CRM server to the information providing server.

1 ... AP (CRM) server, 2 ... CRMDB, 3 ... Data acquisition server, 4 ... Terminal equipment, 5 ... Internal network, 6 ... External network, 7 ... Information providing server

Claims (5)

A sales support system that has a sales support server that works with an information providing server.
The sales support server inputs market information from the information providing server, extracts stocks that match the conditions of the market event, extracts customers who hold the extracted stocks, and stocks and markets corresponding to the customers. A business characterized by generating event information of a type of event condition, further generating a list of the event information as a market event list, and acquiring related information of a brand related to the event information from the information providing server. Support system. When the sales support server displays a list of market events on the terminal device to which the sales support server is connected and a specific market event condition type is selected from the market event list, the brand related to the event information is selected from the information providing server. The sales support system according to claim 1, wherein the action information of the company is displayed on the terminal device. 2. The terminal device is characterized in that when a customer is selected from a list of customers holding a brand provided by the information providing server, the sales support server displays a customer attribute screen on the terminal device. Described sales support system. When the link button provided for each brand is selected on the detail screen of the brand entrusted by the customer on the terminal device,
The sales support system according to claim 2 or 3, wherein the sales support server displays a stock price display screen provided by the information providing server on the terminal device. Login authentication at the migration destination when the sales support server moves to the screen provided by the information providing server, or when moving from the screen provided by the information providing server to the screen of the sales support server. The sales support system according to any one of claims 2 to 4, wherein the sales support system is characterized in that.

Images