JP2015125557A - Information processing device, information processing method and information processing program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform a customer service for notifying a customer of information on insurance under a contract together with get-well greeting after disaster occurrence so as to increase reliability by a prompt contact with the customer after the disaster occurrence.SOLUTION: The information processing device comprises: a disaster information acquisition unit for acquiring disaster-stricken area information on a disaster; a first determination unit for determining whether an address of a customer is included in the disaster-stricken area on the basis of the disaster-stricken area information and address information on the customer; and a notification unit for, when it is determined that the address of the customer is included in the disaster-stricken area, notifying a person in charge to prompt get-well greeting and notification of insurance information to the customer.

Description

  The present invention relates to an information processing apparatus, an information processing method, and an information processing program in an insurance agent or insurance sales company.

  In the above technical field, Patent Document 1 discloses a technique for displaying a disaster risk of a managed object such as real estate on a customer terminal. Patent Document 2 discloses a technique for designing a derivative according to a risk of occurrence of damage based on actual observation data of a typhoon predicted from a correlation between a historical typhoon and a damage amount.

JP 2002-024473 A JP 2003-085361 A

  However, the technique described in the above document is a technique for examining disaster risk in advance, and customer service after the occurrence of a disaster is not intended. Therefore, it was not possible to improve reliability by contacting customers after the disaster occurred.

  The objective of this invention is providing the technique which solves the above-mentioned subject.

In order to achieve the above object, an information processing apparatus according to the present invention provides:
Disaster information acquisition means for acquiring disaster-affected area information;
First determination means for determining whether or not the customer's address is included in the disaster area based on the disaster area information and the customer's address information;
Informing means for informing the person in charge of the visit to the customer and notification of the insurance information to the customer when it is determined that the customer's address is included in the affected area;
Is provided.

In order to achieve the above object, an information processing method according to the present invention includes:
Disaster information acquisition step to acquire disaster area information of the disaster,
A first determination step of determining whether or not the customer's address is included in the disaster area based on the disaster area information and the customer's address information;
A notification step for informing the person in charge of the visit to the customer and the notification of the insurance information to the customer when it is determined that the customer's address is included in the affected area;
including.

In order to achieve the above object, an information processing program according to the present invention provides:
Disaster information acquisition step to acquire disaster area information of the disaster,
A first determination step of determining whether or not the customer's address is included in the disaster area based on the disaster area information and the customer's address information;
A notification step for informing the person in charge of the visit to the customer and the notification of the insurance information to the customer when it is determined that the customer's address is included in the affected area;
Is executed on the computer.

  According to the present invention, reliability can be more effectively obtained from a customer by performing customer service for notifying a visit and insurance information after a disaster occurs.

It is a block diagram which shows the structure of the information processing apparatus which concerns on 1st Embodiment of this invention. It is a figure which shows the outline | summary of a process of the customer service system which concerns on 2nd Embodiment of this invention. It is a figure which shows the example of a display in the customer service system which concerns on 2nd Embodiment of this invention. It is a figure which shows the action schedule registration screen in the customer service system which concerns on 2nd Embodiment of this invention. It is a figure which shows the visit call completion registration screen in the customer service system which concerns on 2nd Embodiment of this invention. It is a block diagram which shows the structure of the customer service system containing the information processing apparatus which concerns on 2nd Embodiment of this invention. It is a sequence diagram which shows the operation | movement procedure of the customer service system containing the information processing apparatus which concerns on 2nd Embodiment of this invention. It is a block diagram which shows the function structure of the insurance agency server as an information processing apparatus which concerns on 2nd Embodiment of this invention. It is a figure which shows the structure of the customer database which concerns on 2nd Embodiment of this invention. It is a figure which shows the structure of the insurance contract database which concerns on 2nd Embodiment of this invention. It is a figure which shows the structure of the disaster area object customer extraction table which concerns on 2nd Embodiment of this invention. It is a figure which shows the structure of the notification information generation table which concerns on 2nd Embodiment of this invention. It is a block diagram which shows the hardware constitutions of the insurance agency server as an information processing apparatus which concerns on 2nd Embodiment of this invention. It is a flowchart which shows the process sequence of the insurance agency server as an information processing apparatus which concerns on 2nd Embodiment of this invention. It is a sequence diagram which shows the operation | movement procedure of the customer service system containing the information processing apparatus which concerns on 3rd Embodiment of this invention. It is a block diagram which shows the function structure of the insurance agency server as an information processing apparatus which concerns on 3rd Embodiment of this invention. It is a figure which shows the structure of the customer database which concerns on 3rd Embodiment of this invention. It is a flowchart which shows the process sequence of the insurance agency server as an information processing apparatus which concerns on 3rd Embodiment of this invention.

  Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the drawings. However, the constituent elements described in the following embodiments are merely examples, and are not intended to limit the technical scope of the present invention only to them.

