JP2017027420A - Insurance information management system, insurance application, and insurance management alert system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent expiration of an insurance contract by promptly making contact with, for example, a family member when it is not possible to confirm safety of an insurance policy holder.SOLUTION: When a date count program 112 of a management server 110 of an insurance information management system 100 is executed and 30 days are counted after a service start date, a notification processing program 114 of the management server 110 is executed and a first safety confirmation notification is transmitted to a registrant terminal 200 from a mail server 130. When a registrant receives the safety confirmation notification at the registrant terminal 200 and logs in an insurance application 210 to respond thereto, the management server 110 determines that the safety of the registrant is confirmed. In a case when no response is received and it is not possible to confirm the safety, the same safety confirmation is performed at the 40th day and the 50th day. When the safety cannot be confirmed at the 50th day, such circumstance is reported to, for example, a family member, thereby enabling, for example, the family to prevent an insurance contract from expiring while an insurance fee has paid.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an insurance information management system, an insurance application, and an insurance management alert system for managing insurance information such as life insurance and non-life insurance, and more particularly to a technique suitable for preventing the expiration of an insurance contract.

  In insurance contracts such as life insurance, the insurance contract may expire if the insurance premium payment of the policyholder to the insurance company is not paid for a certain period, for example, two months. If the insured person dies or is in need of nursing care, the insurance contract will expire and payment of life insurance will be made if the insurer cannot be notified of the situation for a certain period, for example, two months. Insurance contracts may not be fulfilled.

  The insurance company notifies the contractor that the insurance premium has not been paid or the bank cannot be withdrawn by mail, etc., but the contractor and his / her family may miss the notification or may not be able to confirm it. However, there is a disadvantage that the insurance contract cannot be executed and the insurance money cannot be received.

  As an example paying attention to this point, there is an “insurance subscriber information entrustment service method, an insurance subscriber information entrustment service system and an entrustment information management terminal” described in Patent Document 1 below. This is because the consignment information management terminal creates a survival confirmation email and confirms the survival of the insurance subscriber every predetermined period, and if a survival confirmation response is not obtained, it sends a survival confirmation email several more times. If there is still no response, the survival confirmation is not answered, and after the death confirmation is finally obtained, the consignment information is sent to the designated relative.

JP 2008-117041 A

  However, in the background art described above, the death of a policyholder is confirmed by information from an insurance institution or government office / registration department, etc., and it takes time to notify the family, etc., resulting in the expiration of the insurance contract. This may cause inconveniences such as not being able to receive insurance.

  The present invention focuses on the above points, and its purpose is to prevent the expiration of an insurance contract by promptly contacting a family member when the safety of the policyholder cannot be confirmed. .

  The insurance information management system of the present invention provides a database for storing and registering insurance information contracted by a registrant together with a contact information of the registrant and a contact information of a family, etc. for each insurance information registered in the database. Counting means for counting the number of days from the start date, notification processing means for notifying the registrant for safety confirmation when a predetermined count is performed by the counting means, and notification by the notification processing means On the other hand, there is provided a contact processing means for contacting the family when there is no response from the registrant.

  According to one of the main forms, the counting unit performs a plurality of times of counting, and the notification processing unit performs the notification for each of the plurality of times of counting by the counting unit. According to another aspect, the notification processing means performs confirmation of safety for the registrant in both the premium payment period and the grace period, or within the premium payment period. And According to yet another aspect, when insurance premiums are paid after contact by the contact processing means, the safety confirmation for the registrant is notified again according to the registrant's situation. This is characterized in that either of the following notification is performed or the safety confirmation is terminated.

  The insurance application of the present invention is installed in the terminal of the registrant and has a function of responding to a safety confirmation notification from the notification processing means.

  The insurance management alert system of the present invention is characterized in that the insurance information management system and a registrant terminal in which the insurance application is installed are connected through a network. The above and other objects, features and advantages of the present invention will become apparent from the following detailed description and the accompanying drawings.

  According to the present invention, the safety is confirmed when a certain number of days have passed, and when the confirmation is not made, the family is contacted, so that the expiration of the insurance contract can be well prevented.

