Insurance business management system, insurance business management method, program and recording medium

Abstract

To provide an insurance business management system, an insurance business management method, an insurance business management program, and a recording medium capable of managing contents of correspondence to customers such as contract motives and suitable for use by an insurance agent.SOLUTION: The insurance business management system is provided with: an insurance management server; a plurality of agency terminals connected via a network; an insurance management server 11 for storing a customer management table 31, a customer information table 32, and a customer important information table (contract motive table 51) based on a customer card prepared by an agency terminal; specifies a customer retrieved by the agency terminal based on the customer information table 32; and causes the agency terminal to display a list of contract motives or accident records relating to an insurance contract of the customer by referring to the customer important information table.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to an insurance sales management system, an insurance sales management method, a program thereof, and a recording medium suitable for use by insurance agents. [Background technology]

[0002] In recent years, because there are a wide variety of insurance products, when considering purchasing insurance, insurance policyholders often seek advice from insurance agents to find insurance that suits their lifestyle and business. Insurance agents propose the insurance product that they believe is best for the customer at that time, and even after the insurance contract is signed, they make an effort to regularly review and propose whether the customer has properly purchased the necessary insurance.

[0003] For example, Patent Document 1 proposes an insurance information management device that provides warnings regarding contract expiration and renewal, notifies the insured of the timing of interim dividends and maturity refunds, and notifies the insured at the time of life events, thereby increasing customer convenience. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2021-185526 A Summary of the Invention [Problem to be solved by the invention]

[0005] As mentioned above, insurance agents propose the insurance product that they believe is best for the customer at that time, and the customer understands the details and signs up for insurance, but as time passes, customers often forget what they were thinking when they chose that insurance, and their motivation for signing the contract. A customer's previous motivation for signing the contract can serve as a reference for choosing an insurance product when they later review their insurance or when they decide to consider a different insurance, and it is something that insurance agents should manage appropriately. Furthermore, we believe that properly managing not only the motivation for signing the contract, but also important content that insurance agents have interacted with customers on will increase customer convenience.

[0006] The present invention has been made in view of the above circumstances, and has an object to provide an insurance sales management system suitable for use by insurance agents. [Means for solving the problem]

[0007] In order to solve the above problems, the first aspect of the insurance sales management system of the present invention comprises an insurance management server managed by an insurance agency and an agency terminal capable of communicating with the insurance management server, and the insurance management server stores a customer management table that associates and stores the customer names and management IDs of the insurance agency's customers based on customer cards created from the agency terminal, a customer information table that associates and stores the management IDs and customer information of the customers, and a customer important information table that associates and stores the management IDs and customer important information regarding the contract motivation or accident records related to the customer's insurance contracts, and the insurance management server identifies customers searched for from the agency terminal based on the customer information table, and refers to the customer important information table to display a list of the contract motivation or accident records related to the customer's insurance contracts on the agency terminal.

[0008] In the second aspect of the insurance sales management system, in the first aspect, it is also preferable that the contract motivation list sheet, which is a list of the contract motivations, lists the response dates and content of the interactions with the customer regarding the contract motivations in chronological order.

[0009] In the third aspect of the insurance sales management system, in the first aspect, it is also preferable that the accident record list sheet, which is a list of the accident records, lists the response dates and contents of the communications with those involved in the accident regarding the accident records in chronological order.

[0010] In the fourth aspect of the insurance sales management system, in any of the first to third aspects, it is also preferable that the contract motivation list sheet, which is a list of the contract motivations, and the accident record list sheet, which is a list of the accident records, are provided with buttons that enable necessary documents to be uploaded to the insurance sales management system and downloaded to the agent terminal.

[0011] In the insurance sales management system of the fifth aspect, in the second aspect, it is also preferable that the contract motivation list sheet is provided with an insurance contract document checkbox for checking whether or not documents required for an insurance contract have been recorded in the insurance sales management system.

[0012] In the insurance sales management system of the sixth aspect, in the third aspect, it is also preferable that the accident record list sheet is provided with an insurance claim document checkbox for checking whether or not documents necessary for insurance claims have been recorded in the insurance sales management system.

[0013] In the seventh aspect of the insurance sales management system, in the second or fifth aspect, it is also preferable that the contract motivation list sheet is provided with a system input checkbox for checking whether important information on the customer card has been recorded in the insurance sales management system and whether the contract motivation list sheet has been recorded in the system.

[0014] In the eighth aspect of the insurance sales management system, in the sixth aspect, it is also preferable that the insurance claim document check box on the accident record list sheet has a column for recording the attachment date and sending date of the documents required for the insurance claim in the insurance sales management system.

[0015] In order to solve the above problem, an insurance sales management method according to a ninth aspect of the present invention is characterized in that it includes the steps of communicating with an insurance management server that stores a customer management table that associates and stores the customer name and management ID of the insurance agency's customer based on a customer card created from an agency terminal, a customer information table that associates and stores the management ID and the customer information of the customer, and a customer important information table that associates and stores the management ID and important customer information regarding the contract motivation or accident record related to the customer's insurance contract, and identifying a customer searched for from the agency terminal based on the customer information table; and a step of referring to the customer's important information table and displaying on the agency terminal a list regarding the contract motivation or accident record related to the customer's insurance contract.