[First Embodiment]
An information processing apparatus 100 as a first embodiment of the present invention will be described with reference to FIG. The information processing apparatus 100 is an apparatus for customer service in insurance business.

  As illustrated in FIG. 1, the information processing apparatus 100 includes a disaster information acquisition unit 101, a first determination unit 102, and a notification unit 103. The disaster information acquisition unit 101 acquires disaster area information of a disaster. The first determination unit 102 determines whether or not the customer address is included in the disaster area based on the disaster area information and the customer address information. When the notification unit 103 determines that the customer's address is included in the affected area, the notification unit 103 notifies the person in charge 110 of a visit to the customer and notification of insurance information.

  According to this embodiment, reliability can be more effectively obtained from a customer by performing customer service that notifies a visit and insurance information after a disaster occurs.

[Second Embodiment]
Next, an insurance agency server as an information processing apparatus according to the second embodiment of the present invention will be described. In the insurance agent server according to the present embodiment, the disaster information acquisition acquires disaster occurrence area information, and the affected area target customer determination unit determines the customer's address based on the disaster occurrence area information and the customer address information. Is included in the affected area. Then, when the visit / notification information notifying unit determines that the customer's address is included in the affected area, the visit / notification information is notified so as to prompt the sales representative to visit the customer and notify the customer of insurance information. In the present embodiment, the insurance agent or the insurance sales company is targeted. However, since the configuration and operation are the same, the following description will be made with the insurance agent as a representative.

<Customer service system>
With reference to FIG. 2A thru | or FIG. 5, the structure and operation | movement of the customer service system containing the insurance agency server as an information processing apparatus concerning this embodiment are demonstrated.

(Outline of processing)
FIG. 2A is a diagram showing an outline of processing of the customer service system 200 according to the present embodiment.

  In the customer service system 200, XX earthquake 230 and typhoon xx 240 are shown as disasters. The customer service system 200 includes a disaster information notification station 220 for collecting and notifying information on the occurrence of a disaster. The disaster information reporting station 220 includes, for example, the Japan Meteorological Agency 221 for reporting information such as typhoons, heavy rains, and earthquakes. The customer service system 200 has an insurance agent 210. The insurance agent 210 uses the customer database (abbreviated as DB in the drawing) 211, the disaster information from the disaster information reporting station 220, and the customer information from the customer database 211, particularly the address, and the insurance information. And a notification unit 212 that selects and notifies a customer to be notified.

  The person in charge who has been notified of the customer who will be notified of the visit and the insurance information sends the telephone 213 to the mobile phone 231 of the affected area affected by the earthquake and the house 241 of the affected area affected by the typhoon xx. Then, a visit by telephone and notification of insurance information are performed (232 or 242). In addition, it is not limited to a telephone, You may perform the visit using FAX, mail, and other SNS, and the notification of insurance information.

