Insurance Information Management System

Abstract

Providing technology to make it easier to understand the details of insurance contracts. [Solution] The insurance information management system 1 includes an insurance management application 510 that runs on a customer's user terminal 500, a first storage unit 111, 211 on the cloud managed by the insurance agency, which is capable of storing customer contract information acquired from the insurance agency's agent terminal 600 and the insurance company server 400, and a customer information provision unit 114 on the cloud managed by the insurance agency, which provides the contract information stored in the first storage unit 111, 211 to the insurance management application 510 on the user terminal 500 or the agent terminal 600.

Description

Technical Field

[0001] The present disclosure relates to a system for managing insurance contract information.

Background Art

[0002] A variety of insurances (insurance products) are sold by many insurance companies. Individual and corporate customers select and contract for an insurance that matches their own needs from among many insurances. However, once an insurance is subscribed, there is almost no opportunity to review the contract content until the occurrence of a payment reason or contract renewal, and there are cases where not only the contract content of the insurance but also the existence itself of the insurance is forgotten.

[0003] An insurance agency that receives insurance consultations from customers can grasp the contract content of an insurance that it has contracted or brokered on its own. However, for an insurance that a customer has contracted with another insurance agency or an insurance that a customer has directly contracted with an insurance company through the Internet or the like, the existence and contract content of the insurance cannot be known unless directly asked by the customer, and appropriate advice or proposals cannot be given for the customer's consultation. And even if the customer is asked about an insurance that is an out-of-company contract or a direct contract insurance, if the customer himself / herself has forgotten the contract content or the contract itself, appropriate advice or proposals cannot be given.

Summary of the Invention

Problems to be Solved by the Invention

[0004] One of the objects of the present disclosure is to facilitate grasping of insurance contract content.

Means for Solving the Problems

[0005] [1] One aspect of the present disclosure is an insurance information management system for sharing insurance contract information between a customer and an insurance agent, and includes an insurance management application that operates on the customer's user terminal, a first storage unit on the cloud managed by the insurance agent and capable of storing the customer's contract information obtained from the insurance agent's agent terminal and the insurance company's computer, and a customer information provision unit on the cloud managed by the insurance agent and capable of providing the contract information stored in the first storage unit to the insurance management application on the user terminal or the agent terminal.

[0006] According to one aspect of this disclosure, insurance contract information for each customer can be shared between the customer and the insurance agent.

[0007] Insurance agencies typically manage sales information using CRM (Customer Relationship Management) systems provided by external vendors. While CRM excels at internal sharing of product information, sales management information, and customer information (contract information, profile information), it is less effective in improving the convenience of information sharing with customers.

[0008] According to this, the insurance information management system allows insurance contract information to be shared between the customer and the insurance agent. This system includes an insurance management application that runs on the customer's user terminal, the insurance agent's agent terminal, and a first cloud-based storage unit managed by the insurance agent that can store the customer's contract information acquired from the insurance company's computer. This allows the contract information shared between the customer and the insurance agent to be consolidated in the first storage unit. In this case, the contract information can be reliably integrated by obtaining it from the agent terminal if the agent acted as an agent or intermediary in concluding the contract, from the user terminal if the customer directly contracted with another insurance agent or insurance company, and from the insurance company's computer if the insurance company, as the insurer, can provide the contract information. When the information is obtained from the insurance company's computer, accurate contract information held by the insurance company can be obtained, reducing the input work and input errors of contract information at the insurance agent.

[0009] The following four cases are examples of obtaining data from the aforementioned insurance company's computer:

[0010] The first case is when an insurance agent's terminal obtains data including contract information from the insurance company's computer, processes the data as needed by deleting unnecessary data, organizing the data, or adding data, and then transmits the processed data including contract information to the first storage unit for storage.

[0011] The second case is when the insurance agent's terminal obtains data including contract information from the insurance company's computer and transmits it directly to the first storage unit for storage without performing the aforementioned data processing.

[0012] The third case is when the first storage unit directly acquires data including contract information from the insurance company's computer and transmits it to the first storage unit for storage without performing the aforementioned data processing.

[0013] The fourth case is when the first storage unit directly acquires data including contract information from the insurance company's computer, processes the data as described above, and stores it in the first storage unit.

[0014] One embodiment of the above is an insurance information management system that includes a customer information provision unit on the cloud, managed by the insurance agency, which provides the contract information stored in the first storage unit to the insurance management application on the user terminal or the agency terminal.

[0015] According to this, customer contract information integrated into the first memory unit can be provided to the insurance management app or agent terminal regardless of the acquisition method, and a platform can be built that allows customers and insurance agents to centrally manage contract information.

[0016] [2] The above embodiment may include a second cloud-based storage unit managed by the insurance agency, which is capable of storing the customer profile information acquired from the agency terminal.

[0017] Personal information (profile information) about customers' personal and professional lives, obtained by insurance agency sales representatives through gaining customer trust, is a valuable information asset for continuously making timely and accurate sales proposals throughout the customer's lifecycle. However, such information is often managed personally by insurance agency sales representatives and is not fully utilized organizationally in agency sales. According to one embodiment described above, by including a second cloud-based storage unit managed by the insurance agency that can store the customer profile information acquired from the agency terminal, the profile information for each customer can be aggregated in the second storage unit and utilized for organizational sales proposals to customers.

[0018] [3] The above embodiment includes a third storage unit on the cloud managed by the insurance agency, which is capable of storing information regarding the progress of accident response acquired from the agency terminal, and the customer information provision unit may provide the information regarding the progress of accident response to the insurance management application on the user terminal.

[0019] According to this system, information regarding the progress of accident response can be aggregated in a third memory unit and provided to the insurance management app on the user's terminal. This allows customers to be immediately informed of any progress, reducing their anxiety about a lack of information regarding accident response.

[0020] [4] The insurance management application includes an accident response progress display unit that displays information regarding the progress of the accident response, and the accident response progress display unit may include at least one of a personal injury liability unit, a property damage liability unit, and a vehicle compensation unit for each accident.

[0021] According to this, customers can identify what actions they need to take regarding personal injury liability, property damage liability, and vehicle damage insurance, and can also track the progress of each.

[0022] [(5)] The accident response progress display section includes the personal injury compensation section, the property damage compensation section, or the vehicle compensation section within one screen for each accident. The personal injury compensation section, the property damage compensation section, or the vehicle compensation section may include a progress display indicating the degree of progress towards completion of the response or the response history by at least one of characters, numbers, figures, symbols, colors, graphs, still images, or animations.

[0023] Since the accident response progress display section includes the personal injury compensation section, the property damage compensation section, or the vehicle compensation section within one screen for each accident, the customer can grasp the progress status of personal injury compensation, property damage compensation, and vehicle compensation for each accident collectively on one screen.

[0024] Also, for example, when the insured has a car accident and the person in charge of the insurance agency is handling the accident response, the progress status of the process is mainly informed by phone, email, etc. Therefore, during the accident response, it is difficult to grasp what should be done and how far things have progressed. In particular, experiencing insurance accident response is rare, and the matters to be addressed also vary depending on the accident situation and the content of the insurance contract. Thus, it can be a major source of anxiety for customers that it is difficult to grasp the overall picture of the accident response and the degree of progress towards completion.

[0025] In contrast, since the personal injury compensation section, the property damage compensation section, or the vehicle compensation section includes a progress display indicating the degree of progress towards completion of the response or the response history by at least one of characters, numbers, figures, symbols, colors, graphs, still images, or animations, the customer can easily grasp the overall picture of the accident response and the degree of progress towards completion through the progress display.

[0026] [(6)] The one aspect may include a proposal generation section on the cloud that generates proposal information regarding products or services related to accident prevention, disaster prevention, or disease prevention based on the contract information for each customer.

[0027] Insurance is a "preparation" against accidents, disasters, illnesses, etc. In contrast, the said aspect includes a proposal generation unit on the cloud that generates proposal information regarding products or services related to accident prevention, disaster prevention, or illness prevention for each said customer based on the said contract information. Therefore, not only the "preparation" by insurance but also a one-stop service that supports customers including products or services related to the prevention of the occurrence of accidents, disasters, illnesses, etc. can be provided.