It is a whole block diagram which shows Example 1 of the insurance management alert system of this invention. It is a flowchart which shows operation | movement of the said Example 1. FIG. It is explanatory drawing which shows Example 2 of this invention. It is a flowchart which shows the main operation | movement of Example 3 of this invention.

  Hereinafter, the form for implementing this invention is demonstrated in detail based on an Example.

  FIG. 1 shows a first embodiment of an insurance management alert system according to the present invention. In FIG. 1, an insurance management alert system 10 is configured with an insurance information management system 100 as a center. The insurance information management system 100 is connected via the Internet 12 to a registrant terminal 200 that is a large number of insurance contractors and a contact terminal 300 that is a contact address of family members and the like. It is not always necessary to pay the insurance.

  Among these, the insurance information management system 100 includes a management server 110, an insurance information management database 120, and a mail server 130. The management server 110 includes a day count program 112, a notification processing program 114, a contact processing program 116, and a user setting program 118. By executing these programs, the management server 110 counts the number of days from a predetermined calculation date, When the number of days elapses, the corresponding registrant terminal 200 is notified to that effect, and when a predetermined situation is reached, a function to notify the corresponding contact terminal 300 to that effect is provided.

  The insurance information management database 120 can confirm the insurance information such as the insurance amount and payee of insurance for the registrant who uses this alert service, the notification destination of the registrant who confirms the safety confirmation, and the safety of the registrant. The contact information at the time of unconfirmed such as a relative who contacts when there is not, and other data are accumulated.

  The mail server 130 transmits an e-mail for confirming safety to the registrant terminal 200 to which the registrant is notified (hereinafter simply referred to as “mail”), or a response to confirm the safety from the registrant terminal 200. It has a function of receiving an e-mail when it is present or sending an e-mail to the contact terminal 300 of the unconfirmed contact when the safety cannot be confirmed.

  Next, the registrant terminal 200 can use various information devices such as a smartphone, a personal computer, and a tablet terminal, and an insurance application (insurance program) 210 for receiving this alert service is installed. When the insurance application 210 receives a safety confirmation e-mail from the insurance information management system 100, the insurance application 210 informs the registrant by sound, light, vibration, etc. and confirms the safety when the registrant logs in. A function of transmitting a response to the insurance information management system 100 is provided. The contact terminal 300 is used to receive an unconfirmed safety email from the insurance information management system 100, and various information devices such as a smartphone, a personal computer, and a tablet terminal are used.

  Next, the overall operation of this embodiment will be described with reference to the flowchart of FIG. A registrant who receives this alert service provides the insurance information management system 100 with the insurance information that he / she has subscribed to, along with the e-mail address of his / her terminal and the e-mail address of a contact terminal such as a family member. The providing method may be various methods such as mail, mail, and facsimile. The insurance information 210 may be provided to the insurance information management system 100 using the insurance application 210. Such information is stored and registered in the insurance information management database 120. The registrant installs an insurance application on his / her terminal. At this time, if necessary, a contact information such as a family member may be notified in advance that the alert service is being received.

  Further, when the registrant wishes to set the number of safety confirmations and the number of days, the insurance information management system 100 is requested to that effect using the insurance application 210. Then, in the insurance information management system 100, the user setting program 118 is executed, and a setting screen is displayed on the registrant terminal 200. The registrant can set the number of safety confirmations and the number of days using the setting screen. When the registrant does not set, the default number of times and the due date are set. In the following example, safety confirmation is performed on the 30th, 40th, and 50th days from the contract date.

  When the registration of insurance information and the setting of the safety confirmation date and time are completed, the insurance information management system 100 executes the day count program 112 in the management server 110, and counts the number of days elapsed from a predetermined calculation date, for example, the first day of the payment date. Start (step S10). When the 30th day is counted (Yes in step S12), the notification processing program 114 of the management server 110 is executed, and the first safety confirmation notification is sent from the mail server 130 to the registrant terminal 200. (Step S14). The management server 110 waits for a response for a predetermined time (step S16).

  On the other hand, when the registrant receives a safety confirmation notification from the terminal 200 (step S18), the registrant logs in to the insurance application 210 and responds that the notification has been received (step S20).

  In the insurance information management system 100, when the response by the registrant terminal 200 is received by the mail server 130 (Yes in steps S22 and S24), it is determined that the registrant's safety has been confirmed, Repeat the 30-day count. In this way, normally, the operations of steps S10 to S24 are repeated, and the registrant's safety is confirmed every 30 days.

  Next, when the registrant is dead or needs care, and there is no response from the registrant terminal 200 (No in step S24), the day count program 112 is received. Thus, the day count is restarted (step S26). When the 40th day after 10 days from the 30th is counted (Yes in step S28), the notification processing program 114 of the management server 110 is executed, and the second safety confirmation notification is sent to the mail server 130. To registrant terminal 200 (step S30). The management server 110 waits for a response for a predetermined time (step S32).

  On the other hand, when the registrant receives a safety confirmation notification from the terminal 200 (step S34), the registrant logs in to the insurance application 210 and responds that the notification has been received (step S36). In the insurance information management system 100, when the mail server 130 receives a response from the registrant terminal 200 (Yes in steps S38 and S40), the insurance information management system 100 determines that the registrant's safety has been confirmed, and the notification processing program 114 starts again. Repeat the 30-day count.

  Next, when there is no response from the registrant terminal 200 for the above-described safety confirmation on the 40th day (No in step S40), the day count program 112 restarts the day count (step S42). When the 50th day after 10 days from the 40th day is counted (Yes in step S44), the notification processing program 114 of the management server 110 is executed, and the third safety confirmation notification is sent to the mail server 130. To registrant terminal 200 (step S46). The management server 110 waits for a response for a predetermined time (step S48).

  On the other hand, when the registrant receives the safety confirmation notification from the terminal 200 (step S50), the registrant logs in to the insurance application 210 and responds that the notification has been received (step S52). In the insurance information management system 100, when the mail server 130 receives a response from the registrant terminal 200 (Yes in steps S54 and S56), it is determined that the safety of the registrant has been confirmed. Repeat the 30-day count.

  Next, when there is no response from the registrant terminal 200 with respect to the above-described safety confirmation on the 50th day (No in step S56), the management server 110 is in a state in which the registrant has died or needs care. Judge that it is. Then, the contact processing program 116 is executed, referring to the insurance information of the corresponding registrant, and contacting the corresponding contact terminal 300 that the safety has not been confirmed by mail transmission by the mail server 130 (step S58).

  Thus, according to the present embodiment, when the registrant's safety cannot be confirmed at the time when 50 days have elapsed, it is determined that the registrant cannot respond, for example, that the registrant has become dead or needs care. The family is notified of this. For this reason, the family etc. can confirm the situation where the registrant is placed, and perform processing such as payment of insurance premiums, thereby avoiding the expiration of the insurance contract.

  Next, Embodiment 2 of the present invention will be described with reference to FIG. In general, in the case of monthly payment, the insurance premium is often from the first day to the last day of the payment due date to which the contract anniversary date of each month belongs. And even if the premium is not paid within the payment period, in many cases there is a grace period, so if you pay the premium within this period, you will be able to avoid the expiration of the insurance contract. be able to.

  In the first embodiment described above, as shown in FIG. 3A, safety confirmation is performed using two months between the payment period and the payment grace period. In this case, for example, if the registrant's safety could not be confirmed on the 50th day and the contact terminal 300 is notified to that effect, the contact family will pay the insurance premium within the remaining 10 days. become.

  On the other hand, in this embodiment, as shown in FIG. 5B, safety confirmation is performed on the 15th, 20th, and 25th of the payment period. In this way, you can prompt the payment of the insurance premium within the payment period, and even if it is not done, you can prevent the expiration by paying the insurance premium within the subsequent grace period . However, the frequency of safety confirmation for the registrant increases.

  In the above example, the safety was confirmed on the 15th, 20th, and 25th of the payment date, but for example, the registrant is between 1 and 14 days (or 16-19 days, 21-24 days). In addition, when the registrant is logged in to the insurance application 210, it can be considered that the safety has been confirmed. Therefore, the safety confirmation is not performed after that, and the safety confirmation is confirmed again from the 15th of the next payment date. May be performed.

  The example of Fig. (C) is a modification of Fig. (B). When the safety confirmation could not be made on the 25th day of the payment period, the insurance was issued on the 50th day, that is, 10 days before the payment grace period. The contact terminal 300 confirms whether or not a fee has been paid. Before the end of the grace period, as a precautionary measure, a notice that the insurance contract will expire if payment is not paid is made to prevent the expiration of the insurance contract.

  Next, Embodiment 3 of the present invention will be described with reference to FIG. This example relates to a process after a family member of a contact who has received a confirmation that the registrant has not confirmed safety has paid an insurance premium. In the case of safety unconfirmed, the registrant may accidentally fail to log in for safety confirmation, or a situation where the registrant cannot log in, for example, a care-necessary state may be considered. Therefore, in this embodiment, when a family member or the like pays an insurance premium (step S62) after receiving an unconfirmed safety notification (step S58) at the contact terminal 300 (step S60), this is indicated in the insurance information management. The system 100 is notified (step S64).