(Display example)
FIG. 2B is a diagram illustrating a display example of a screen that prompts for a visit and notification of insurance information in the customer service system 200 according to the present embodiment. Note that the screen that prompts the visit and notification of insurance information is not limited to the display example of FIG. 2B.

  A display screen 250 in FIG. 2B is a screen for notifying a damaged area caused by typhoon xx, and a period of damage occurrence (for example, 2013/10/8 to 2013/10/11) and a damaged area are notified. The display screen 260 is a disaster area target customer list in which the damage area caused by the typhoon xx and the customer database 211 are compared to determine and display a customer who may be affected by the disaster. The address and contact information (telephone, e-mail, etc.) of each policyholder is displayed in the affected area target customer list. A period (for example, 10/15 to 10/31) for the person in charge to visit is displayed along with the customer list for the affected area. The display screen 270 displays the attribute information of “Taro Yamada” selected from the customer list for the disaster area and information to be notified to “Taro Yamada” (in FIG. 2B, the coverage area, coverage period, insurance amount, special contract of the contract insurance) Status etc.) is displayed.

  The person in charge makes a call while referring to the display screen 270, or transmits the display screen 270 to the affected area target customer by e-mail or FAX.

(Action schedule registration screen)
FIG. 2C is a diagram showing an action schedule registration screen 280 in the customer service system 200 according to the present embodiment. The action schedule registration screen 280 displays, for example, a schedule for a visitor to make a visit call for the customer selected from the customer list to be visited displayed on the display screen 260 of FIG. 2B via the action schedule registration screen 280. By registering, it is used for managing whether there is no missed call within a predetermined period.

  On the action schedule registration screen 280, the visit call 281 is selected as the contact schedule item type from the item information input field, and the current case status is set to incomplete (uncalled) 282. Here, the contact includes not only the meeting between the person in charge and the customer, but also the telephone call from the person in charge to the customer, FAX, mail, contact using other SNS, and the like.

  Then, on the action schedule registration screen 280, as the action schedule of the contact information, the visit call 283 is selected, the contact information is “Taro Yamada” 284, and the telephone number 285 is set. As the details of the visit, enter “Damage of Typhoon xx Confirming the damage status to the customer If there is damage, notification of insurance coverage and procedures” (286). As the visit period and time zone, October 15 to October 31 and 12 o'clock to 13 o'clock are set as in FIG. 2B (287).

  When the incomplete 288 is selected as the status, and the save and the end button 289 is clicked, the action schedule of the visit call is registered. After that, during the period, a visit call will be notified, and on the last day, a warning will be given to manage the contact service by visit visit to the person in charge or the department in charge.

  The action schedule registration is not registration by the person in charge, but the information processing apparatus of this embodiment automatically sets a default visit period based on the disaster occurrence area, period and customer address, and notifies the person in charge. It may be configured to.

(Visit call completion registration screen)
FIG. 2D is a diagram showing a visit call completion registration screen 290 in the customer service system 200 according to the present embodiment. Completion registration on the visit call completion registration screen 290 is used to manage whether there is no missed call within a predetermined period. For example, when the person in charge executes and completes the action reservation registered from the action schedule registration screen 280 of FIG. 2C or the action reservation automatically registered by default by the information processing apparatus, the visit call completion is registered. Completion registration on the visit call completion registration screen 290 is used as contact history information for generating a contact schedule with the customer thereafter.

  On the visit call completion registration screen 290, the visit call 291 is selected as the contact schedule item type in the case information, and the current case status is set to completed (call completed) 292.

  Also, on the visit call completion registration screen 290, the telephone 293 is selected as the contact type of the completed contact, and for example, 2013/10/22 (294) is input as the corresponding date. In addition, “OUT” (295) indicating a call from the person in charge to the customer as the contact content, a sympathy call 296, and “confirm the damage status to the customer and confirm that there is no damage” (297) are entered as the content. .

  Then, when the completion 298 is set as the status, and the save and the end button 299 is clicked, the visit call completion is registered as the contact history. Thereafter, this contact history is used to generate other contact schedules for the customer. For example, if there is damage to the customer, a schedule may be generated and registered so as to contact again after a certain period of time (after one month / half year / one year later, etc.).