[0028] 〔7〕The said proposal generation unit may be configured to be able to generate the said proposal information for each said customer based on the profile information regarding the public and private aspects of the said customer.

[0029] According to this, based on the analysis of the customer's profile information, more accurate proposal sales of products and services can be carried out.

[0030] 〔8〕The said user terminal may include a settlement app that executes settlement processing for purchases made in the said insurance management app. [[ID=!4]]

[0031] According to this, since the settlement app can be used for settlement in the insurance management app, purchases and settlements of insurance, etc. in the insurance management app can be executed smoothly. That is, an insurance management app can be constructed as a platform that can provide not only various insurances but also products or services related to the prevention of related accidents, disasters, illnesses, etc. in one stop.

[0032] 〔9〕One aspect of the present disclosure may include a notification unit that notifies the said insurance management app of information regarding the expiration of the contract period based on the said contract information of the insurance contracted by the said customer through the said insurance agent and the said contract information of the insurance contracted through another insurance agent.

[0033] According to this, the notification unit can automatically notify customers of information regarding the expiration of each insurance policy they have, based on the contract information stored in the first memory unit, making it easy to manage contract renewals and other matters even if they have many insurance policies. Furthermore, since the insurance policies targeted by the notification unit include not only those contracted through insurance agents but also those contracted through other insurance agents, notifications can be sent for all insurance policies, regardless of whether they are contracted by the company or another company.

[0034]

[10] One aspect of the present disclosure is an insurance information management method for sharing insurance contract information between a customer and an insurance agent, the method comprising: storing the customer's contract information obtained from an insurance management application running on the customer's user terminal, the insurance agent's agent terminal, and the insurance company's computer in a first storage unit on the cloud managed by the insurance agent; and providing the contract information stored in the first storage unit to the insurance management application on the user terminal or the agent terminal.

[0035] This allows for the sharing of individual customer insurance contract information between the customer and the insurance agent. Furthermore, it can perform similar functions to the aforementioned insurance information management system.

[0036]

[11] The above embodiment may include storing the customer profile information obtained from the agent terminal in a second storage unit on the cloud managed by the insurance agent.

[0037] According to this, customer-specific profile information can be aggregated in the second memory unit, which can then be used for organized sales proposals to customers.

[0038]

[12] The above embodiment may include storing information regarding the progress of accident response obtained from the agent terminal in a third storage unit on the cloud managed by the insurance agent, and providing the information regarding the progress of accident response stored in the third storage unit to the insurance management application on the user terminal.

[0039] According to this system, information regarding the progress of accident response can be aggregated in a third memory unit and provided to the insurance management app on the user's terminal. This allows customers to be immediately informed of any progress, reducing their anxiety about a lack of information regarding accident response.

[0040]

[13] The insurance management application includes an insurance list display unit that displays the insurance for each product category, the insurance list display unit includes an insurance display unit for each product category, and the insurance display unit may be configured to allow visual confirmation of whether or not the insurance in the product category is already in contract.

[0041] The insurance management app includes an insurance list display section that shows insurance policies categorized by product category. This makes it easy for customers to comprehensively understand various insurance policies. Furthermore, the insurance list display section includes an insurance display section for each product category, and the insurance display section allows customers to visually see whether or not they have contracted insurance policies in that product category. This makes it easy for customers to see which product categories they currently have insurance policies in.

[0042]

[14] The insurance management application may include a contracted insurance list display unit that lists and displays the contracted insurances when one of the insurance display units is selected on the user terminal.

[0043] This allows for easy access to contract information for insurance policies that have already been contracted for each product category.

[15] The insurance management application may be a mini-application used on a super application that includes messaging functionality used on the user terminal.

[0044] According to this, customers can access the insurance management app from a super app with messaging functions they are familiar with, increasing the opportunities for customers to see the insurance management app and its notifications. In particular, when the insurance management app is displayed in a browser, it is necessary to open the browser, select it from bookmarks, and then display it. However, with the aforementioned mini-app, such operations are unnecessary, improving convenience and making it easier for customers to access. Furthermore, using a mini-app eliminates the need to develop a dedicated app, which is an advantage for insurance agencies as it makes implementation easier. [Effects of the Invention]

[0045] According to one aspect of this disclosure, insurance contract information can be shared between the customer and the insurance agent for each customer. [Brief explanation of the drawing]

[0046] [Figure 1] A diagram illustrating an insurance information management system according to one embodiment. [Figure 2] A functional block diagram of an insurance information management system according to one embodiment. [Figure 3] An explanatory diagram of the top screen of an insurance management app according to one embodiment. [Figure 4] An explanatory diagram of an example of the insurance list screen, continuing from Figure 3. [Figure 5] An explanatory diagram of an example of the contracted insurance list screen, continuing from Figure 4. [Figure 6] This is an explanatory diagram of an example of a car insurance contract information screen, continuing from Figure 5. [Figure 7] An explanatory diagram of an example of the product lineup screen, continuing from Figure 3. [Figure 8] This is an explanatory diagram of an example of the accident response progress confirmation screen, following Figure 3. [Figure 9] An explanatory diagram of an example of the accident response progress screen, following Figure 8A. [Figure 10] An explanatory diagram illustrating the display modes of the accident response progress display unit. [Figure 11] Functional block diagram of an insurance information management system according to a modified embodiment.

[0047] Figures 3 to 10 are examples of screens of the insurance management app 510, which will be described later. Figure 3 shows the entire home screen of the insurance management app 510, while Figures 4 to 10 show excerpts of parts of each screen of the insurance management app 510. [Modes for carrying out the invention]

[0048] The following describes an embodiment relating to one aspect of this disclosure. The following embodiment is not intended to unduly limit the content of the claims of this disclosure, and not all of the configurations described in this embodiment are necessarily essential as solutions of this disclosure.

[0049] All embodiments and optional embodiments included in this disclosure may be combined to form new embodiments. Furthermore, all technical features and optional technical features included in this disclosure can be combined to form new technical features.

[0050] As used in this disclosure, the term "or" is used as an inclusive term. For example, "A or B" means "A, B, or both A and B." "A," "B," and "both A and B" each satisfy the condition "A or B."

[0051] The terms “first,” “second,” and “n” (where n is a natural number) used in this specification, claims, and drawings are used to distinguish different elements and do not indicate any particular order or hierarchy. Components common to each embodiment are denoted by the same reference numerals, and redundant explanations are omitted.

[0052] All steps and processes described herein, in the claims and drawings, i.e., in this disclosure, are illustrative and may be performed in the order described or randomly, as long as it does not cause inconsistencies in data processing. For example, where it is stated that a method includes steps A and B, it may include steps A and B performed sequentially, or steps B and A performed sequentially. Where it is stated that a method may further include step C, step C may be added to the method in any order, as long as it does not cause inconsistencies in data processing. For example, a method may include steps A, B and C performed sequentially, steps A, C and B, steps C, A and B, and so on.

[0053] As used in this disclosure, the term "**part" may include, for example, one or more hardware components, as well as a "functional component" consisting of one or more hardware components and one or more programs executed thereon. As used in this disclosure, the term "**system" performs a predetermined function through a combination of one or more hardware components and one or more programs executed thereon. The hardware described in this disclosure (examples include computers, servers, server computers, databases, user terminals, and the electronic devices comprising them) may include not only those consisting of a single physical device, but also those consisting of two or more physical devices connected in a communicative manner. Computers, servers, databases, combinations thereof, and various services such as SaaS provided by combinations thereof may include those built on a cloud provided by a cloud provider. In this case, the term "server" as used in this disclosure refers to a computer system that provides services and data to networked computers, including a control unit, storage unit, and communication unit, but its storage unit may include not only memory and storage, but also databases and data storage connected on a network (e.g., on a cloud environment). The programs described in this disclosure may include not only those that run and perform functions on a single piece of hardware, but also those that run and perform functions on multiple pieces of hardware that can communicate with each other.

