Business support system
The sales support system integrates case and contact history information on a timeline format, simplifying input and management, enhancing sales activity understanding and efficiency.
Patent Information
- Application Number
- JP2023072132
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-26
- Publication Date
- 2024-11-08
AI Technical Summary
Conventional sales support systems complicate the input and management of project information and customer contact history, making it difficult to grasp historical information and understand sales activities effectively.
A sales support system with a sales support server that integrates case information and contact history information, displaying them on the same screen in a timeline format, allowing easy association and input, and providing search and aggregation functions.
Facilitates efficient management and understanding of sales activities by simplifying the input of contact history information, enabling easy recognition of sales progress and results, and supporting effective sales strategies.
Smart Images

Figure 2024157658000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a sales support system, and more particularly to a sales support system capable of linking and managing information on proposals to customers with contact history information by utilizing a CRM (Customer Relationship Management) system. [Background technology]
[0002] [Prior Art] Conventional sales support systems are basically used by accessing from a terminal device a CRM server that manages customer information and an information providing server that provides information such as stock prices.
[0003] In addition, information on projects proposed to customers (project information) is management information such as sales budget results and progress for financial products such as investment trusts and stocks, and this project information is usually managed using spreadsheet software. Furthermore, in order to manage sales activities related to case information, in addition to entering the case information into the spreadsheet software, it was necessary to enter the case information in association with customer contact history information, etc. in the CRM system, making the input work cumbersome.
[0004] Furthermore, conventionally, case information and contact history information were not managed in a unified manner, and therefore case information and contact history information were displayed separately. For this reason, it has not been possible to easily grasp in chronological order what sales activities were carried out and what results were obtained for a project proposed to a customer.
[0005] [Related Technology] In addition, a related prior art is JP 2021-022164 A, "Sales Support System" (Patent Document 1). Patent Document 1 discloses a sales support system that links a CRM server and an information providing server, and that can easily shift from the CRM server to the information providing server, particularly with regard to market events. [Prior art documents] [Patent documents]
[0006] [Patent Document 1] Patent Publication No. 2021-022164 Summary of the Invention [Problem to be solved by the invention]
[0007] However, in conventional sales support systems, the case information proposed to customers and contact history information with customers were managed separately, which resulted in cumbersome input and confirmation work for both, and the problem was that it was not easy to grasp the contact history information related to each case information.
[0008] Incidentally, Patent Document 1 does not disclose any configuration for facilitating the input of contact history information related to case information and for easily understanding case information and contact history information.
[0009] The present invention has been made in consideration of the above-mentioned situation, and aims to provide a sales support system that makes it easy to input contact history information related to case information and enables easy understanding of case information and the contact history information related to it. [Means for solving the problem]
[0010] The present invention, which solves the problems of the above-mentioned conventional examples, is a sales support system having a sales support server that registers case information that proposes financial products to customers and manages progress, and is characterized in that the sales support server displays a contact history registration screen on a connected terminal device, which allows the user to input contact history information for customers in association with the case information, allows the user to input contact information related to the case information from the contact history registration screen, and associates the case information with the contact history information and displays it on the terminal device.
[0011] In addition, in the above-mentioned sales support system, the present invention is characterized in that the sales support server displays the contact history information, contact method and status in timeline format on the same screen on the terminal device where the case information is displayed.
[0012] In the sales support system of the present invention, the sales support server can input information about the customer's transactions with other companies into the case information.
[0013] In the sales support system of the present invention, the sales support server has a search function for searching case information using a specific keyword.
[0014] In the sales support system according to the present invention, the sales support server has a function of counting amounts for each specific group. Effect of the Invention
[0015] According to the present invention, a sales support system has a sales support server that registers case information that proposes financial products to customers and manages progress, and the sales support server displays a contact history registration screen on a connected terminal device, which allows the user to input contact history information for customers in association with the case information, allows the user to input contact information related to the case information from the contact history registration screen, and displays the case information and contact history information in association with each other on the terminal device.This reduces the work of inputting contact history information in association with the case information, and allows sales representatives to easily grasp contact history information related to case information, allowing them to carry out efficient and effective sales activities.
[0016] Furthermore, according to the present invention, the sales support server is the sales support system that displays the contact history information, contact method and status in timeline format on the same screen on the terminal device where the case information is displayed, thereby having the effect of easily displaying the history of the contact history information related to the case information in chronological order, thereby providing information that is useful for sales activities.
[0017] Furthermore, according to the present invention, the sales support server is the sales support system that allows the input of information about a customer's transactions with other companies into the case information, which has the effect of supporting sales activities that encourage customers to switch from other companies to the company. [Brief description of the drawings]
[0018] [Figure 1] FIG. 1 is a schematic diagram of the configuration of the present system. [Diagram 2] FIG. 13 is an explanatory diagram showing an example of a case registration screen. [Diagram 3] FIG. 13 is an explanatory diagram showing an example of a case / contact history display screen. [Figure 4] FIG. 13 is an explanatory diagram showing an example of a contact history registration screen. [Diagram 5] FIG. 13 is an explanatory diagram showing a contact history registration screen from a history creation button. [Figure 6] FIG. 13 is an explanatory diagram showing a case search screen (for operators); [Figure 7] FIG. 13 is an explanatory diagram showing a case summary screen (for headquarters employees). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0019] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described with reference to the drawings. [Outline of the embodiment] In a sales support system (this system) relating to an embodiment of the present invention, a sales support server allows a terminal device to connect and register case information for financial products to be proposed to a customer, and further displays a contact history registration screen for inputting contact history information with the customer in association with the case information. The contact information related to the case information is input from the contact history registration screen, and the case information and contact history information are displayed in association with each other on the terminal device. This makes it easy to input contact history information associated with case information, and enables sales representatives to easily associate and recognize the case information and contact history information, thereby supporting sales activities.
[0020] [This system: Figure 1] The configuration of this system will be described with reference to Fig. 1. Fig. 1 is a schematic diagram of the configuration of this system. As shown in FIG. 1, this system comprises a sales support server 1 which processes sales support, a user terminal 2 which serves as a terminal device for a salesperson, a headquarters terminal 3 which serves as a terminal device for a person in charge at the headquarters, and a network 4. For ease of explanation, only one user terminal 2 and one headquarters terminal 3 are shown in FIG. 1, but actually a plurality of terminals are connected to the network 4.
[0021] Each part of this system will now be described. The sales support server 1 includes a control unit 11, a storage unit 12, and an interface unit 13. The control unit 11 reads and executes processing programs stored in the storage unit 12 to realize functions that will be described later. The storage unit 12 stores processing programs, as well as customer information, case information, contact history information, and the like relating to CRM. The interface unit 13 is an interface unit for connecting to the network 4 .
[0022] The user terminal 2 is a terminal device such as a personal computer or tablet used by a sales representative, which connects to the sales support server 1 via the network 4, searches for customer information, case information, contact history information, etc. stored in the sales support server 1, and displays them for viewing. Furthermore, the user terminal 2 inputs various information such as customer information, case information, and contact history information, transmits the information to the sales support server 1, and registers the various information in the sales support server 1.
[0023] The headquarters terminal 3 is a terminal device such as a personal computer used by a person in charge at the headquarters (for example, a branch office) that serves as the base of sales activities, and has the same functions as the user terminal 2 and performs processes such as tabulation. The network 4 is assumed to be an intranet or an encrypted Internet.
[0024] [Outline of processing (function) in this system] Next, an overview of the processing in this system will be described. The processes (functions) of this system include case registration processing, contact history registration processing, case search processing, and case aggregation processing. The case registration process is a process for registering management information about a case proposed to a customer. Specifically, the control unit 11 of the sales support server 1 stores the proposal content (financial products, etc.) and the goal of realizing the proposal, etc., in association with the customer in the storage unit 12 based on the input from the user terminal 2.
[0025] The contact history registration process is a process in which a sales representative registers information (contact history information) about the history of contact with customers during sales activities, and the control unit 11 of the sales support server 1 stores this information in chronological order in the memory unit 12 based on input from the user terminal 2. A feature of this system is that contact history information is input and stored in association with case information. This allows case information and corresponding contact history information to be displayed on the same screen on the user terminal 2, as described below, making it easy to understand how the customer has been approached for each case.
[0026] The case search process is a function for sales representatives, and is a process for searching for case information. In this system, the control unit 11 of the sales support server 1 filters various items entered from the user terminal 2 to narrow down the case information, and displays the search results on the user terminal 2.
[0027] Case aggregation processing is a function intended for headquarters employees, and in this system, the control unit 11 of the sales support server 1 filters the data using various items in response to instructions entered from the headquarters terminal 3, and also switches the aggregation unit and displays the aggregation results on the headquarters terminal 3.
[0028] As described above, the control unit 11 of the sales support server 1 executes the processing programs stored in the storage unit 12 to realize the processing means of each process. The details of each process will be described later using examples of display screens on the user terminal 2 or the headquarters terminal 3.
[0029] [Case registration process: Figure 2] The matter registration process will be described with reference to Fig. 2. Fig. 2 is an explanatory diagram showing an example of a matter registration screen. When an instruction to "register a case" is input on the user terminal 2, the instruction is sent to the sales support server 1, and the case registration process is started. The sales support server 1 then displays a case registration screen as shown in Fig. 2 on the user terminal 2. The case registration process is started after the customer information has been specified.
[0030] As shown in FIG. 2, the deal registration screen 20 allows the input of a proposed issue, category, target contract date, target amount, memos, etc., and the sales representative inputs each item on the deal registration screen 20.
[0031] Furthermore, as a feature of this system, information about other companies obtained through contact with customers is input and displayed together with the case information. Specifically, on the user terminal 2, the financial institution to be included, the trading name of the other company, the estimated amount, etc. are input as the other company transaction information 21 on the case registration screen 20. By providing the other company transaction information 21, it is possible to provide useful information when conducting sales activities to induce customers to switch transactions from other companies to the company.
[0032] In addition, in order to perform the case registration process with customer information identified, it is also possible for the sales support server 1 to input customer attributes such as other company transaction information 21 as related information in advance into the case registration screen 20, and for the case registration screen 20 containing the customer attributes to be displayed on the user terminal 2. As a result, if related information is entered into any of the case information for the customer, the sales support server 1 will automatically enter the related information when registering case information thereafter, simplifying the input process.
[0033] Once the input is complete and the “Save” command is entered on the case information registration screen 20, the entered data is sent to the sales support server 1 and stored in the memory unit 12 of the sales support server 1 as case information corresponding to the customer. In this manner, the case registration process is carried out.
[0034] [Case / contact history display screen: Figure 3] Before describing the contact history registration process, the case / contact history display screen, which is a feature of this system, will be described with reference to Fig. 3. Fig. 3 is an explanatory diagram showing an example of the case / contact history display screen. As shown in FIG. 3, the case / contact history display screen 30 displays case information and chronological contact history information together.
[0035] In the example of Fig. 3, the customer's name is displayed at the top of the case / contact history display screen 30, and below that is divided into two large display areas. In Fig. 3, a case information display section 31 that displays the contents of the case information is provided on the left side, and a timeline display section 32 that displays the contents of the contact history is provided on the right side.
[0036] The case information display section 31 has a status display section 33 at the top, which displays the progress of the case. There are three status stages: (1) information acquisition, (2) proposal, and (3) contract, and the current status is displayed in a conspicuous color to make it visually easy to understand. In the example of Figure 3, the current status is shown with a line drawn under (1) information acquisition. The registration and change of the status is performed when the contact history information is registered, as described below.
[0037] Below the status display section 33, the contents of the case (proposal) registered by the case registration process are displayed. In the example of FIG. 3, the proposed name, category, target contract date, target amount, memo, etc. are displayed, and further, as other company transaction information 34, the incorporating financial institution, other company transaction name, and estimated amount are displayed.
[0038] The timeline display section 32 displays, in chronological order, the contents of information on sales activities involving contact with customers (contact history information) for the case information displayed on the left side. Examples of contact history information include date, linking status 35, and memo, and the contents registered by the contact history registration process described below are displayed in chronological order.
[0039] In this system, by clicking on the history creation button 37 displayed in the upper right corner of the timeline display section 32, the contact history registration process is started and contact history information corresponding to the case information displayed in the case information display section 31 can be registered. Alternatively, the contact history information registration process may be started by clicking the status change button 36 in the upper right corner of the case information display section 31.
[0040] As shown in FIG. 3, the linked status 35 is a status linked to the status of the case information displayed in the case information display section 31, and registers and displays a more detailed state corresponding to the status of the case information. Specifically, the linking status 35 is represented as a pair of activity content (action, contact method) 35a and post-contact status 35b, and examples of activity content 35a include direct mail, seminars, posting, phone calls, visits with section managers, visits with department managers, and visits with branch managers.
[0041] Examples of the post-contact status 35b include information acquisition, proposal, hold, missed out, contract, etc. The post-contact status 35b is displayed in different colors according to the content, so that the progress can be easily recognized. A memo is displayed to the right of the linking status 35. If the memo is long, only a part of it is displayed.
[0042] In this way, in this system, the case / contact history display screen 30 displays the contact history for each case proposed to a customer in chronological order on the same screen as the content of the proposal, so that it is easy to understand when and how the customer was approached and the progress status as a result, and this information can be used in future sales activities.
[0043] [Contact history registration process: Figure 4] Next, the contact history registration process will be described with reference to Fig. 4. Fig. 4 is an explanatory diagram showing an example of a contact history registration screen. When, for example, "contact history registration" is selected from the main screen on the user terminal 2, the contact history registration process is started, and communication between the user terminal 2 and the sales support server 1 is started.
[0044] In this system, in order to register contact history information in association with case information, the contact history registration process first identifies the case information. Specifically, on the user terminal 2, the customer information is searched to identify the customer, and when the status selection section 41 and proposed stock input field in Fig. 4(a) are displayed, the status is specified to narrow down the case information. Then, in the proposed stock field, the user clicks the ▽ on the far right and selects the desired stock from the proposed stocks displayed in a pull-down menu to identify the case information. If it is a new case, the case information is registered using the case registration process shown in Fig. 2.
[0045] When the case is specified, the sales support server 1 causes the user terminal 2 to display, for the case, a contact history registration screen including a linking status selection section 42 and a memo input field as shown in FIG. 4(a). Also, when the status change button 36 is clicked on the case / contact history display screen 30 in FIG. 3, the contact history registration screen in FIG. 4 is displayed.
[0046] As shown in Figure 4(a), the contact history registration screen has a status selection section 41, a proposed stock, a linking status selection section 42, and a memo section, and initially displays the information currently stored in the sales support server 1. In other words, the status selection unit 41 displays the current status of the case information stored in the sales support server 1, and the linking status selection unit 42 displays the current linking status of the contact history information corresponding to the case information. In the example of FIG. 4(a), the status of the case information is "Proposed", and the linking status of the contact history information is also "Proposed".
[0047] Here, when changing the status or the linking status, a pull-down menu is used for selection. In particular, in the association status selection section 42, the activity details 35a and the post-contact status 35b shown in FIG. 3 can be selected by a pull-down menu. When contact history information such as status, linking status, and memos is input from the user terminal 2, the user terminal 2 sends the input information with a date and time attached to it to the sales support server 11, and the sales support server 11 stores the date and time information, linking status, and memos in association with the case information.
[0048] In the linked status selection section 42, it is possible to select a more detailed status than in the status selection section 41. For example, states such as on hold and rejected can be selected, and when on hold or rejected is selected, on the case / contact history display screen 30 shown in Figure 3, the linked status 35 in the timeline display section 32 is displayed as post-contact status 35b, and the date on which the case became on hold or rejected is displayed as "on hold / rejected date" in the case information display section 31 (not shown).
[0049] Furthermore, when a linking status is selected in the linking status selection section 42, an input field for registering supplemental information corresponding to the selected linking status is displayed. FIG. 4(b) shows the contact history registration screen when the post-contact status is changed to "contracted" in the linking status selection unit 42 from the state of FIG. 4(a). As shown in FIG. 4(b), when the linking status is changed to “contracted”, a contract date field 43 and a contract amount field 44 are displayed as corresponding supplementary information, allowing the date and amount to be entered, respectively.
[0050] The information entered on the contact history registration screen is stored in the sales support server 1 and displayed in correspondence with the case information on the case / contact history display screen 30 shown in FIG. When "contract" is selected in the linking status, the status of the case information (status of the status selection unit 41) is also changed to "contract" (not shown).
[0051] The contact history registration screen in Figure 4 allows you to fix the customer, change the proposed stock using a pull-down menu, and register contact history information while sequentially specifying project information. This is convenient when registering contact history for multiple projects for a specific customer and reduces the amount of input work.
[0052] [Contact history registration screen from the Create History button: Figure 5] Next, the process of registering a contact history from the history creation button 37 on the case / contact history display screen 30 shown in Fig. 3 will be described with reference to Fig. 5. Fig. 5 is an explanatory diagram showing the contact history registration screen to which the screen is shifted from the history creation button on the case / contact history display screen. When the Create History button 37 is clicked on the case / contact history display screen 30 in FIG. 3, the sales support server 1 proceeds to the contact history registration process and causes the user terminal 2 to display a contact history registration screen as shown in FIG.
[0053] As shown in FIG. 5, when the screen is shifted to from the history creation button 37, the screen is already associated with the customer and the case information, and the screen is for inputting the association status selection section 45 and memos. The association status selection section 45 is used to input the activity details 35a and post-contact status 35b selected by a pull-down menu in the same manner as in the example of FIG. Here, the selected linking status is "Proposed."
[0054] The information entered on the contact history registration screen in Figure 5 is also time-stamped and sent to the sales support server 1, as in the case of Figure 4, and is stored in the sales support server 1 in association with the customer and case information.
[0055] In this way, in this system, by using the contact history registration screens shown in Figures 4 and 5, contact history information can be easily linked to case information and registered, significantly reducing the burden on sales representatives when entering contact history information and improving work efficiency. Furthermore, in this system, the sales support server 1 stores case information and contact history information in association with each other based on the contents registered on the contact history registration screen, and can display both together on the case / contact history display screen 30. This allows the user terminal 2 to clearly display the progress of work and the history of sales activities, which can be used in future sales activities.
[0056] [Case search process: Figure 6] Next, the case search process for the handler will be described with reference to Fig. 6. Fig. 6 is an explanatory diagram showing a case search screen (for the handler). When an instruction for "case search" is input from the user terminal 2, the sales support server 1 transitions to case search processing and causes the user terminal 2 to display a case search screen shown in FIG.
[0057] As shown in Figure 6, the case search screen allows users to input any block, department, branch, section, agent, customer, and period (target contract date, contract date, etc.) as search conditions, and these conditions can be combined to search for case information. Then, the job information that matches the conditions is extracted and displayed as a list of job search results on the job search screen. In the example of Figure 6, the extracted job information is omitted.
[0058] Furthermore, in the case search process, it is possible to narrow down the results by filtering based on the case status, etc. This makes it possible to easily extract desired case information.
[0059] [Case summary processing: Figure 7] Next, the case summary process for headquarters employees will be described with reference to Fig. 7. Fig. 7 is an explanatory diagram showing a case summary screen (for headquarters employees). When an instruction for "case summary" is input from the user terminal 2, the sales support server 1 transitions to case summary processing, and causes the user terminal 2 to display a case summary screen shown in FIG.
[0060] As shown in Figure 7, the case summary screen allows users to enter any block, department, branch, section, handler, customer, and period (target contract date, etc.) as extraction conditions, and the entered conditions are combined to extract case information. The extracted case information is then displayed in a list, and the total target amount and the like are tallied and displayed based on the extracted case information.
[0061] In this case, the system can also switch the group unit for tabulation and display the results. Here, the tabulation unit is "handler," and tabulation is performed for each handler. Note that even a singular number such as "handler" is considered a type of group for tabulation units. Furthermore, in the case aggregation process, similar to the case search process of FIG. 6, it is also possible to narrow down the results by case status, etc.
[0062] This will make it easier for headquarters employees to check the aggregated data and grasp progress, improving the efficiency of management operations.
[0063] [Effects of the embodiment] According to this system, the sales support server 1 allows the connected user terminal 2 to register case information for financial products to be proposed to customers, and further allows the contact history registration screen to input contact history information for the customer in association with the case information, and displays the case information and contact history information in association with each other on the user terminal 2. This significantly reduces the work of inputting case information and contact history information in association with each other, and also makes it possible to easily associate and recognize the case information and contact history information, which can be used in future approaches, thereby supporting sales activities.
[0064] Furthermore, according to this system, the sales support server 1 displays case information and the corresponding contact history information in a timeline format on the user terminal 2 as a case / contact history display screen 30, so that sales personnel can easily grasp the chronological history of what sales activities have been carried out for each case and what the results have been, and can use this information in future sales activities. [Industrial Applicability]
[0065] The present invention is suitable for a sales support system that makes it easy to input contact history information in relation to case information and that can easily grasp case information and contact history information. [Explanation of symbols]
[0066] 1...Sales support server, 2...User terminal, 3...Head office terminal, 4...Network, 11...Control unit, 12...Memory unit, 13...Interface unit, 20...Case registration screen, 21...Transaction information with other companies, 30...Case / contact history display screen, 31...Case information display unit, 32...Timeline display unit, 33...Status display unit, 34...Transaction information with other companies, 35...Linking status, 36...Status change button, 37...History creation button, 41...Status selection unit, 42, 45...Linking status selection unit, 43...Contract date field, 44...Contract amount field
Claims
1. A sales support system having a sales support server that registers project information for proposing financial products to customers and managing the progress, The sales support system is characterized in that the sales support server displays a contact history registration screen on a connected terminal device, which allows the user to input contact history information with customers in association with the case information, allows the user to input the contact information related to the case information from the contact history registration screen, and associates the case information with the contact history information and displays it on the terminal device.
2. The sales support system according to claim 1, wherein the sales support server displays the contact history information, including the contact method and status, in timeline format on the same screen on which the case information is displayed on the terminal device.
3. 3. The sales support system according to claim 1, wherein said sales support server is capable of inputting information about transactions with other companies by said customer into said case information.
4. 3. The sales support system according to claim 1, wherein the sales support server has a search function for searching case information using a specific keyword.
5. 3. The sales support system according to claim 1, wherein the sales support server has a function of counting amounts for each specific group.
Citation Information
Patent Citations
Computer-readable recording medium with insurance sales supporting data recorded thereon
JP2002099708A
Business support system
JP2011096209A
Business support system
JP2021022164A