[0016] An insurance sales management program according to a tenth aspect of the present invention describes the insurance sales management method according to the ninth aspect as a computer program and makes it executable.

[0017] A recording medium according to an eleventh aspect of the present invention records the computer program according to the tenth aspect. Effect of the Invention

[0018] According to the present invention, it is possible to provide an insurance sales management system and the like that can manage the details of the responses that an insurance agency has made to customers, such as the motivation for a contract. [Brief description of the drawings]

[0019] [Figure 1] 1 is a configuration block diagram of an insurance sales management system 1 according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a configuration block diagram of the insurance management server 11. [Diagram 3] 1A is an example of a top page 121 displayed after login, and FIG. 1B is an example of a customer card 122 according to the first embodiment. [Figure 4]1A is an example of a customer management table 31, and FIG. 1B is an example of a customer information table 32. [Diagram 5] 13A is an example of a family information table 33, (B) is an example of an account information table 34, (C) is an example of a delivery destination information table 35, and (D) is an example of a contract information table 37. [Figure 6] 13 is a display example of a contract motivation list sheet 127. [Figure 7] 13 is an example of a contract motivation table 51. [Figure 8] 1 is an example of an insurance contract document automatic display table 52. [Figure 9] 13 is a display example of a search page 124. [Figure 10] 1A is a flowchart showing a preparation process for using the insurance sales management system 1, and FIG. 1B is a flowchart showing a process for using the insurance sales management system 1. [Figure 11] FIG. 11 is a configuration block diagram of an insurance sales management system 10 according to a second embodiment of the present invention. [Figure 12] 13 is an example of a customer card 122 according to the second embodiment. [Figure 13] 13 is a display example of an accident record list sheet 130. [Figure 14] 13 is an example of an accident record table 61. [Figure 15] 1A is a flowchart showing a preparation process for using the insurance sales management system 10, and FIG. 1B is a flowchart showing a process for using the insurance sales management system 10. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] Next, a preferred embodiment of the present invention will be described with reference to the drawings. In this specification, the terms "enterprise", "corporation", and "company" are used, but all of them are described in accordance with commercial practice and are treated as synonyms. For example, the term "company" is not limited to corporations established under the Companies Act, and the term "enterprise" is not limited to profit-making organizations and groups. In addition, even if an organization or group is not expressed by the terms "enterprise", "corporation", or "company", such as a university, hospital, local government, or association, the present invention is applicable by replacing the terms with the structure of the organization.

[0021] First Embodiment (Configuration of insurance sales management system) FIG. 1 is a configuration block diagram of an insurance sales management system 1 according to a first embodiment of the present invention. In the insurance sales management system 1, an insurance management server 11 owned and managed by an insurance agency A and an agency terminal 12 (multiple are possible) are connected via a communication network 3, and data can be transmitted and received between them. The agency terminal 12 of the insurance agency A is a general-purpose personal computer (PC), a smartphone, a tablet, or the like, and is a device that includes at least a calculation unit, a storage unit, a communication unit, an operation unit (not shown), and a display unit 13, and is capable of outputting to a printer (not shown). A dedicated Web application, which will be described later, is installed in each agency terminal 12.

[0022] 2 is a configuration block diagram of the insurance management server 11. The insurance management server 11 has at least a server communication unit 111, a server control unit 112, and a server storage unit 113. The server communication unit 111 is a communication control device such as a network adapter, a network interface card, a LAN card, etc., and is connected to a communication network 3 such as the Internet or a mobile phone communication network by wire or wirelessly. The server control unit 112 is a control calculation unit composed of one or more processors such as a CPU (Central Processing Unit), a multi-core CPU or a GPU (Graphics Processing Unit), and memories such as RAM and ROM, and controls communication control of the server communication unit 111, storage of information in the server storage unit 113, reading of information from the server storage unit 113, and Web applications. Details of these controls will be described later. The server storage unit 113 is composed of a computer-readable storage medium such as a memory card or a HDD (Hard Disk Drive), and includes a customer card database 30 and a contract motivation database 50 linked to the customer card database 30 (hereinafter referred to as the "customer card DB 30" and the "contract motivation DB 50", respectively). The data in these DBs 30 and 50 is updated by the server control unit 112 based on information entered via the Web application.

[0023] The customer card DB30 comprises a customer management table 31, a customer information table 32, a family information table 33, an account information table 34, a delivery destination information table 35, and a contract information table 37. The contract motivation DB50 comprises a contract motivation table 51, and optionally an insurance policy document automatic display table 52. Information regarding a customer's contract motivation is one piece of important customer information that should be properly managed by an insurance agency, and the contract motivation table 51 is one of the important customer information tables referred to in the claims. The details of these tables will be described later.

[0024] (Create a customer card) When a worker starts a web application on the agency terminal 12, communication with the insurance management server 11 is initiated, and a dedicated web page is displayed on the display unit 13 of the agency terminal 12. Fig. 3(A) is an example of the web page (top page 121) displayed after login. The top page 121 includes at least a new customer registration button 121A and a customer search button 121B.