[0054] The "information" subject to data processing as used in this disclosure includes programs, content, and data, which are represented by high and low signal values ​​as binary bit sets consisting of 0s and 1s, and calculations and communications are performed by a computer comprising one or more hardware components. The computer is composed of one or more processors, memory, circuit boards, wiring, etc., and all user terminals and servers described in this embodiment are composed of such a computer.

[0055] The following describes embodiments of systems, methods, apparatus, programs, etc., according to one aspect of this disclosure.

[0056] 1. Overview of the Embodiment

[0057] One aspect of the disclosure described below is a system (insurance information management system) for sharing insurance-related information (insurance information) between an insurance agency and its customers via a network. In this system, the insurance agency and its customers can each perform actions such as registering, updating, and displaying insurance information on a server that has the function of managing insurance-related information. Therefore, insurance-related information registered by the insurance agency on the server can be viewed (or edited) by the policyholder, while insurance-related information registered by the customer (policyholder) on the server can be viewed (or edited) by the insurance agency.

[0058] This allows insurance agents to have access to information about all the insurance policies their clients have contracted, enabling them to provide timely and appropriate services. On the other hand, clients can easily access information about all the insurance policies they have contracted. In particular, even if they have multiple policies from multiple insurance companies, clients can manage them all in one place and quickly grasp the information. Furthermore, when consulting with a third party about insurance, clients can consult based on accurate information about their insurance policies that has been centrally managed, thus alleviating their anxieties when seeking advice.

[0059] Unless otherwise specified, the terms used in this specification, the claims, and the drawings (hereinafter referred to as the “Disclosure”) are synonymous with the general terms used in the industry relating to any form of the Disclosure. The industry relating to any form of the Disclosure may include, but is not limited to, the insurance industry, the IT industry, and others. Some terms used in this Disclosure are defined below.