(System configuration)
FIG. 3 is a block diagram showing a configuration of the customer service system 200 including the information processing apparatus 310 of the insurance agency 210 according to the present embodiment.

  The customer service system 200 includes an information processing apparatus 310 of an insurance agency 210, a disaster information notification station 220, and customer communication terminals (including telephones) 341 to 344, which are connected to each other via a network 330. In the customer service system 200, the telephone 321 of the insurance agency 210 and the communication terminals 341 to 344 are connected by a telephone line network 350, separately from the network 330.

  The insurance agent 210 informs the person in charge of the customer who should make a visit call, which is selected based on the disaster information area information from the disaster information reporting station 220 by the information processing device 310 and the information processing device 310. For example, it has a communication terminal 320 connected to an in-house LAN and a telephone 321 for a sneak call.

  The configuration of the customer service system 200 in FIG. 3 is an example, and the present invention is not limited to this. For example, the visit call may be a call through the network 330, a call through the telephone network 350, or another wired or wireless call.

(Operation procedure)
FIG. 4 is a sequence diagram showing an operation procedure of the customer service system 200 including the information processing apparatus 310 according to the present embodiment.

  In step S401, the disaster information notification station 220 notifies the information processing apparatus 310 of the disaster information. In step S403, the information processing apparatus 310 acquires the disaster area from the received disaster information. Next, in step S <b> 405, the information processing apparatus 310 determines a customer whose address is the disaster area acquired from the disaster information as a disaster area target customer from the customer database 211. At this time, not only the address of the policyholder but also the customer who should make a call may be determined from the address of a parent, child, or relative. In this case, it is desirable that the contents of the visit call be different between the policyholder and the parties concerned.

  In step S407, the information processing apparatus 310 transmits the determined affected area target customer or related person to the communication terminal 320 of the sales representative and notifies it. The information to be notified includes a visit call period, which is a period in which a visit call should be made, together with a list of customers affected by the disaster area. In step S409, the sales representative's communication terminal 320 displays the received affected area target customer list and the visit call period, and prompts the sales representative to make a visit call.

  In step 411, when there is a request for notification content from the communication terminal 320 to the customer selected from the customer list, the information communication apparatus 310 generates notification content for the selected customer in step S 413, and the communication terminal To 320. The notification content is generated from the insurance type and contract content information from the customer database 211 and the insurance content information from the insurance contract database 411 storing details of the insurance content. In step S415, the sales representative's communication terminal 320 displays the content of notification to the selected customer.

  If the sales representative indicates a visit call by the information processing device 310 in step S417, the information processing device 310 automatically sends the generated notification content to the customer selected in step S419 to the customer selected automatically. Make a visit call. On the other hand, the sales representative may make a visit call using the telephone 321 in step S421 while referring to the notification content of the communication terminal 320. Visiting calls are not limited to these.