[0025] When the user presses the new customer registration button 121A, a new customer card 122 is displayed, and customer information can be entered into the customer card 122. FIG. 3(B) is an example of the customer card 122. In the customer card 122, an input form for individual or corporation can be selected in the classification box 122A. If the individual form is selected, a personal information input box 122B and an employer information input box 122C are displayed, and if the corporation is selected, a representative information input box and a corporation information input box (not shown) are displayed. The personal information input box and the representative information input box have input boxes for the name, furigana, gender, age, date of birth, position, home phone number, mobile phone number, and email address. The employer information input box and the corporation information input box have input boxes for the company name, furigana, branch office, department, corporation representative, main phone number, direct phone number, and person in charge. In addition, the customer card 122 has a business details input box, a main client input box, a financial information input box, an introducer input box 122I, a special notes input box, a creation date input box, and a last updater input box, and workers can enter text into these boxes.

[0026] When the worker presses the add button 122Z (see FIG. 3(B)) to create the customer card 122, the server control unit 112 stores the new information in the customer management table 31. FIG. 4(A) is an example of the customer management table 31. In the customer management table 31, a management ID, a customer name, and a reference ID are stored in association with each other. The server control unit 112 assigns a new management ID to the individual name (customer name) entered in the personal information input box 122B on the customer card 122 or the corporate representative name (customer name) entered in the representative information input box, and stores the new management ID in the customer management table 31. The reference ID is used when linking with another customer card 122, for example, a subsidiary and a parent company. Next, the server control unit 112 stores the new customer information in the customer information table 32. FIG. 4(B) is an example of the customer information table 32. In the customer information table 32, the customer information inputted to the customer card 122 (see FIG. 3(B)) is stored in association with one management ID given in the customer management table 31.

[0027] As shown in Fig. 3(B), the customer card 122 has a family information button 122M, an account information button 122N, a delivery destination information button 122O, a contract information button 122P, and a contract motivation record button 122Q. When the worker presses the family information button 122M, the account information button 122N, the delivery destination information button 122O, or the contract information button 122P, a family information input form, an account information input form, a delivery destination information input form, and a contract information input form linked to the customer card 122 are displayed on the display unit 13, respectively, and input into each form becomes possible. When the worker presses the add button 122Z, the input information is recorded in association with the customer card 122. Fig. 5(A) shows an example of the family information table 33, Fig. 5(B) shows an account information table 34, Fig. 5(C) shows a delivery destination information table 35, and Fig. 5(D) shows a contract information table 37. The server control unit 112 stores the management ID, family category (spouse, child, relative, etc.) and name of the customer card 122 in a family information table 33 in association with each other, stores the management ID and account information in an account information table 34 in association with each other, stores the management ID and delivery destination information in a delivery destination information table 35 in association with each other, and stores the management ID and customer insurance contract information for each insurance contract in a contract information table 37. As shown in the contract information table 37, vehicle information is entered from a contract information input form (not shown), and the vehicle name, registration number, and grade are registered.

[0028] (Creating a contract motivation record) Next, when the worker is involved in the customer's insurance application, he / she inputs information about the reason for signing up for insurance into the system 1. When the worker presses the contract motivation record button 122Q (see FIG. 3(B)) on the customer card 122, a contract motivation list sheet 127 on the customer card 122 is displayed. FIG. 6 is a display example of the contract motivation list sheet 127. The contract motivation list sheet 127 can be entered, viewed, and printed. The contract motivation list sheet 127 includes a policyholder input box 127A, a category box 127B, an insurance type input box 127C, a contract motivation input box 127D, a file selection button 127E, an upload button 127F, a download button 127G, an insurance contract document check box 127H, a system input check box 127I, an approval field 127J, and a contract date input box 127K.

[0029] In the policyholder input box 127A, the policyholder name related to the customer of the customer card 122 can be entered as text. In the classification box 127B, life insurance / non-life insurance can be selected. In the insurance type input box 127C, when life insurance is selected in the classification box 127B, whole life insurance, term insurance, cancer insurance, endowment insurance, disability insurance, family income insurance, corporate group insurance, education insurance, etc. can be selected from the selection box. When non-life insurance is selected, fire insurance, corporate fire insurance, personal liability insurance, automobile insurance, product liability insurance (PL insurance), facility liability insurance, store liability insurance, store closure insurance, income guarantee insurance, work accident insurance, golfer insurance, medical practitioner liability insurance, transportation insurance, etc. can be selected from the selection box. The insurance type that appears in the insurance type input box 127C corresponding to the classification box 127B is registered in advance in the server storage unit 113 of the insurance sales management system 1, and the registration can be updated, for example, from a setting button (not shown) provided on the top page 121.

[0030] In the contract motivation input box 127D, the contract history and the customer's intentions can be entered in chronological order. The contract motivation input box 127D has a response date field 126A and a response content field 126B. The response date field 126A has a calendar input button in the box, and the response date can be input by selecting a date from a pop-up calendar or by text input. In the response content field 126B, the response content can be input as text corresponding to the response date. In the contract motivation input box 127D, the response date and the response content are entered in a row in chronological order, and a row can be added by using the plus button. The worker records the response content in the contract motivation input box 127D when the customer inquires about the customer's insurance contract, or when materials are sent or proposed to the customer. An input example is shown below.