[0060] "Insurance" does not limit itself to any type of insurance; it can refer to any type of insurance. Insurance may include both individual and corporate insurance. Examples of individual insurance include, but are not limited to, automobile insurance, fire insurance, accident insurance, life insurance, long-term care insurance, disability insurance, income protection insurance, medical insurance, education insurance, pension insurance, and pet insurance. Examples of corporate insurance include, but are not limited to, executive insurance, liability insurance (premises liability, directors' and officers' liability, product liability, contractor's liability, etc.), group life insurance, and cyber insurance. In this disclosure, the term "insurance" may also be referred to as "insurance product."

[0061] "Insurance information" includes information about contracted insurance. Therefore, insurance information may include contract information and profile information as described below. The term "insurance information" may also be referred to as "information about insurance" in this disclosure.

[0062] "Information regarding contracted insurance" may include current insurance contract information relating to active contracts and past insurance contract information relating to contracts that have reached maturity.

[0063] The term "customer" refers to, but is not limited to, the "policyholder" who enters into an insurance contract with an insurance company, and may also include the "insured" under that contract. The policyholder and the insured may be the same person or different people.

[0064] "Customer information" may include contract information and profile information.

[0065] "Contract information" may include, but is not limited to, examples of policyholder information (policyholder's name, address, contact information, etc.), insured information (name, date of birth, gender, etc. of the insured person), policy number, type and details of insurance (name of insurance, coverage details, sum insured, etc.), insurance period (start date, end date, maturity date, etc.), premium (premium amount, payment method, payment frequency, etc.), beneficiary information (insurance beneficiary, relationship, etc.), special provisions (additional coverage details, etc.), exclusions, payment conditions, contract date, policy issuance date, and insurance company name. Due to the large amount of information and the unique specialization and complexity of insurance, it is difficult for customers to centrally manage insurance information for multiple policies from one or more insurance companies, but one aspect of this disclosure enables centralized management by the customer and the insurance agent.

[0066] "Profile information" may include, for example, occupation, place of origin, customer's family structure, family events, customer and family hobbies, sports, travel memories, children's extracurricular activities, wedding anniversary, how they spend their holidays, favorite foods, educational background, and social relationships. Such profile information may include, for example, non-public information obtained by an insurance agent's sales representative through sales activities with the customer, and publicly available information of the customer that the customer themselves or a third party makes public on the internet. Since contract information includes policyholder information and insured information, profile information may include some information that is common to contract information.

[0067] The term "product" can include both tangible goods (products in the narrow sense) and services. When referring to insurance products as mentioned above, it means insurance as a service.

[0068] 2. Overview of the Insurance Information Management System

[0069] The following describes an example of an embodiment of the insurance information management system described herein. Figure 1 is an explanatory diagram illustrating the overall configuration of the insurance information management system 1.

[0070] The insurance information management system 1 may include an insurance management server 100, an agent server 200, an external application server 300, an insurance company server 400, a user terminal 500, and an agent terminal 600. These are configured to be connectable to a network N such as the Internet.

[0071] Both the insurance management server 100 and the agent server 200 can be built on-premises, on dedicated servers, as SaaS, or in a cloud environment provided by a cloud provider. Examples of cloud environments from cloud providers include Amazon Web Services (Amazon and AWS are registered trademarks), Microsoft Azure (Microsoft and Azure are registered trademarks), and Google Cloud Platform (Google and GCP are registered trademarks), but are not limited to these and other cloud environments are also acceptable.

[0072] The insurance information management system 1 is not limited to the example in Figure 1, but may include any computer (including a database) that functions as an insurance management server 100, an agent server 200, an external application server 300, an insurance company server 400, a user terminal 500, and an agent terminal 600, regardless of the type, configuration, or number of hardware components. There may be at least as many user terminals 500 as there are customers. There may be as many agent terminals 600 as there are terminals in one or more insurance agencies. In this case, the agent terminals 600 may include not only insurance agencies operated by the same entity, but also multiple insurance agencies operated by different entities.

[0073] The insurance management server 100 may be, but is not limited to, a server computer. The control unit 101 includes one or more processors. The storage unit 102 includes volatile memory such as RAM and non-volatile memory such as a hard disk. The storage unit 102 includes an OS, server program, and database that enable the server computer to function as the insurance management server 100. The communication unit 103 includes at least one of a communication interface for wired communication and a communication interface for wireless communication. The insurance management server 100 enables the insurance management application 510 to function as a mini-application usable from the external application server 300, which will be described later. The control unit 101, storage unit 102, and communication unit 103 that constitute the insurance management server 100 can be built in a cloud environment provided by a cloud provider. The insurance management server 100 is managed by an insurance agency that provides services to customers.

[0074] The agency server 200 may, but is not limited to, a server computer. The physical configuration of the control unit 201, storage unit 202, and communication unit 203 may be the same as that of the control unit 101, storage unit 102, and communication unit 103, respectively. The storage unit 202 includes an OS, server program, and database that enable the server computer to function as the agency server 200. The agency server 200 is managed by an insurance agency that provides services to customers. The agency server 200 may be configured to include at least one of the following: an on-premise server of the insurance agency, a dedicated server, a CRM (Customer Relationship Management) service provided by an external provider on the cloud, or a server (including a database) built in a cloud environment provided by a cloud provider.

[0075] The external application server 300 may, but is not limited to, a server computer. The physical configurations of the control unit 301, storage unit 302, and communication unit 303 may be the same as those of the control unit 101, storage unit 102, and communication unit 103, respectively. The external application server 300 provides a super application 515 that runs on the user terminal. A super application 515 is an application that functions as a platform in which multiple applications are integrated. A mini application is an application that can be used from the platform of the super application 515. The external application server 300 is managed by an external service provider that provides platform services to customers. An example of a super application 515 realized by such an external application server 300 is LINE®.

[0076] The insurance company server 400 may, but is not limited to, a server computer. The insurance company server 400 constitutes a "computer" in one embodiment. The physical configuration of the control unit 401, storage unit 402, and communication unit 403 may be the same as that of the control unit 101, storage unit 102, and communication unit 103, respectively. The insurance company server 400 is managed by the insurance company that is the insurer.

[0077] The user terminal 500 is a computer managed by the customer. The user terminal 500 may be, for example, a personal computer, a smartphone, a tablet, or a wearable device, but is not limited to these, and can be any terminal that functions as a computer. The physical configuration of the control unit 501, the storage unit 502, and the communication unit 503 may be the same as that of the control unit 101, the storage unit 102, and the communication unit 103, respectively.

[0078] The operation unit 504 is an input device such as a touch panel, mouse, or keyboard. The display unit 505 is a display device having a display screen such as a liquid crystal display or an organic EL display.

[0079] The agent terminal 600 is the insurance agency's computer. The agent terminal 600 may be located inside or outside the insurance agency. The agent terminal 600 may be, but is not limited to, a personal computer, tablet, or smartphone. The physical configuration of the control unit 601, storage unit 602, communication unit 603, operation unit 604, and display unit 605 may be the same as that of the control unit 101, storage unit 102, communication unit 103, operation unit 504, and display unit 505, respectively. The agent terminal 600 is managed by the insurance agency.

[0080] The various programs that constitute the insurance information management system 1, which are stored and executed on the insurance management server 100, the agent server 200, the user terminal 500, and the agent terminal 600, may be provided to them via the network N or via a computer-readable storage medium.

[0081] The insurance information management system 1 described above allows insurance contract information to be shared between the customer and the insurance agent for each customer. For example, by combining the insurance application system 10 (front-end insurance management application 510 and back-end insurance management server 100), which serves as a point of contact with the user terminal 500, with the agent server 200 that stores customer information (contract information, profile information), the insurance application system 10 can be made to function as a customer contact tool (CRM tool), thereby enabling effective utilization of the data stored in the agent server 200. This makes it possible, for example, to introduce a CRM tool while utilizing an existing agent server.

[0082] 3. Functions realized by the embodiment

[0083] Figure 2 is a functional block diagram implemented in this embodiment.

[0084] 3.1 Functions provided by the insurance management server 100

[0085] The insurance management server 100 implements each functional unit by executing an insurance management program (not shown in the diagram).

[0086] The linkage unit 110 is primarily implemented by the control unit 101 and the communication unit 103. The linkage unit 110 sends and receives data between the agency server 200 and the user terminal 500. In other words, the linkage unit 110 operates as an "acquisition unit" that acquires data, including contract information, from the user terminal 500 and the agency server 200. The linkage unit 110 operates in conjunction with the linkage unit 210 of the agency server 200 to synchronize and store customer information and contract information in the respective customer information storage units 111, 211 and contract information storage units 113, 213. The synchronization method can be selected according to the specifications of the insurance management server 100 and the agency server 200, and can include file synchronization tools, API integration, message queue synchronization, database replication, etc.

[0087] The customer information storage unit 111 is primarily implemented by the storage unit 102 and includes a storage device such as a database that stores customer information (data including customer information). The customer information storage unit 111 constitutes the "second storage unit". A customer may include a policyholder and an insured, but in this embodiment, the customer is the policyholder. The customer information storage unit 111 includes customer information for each customer.

[0088] Customer information is unique to each customer and includes contract information and profile information. Contract information may include, for example, business partner ID, customer number, contract name, address, telephone number, email address, individual / corporate type, date of birth, etc.

[0089] The customer ID is a common ID used to identify customers in the components of the insurance information management system 1, which includes the agency server 200, agency terminal 600, insurance management server 100, insurance management application 510, messaging unit 516, and super application 515. The customer number is a number used to distinguish customers in the operations of insurance agencies and is associated with the customer ID.

[0090] Profile information is personal information relating to a customer's public and private life. Profile information may include information about the policyholder, the insured, and their relationships. For example, profile information may include occupation, place of origin, family structure, family events, hobbies, sports, travel memories, children's extracurricular activities, wedding anniversaries, how holidays are spent, favorite foods, educational background, and social relationships. Profile information may include both confidential and public information. Confidential information is, for example, information obtained directly from a customer by an insurance agent through sales activities. Public information is information made public on the internet by the customer themselves or by a third party. Therefore, the source of the profile information is irrelevant.

[0091] The subscriber information and profile information may or may not be distinguished to contain only different information. In the latter case, one or more identical pieces of information may be included redundantly.

[0092] The application management ID storage unit 112 is primarily implemented by the storage unit 102 and includes a storage device such as a database that stores information related to the management of various applications for each customer. The application management ID storage unit 112 may include, but is not limited to, a business partner ID, an insurance management application ID, and a super application ID.

[0093] The customer ID is the same as the customer ID included in the aforementioned customer information. The insurance management app ID is data that identifies the insurance management app 510 on user terminal 500. The super app ID is data that identifies the super app 515 on user terminal 500. User terminal 500 and super app 515 are identified by the insurance management app ID and the super app ID.

[0094] The contract information storage unit 113 is primarily implemented by the storage unit 102 and includes a storage device such as a database that stores contract information for insurance policies currently in place for each customer. The contract information storage unit 113 constitutes the "first storage unit". By holding contract information, the contract information storage unit 113 aggregates data such as contract information acquired from the agency server 200 or user terminal 500 to the insurance management server 100, enabling the sharing of contract information between the insurance agency's agency terminal 600 and the customer's user terminal 500.

[0095] Contract information may include the customer ID, insurance company name, policy number, insurance period (start date), insurance period (end date), lifetime flag, premium, premium payment method, insurance type name, and insured name. Depending on the type of insurance, it may also include, but is not limited to, the following information. Identical information items across different insurance types are used interchangeably. <Auto Insurance> Vehicle name, registration number (license plate), insurance amount, vehicle insurance amount, bodily injury compensation amount, property damage compensation amount, replacement vehicle / rental car (daily rate), vehicle insurance type, personal injury / injury compensation type, age conditions, family-only coverage, etc. <Fire Insurance> Number of family members living together, district and date, total floor area, location of building and household goods, building structure, etc. <Earthquake Insurance> Location of building and household goods, building structure, etc. <Medical / Cancer Insurance> Daily hospitalization benefit, daily outpatient benefit, lump-sum payment for three major diseases, lump-sum payment for specific diseases, lump-sum payment upon cancer diagnosis, number of days of hospitalization, anticancer drugs, etc. <Accident Insurance> Death, hospitalization, outpatient treatment, coverage scope, eligible persons, etc. <Child Insurance> Maturity benefits, lump sum payments, educational annuities, etc. <Pet Insurance> Covers hospitalization, outpatient visits, surgery, etc. <Long-term care insurance> Lump-sum payment, pension, payment criteria, payment methods, etc. <Pension Insurance> Pension amount, accumulated amount, payment method, etc.

[0096] The registration items for each insurance policy included in the above contract information are defined in the insurance registration item table. The insurance registration item table is stored in the contract information storage unit 113 and can be edited by the agent terminal 600.

[0097] The customer information provision unit 114 is primarily implemented by the control unit 101 and the communication unit 103. Based on a transmission request from the agency server 200 or the insurance management application 510, the customer information provision unit 114 selects the necessary information about the customer who made the transmission request from the storage unit 102 and performs the process of transmitting it through the communication unit 103. The selected information may be customer information or contract information.

[0098] The notification unit 115 is primarily implemented by the control unit 101 and the communication unit 103. The notification unit 115 sends notifications to the user terminal 500, and the notification content is displayed in the insurance management application 510. The notification may include, but is not limited to, information related to contract information (insurance period end date, information registration by the insurance agent, etc.), information related to accident response progress management, and information related to product information (preventive products, preventive services, product suggestion information). Other content may also be included as notification content. The notification settings may be set by the insurance agent, or the customer may be able to set them on the account settings screen of the insurance management application 510 (see Figure 3).

[0099] The accident response progress management memory unit 116 is primarily implemented by the memory unit 102 and includes a storage device such as a database that stores information regarding the progress of accident response. The accident response progress management memory unit 116 constitutes the "third memory unit". The accident progress management table stored in the accident response progress management memory unit 116 may include, for example, the customer ID, the overall progress of the accident case (in progress, completed, withdrawn), the date of the accident, the policy number, the policyholder name, the date and time of receipt, the type of compensation (personal injury, property damage, vehicle), personal injury compensation progress, personal injury compensation progress update date, property damage compensation progress, property damage compensation progress update date, vehicle compensation progress, vehicle compensation progress update date, and accident progress management ID, but is not limited to these and may include other information or omit some information.

[0100] The progress of personal injury liability, property damage liability, and vehicle compensation can be organized into four stages: Stage 1, Stage 2, Stage 3, and Stage 4 (Completion), along with five statuses including withdrawal. However, the number of stages is not limited to these, and there may be more than four stages (see Figures 9 and 10). Stages 1 through 4 can be defined as follows, for example, but the number of stages and the content of each stage can be configured according to the insurance agent, type of insurance, coverage details, accident details, etc. For example, "accident acceptance" may be considered Stage 1 before matching the accident situation in Stage 1 below. Also, "Step 1" through "Step 4" in the definitions below refer to the progress indicators shown in Figures 9 and 10.

[0101] <Personal Liability Compensation Progress Update> • Stage 1 (Step 1): Matching accident details (25% of 100% completion) • Stage 2 (Step 2): Completion of treatment (50% of 100% completion) • Stage 3 (Step 3): Determination of compensation amount (75% of 100% completion) • Stage 4 (Step 4): Payment complete (100% of progress) <Property Damage Compensation Progress Information> • Stage 1 (Step 1): Matching accident details (25% of 100% completion) • Stage 2 (Step 2): Determination of the amount of damage (50% of 100% completion) • Third stage (Step 3): Determination of fault ratio / determination of compensation amount (75% of 100% completion) • Stage 4 (Step 4): Payment complete (100% of progress) <Vehicle compensation progress> • Stage 1 (Step 1): Matching accident details (25% of 100% completion) • Stage 2 (Step 2): Determination of the amount of damage (50% of 100% completion) • Third stage (Step 3): Determination of fault ratio / determination of compensation amount (80% of 100% completion) • Stage 4 (Step 4): Payment complete (100% of progress)

[0102] The product information storage unit 117 is primarily implemented by the storage unit 102 and includes a storage device such as a database that stores information about products or services related to accident prevention, disaster prevention, or disease prevention. This information may include links to websites that introduce and sell such products or services. These links are accessed by pressing the buttons for insurance products and insurance-related products included in the product lineup screen 570 of the home screen 520 of the insurance management application 510, which will be described later.

[0103] Products or services related to accident prevention, disaster prevention, or disease prevention are selected by insurance agents. Each product or service can be associated with insurance (insurance products).

[0104] Information on products or services related to accident prevention, disaster prevention, or disease prevention associated with various types of insurance (insurance products) may include, but is not limited to, the following. Furthermore, such information may also include items that are not preventative products or services. • Car insurance: Vehicle inspection service, domestic travel • Pet insurance: available at pet shops, veterinary clinics, and pet supply stores. • Long-term care insurance: Long-term care services • Medical insurance: comprehensive health checkups, health items (health equipment, health foods, etc.), fitness gyms • Earthquake insurance: disaster prevention supplies • Fire insurance: Fire extinguishing supplies • Education insurance: cram school

[0105] Insurance is a "preparation" for accidents, disasters, illnesses, etc., but it is possible to provide a one-stop service that supports customers not only through insurance "preparation," but also by including products or services related to the prevention of accidents, disasters, illnesses, etc. that may arise from various types of insurance.

[0106] The proposal generation unit 118 is primarily implemented by the control unit 101. The proposal generation unit 118 generates proposal information for each customer based on the customer's personal and professional profile information.

[0107] Personal information (profile information) about customers' personal and professional lives, obtained by insurance agency sales representatives through gaining customer trust, is a valuable sales information asset for providing timely and accurate product proposals to customers over the long term. However, such information is often managed personally by insurance agency sales representatives and is not fully utilized organizationally in agency sales. In contrast, the proposal generation unit 118 customizes and proposes products or services to each customer based on the profile information stored in the customer information storage unit 111.

[0108] 3.2 Functions implemented by the Agent Server 200

[0109] The linking unit 210 is primarily implemented by the control unit 201 and the communication unit 203. The linking unit 210 transmits and receives data between the insurance management server 100 and the user terminal 500. In other words, the linking unit 210 functions as an acquisition unit that obtains data such as customer information and contract information from the agent terminal 600 and the insurance management server 100. The linking unit 210 also performs operations to synchronize and store customer information and contract information in the respective customer information storage units 211, 111 and contract information storage units 213, 113 in communication with the linking unit 110 of the insurance management server 100. The method of synchronization is the same as described above for the linking unit 110.

[0110] The customer information storage unit 211 is primarily implemented by the storage unit 202 and includes a storage device such as a database that stores customer-related information (data including customer information). The customer information storage unit 211 constitutes the "second storage unit". The configuration, functions, and data stored in the customer information storage unit 211 are the same as those of the customer information storage unit 111 of the insurance management server 100.

[0111] The application management ID storage unit 212 is primarily implemented by the storage unit 202 and includes a storage device such as a database that stores information related to the management of various applications for each customer. The configuration, functions, and data stored in the application management ID storage unit 212 are the same as those of the application management ID storage unit 112 of the insurance management server 100.

[0112] The contract information storage unit 213 is primarily implemented by the storage unit 202 and includes a storage device such as a database that stores contract information for insurance policies currently in place for each customer. The contract information storage unit 213 constitutes the "first storage unit". The configuration, functions, and data stored in the contract information storage unit 213 are the same as those of the contract information storage unit 113 of the insurance management server 100.

[0113] The insurance information storage unit 214 is primarily implemented by the storage unit 202 and includes a storage device such as a database that stores information on insurance products handled by the insurance company (insurance information). This insurance information can be used when registering insurance contract information and other details of insurance contracts made by customers at the agent terminal 600 to the agent server 200. Therefore, customer contract information can be correctly registered to the agent server 200.

[0114] The accident response progress management memory unit 215 is primarily implemented by the memory unit 202 and includes a storage device such as a database that stores information regarding the progress of accident response. The accident response progress management memory unit 215 constitutes the "third memory unit". The configuration, functions, and data stored in the accident response progress management memory unit 215 are the same as those of the accident response progress management memory unit 116 of the insurance management server 100.

[0115] 3.3 Functions implemented by user terminal 500

[0116] The user terminal 500 implements various functional units by executing the insurance management application 510.

[0117] The interoperability unit 511 is mainly implemented by the control unit 501 and the communication unit 503, and performs data transmission and reception with the insurance management server 100.

[0118] The input unit 512 is primarily implemented by the control unit 501 and the operation unit 504, and performs input operations for the insurance management application 510. The input operations performed by the input unit 512 vary depending on the type of user terminal 500; for example, if it is a smartphone, input is performed via touch operation.

[0119] The data storage unit 513 is primarily implemented by the storage unit 502 and stores various programs and data used to run the insurance management application 510.

[0120] The display control unit 514 is mainly implemented by the control unit 501 and the display unit 505, and generates various screens of the insurance management application 510 for display on the display unit 505 based on data transmitted from the insurance management server 100. The screens shown in Figures 3 to 10, which will be described later, are generated by this display control unit 514.

[0121] The user terminal 500 has a super application 515 and a messaging unit 516, which is a native function of the super application 515. The insurance management application 510 is configured as a mini-application that runs within the super application 515. The insurance management application 510 could be configured as a native application, but this would require the development of the application itself, which would be a burdensome disadvantage. In contrast, since the insurance management application 510 is a mini-application, it can be created using web technology that runs within the super application 515, significantly reducing the development burden. The super application 515 includes a settlement unit 517. As a result, the insurance management application 510 is configured to perform insurance-related settlement processing (such as payment of insurance amounts) with the settlement unit 517.

[0122] 3.4 Functions enabled by the agent terminal 600

[0123] The interoperability unit 610 is mainly implemented by the control unit 601 and the communication unit 603, and performs data transmission and reception with the agent server 200.

[0124] The input unit 611 is primarily implemented by the operation unit 604 and performs the function of inputting information handled by the insurance information management system 1.

[0125] The display control unit 612 is mainly implemented by the control unit 501 and the display unit 505, and generates various screens for display on the display unit 505 based on data transmitted from the agency server 200.

[0126] The contract information acquisition unit 613 is mainly implemented by the control unit 601 and the communication unit 603, and works in cooperation with the cooperation unit 410 of the insurance company server 400 to perform the function of acquiring customer contract information and other data stored in the contract information storage unit 411.

[0127] 3.5 Functions enabled by the insurance company server 400

[0128] The collaboration unit 410 is mainly implemented by the control unit 401 and the communication unit 403, and performs data transmission and reception with the agent terminal 600 and with the agent server 200. Specifically, the collaboration unit 410 performs the process of transmitting contract information stored in the contract information storage unit 411 to the agent terminal 600 and the agent server 200.

[0129] The contract information storage unit 411 is primarily implemented by the storage unit 402 and includes a storage device such as a database that stores contract information for insurance policies currently in place for each customer.

[0130] 4. How to share insurance information

[0131] This section explains how insurance information is shared in the insurance information management system 1. The following explanation uses the example of an insurance agent operating the agent terminal 600, specifically a sales representative who interacts with customers at an insurance agency.

[0132] 4.1 Accumulation of customer information, contract information, etc. by insurance agents

[0133] As part of their daily sales work, insurance agents operate the agent terminal 600 to input customer information (including contract information) into the customer information input screen provided by the agent server 200. The customer information is transmitted to the agent server 200 via the linkage unit 610.

[0134] Here, the contract information transmitted from the agent terminal 600 to the agent server 200 may include data obtained by the agent terminal 600 from the insurance company server 400. APIs may be used to obtain this data. The cooperation unit 410 of the insurance company server 400 transmits the contract information stored in the contract information storage unit 411 to the agent terminal 600 in response to a transmission request from the agent terminal 600, and the agent terminal 600 obtains it. Therefore, the insurance company, as the insurer, can provide customers with accurate contract information it holds. Insurance agents can avoid the trouble of manually entering all contract information themselves. Note that the contract information may also be automatically transferred directly from the insurance company server 400 to the agent server 200 via API.

[0135] The agency server 200 acquires contract information from the agency terminal 600 via the linkage unit 210 and stores it in the contract information storage unit 213. Since the contract information includes a business partner ID for identifying the customer, the customer information is associated not only with the contract information storage unit 213 but also with the customer information storage unit 211. Therefore, if an insurance agency simply inputs customer information into the agency server 200, the customer information can be transferred to the insurance management server 100 via the customer information storage unit 211.

[0136] The customer information stored in the customer information storage unit 211 may include contract information (e.g., renewal information for existing contracts, contract information for new contracts, etc.) and profile information. The contract information and profile information are transmitted to the insurance management server 100 via the linkage unit 210. The linkage unit 110 of the insurance management server 100 retrieves the contract information and profile information. The linkage unit 210 and the linkage unit 110 automatically transfer the contract information and profile information registered in one to the other, for example, through API linkage. The control unit 101 of the insurance management server 100 stores the contract information in the contract information storage unit 113 and the profile information in the customer information storage unit 111. In this way, the contract information and profile information stored in the agency server 200 can be distributed to the insurance management server 100 without human intervention.

[0137] The customer information displayed by the insurance agent's sales representative on the agent terminal 600 is customer information stored on the agent server 200. When the agent terminal 600 requests the transmission of customer information for a specific customer, the agent server 200 transmits the customer information from the customer information storage unit 211 to the agent terminal 600. The display control unit 612 of the agent terminal 600 displays the received customer information on the screen.

[0138] In an insurance agency, customer information can only be displayed on the agency terminal 600, which is capable of communicating with the agency server 200, and can be displayed if the agent has the necessary access rights. Therefore, customer profile information, which was often managed personally by sales representatives, can be easily shared within the company, enabling sales activities that follow up with customers in a more organized manner.

[0139] 4.2 Registration of contract information, etc. by customers

[0140] This document explains how to register contract information with the insurance management server 100 when a customer has purchased insurance through another insurance agency or through online insurance, etc.

[0141] Home screen 520 [Figure 3]: The customer opens the insurance management app 510 by operating the user terminal 500. This opens the home screen 520 shown in Figure 3, and pressing the insurance registration buttons 520c and 520g displays the insurance list selection screen (not shown). Alternatively, pressing the insurance list confirmation button 520b from the home screen 520 transitions the screen to the insurance list screen 530 (Figure 4), and pressing the insurance registration button 530e also displays the insurance list selection screen.

[0142] The insurance list selection screen displays the same information as the insurance list display unit 530c shown in Figure 4, where multiple insurance policies are listed on a single screen for each product category (insurance type). This allows customers to comprehensively understand various insurance policies on a single screen.

[0143] Insurance list screen 530 [Figure 4]: The insurance list display unit 530c in Figure 4 includes multiple insurance display units 530c1 to 530c12, each capable of independently selecting multiple product categories. Each insurance display unit 530c1 to 530c12 is formed in a tile shape and arranged to connect them in a rectangular ring shape. This type of display configuration for the insurance list display unit 530c is merely an example of an image design and is not limited to it; other display configurations are also possible. For example, the insurance list display unit 530c may be ring-shaped, with the ring shape divided circumferentially to form the insurance display units.

[0144] Insurance display sections 530c1 to 530c12 may include identification elements for visually identifying the presence or absence of insurance. Figure 4 illustrates the coloring of insurance display sections 530c1 to 530c12 that have insurance as an example of an identification element. This allows customers to easily see the product category in which they have insurance. The identifiable configuration is not limited to the example in Figure 4, and other display forms such as flashing displays, or the addition of letters and symbols may also be used.

[0145] When any of the insurance display units 530c1 to 530c12 of the insurance list display unit 530c are selected on the aforementioned insurance list selection screen, the contract information registration screen is displayed (not shown). The contract information registration screen has the same configuration as the contract information screen 550 described later in Figure 6, and the customer can input the contract information 551 for each item of the contract information 551 using an input form or a pull-down selection. The contract information 551 registered by the customer is registered in the contract information storage unit 113 of the insurance management server 100 and automatically transferred to the contract information storage unit 213 of the agent server 200, so that it can be confirmed on the agent terminal 600. In this way, the contract information 551 registered by the customer is shared with the insurance agent.

[0146] 4.3 Checking contract information in the Insurance Management App 510

[0147] Insurance contract list screen 540 [Figure 5]: When a customer presses any of the insurance display units 530c1 to 530c12 on the insurance list screen 530 (Figure 4), the contracted insurance list screen 540, which includes a list of contracted insurance policies, is displayed. Figure 5 is an example of the contracted insurance list screen 540 for automobile insurance, which is displayed when the insurance display unit 530c1 for automobile insurance is pressed. The contracted insurance list screen 540 includes two contracted insurance display units 541a and 541b, and the number of contracted insurance display units displayed there depends on the number of registered insurance policies.

[0148] The contract insurance display sections 541a and 541b include an information display section 542. The contract insurance display section 541a displays a notification display 542a as the information display section 542. This allows the customer's attention to be drawn to each insurance contract. Here, "Expiration Date Approaching" is used as an example of the notification display 542a, but it is not limited to this, and the notification content may be other, such as the remaining number of days in the contract period.

[0149] The contract insurance display section 541b displays the contract agency display 542b as the information display section 542. The example contract agency display 542b displays "Best Selection," the name of the insurance agency that manages the insurance information management system 1, allowing customers to quickly identify the insurance agency with which they have made their insurance contract. The contract agency display 542b can include a contact link (homepage or phone number) for the insurance agency that is displayed when it is clicked. This eliminates the need for customers to search the web for the insurance agency's contact information and makes it easier for them to consult or inquire with the insurance agency.

[0150] The contracting agent display 542b can be left blank if the contract was made through an insurance agency other than the one managing the insurance information management system 1. Alternatively, it may include displaying the name of the other insurance agency that acted as an agent or intermediary for the contract, or displaying "Customer Contract" if the customer contracted directly with the insurance company, such as with online insurance. This would eliminate the need for customers to search for information on which insurance agency they contracted with for each insurance policy, thereby improving customer convenience. Information regarding other insurance agencies and customer contracts can be entered into the insurance information management system 1 by the customer or by the insurance agency after obtaining the information from the customer.

[0151] Figure 5 shows an example where one information display section 542 is displayed within the frame of one contract insurance display section 541a, 541b, but it may include multiple information display sections 542 with different content. For example, it may include both "Expiration Date Approaching" and "Best Selection Contract," as well as other information.

[0152] Contract information screen 550 [Figure 6]: Pressing the contract insurance display unit 541a transitions to the contract information screen 550 shown in Figure 6. The contract information screen 550 displays the contract information 551. The dashed-dot frame in the figure indicates the field where the contract information 551 is entered for explanatory purposes and is not included in the actual contract information screen 550. This allows the contract information 551 to be shared with the customer. The contract information screen 550 contains contract information stored in the contract information storage unit 113 of the insurance management server 100. In addition to this contract information, the contract information screen 550 can also include contract-related information such as contract renewal history.

[0153] The contract information screen 550 includes an edit button 552. The edit button 552 is displayed when the customer enters the contract information themselves, but is not displayed when the insurance agent registers the contract information. Figure 6 shows the edit button 552 as an example of customer input. By pressing this edit button 552, the customer can edit each item of the contract information 551. The edited contract information 551 is then registered in the contract information storage unit 113 of the insurance management server 100 and automatically transferred to the contract information storage unit 213 of the agent server 200, so that it can be viewed on the agent terminal 600.

[0154] The above explanation used automobile insurance as an example, but for other insurance products included in the insurance list display unit 530c, the content of the contracted insurance list screen 540, the contracted insurance display units 541a and 541b, and the information display unit 542, as well as the operation of the screen transitions, can be configured according to the insurance product.

[0155] 4.4 Displaying the Product Lineup Screen

[0156] Pressing the product lineup button 520d on the home screen 520 in Figure 3 displays the product lineup screen 570 shown in Figure 7. The product lineup screen 570 includes not only insurance products but also products and services related to insurance products (referred to as "insurance-related products" in this disclosure). The buttons for insurance products and insurance-related products are linked, and pressing them transitions the screen to a website or brochure explaining that insurance product, etc.

[0157] Insurance-related products include, but are not limited to, rental cars, car repairs, cancer risk screenings, health items, NISA, iDeCo, and disaster prevention items. Furthermore, while the examples in Figure 7 represent a product lineup for "personal preparedness for daily life," a product lineup for "corporate preparedness for business management" can also be constructed to include insurance products and insurance-related products.

[0158] 4.5 Sharing of accident response progress

[0159] Pressing the accident response progress confirmation button 520e on the home screen 520 in Figure 3 displays the accident response progress confirmation screen 580. All information regarding the progress of the accident response is registered by the insurance agency handling the accident response; there is no information registered by the customer, although information registered by the customer may be included.

[0160] Figure 8 shows an example of the accident response progress confirmation screen 580. The accident response progress confirmation screen 580 includes an accident display section 581 for each accident. If there are multiple accidents, multiple accident display sections 581 are displayed, and the progress of each accident response is managed individually. The accident display section 581 includes the date of the accident, the accident response details (personal injury liability, property damage liability, vehicle compensation), and a status display 582.

[0161] The status display 582 changes according to the status of the accident response, as shown in Figure 8A as "In Progress," Figure 8B as "Completed," and Figure 8C as "Withdrawn" when the accident response is stopped midway. Pressing the accident display unit 581 displays the accident response progress confirmation screen 590 for that accident.

[0162] Figure 9 shows an example of the accident response progress confirmation screen 590. In addition to displaying the policy number and the date of the accident, the accident response progress display section 591 is included. The accident response progress display section 591 includes the bodily injury liability section 591a, the property damage liability section 591b, and the vehicle damage compensation section 591c. The progress of property damage liability, bodily injury liability, and vehicle damage compensation differs depending on the accident and negotiations with the other party, so each is displayed separately. This allows the customer to easily check what actions they need to take regarding bodily injury liability, property damage liability, and vehicle damage compensation, and to check the different progress statuses of each on a single screen. Therefore, customer anxiety can be reduced.

[0163] The personal injury liability section 591a, the property damage liability section 591b, and the vehicle compensation section 591c each include a progress indicator 592. The progress indicator 592 can consist of at least one of the following to show the degree of progress toward completion of the response or the response history: text, numbers, figures, symbols, colors, graphs, still images, or animations. This allows the customer to easily grasp the overall picture of the accident response and the degree of progress toward completion of the response through the progress indicator.

[0164] In Figure 9, the progress display 592 is composed of a combination of three different display elements: a horizontal bar graph-like display 592a representing "Step 1," "Step 2," "Step 3," and "Step 4" as if they were roads; a graphic representation 592b showing a car and a goal flag moving in sync with the steps in the graph-like display 592a; and a percentage display 592c showing "25% complete," "50% complete," "75% complete," and "100% complete."

[0165] Once the accident response is complete, the progress indicator 592 changes to an image as shown in Figure 10A. Furthermore, if no action is required regarding bodily injury liability, property damage liability, or vehicle damage compensation, the progress indicator 592 will display in a format similar to that shown in 10B, for example.

[0166] The status changes of the progress indicator 592 are automatically updated in accordance with changes in the data stored in the accident progress management table of the accident response progress management storage unit 116 of the insurance management server 100, as described above. Furthermore, the definitions of "Step 1," "Step 2," "Step 3," and "Step 4" for bodily injury liability, property damage liability, and vehicle compensation are as explained in the accident response progress management storage unit 116.

[0167] For example, if an insured person is involved in a car accident and an insurance agent is handling the accident, it can be difficult to grasp what has progressed and to what extent. In particular, since experience with insurance accident handling is rare, and the matters that need to be addressed vary depending on the circumstances of the accident and the content of the insurance contract, it can be difficult for customers to grasp the overall picture of the accident handling and the degree of progress toward completion, which can be a major source of anxiety for them. However, the insurance management app 510, by including an accident handling progress confirmation screen 590, allows users to check the progress of the accident handling being carried out by the insurance agent, thereby alleviating the anxiety felt by customers who are not involved in the accident handling and cannot fully grasp the overall picture.

[0168] 4.6 Display of the Useful Information for Daily Life screen

[0169] Pressing the "Useful Information for Daily Life" button 520f on the home screen 520 in Figure 3 will take you to an external shopping site (not shown). The external shopping site includes pages introducing and purchasing insurance and insurance-related products, and through these pages, users of the insurance management app 510 can purchase insurance and insurance-related products at special prices.

[0170] External shopping sites, in addition to the aforementioned introduction and purchase pages, include a product list section that displays products and services recommended by insurance agencies to address risks that cannot be resolved by insurance. This product list section includes multiple categories, such as health, prevention, testing, automobiles, disaster prevention, end-of-life planning, elderly care, childcare, pets, and business, and is specifically organized in a circular format, similar to the insurance list section 530c shown in Figure 4. Each category in the product list section has a link; clicking the category button opens a flyer page introducing products and services particularly recommended by the insurance agency within that category. These flyer pages can be web pages or PDF files. While external shopping sites have value in including a large number of products and services, it can be difficult for customers to find the products and services they need. However, by having insurance agencies introduce particularly recommended products and services in the form of flyer pages, customer access to these products and services can be made easier.

[0171] 5. Variations

[0172] Modification 1: In the above embodiment, the progress of property damage liability, bodily injury liability, and vehicle compensation was defined in stages 1 to 4, but the number of stages may be defined as two or more stages other than four.

[0173] Modification 2: In the above embodiment, the progress of property damage liability, bodily injury liability, and vehicle compensation were all defined in four stages, but each of the three stages may be defined with a different number of stages.

[0174] Modification 3: In the above embodiment, the agent terminal 600 is shown to display customer information and contract information registered in the agent server 200. However, the system may be configured to display customer information and contract information held by the insurance management server 100.

[0175] Modification 4: In the above embodiment, the example was that the agent terminal 600 registers and updates customer information and contract information with the agent server 200, but it may also be configured to register and update information with the insurance management server 100. In this case, the customer information and contract information registered and updated by the insurance management server 100 can be synchronized with the agent server 200 by the linkage units 110 and 210.

[0176] Modification 5: Figure 11 is a functional block diagram of a modified version of the insurance information management system 1 of the above embodiment. This insurance information management system 1 integrates the functions of the agent server 200 and the insurance management server 100 of the above embodiment and is constructed as an insurance management server 700. The insurance management server 700 can be built, for example, on a cloud environment provided by a cloud provider. Examples of cloud environments provided by cloud providers include AWS, Azure, and GCP, as described in the Insurance Information Management System 1.

[0177] The collaboration unit 710, customer information storage unit 711, application management ID storage unit 712, contract information storage unit 713, insurance information storage unit 714, accident response progress management storage unit 715, customer information provision unit 716, notification unit 717, product information storage unit 718, and proposal generation unit 719 in the insurance management server 700 correspond to the collaboration units 110, 210, customer information storage units 111, 211, application management ID storage units 112, 212, contract information storage units 113, 213, insurance information storage unit 214, accident response progress management storage units 116, 215, customer information provision unit 114, notification unit 115, product information storage unit 117, and proposal generation unit 118 of the insurance management server 100 and the agency server 200, respectively, and have the same functions. In other words, the collaboration unit 710 to the accident response progress management storage unit 715 is functionally equivalent to the agency server 200 as the "agency server unit," and the collaboration unit 710 to the proposal generation unit 719 is functionally equivalent to the insurance management server 100 as the "insurance management server unit."

[0178] The customer information storage unit 711 constitutes the "second storage unit" of the present invention, and similarly, the contract information storage unit 713 constitutes the "first storage unit," and the accident response progress management storage unit 715 constitutes the "third storage unit." All of these can be configured as databases built on the cloud.

[0179] The insurance management server 700 may be configured to acquire data such as contract information through one of the following acquisition routes, for example.

[0180] (1) Data including contract information is entered into the input section 611 of the agent terminal 600, the agent terminal 600 sends the data including the contract information to the insurance management server 700, and the insurance management server 700 retrieves it.

[0181] (2) The agent terminal 600 obtains data including contract information from the insurance company server 400, the agent terminal 600 sends the data including contract information to the insurance management server 700, and the insurance management server 700 obtains it. In this case, the agent terminal 600 may perform data processing on the data including contract information obtained from the insurance company server 400, such as deleting unnecessary data or adding additional information, and then send the processed data to the insurance management server 700. Alternatively, the agent terminal 600 may send the data including contract information obtained from the insurance company server 400 to the insurance management server 700 as is. In this case, the insurance management server 700 may be further configured to include a "data processing unit" that performs the aforementioned data processing, or the insurance management method may be configured to include a data processing step.

[0182] (3) The insurance company server 400 sends data containing contract information to the insurance management server 700, and the insurance management server 700 retrieves it. In this case, the insurance management server 700 may be configured to include a "data processing unit" that performs functions to process the data containing contract information obtained from the insurance company server 400, such as deleting unnecessary data, organizing data, and adding data, or it may be configured to include a data processing step as part of the insurance management method.

[0183] Furthermore, each of the above data processing methods may include information processing that associates suitable data from data containing contract information with multiple different types of contract information items.

[0184] According to this modified example 5, insurance contract information can be shared between the customer and the insurance agent for each customer.

[0185] Furthermore, the data, including contract information, obtainable from the insurance company server 400 is intended for use by insurance agencies and is not for sharing contract information with customers. It cannot be used for purposes other than management by insurance agencies. In contrast, according to the aforementioned data processing unit or data processing steps, the data can be used not only by insurance agencies but also for sharing contract information with customers.

[0186] Although each embodiment of the present disclosure has been described in detail above, it will be readily apparent to those skilled in the art that many modifications are possible without substantially departing from the novelty and effects of the present disclosure. All such modifications are included within the scope of the present disclosure. [Explanation of Symbols]

[0187] 1. Insurance Information Management System 10 Insurance App System 100 Insurance Management Servers 200 Agent Servers 300 External application servers 400 Insurance Company Servers 500 user terminals 600 Agent Terminals 700 Insurance Management Server

Claims

1. This is an insurance information management system that allows customers and insurance agents to share insurance contract information. A first cloud-based storage unit managed by the insurance agency, which is capable of storing the customer's contract information obtained from the customer's user terminal, the insurance agency's agent terminal, and the insurance company's computer, A customer information provision unit on the cloud, managed by the insurance agency, provides the contract information stored in the first storage unit to the insurance management application on the user terminal or the agency terminal, Includes a notification unit that notifies the insurance management app of information regarding the expiration of the contract period based on the contract information of the insurance contracted by the customer through the insurance agent and the contract information of the insurance contracted through other insurance agents, Insurance information management system.

2. An insurance information management system for sharing insurance contract information between a customer and an insurance agent, A first cloud-based storage unit managed by the insurance agency, which is capable of storing the customer's contract information obtained from the customer's user terminal, the insurance agency's agent terminal, and the insurance company's computer, A customer information provision unit on the cloud, managed by the insurance agency, provides the contract information stored in the first storage unit to the insurance management application on the user terminal or the agency terminal, It includes a third storage unit on the cloud managed by the insurance agency, which is capable of storing information regarding the progress of accident response acquired from the agency terminal, The customer information provision unit provides information regarding the progress of the accident response to the insurance management application on the user terminal. The aforementioned insurance management application includes an accident response progress display unit that displays information regarding the progress of the accident response, The accident response progress display unit includes at least one of the personal injury liability unit, property damage liability unit, and vehicle compensation unit in one screen for each accident. The aforementioned personal injury liability unit, property damage liability unit, or vehicle compensation unit includes a progress indicator that shows the degree of progress toward completion of the response or the response history using at least one of the following: characters, numbers, figures, symbols, colors, graphs, still images, or animations. Insurance information management system.

3. Includes a second storage unit on the cloud managed by the insurance agency, which is capable of storing the customer profile information acquired from the agency terminal, The insurance information management system according to claim 1 or 2.

4. For each of the aforementioned customers, a cloud-based proposal generation unit generates proposal information regarding products or services related to accident prevention, disaster prevention, or disease prevention based on the aforementioned contract information, The insurance information management system according to claim 1 or 2.

5. The proposal generation unit is configured to generate proposal information for each customer based on the customer's personal and professional profile information. The insurance information management system according to claim 4.

6. The user terminal includes a settlement unit that performs settlement processing for purchases made in the insurance management application. The insurance information management system according to claim 1 or 2.

7. This is an insurance information management method that shares insurance contract information between the customer and the insurance agent. The insurance management application running on the customer's user terminal, the insurance agent's agent terminal, and the insurance company's computer are used to store the customer's contract information in a first cloud-based storage unit managed by the insurance agent. The contract information stored in the first storage unit is provided to the insurance management application on the user terminal or the agent terminal. This includes notifying the insurance management app of information regarding the expiration of contract periods based on the contract information of insurance contracted by the customer through the insurance agent and the contract information of insurance contracted through other insurance agents, Insurance information management methods.

8. An insurance information management method for sharing insurance contract information between a customer and an insurance agent, The insurance management application running on the customer's user terminal, the insurance agent's agent terminal, and the insurance company's computer are used to store the customer's contract information in a first cloud-based storage unit managed by the insurance agent. The contract information stored in the first storage unit is provided to the insurance management application on the user terminal or the agent terminal. The information regarding the progress of accident response obtained from the aforementioned agency terminal is stored in a third storage unit on the cloud managed by the insurance agency. To provide information regarding the progress of the accident response to the insurance management application on the user terminal, The insurance management application includes an accident response progress display unit that displays information regarding the progress of the accident response, the accident response progress display unit includes at least one of a personal injury liability unit, a property damage liability unit, and a vehicle compensation unit on one screen for each accident, and the personal injury liability unit, the property damage liability unit, or the vehicle compensation unit displays the degree of progress toward completion of the response or the response history using at least one of characters, numbers, figures, symbols, colors, graphs, still images, or animations. Insurance information management methods.

9. This includes storing the customer profile information obtained from the agency terminal in a second storage unit on the cloud managed by the insurance agency. The insurance information management method according to claim 7 or 8.

10. For each customer, the method includes generating suggestion information regarding products or services related to accident prevention, disaster prevention, or disease prevention based on the contract information. The insurance information management method according to claim 7 or 8.

Images