When this is received by the insurance information management system 100 (step S66), the insurance information management system 100 contacts the family and inquires the registrant to determine the situation and decides the subsequent response.
a. If the registrant is alive and simply fails to log in for safety confirmation, the safety confirmation for the registrant shown in the first or second embodiment is performed again (step S68a). For example, when the safety confirmation cannot be performed due to a long-term overseas trip or the like, the case where the insurance application 210 is forgotten to be installed when the registrant terminal 200 is replaced is applicable.
b. When the registrant is in a state where it is not possible to respond to safety confirmation such as a care-requiring state, the safety confirmation shown in the first or second embodiment is performed on the contact terminal 300 such as a family member ( Step S68b).
c. When the payment of the insurance premium is terminated due to the death of the registrant or the family wishes to terminate the insurance contract, the safety confirmation operation is terminated (step S68c).

  By doing in this way, the continuity of the safety confirmation service can be ensured and a sense of security can be given to the user.

In addition, this invention is not limited to the Example mentioned above, A various change can be added in the range which does not deviate from the summary of this invention. For example, the following are also included.
(1) The count days of 30 days, 40 days, 50 days to 15 days, 20 days, and 25 days shown in the above embodiment are merely examples, and may be changed as needed. Moreover, in the said Example, although the inquiry for safety confirmation was performed 3 times in total, you may set the frequency | count as needed. Further, even when the user sets the number of days and the number of times, the user may set the due date and the number of times within a preset limit range, instead of freely setting everything.
(2) In the above embodiment, when the safety confirmation on the 50th day to the 25th day could not be confirmed, the family was contacted, but on the 30th day, the 40th day, the 15th day and the 20th day. You may make it contact whether it was able to confirm safety. By doing so, the family and the like can know that the registrant lives as usual.
(3) In the above embodiment, e-mail is used for safety confirmation and communication, but various communication functions such as telephone, facsimile, mobile phone short message, and messenger application may be used.
(4) In the above-described embodiment, the case where the insurance premium is paid monthly has been described.

  According to the present invention, when the appropriate number of days have passed, the safety is confirmed, and when it is not confirmed, the family etc. is contacted. It is effective in fields such as non-life insurance.