[0031] (Input example 1: Purchasing motivation record for comprehensive income protection insurance) July 1, 2023: When I went to process my life insurance, I was consulted about canceling my savings insurance in order to purchase large equipment with cash. I also received a consultation about joining nursing care (disability) insurance. July 2, 2023: I received another inquiry by email. I designed and proposed Type B maturity at age C and Type D maturity at age E for Insurance Company A. I am currently asking by email whether to include death benefits. July 10, 2023: I received a phone inquiry about the details of nursing care insurance. After explaining that there are many types of insurance, we decided to make a corporate contract with a one-time premium that will cover up to age F in the event of inability to work, taking into account the age of the child. The design documents will be sent at a later date. July 12, 2023: Design documents sent

[0032] (Input example 2: Automobile insurance contract motivation record) August 1, 2023: I received an email asking about his wife's car insurance. He said he wanted to apply as soon as possible. I asked for the vehicle inspection certificate. August 2, 2023: A photo of the vehicle inspection certificate arrives. A second car discount is proposed and accepted. The debit details are currently being confirmed. August 5, 2023: Direct debit form and design documents sent.

[0033] Next, the file selection button 127E can refer to the file of the document required for the insurance contract. In response to the selection of the file selection button 127E, the calculation unit of the agency terminal 12 refers to the file to be uploaded from the terminal 12 to the insurance sales management system 1 by specifying a path or dragging and dropping. The upload button 127F is a button for uploading the document data referred to by the file selection button 127E to the insurance sales management system 1. When the selection of the upload button 127F is accepted, the server control unit 112 transmits the file to the contract motivation DB 50 of the insurance sales management system 1. In the case of the above input example 1, the worker selects and uploads the data of the credit card payment application form or the account transfer request form received from the customer. The worker also uploads other documents, for example, if there is a discount for a medical certificate or a gold license in the above input example 1. The file selection button 127E and its paired upload button 127F can add the number of items by using the plus button. Meanwhile, the download button 127G displays the file name of the insurance contract document data uploaded from the sheet 127 to the insurance sales management system 1, and pressing the button allows each document to be downloaded to the terminal 12.

[0034] The insurance contract document check box 127H is a field for checking whether or not the documents required for the insurance contract have been recorded in the insurance sales management system 1. In the insurance contract document check box 127H, a payment method check box 128A for the credit card payment application or the direct debit request and a design document check box 128B are prepared as defaults. The other check boxes 128C, 128D, etc. are created by the worker by inputting the document name in text. The number of check boxes can be increased by pressing the plus button. In the case of the above input example 1, the worker checks the payment method check box 128A after uploading either the credit card payment application or the direct debit request, and checks the design document check box 128B after uploading the design document. In the case of the above input example 2 for automobile insurance, the worker further creates a vehicle inspection certificate check box 128C, and checks the check box 128C after uploading the vehicle inspection certificate. If a medical certificate or a gold driver's license is required, these check boxes 128D, 128E, etc. are created and checked after uploading.

[0035] The system input check box 127I is a column for checking whether important matters among the customer information on the customer card 122 (see FIG. 3(B)) have been recorded in the system 1. The important matters on the customer card 122 are the matters in the following check columns: workplace check column 129A, emergency contact check column 129B, family information check column 129C, vehicle information check column 129D, delivery destination check column 129E, introducer check column 129F, and date of birth check column 129G. The system input check box 127I also has a record check column 129H for checking whether the contract motivation list sheet 127 has been filled in. The worker checks the customer card 122, and if the filling is completed, checks the check columns 129A to 129G, and if the input on the contract motivation list sheet 127 is completed, checks the check column 129H. When the insurance contract is completed with the consent of the customer and the approval of the approver in the insurance company A, the worker inputs the date in the contract date input box 127K. When the worker presses the Add button 127Z, the server control unit 112 stores the new contract motivation information in the contract motivation table 51 of the contract motivation DB 50, linking it to the customer card 122. When the worker presses the Print button 127P, the server control unit 112 outputs the displayed contract motivation list sheet 127 in an A4 size portrait print layout to the printer connected to the agency terminal 12. The printout has the initial creation date and last update date of the contract motivation list sheet 127 added to the header, and the page number added to the footer.

[0036] 7 is an example of a contract motivation table 51 of the contract motivation DB 50. In the contract motivation table 51, the contract motivation information entered in the input boxes 127A-127F and 127H-127K, i.e., the policyholder name, insurance type, contract motivation information, file information, insurance contract document check information, system input check information, person in charge, approver, and contract date, are stored in association with the management ID of the customer on the customer card 122. Of these, the contract motivation information, file information, insurance contract document check information, and system input check information have sub-tables 511-514, and table 51 stores the names of the sub-tables to be referenced.

[0037] Sub-table 511 is a contract motivation chronological table 511 that stores the contents entered in contract motivation input box 127D, where the date of the response and the content of the response related to the contract motivation are stored in association with each other and arranged in chronological order. Sub-table 512 is a file information table 512 that manages files uploaded with file selection button 127E, where file names, file paths, and links are stored in association with each other. The file path indicates the storage location of the file in server storage unit 113, such as a folder or directory.