<Functional configuration of insurance agent server>
FIG. 5 is a block diagram showing a functional configuration of an insurance agency server as the information processing apparatus 310 according to the present embodiment.

  The information processing apparatus 310 communicates with the disaster information notification station 220 and the customer communication terminals 341 to 344 via the network 330 and also has a communication control unit 501 that communicates with the sales representative communication terminal 320 via the in-house LAN. Have. Note that a communication control unit that performs communication via the network 330 and in-house LAN communication may be provided separately.

  The customer information acquisition unit 502 extracts customer information including address information included in the range of the disaster area from the customer database. In the customer information of the customer database, not only existing customers but also new customers, customers who have received contract transfer, and prospective customers who have not yet contract but may have contracts are stored in advance. The customer information storage unit 503 associates the customer information acquired by the customer information acquisition unit 502 with the contact schedule for the customer, organizes the information for each customer, and stores it in the customer database 211.

  The disaster information acquisition unit 505 acquires disaster information including disaster area information from the disaster information notification station 220 via the network 330 and the communication control unit 501. The disaster area acquisition unit 506 acquires the disaster area from the disaster information acquired by the disaster information acquisition unit 505. The disaster level can be acquired together with the affected area. The stricken area target customer determination unit 507 has a stricken area target customer extraction table 507a, and is based on a comparison between the stricken area acquired by the stricken area acquiring unit 506 and the address of the policyholder stored in the customer database 211. Determine customers affected by the affected area. As described above, not only the affected area target customers but also the parents, children, relatives and related persons of the affected area target customers may be determined.

  The visit destination / notification information request receiving unit 508 receives a request for the visit destination / notification information from the communication terminal 320 of the branch office or the sales staff via the communication control unit 501. The visit destination / notification information generation unit 509 has a notification information generation table 509a, and in response to a request for the visit destination / notification information, visits the affected area target customers determined by the affected area target customer determination unit 507. First, the contents of the insurance contracted by the affected area target customer are acquired from the insurance contract database 411 and notification information is generated. The visited / notified information notifying unit 511 notifies the generated visited / notified information to the communication terminal 320 of the department branch or the sales staff via the communication control unit 501.

  The visit / notification request reception unit 512 and the visit / notification transmission unit 513 are optional treatment units. The visit / notification request receiving unit 512 receives, via the communication control unit 501, a request for sending a visit / notification to a customer in the disaster area from the communication terminal 320 of the department branch or the sales staff. The visit / notification transmission unit 513 transmits a visit / notification to the generated visit destination via the communication control unit 501 to the communication terminals 341 to 344 of the affected area target customer.

(Customer database)
FIG. 6A is a diagram showing a configuration of the customer database 211 according to the present embodiment. In the customer database 211, customer attribute information, insurance information under contract, and customer contact schedule are accumulated for each customer, and judgment of customers affected by the disaster area and schedule of visits to customers affected by the disaster area are stored. Used for management and. The configuration of the customer database 211 is not limited to FIG. 6A.

  The customer database 211 stores customer attribute information in association with a customer identifier (abbreviated as customer ID in the drawing) 611. The customer attribute information includes, for example, a customer name 612, an address 613, and a telephone number or e-mail address 614 as a contact address. Further, the customer database 211 stores one or a plurality of contract insurance information 615 in association with the customer identifier 611. The contract insurance information 615 includes, for example, an insurance type, a contract number, an insurance contractor, and a maturity. The customer database 211 stores a contact schedule 616 in association with the contract insurance information 615 of the customer identifier 611. The contact schedule 616 includes a next action schedule, a status indicating incompletion or completion, a contact history 1, a contact history 2, and so on.

(Insurance contract database)
FIG. 6B is a diagram showing a configuration of the insurance contract database 411 according to the present embodiment. The insurance contract database 411 stores contract contents regarding insurance handled by the insurance agent. The insurance contract database 411 is not limited to FIG. 6B.

  The insurance contract database 411 stores insurance contents 622 in association with each insurance type 621. The insurance content 622 includes, for example, a contract content, an insurance target period, an insurance amount, a special insurance coverage, and the like.

(Disaster area target customer extraction table)
FIG. 7A is a diagram showing a configuration of a disaster area target customer extraction table 507a according to the present embodiment. The disaster area target customer extraction table 507a is for extracting customers who may be residing in the disaster area based on the comparison between the disaster area of the disaster that has occurred and the customer residence position stored in the customer database 211. used.

  The affected area target customer extraction table 507a stores the occurrence disaster 711 and the affected area 712 caused by the occurrence disaster 711. And the disaster area target customer information 713 extracted from the customer database 211 of the disaster area target customer who makes the disaster area 712 a residence position (for example, address) is memorize | stored. The extracted disaster area target customer information 713 includes a customer identifier, a customer name, an address, contact information, an insurance type and a situation.