10: Insurance management alert system 12: Internet 100: Insurance information management system 110: Management server 112: Days counting program 114: Notification processing program 116: Contact processing program 118: User setting program 120: Insurance information management database 130: Mail server 200 : Registrant terminal 210: Insurance application 300: Contact terminal

Claims (7)

A database for storing and registering insurance information contracted by the registrant, along with the registrant's notification address and contact information of the family,
Counting means for counting the number of days from a predetermined date for each insurance information registered in the database;
Notification processing means for notifying the registrant for safety confirmation when a predetermined count is performed by the counting means;
Contact processing means for contacting the family or the like when there is no response from the registrant in response to the notification by the notification processing means;
An insurance information management system characterized by comprising: The counting means counts a plurality of times,
The insurance information management system according to claim 1, wherein the notification processing unit performs the notification every time the counting unit counts a plurality of times.   The insurance information management system according to claim 1 or 2, wherein notification for confirming safety to the registrant by the notification processing means is performed both during a premium payment period and a grace period.   The insurance information management system according to claim 1 or 2, wherein the notification processing means performs notification for confirming the safety of the registrant within the payment period of insurance premiums. When insurance premiums are paid after contact by the contact processing means, depending on the registrant's situation,
Re-notify registrants of safety confirmation
Notification of safety confirmation to family members,
End safety confirmation,
The insurance information management system according to any one of claims 1 to 4, wherein any one of the processes is performed.   An insurance application installed on the registrant's terminal according to any one of claims 1 to 5 and having a function of responding to a safety confirmation notification from the notification processing means.   An insurance management alert, wherein the insurance information management system according to any one of claims 1 to 5 and a registrant terminal in which the insurance application according to claim 6 is installed are connected through a network. system.

Images