[0038] Sub-table 513 is insurance contract document check table 513 in which the presence or absence of checks in check fields 128A-128H of insurance contract document check box 127H is recorded, and if there is a check, "Yes" is recorded, and if there is no check, "No" is recorded. Sub-table 514 is system input check table 514 in which the presence or absence of checks in check fields 129A-129H of system input check box 127I is recorded, and if there is a check, "Yes" is recorded, and if there is no check, "No" is recorded.

[0039] Here, in the insurance contract document check box 127H, the check boxes 128C- other than the payment means check box 128A and the design document check box 128B may be created by an operator, but it is also preferable that they are automatically created by the insurance sales management system 1. When the contract motivation list sheet 127 is opened by the contract motivation record button 122Q and an insurance type is selected in the insurance type input box 127C, the server control unit 112 automatically creates the insurance contract document check box 127H according to the selected insurance type. FIG. 8 is an example of the insurance contract document automatic display table 52 of the contract motivation DB 50. In the insurance contract document automatic display table 52, the necessary insurance contract documents are stored in association with the insurance type in the insurance type input box 127C. When an insurance type is selected in the insurance type input box 127C, the server control unit 112 refers to the insurance contract document automatic display table 52, and automatically creates, for example, a check column for the vehicle inspection certificate in the case of automobile insurance, a check column for a certified copy of the building register in the case of fire insurance, and a check column for a financial statement in the case of personal injury insurance, in the insurance contract document automatic display table 52. Registration of the insurance contract document automatic display table 52 can be updated, for example, from a setting button (not shown) provided on the top page 121.

[0040] Similarly, the system input check box 127I may be checked by an operator, but it is also preferable that the check box be automatically checked by the insurance sales management system 1. When the contract motivation list sheet 127 is opened, the server control unit 112 refers to the customer information table 32, the family information table 33, the delivery destination information table 35, and the contract information table 37, and if data has already been entered, automatically checks the check boxes 129A to 129G.

[0041] It is also preferable that the insurance sales management system 1 has a modification that issues an alert if the insurance contract document check box 127H and the system input check box 127I are not checked. When the worker thinks that he has finished inputting and presses the Add button 122Z, the server control unit 112 refers to the insurance contract document check table 513 and the system input check table 514, and if there is no check, it is also preferable that the server control unit 112 issues an alert such as "Insufficient documents" or "Insufficient input" on the display unit 13 of the terminal 12 and then closes the page.

[0042] (Search for customer card) When a customer card 122 is created, the customer for whom the card has already been created can be searched and called up from the system 1. When a worker is involved in an insurance contract for a customer and wants to keep a record of the interaction, the worker presses a customer search button 121B from the top page 121 (see FIG. 3(A)) and searches for the customer card 122 from a search page 124. FIG. 9 is a display example of the search page 124. The search page 124 has a search condition area 124B in the area below the display and a result display area 124A in the area above the display. The search condition area 124B has a kana search field, a customer name search field, a postal code search field, an address search field, an introducer search field, a phone number search field, a fax number search field, and a search button 124Z. Before the search button 124Z is pressed, nothing is displayed in the result display area 124A. When the worker inputs conditions in the search field and presses the search button 124Z, the server control unit 112 refers to the customer information table 32 and displays in the result display area 124A one line of the customer candidate list 124X for the customers who meet the searched conditions, including the customer name (personal name / corporate representative name), telephone number (personal telephone number), mobile phone (mobile phone number), corporate name / place of employment (company name), telephone number (main) (main telephone number), and telephone number (direct) (direct telephone number). When the worker selects (clicks) a customer to be referred to from the customer candidate list 124X, the server control unit 112 identifies the customer from the customer information table 32 and displays the customer card 122 in a pop-up. When the worker presses the contract motivation record button 122Q from here, the contract motivation list sheet 127 linked to the customer card 122 is displayed (see FIG. 6).

[0043] (Use of insurance sales management system) An insurance sales management method using the insurance sales management system 1 configured as above will be described. FIG. 10 shows the workflow of insurance sales management, FIG. 10(A) is a preparation flowchart for using the insurance sales management system 1, and FIG. 10(B) is a flowchart for using the insurance sales management system 1. In the preparation flowchart (FIG. 10(A)), when the insurance sales management system 1 is started from the agency terminal 12 and the new customer registration button 121A is pressed from the top page 121, the system moves to step S1, the customer card 122 is displayed on the agency terminal 12, and the creation of the customer card 122 is permitted. When the worker finishes inputting and presses the add button 122Z, the system moves to step S2, and the customer information is stored in the customer management table 31, the customer information table 32, the family information table 33, the account information table 34, and the delivery destination information table 35. Next, the system moves to step S3, and permits input of the contract motivation list sheet 127. When the worker finishes inputting and presses the Add button 127Z, the system moves to step S4, stores the contract motivation information in the contract motivation table 51, and ends the system. In the flowchart of system usage (FIG. 10(B)), when the insurance sales management system 1 is started from the agency terminal 12 and the customer search button 121B is pressed from the top page 121, the system moves to step S11 and the customer card search page 124 is displayed on the agency terminal 12. When the worker inputs conditions and presses the Search button 124Z, the system moves to step S12 and displays the customer candidate list 124X in the result display area 124A. When the worker selects a customer to refer to and presses the contract motivation record button 122Q of the customer card 122, the system moves to step S13 and displays the contract motivation list sheet 127 of the customer on the terminal 12. From here, the worker can check the contract motivation response record, print it, check (download) the insurance contract documents, and perform additional work.