(Notification information generation table)
FIG. 7B is a diagram showing a configuration of the notification information generation table 509a according to the present embodiment. The notification information generation table 509a is used to generate notification information to be notified to customers in the affected area from the disaster or damage level that occurred and the insurance type.

  The notification information generation table 509a stores the occurrence disaster 721 and the damage level 722 of the occurrence disaster 721. Further, the notification information generation table 509a stores an insurance type 723. The notification information generation table 509a stores notification information 724 generated based on the damage level 722 and the insurance type 723. The notification information 724 includes the insurance coverage, the insurance coverage period, the insurance amount, the special coverage status, and the like.

<< Hardware configuration of insurance agency server >>
FIG. 8 is a block diagram showing a hardware configuration of an insurance agency server as the information processing apparatus 310 according to the present embodiment.

  In FIG. 8, a CPU 810 is a processor for arithmetic control, and the CPU 810 executes programs and modules stored in the storage 850 while using the RAM 840, whereby each functional configuration of the information processing apparatus 310 shown in FIG. The function of the part is realized. The ROM 820 stores fixed data and programs such as initial data and programs. Further, the communication control unit 501 communicates with the disaster information notification station 220 or the customer communication terminals 341 to 344 via the network 330 and also communicates with the communication terminal 320 of the sales staff via the in-house LAN. Note that the number of CPUs 810 is not limited to one, and may be a plurality of CPUs or may include a GPU for image processing.

  The RAM 840 is a random access memory that the CPU 810 uses as a work area for temporary storage. The RAM 840 has an area for storing data necessary for realizing the present embodiment. The disaster information 841 is information including a disaster area related to the disaster acquired from the disaster information reporting station 220. The disaster area target customer extraction table 507a is a table of FIG. 7A used for extracting a disaster area target customer from the disaster area of the disaster information 841 and the customer residence position of the customer database 211. The notification information generation table 509a is a table of FIG. 7B used to generate notification information to be notified to a disaster area target customer from a disaster or insurance type that has occurred. The disaster area target customer list display data 844 is display data for displaying the list of disaster area target customers extracted using the disaster area target customer extraction table 507a on the communication terminal 320 of the sales staff. The notification information display data 845 is display data for displaying the notification information generated using the notification information generation table 509a on the communication terminal 320 of the sales representative. Transmission / reception data 846 indicates transmission / reception data transmitted / received via the communication control unit 501.

  The storage 850 stores a database, various parameters, or the following data or programs necessary for realizing the present embodiment. The customer database 211 is a database of FIG. 6A that stores customer attribute information, insurance contract information, and contact schedules in a searchable manner for each customer. The insurance contract database 411 is a database shown in FIG. 6B that stores the contract contents, the insurance coverage period, the insurance amount, the insurance coverage status, and the like for each insurance type.

  The storage 850 stores the following programs. The information processing device control program 851 is a control program that controls the entire information processing device 310. The disaster area target customer determination module 852 is a module that determines a disaster area target customer from the customers in the customer database 211 using the disaster area target customer extraction table 507a. The notification information generation module 853 is a module that uses the notification information generation table 509a to generate notification information from the damage level and the contract insurance of the customers affected by the disaster area. The visit / notification transmission module 854 is a module that transmits the notification information generated by the notification information generation module 853 together with the visit to the affected area target customer determined by the affected area target customer determination module 852.

  Note that the RAM 840 and the storage 850 in FIG. 8 do not show programs and data related to general-purpose functions and other realizable functions that the information processing apparatus 310 has.