[0044] (Action and effect) As described above, according to the insurance sales management system 1 of this embodiment, the contract motivations (contract history and intention understanding) until the customer subscribes to the insurance are recorded and managed in chronological order. Therefore, when the customer is considering a different insurance, the person in charge can look back at the contract motivation list sheet 127 to know how the customer thought at the time and what advice the customer received to choose that insurance, and can use it as reference material when designing the next insurance product. Also, if the customer complains after the insurance contract or at the time of insurance renewal, the misunderstanding can be cleared up by explaining it by looking back at the contract motivation list sheet 127, which leads to the prevention of trouble.

[0045] Moreover, according to the insurance sales management system 1 of this embodiment, all documents related to the insurance contract can be linked and managed in the contract motivation list sheet 127. That is, not only can the timeline of the contract motivation be confirmed, but also insurance contract documents such as payment means and necessary documents (driver's license, medical certificate, etc.) are centrally managed in the system 1, and a checklist (insurance contract document check box 127H) is also prepared, so that the progress of how much insurance contract documents have been prepared can be shared not only with the person in charge of the insurance contract, but with all the staff of the insurance agency A.

[0046] Second Embodiment (Configuration of insurance sales management system) FIG. 11 is a block diagram of an insurance sales management system 10 according to a second embodiment of the present invention. The same elements as those in the first embodiment are denoted by the same reference numerals and will not be described. The insurance sales management system 10 according to this embodiment includes an insurance management server 11, an agency terminal 12 (multiple are possible), and a communication network 3. The server storage unit 113 of the insurance management server 11 includes an accident record database 60 (hereinafter referred to as "accident record DB60") in addition to the customer card DB30. The accident record DB60 includes an accident record table 61 (described later). Information on the progress of an accident (accident record) when a customer has an accident is one of the customer important information that should be appropriately managed by an insurance agency, and the accident record table 61 is one of the customer important information tables referred to in the claims. The customer card 122 according to this embodiment includes an accident record button 122R (see FIG. 12). In this embodiment, the contract motivation DB50 is an optional configuration, so the contract motivation DB50 is indicated by a dashed line in FIG. 11, and the contract motivation record button 122Q is indicated by a dashed line in FIG. 12.

[0047] (Creating an accident record) When a customer has an accident, the worker inputs information about the accident into the system 10. When the worker presses the accident record button 122R on the customer card 122, the accident record list sheet 130 on the customer card 122 is displayed. FIG. 13 is a display example of the accident record list sheet 130. The accident record list sheet 130 can be input, viewed, and printed. The accident record list sheet 130 has a title input box 130A, an insurance claim document check box 130B, a file selection button 130C, an upload button 130D, a download button 130E, and an accident record input box 130F.

[0048] In the title input box 130A, the identification name of the accident can be entered as text, such as the date. The insurance claim document check box 130B is a column for checking the recording, installation, and sending of documents required for insurance claim, such as (i) photos, (ii) estimates, (iii) licenses, (iv) settlement agreements, and (v) invoices, and includes a record check column 131A, an installation date column 131B, and a sending date column 131C. In the record check column 131A, a check is placed when the recording of document data in the system 10 has been completed using the upload button 130D, which will be described later. The installation date column 131B and the sending date column 131C each include a calendar input button in the box, and the installation date / sending date of the document can be entered by selecting a date from a pop-up calendar or by entering text.

[0049] Next, the file selection button 130C allows reference to the document files (i) to (v) above. In response to the selection of the file selection button 130C, the calculation unit of the agency terminal 12 refers to the file to be uploaded from the terminal 12, and uploads it to the system 10 by the upload button 130D. When the selection of the upload button 130D is accepted, the server control unit 112 transmits the file to be uploaded to the accident record DB 60. The file selection button 130C and its paired upload button 130D can also add the number of files by pressing the plus button. The download button 130E displays the file name of the insurance contract document data uploaded from the sheet 130 to the system 10, and pressing the button allows each document to be downloaded to the terminal 12.

[0050] In the accident record input box 130F, comments on the progress of the accident can be input in chronological order. The accident record input box 130F has a response date field 132A, a response time field 132B, a negotiation / contact field 132C, a response content field 132D, and a responder field 132E. In the accident record input box 130F, the response date, time, negotiation / contact, response content, and responder are entered in rows in chronological order, and rows can be added with the plus button. The response date field 132A has a calendar input button in the box, and the response date can be input by selecting a date from a pop-up calendar or by text input. The response time field 132B can be used by workers as necessary and allows text input. The negotiation / contact field 132C allows text input of the company name, person in charge, etc. of the negotiation partner. The response content field 132D allows text input of the response content corresponding to the response date. In the respondent column 132E, the name of the employee of Insurance Company A is displayed in a select box.

[0051] (Input example 3: Mr. Aaa Taro, accident record of fire insurance claim due to water leakage) Response date: September 1, 2023 time:- Negotiations / Contact: Real estate management company A Response: Mr. Aaaaa Taro contacted us to say that sewage was backing up from the utility washing machine drain in Room 101. Response date: September 1, 2023 Time: 10:00 Negotiations / Contact: Mr. Aaa Taro Response: Mr. Aaaa Taro notified us that he would be receiving a call from Company A regarding a water leak in rental apartment B. Receptionist:□□ Response date: September 24, 2023 Time: 2 p.m. Negotiations / Contact: Company A, Mr. C Response: I was contacted about the details of the accident. I requested photos and an estimate. Respondent: ●● Response date: September 25, 2023 time: Negotiations / Contact: Mr. Aaa Taro Response: The insurance claim form was submitted.

[0052] (Example 4: Mr. Aaa Taro, accident record of automobile insurance claim due to collision) Response date: October 1, 2023 Time: 22:00 Negotiations / Contact: Mr. Aaa Taro Response: Accident occurred Response date: October 2, 2023 Time: 10:00 Negotiations / Contact: Mr. Aaa Taro Content of the call: Report of a collision with another vehicle. Collision with a vehicle turning right at address XX, ward XX, rendering the vehicle unable to move. The other party's insurance company is D Company. The other party's phone number is XXX-XXXX-XXXX. Receptionist:▲▲ Response date: October 3, 2023 time: Negotiations / Contact: Company D, Mr. E Response: Talk about the accident. The police told me that there was damage to the exterior wall at the accident site. Since I felt that there would be a dispute with the other party, I proposed a special lawyer's agreement. After the explanation, I agreed. Receptionist:▲▲ Response date: October 10, 2023 time: Negotiations / Contact: Company D, Mr. E Response: Obtaining accident certificate. Respondent: ●● Response date: October 20, 2023 time: Negotiations / Contact: Attorney F Response: I received an inquiry about whether to include a research company. Receptionist:▲▲ ...

[0053] When the worker presses the Add button 130Z, the server control unit 112 stores new contract motivation information in the accident record table 61 of the accident record DB 60, linking it to the customer card 22. When the worker presses the Print button 130P, the server control unit 112 outputs the displayed accident record list sheet 130 in an A4 size portrait print layout to the printer connected to the agency terminal 12. The printout has the initial creation date and last update date of the accident record list sheet 130 added to the header, and the page number added to the footer.

[0054] 14 is an example of an accident record table 61 of the accident record DB 60. In the accident record table 61, the accident information input in the input boxes 130A-130D, 130F, that is, the title, insurance claim document check information, file information, and accident record information, are stored in association with the management ID of the customer on the customer card 122. Of these, the insurance claim document check information, file information, and accident record information have sub-tables 611-613, and the names of the sub-tables to be referenced are stored in table 61.

[0055] The lower table 611 is an insurance claim document check table 611 in which the presence or absence of checks in the check fields 131A to 131C of the insurance claim document check box 130B, as well as the installation date and the sending date are recorded. If there is a check, "Yes" is recorded, and if there is no check, "No" is recorded, and the installation date and the sending date of each document are recorded in association. The lower table 612 is a file information table 612 for managing files uploaded by the file selection button 130C, in which a file name, a file path, and a link are stored in association with each other. The file path indicates the storage location of the file in the server storage unit 113, for example, a folder or a directory. The lower table 613 is an accident record chronological table 613 for storing the contents entered in the accident record input box 130F, in which each piece of information 132A to 132E is stored in association with each other and arranged in chronological order. When a customer has an accident, or when there is progress in resolving the accident, the worker searches for the customer card 122 from the search page 124 (see FIG. 9). From here, when the accident record button 122R is pressed, the accident record list sheet 130 is displayed.

[0056] Here, it is also preferable that the insurance sales management system 10 has a variation that issues an alert if the insurance claim document check box 130B is not checked. When the worker thinks that he has finished inputting and presses the add button 130Z, the server control unit 112 refers to the insurance claim document check table 611, and if the check is "no", it is also preferable that the server control unit 112 issues an alert such as "Documents are missing" on the display unit 13 of the terminal 12 and then closes the page.

[0057] (Use of insurance sales management system) Next, an insurance sales management method using the insurance sales management system 10 configured as above will be described. FIG. 15 shows the workflow of insurance sales management, FIG. 15(A) is a preparation flowchart for using the insurance sales management system 10, and FIG. 15(B) is a flowchart for using the insurance sales management system 10. In the preparation flowchart (FIG. 15(A)), when the insurance sales management system 10 is started from the agency terminal 12 and the new customer registration button 121A is pressed from the top page 121, the system proceeds to step S21, the customer card 122 is displayed on the agency terminal 12, and the creation of the customer card 122 is permitted. When the worker finishes inputting and presses the add button 122Z, the system proceeds to step S22, and the customer information is stored in the customer management table 31, the customer information table 32, the family information table 33, the account information table 34, and the delivery destination information table 35. Next, the system proceeds to step S23, and permits input of the accident record list sheet 130. When the worker finishes inputting and presses the Add button 130Z, the system moves to step S24, stores the accident record information in the accident record table 61, and ends the system. In the flowchart of system usage (FIG. 15(B)), when the insurance sales management system 10 is started from the agency terminal 12 and the customer search button 121B is pressed from the top page 121, the system moves to step S31 and the customer card search page 124 is displayed on the agency terminal 12. When the worker inputs conditions and presses the Search button 124Z, the system moves to step S32 and displays the customer candidate list 124X in the result display area 124A. When the worker selects a customer to refer to and presses the Accident Record button 122R on the customer card 122, the system moves to step S33 and displays the customer's accident record list sheet 130 on the terminal 12. From here, the worker can check the accident progress, print it, check (download) the insurance claim documents, and perform additional work.

[0058] (Action and effect) As described above, according to the insurance sales management system 10 of this embodiment, important details of the insurance agency's response to customers, particularly the response records when the customer has an accident, are stored and managed in chronological order. Therefore, when insurance agency A receives an inquiry from an accident-related party, the responder can learn the accident summary, the course of the incident, and the progress by looking at the accident record list sheet 130, so that all staff members of insurance agency A can respond quickly and efficiently until the incident is resolved. In addition, since inquiries from accident-related parties that require urgent responses require delicate responses, responding by looking at the accident record list sheet 130 can lead to the prevention of trouble.

[0059] Moreover, according to the insurance sales management system 10 of this embodiment, all documents related to the accident can be linked and managed to the accident record list sheet 130. That is, not only can the timeline of the accident progress be confirmed, but also insurance claim documents such as estimates and appraisals for building and automobile repairs, on-site and actual photos, medical fee statements, and settlement agreements are managed in a unified manner by the system 10, and a checklist (insurance claim document checkbox 130B) is also prepared, so that the progress of the insurance claim documents can be shared not only with the person involved in the transaction, but also with all the staff of the insurance agency A.

[0060] Although the preferred embodiment and modified examples of the present invention have been described above, these can be modified and combined based on the knowledge of those skilled in the art, and such forms are also included in the scope of the present invention. In addition, since the present invention is constructed so that the contract motivation information and accident record information can be handled not only by the insurance salesperson in charge but also by the entire insurance agency, it is also effective in the business succession of the insurance agency, making it easy to take over the business. [Explanation of symbols]

[0061] 1,10...insurance sales management system, 11...insurance management server, 12...agency terminal, 31...customer management table, 32...customer information table, 51...contract motivation table (customer important information table), 61...accident record table (customer important information table), 122...customer card, 127...contract motivation list sheet, 130...accident record list sheet 127F,130D...upload button 127G,130E...download button 127H...insurance contract document check box 127I...system input check box, 130B...insurance claim document check box

Claims

1. An insurance management server managed by an insurance agency and an agency terminal capable of communicating with the insurance management server, The insurance management server, based on the customer card created at the agent terminal, storing a customer management table for storing the customer names and management IDs of the customers of the insurance agency in association with each other, a customer information table for storing the management IDs and the customer information of the customers in association with each other, and a customer important information table for storing the management IDs and the customer important information related to the contract motivation or accident record related to the insurance contract of the customers in association with each other; The insurance management server identifies the customer searched for from the agent terminal based on the customer information table, and displays a list of contract motivations or accident records related to the insurance contract of the customer on the agent terminal by referring to the customer important information table. An insurance sales management system characterized by:

2. 2. The insurance sales management system according to claim 1, wherein the contract motivation list sheet, which is a list of the contract motivation, lists the dates and contents of interactions with the customer regarding the contract motivation in chronological order.

3. 2. The insurance sales management system according to claim 1, characterized in that the accident record list sheet, which is a list of the accident records, lists the dates and contents of correspondence regarding communications with those involved in the accident regarding the accident records in chronological order.

4. The insurance sales management system described in claim 1, characterized in that the contract motivation list sheet, which is a list of the contract motivations, and the accident record list sheet, which is a list of the accident records, are provided with buttons that enable necessary documents to be uploaded to the insurance sales management system and downloaded to the agent terminal.

5. 3. The insurance sales management system according to claim 2, wherein the contract motivation list sheet includes an insurance contract document check box for checking whether documents required for an insurance contract have been recorded in the insurance sales management system.

6. 4. The insurance sales management system according to claim 3, wherein the accident record list sheet includes an insurance claim document check box for checking whether documents required for insurance claims have been recorded in the insurance sales management system.

7. The insurance sales management system according to claim 2, characterized in that the contract motivation list sheet is provided with a system input checkbox for checking whether important information on the customer card has been recorded in the insurance sales management system and whether the contract motivation list sheet has been recorded in the system.

8. The insurance sales management system according to claim 6, characterized in that the insurance claim document check box on the accident record list sheet includes a column for recording the attachment date and the sending date of the documents required for the insurance claim in the insurance sales management system.

9. based on the customer card created from the agency terminal, communicates information with an insurance management server that stores a customer management table that associates and stores the customer name and management ID of the customer of the insurance agency, a customer information table that associates and stores the management ID and the customer information of the customer, and a customer important information table that associates and stores the management ID and the customer important information related to the contract motivation or accident record related to the insurance contract of the customer, Identifying the customer searched for from the agency terminal based on the customer information table; a step of displaying a list of contract motivations or accident records related to the insurance contract of the customer on the agent terminal by referring to the customer important information table of the customer; An insurance sales management method comprising:

10. 10. An insurance sales management program, comprising: a computer program that executes the insurance sales management method according to claim 9.

11. A computer-readable recording medium having the computer program according to claim 10 recorded thereon.

Images