《Insurance agent server processing procedure》
FIG. 9 is a flowchart showing a processing procedure of the insurance agency server as the information processing apparatus 310 according to the present embodiment. This flowchart is executed by the CPU 810 in FIG. 8 using the RAM 840, thereby realizing the functional configuration unit in FIG.

  In step S <b> 901, the information processing apparatus 310 waits for information on the presence / absence of a disaster from the disaster information notification station 220. When receiving the disaster information from the disaster information reporting station 220, the information processing apparatus 310 acquires the disaster information in step S903. In step S901, the sales representative may wait for a disaster information acquisition instruction from the disaster information notification station 220.

  In step S <b> 905, the information processing apparatus 310 determines a disaster area target customer from the disaster area of the disaster information and the customer residence position of the customer database 211. Next, in step S907, the information processing apparatus 310 generates a visit and notification information corresponding to the disaster and disaster level, the affected area target customer, the contract insurance, and the like. Then, in step S909, the information processing apparatus 310 notifies the sales representative's communication terminal 320 of the affected area target customer as the visit destination and the notification information.

  As an option, in response to an instruction from the sales representative's communication terminal 320, the information processing apparatus 310 notifies the communication terminals 341 to 345 of the visitees directly via the network 330 that they are visiting in step S 911. Send.

  According to the present embodiment, it is possible to provide customer service for notifying a visitor after the occurrence of a disaster as well as information on insurance under contract, thereby improving reliability by prompt contact with the customer after the occurrence of a disaster.

[Third Embodiment]
Next, an insurance agency server as an information processing apparatus according to the third embodiment of the present invention will be described. When compared with the second embodiment, the insurance agency server according to this embodiment determines whether or not the notification is transmitted to the customer and determines that the notification is not transmitted. The visit / notification information reporting unit is different in that the sales representative is notified to urge the sales representative to notify the customer's relative or the client's requester. Since other configurations and operations are the same as those of the second embodiment, the same configurations and operations are denoted by the same reference numerals, and detailed description thereof is omitted.

<< Operation procedure of customer service system >>
FIG. 10 is a sequence diagram showing an operation procedure of the customer service system including the information processing apparatus 1010 according to this embodiment. In FIG. 10, steps similar to those in FIG. 4 of the second embodiment are denoted by the same step numbers and description thereof is omitted.

  In the present embodiment, when a visit call to a disaster area target customer who is an insurance contractor cannot be connected in step S419 or step S421, a visit call is made to another contact related to the insurance contractor. . The other contact person is, for example, a parent, a child, a relative, or a client registered by an insurance policyholder.

  If the visit call cannot be connected, the information processing apparatus 1010 refers to the customer database 1011 in step S1031, and searches for other contact information related to the affected area target customer. The information processing apparatus 1010 notifies the other contact information that has been searched to the communication terminal 320 of the sales representative, and the communication terminal 320 displays the other contact information in step S1033.

  If the sales representative indicates a visit call by the information processing apparatus 1010 in step S1035, the information processing apparatus 1010 automatically inserts the generated notification content into the fixed phrase in step S1037 and automatically sends it to other contacts. Make a visit call. On the other hand, the sales representative may make a visit call to another contact using the telephone 321 in step S1041 while referring to the notification content of the communication terminal 320. Visiting calls are not limited to these.

<Functional configuration of insurance agent server>
FIG. 11 is a block diagram illustrating a functional configuration of an insurance agency server as the information processing apparatus 1010 according to the present embodiment. In FIG. 11, the same functional components as those in FIG. 5 of the second embodiment are denoted by the same reference numerals, and description thereof is omitted.

  When compared with the customer database 211, the customer database 1011 stores other notification destinations that notify the visitor and the insurance information when the visitor and the insurance information cannot be notified.

  The disconnection information acquisition unit 1114 acquires information indicating the disconnection when the visitor call by the sales representative is interrupted or when the communication by the visitor / notification transmission unit 513 is interrupted. The disconnection determination unit 1115 determines that a visit call is not actually transmitted to the customer from the information indicating the acquired disconnection.

  The other contact acquisition unit 116 refers to the customer database 1011 that stores other contacts, and acquires other contacts related to the determined affected area target customer. Then, the visit destination / notification information generation unit 509 refers to another contact from the other contact acquisition unit 116 and generates a visit destination and notification information.

(Customer database)
FIG. 12 is a diagram showing a configuration of the customer database 1011 according to the present embodiment. In FIG. 12, elements similar to those in FIG. 6A of the second embodiment are denoted by the same reference numerals, and description thereof is omitted. Further, the configuration of the customer database 1011 is not limited to FIG.

  The customer database 1011 stores other contact information 1217 in association with the customer identifier 611. Other contact information 1217 includes family contact information, child contact information, parent contact information, relative contact information, and other client contact information.

《Insurance agent server processing procedure》
FIG. 13 is a flowchart showing a processing procedure of the insurance agency server as the information processing apparatus 1010 according to the present embodiment. This flowchart is executed by the CPU 810 of FIG. 8 using the RAM 840, thereby realizing the functional configuration unit of FIG. In FIG. 13, the same steps as those in FIG. 9 of the second embodiment are denoted by the same step numbers, and the description thereof is omitted.

  In step S1313, the information processing apparatus 1010 determines whether the visit is completed or not. If the visit is complete, the process ends. If not, the information processing apparatus 1010 extracts other contact information from the customer database 1011 in step S1315 and notifies the communication terminal 320 of the sales representative.

  According to the present embodiment, in addition to the effects of the second embodiment, the probability that a visit or notification information reaches a customer is improved, and the reliability is improved by contacting not only the customer but also a relative or a client. Can do.

[Other Embodiments]
The present invention has been described above with reference to the embodiments, but the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. In addition, a system or an apparatus in which different features included in each embodiment are combined in any way is also included in the scope of the present invention.

  In addition, the present invention may be applied to a system composed of a plurality of devices, or may be applied to a single device. Furthermore, the present invention can also be applied to a case where an information processing program that implements the functions of the embodiments is supplied directly or remotely to a system or apparatus. Therefore, in order to realize the functions of the present invention on a computer, a program installed in the computer, a medium storing the program, and a WWW (World Wide Web) server that downloads the program are also included in the scope of the present invention. . In particular, at least a non-transitory computer readable medium storing a program for causing a computer to execute the processing steps included in the above-described embodiments is included in the scope of the present invention.

Claims (6)

Disaster information acquisition means for acquiring disaster-affected area information;
First determination means for determining whether or not the customer's address is included in the disaster area based on the disaster area information and the customer's address information;
Informing means for informing the person in charge of the visit to the customer and notification of the insurance information to the customer when it is determined that the customer's address is included in the affected area;
An information processing apparatus comprising: A customer database storing address information of the customer;
The customer database is associated with the customer identifier, customer attribute information indicating the customer attribute, insurance contract information of insurance contracted by the customer, contact schedule of the person in charge with the customer, and The information processing apparatus according to claim 1, wherein a contact history is stored.   The information processing apparatus according to claim 1, wherein the insurance information includes a contract content corresponding to at least the disaster type and a contracted insurance type, an insurance coverage period, an insurance amount, and a special insurance status. A second determination means for determining whether or not the notification is transmitted to the customer;
2. The notification means, when determining that the notification is not transmitted, notifies the person in charge to notify the relative of the customer or a target person designated by the customer. 4. The information processing apparatus according to any one of items 1 to 3. Disaster information acquisition step to acquire disaster area information of the disaster,
A first determination step of determining whether or not the customer's address is included in the disaster area based on the disaster area information and the customer's address information;
A notification step for informing the person in charge of the visit to the customer and the notification of the insurance information to the customer when it is determined that the customer's address is included in the affected area;
An information processing method including: Disaster information acquisition step to acquire disaster area information of the disaster,
A first determination step of determining whether or not the customer's address is included in the disaster area based on the disaster area information and the customer's address information;
A notification step for informing the person in charge of the visit to the customer and the notification of the insurance information to the customer when it is determined that the customer's address is included in the affected area;
An information processing program that causes a computer to execute.

Images