JP2009122796A - System in sales agency and sales merchandise explanation support method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system and a method for leaving what type of explanations has been made, and what type of process has been performed about merchandise as records about sales configurations to perform the face-to-face sales of merchandise. <P>SOLUTION: In an in-agency system to be used for selling insurance product to be sold by an insurance company through an agency, a counter terminal means to be operated by a counter person in charge provides an insurance explanation support means for supporting insurance product explanations by the counter person in charge; an insurance instruction printing means for printing an insurance instruction from the printing means; and a database management means for managing a database; and the insurance explanation support means records an insurance product explaining operation by the counter person in charge with a time as a log by using the database management means, and the insurance instruction printing means prints an insurance instruction customized for each insurance contractor on which the insurance product explaining operation has been printed. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention is, for example, a system in a sales agent when selling a product that requires or is required to be solicited or sold carefully, such as an insurance product sold by an insurance company, through an agent, and sales. The present invention relates to a sales product explanation support method in an in-agent system.

Conventionally, for example, the following techniques have been known as a selling method and a system used at the time of selling insurance products sold by an insurance company through an agent.
The following Patent Document 1 discloses an insurance contract system in which insurance diplomats comprehensively provide various types of insurance using a portable terminal device while interacting with an insurance contract subject or an insurance contractor. In this system, the server device has an insurance product information DB, which is connected to a portable terminal device used by insurance diplomats via a network, and the terminal device is stored in the insurance product information DB. It is accessible. The insurance agent selects the insurance product desired by the policyholder or policyholder from the insurance product information DB, and the insurance plan for each insurance product according to the prescribed conditions of the policyholder or policyholder And presents the created security plan to the terminal device. The policyholder or policyholder selects a desired security plan from the presented security plans, and the insurance agent makes a request for the insurance contract to the server device based on the selected security plan.

In addition, Patent Document 2 below provides an insurance contract system that can make an insurance contract quickly and safely on the Internet, and can leave data relating to a record of the procedures performed at the time of the contract. The following insurance contract system is disclosed.
That is, in an insurance contract system for making an insurance contract with a user through a network, a first request means for presenting an input form and requesting the user to input necessary items, and a contract including the input necessary items The second request means for creating the contents confirmation data and presenting it to the user to request the provision of an electronic signature, the third request means for requesting the designation of the payment method of the insurance premium, and the user attached the electronic signature Contract means for establishing an insurance contract based on the content confirmation data and designation of the payment method, and creating the contract content data when the insurance contract is established, and sending it to the user with an electronic signature Completion notification means for notifying the completion of the contract, and the contents and processing of the processing performed by the first request means, the second request means, the third request means, the contract means, and the completion notification means It comprises a log recording means for recording time as log data.
JP 2003-036355 A JP 2001-306911 A

  Conventionally, in insurance product sales where face-to-face sales are obligatory, policyholders have to respond to written documents such as “I accept the explanations” as evidence that the policyholders explained the explanations. I was signing and stamping. And if the policyholder claims that he did not hear the explanation at the time of the contract, there was no appropriate means to prove the fact explaining the contents of the insurance product.

  In the said patent document 1, the verification of the fact of the description in the above insurance explanation was not considered. Moreover, in the above-mentioned Patent Document 2, it was possible to leave data regarding the record of the procedure performed at the time of the contract, but it was not considered to prove the fact explaining the contents of the insurance product. Even if the processing data was left in between, data indicating the fact of explanation about the insurance product actually performed face-to-face could not be simply recorded as a record.

The in-sales agent system of the present invention is an in-sales agent system used when selling sales products through a sales agent, and includes a window terminal means, a database management means for managing a database, and a printing means. The window terminal means includes sales product explanation support means for supporting explanation of sales products, and insurance manual printing means for printing sales product instructions from the printing means, the sales product explanation support means, Supporting the explanation of the sales product using the counter terminal means by the contact person in charge, the operation information indicating the fact of the explanation of the sales product is recorded in the database using the database management means, and the sales product description The printing means prints operation information indicating the fact of the explanation of the sales product recorded in the database on the sales product description.
Moreover, the system in the sales agent of the present invention further reproduces the numbered ticket issuing means for issuing a numbered ticket for customers coming to the sales agent and the information printed on the numbered ticket surface issued by voice, And / or a numbered ticket number calling means for signaling a customer who has received a numbered ticket by displaying the information, and issuing information about the ticketing of the numbered ticket and a signal to the customer who has received the numbered ticket, Recording in the database and printing on the sales merchandise certificate.
Further, in the sales agent system according to the present invention, the sales product manual printing means prints using means capable of detecting falsification of the sales product manual on which the operation for explaining the insurance product is printed. It is characterized by.

According to the present invention, it is possible to easily prove the fact explaining the contents of the sales product in the product sales for which face-to-face sales are required.
Further, according to the present invention, DB cooperation and data association can be easily performed using a numbered ticket or a numbered ticket number once issued as a key.
Furthermore, according to the present invention, it is possible to detect falsification of the sales product manual at the sales company to which the sales product manual is submitted.

  Hereinafter, the present invention will be described with reference to the drawings.

First, Example 1 will be described. FIG. 1 is a system configuration diagram illustrating an example of a system configuration according to the first embodiment. The first embodiment of the present invention uses an insurance product sales agent as an example, but can be applied to a sales agent of financial products such as stocks and investment trusts in addition to insurance products.
In this figure, reference numeral 101 is an agency system, reference numeral 102 is a numbered ticket issuing device, reference numeral 103 is a window terminal device, reference numeral 104 is a reception program, reference numeral 105 is an insurance explanation support program, reference numeral 106 is an insurance manual printing program, reference numeral Reference numeral 107 is a DB apparatus, reference numeral 108 is a log DB, reference numeral 109 is a numbered ticket DB, reference numeral 110 is a numbered ticket number calling apparatus, reference numeral 111 is a printing apparatus, reference numeral 112 is a network in the agency, reference numeral 113 is a network, reference numeral 114 is an insurance company Internal network, reference numeral 115 is an insurance company system, reference numeral 116 is an insurance description input apparatus, reference numeral 117 is a log reference apparatus, reference numeral 118 is a contract DB apparatus, and reference numeral 119 is a contract DB.

The in-agency system 101 is an in-agency system, and includes a numbered ticket issuing device 102, a window terminal device 103, a DB device 107, a numbered ticket number calling device 110, and a printing device 111. It is connected.
The numbered ticket issuing device 102 is a device for issuing a numbered ticket to a customer who has come to the agency. The window terminal device 103 is installed at the window of the agency and is mainly operated by a person in charge of the agency. The window terminal apparatus 103 includes a reception program 104, an insurance explanation support program 105, and an insurance manual printing program 106. . The reception program 104 is a program that supports customer reception work at a window. The insurance explanation support program 105 is a program for supporting the explanation of insurance by the agent in charge of the agent. The insurance manual printing program 106 is a program for printing out the insurance manual.

The DB device 107 is a device that holds a log DB 108 and a numbered ticket DB 109. The log DB 108 is a log DB (database). The numbered ticket DB 109 is a DB (database) that records the details of numbered ticket issuance.
The numbered ticket number calling device 110 displays and / or reproduces the number printed on the ticket surface of the numbered ticket issued by the numbered ticket issuing device 102 to the customer by the operation of the agent in charge at the agency. It is a device that calls the customer to come to the window by announcing and signaling the customer.
The printing apparatus 111 is mainly a printing apparatus such as a printer. The in-agent network 112 is an in-agent network, which connects each device in the agent and is connected to a network 113 that is a network outside the agent.
The network 113 is a network such as the Internet. In this embodiment, the agency network 112 and the insurance company network 114 are connected.
The insurance company system 115 is a system in the insurance company, and includes an insurance instruction input device 116, a log reference device 117, and a contract DB device 118, which are connected by an insurance company network 114. The insurance manual input device 116 is a device for inputting an insurance manual. The log reference device 117 is a device for referring to a log. The contract DB device 118 is a device that stores the contract DB, and is composed of the contract DB 119. The contract DB 119 is a DB (database) for insurance contract information.

Before explaining the details of each device, the configuration of a PC (Personal Computer) used to realize the window terminal device 103, the DB device 107, the log reference device 117, and the contract DB device 118 in this embodiment. Let me state.
FIG. 2 is a diagram illustrating an example of a configuration of a general PC.
In this figure, reference numeral 201 is a CPU, reference numeral 202 is a memory, reference numeral 203 is an interface, reference numeral 204 is a network interface, reference numeral 205 is a keyboard, reference numeral 206 is a screen, reference numeral 207 is a scanner, reference numeral 208 is a printer, reference numeral 209 is a hard disk, Reference numeral 210 denotes a clock.
The CPU 201 is a central processing unit that can execute a program recorded in the memory 202 or transferred from the hard disk 209 to the memory 202 in advance.
Note that the program is stored in the PC via a removable storage medium that can be used by the PC or a communication medium (a communication line or a digital signal or a carrier wave on the communication line) through the network interface 204 described below when necessary. May be introduced.
The memory 202 temporarily stores programs and data. The network interface 204 is a device for communicating with a PC or the like outside the PC system. A keyboard 205 is a device operated by an operator of the PC system in order to input commands and data to the PC system. A screen 206 is a device for displaying processing results and the like. The scanner 207 is an apparatus for mainly optically reading a printed matter or the like and inputting it as an image into the PC system. The printer 208 is a device for printing the processing results of the PC system on a print medium such as paper. The hard disk 209 is a device for storing programs and data, and the program and data stored in this device has a feature that even if it is turned on after the power is turned off, it is normally stored. Yes. The clock 210 is a device for the CPU 201 to know the current approximate time. The interface 203 is a device for connecting each device in the PC.

In the present embodiment, system initialization is divided into two types: system installation and initialization for each business division such as every day. FIG. 3 is a diagram showing an initialization process flow at the time of system installation, and is a diagram showing an outline of the initialization process flow at the time of system installation.
Step 301 is a process in which each processing device is configured to be able to set the time using NTP (Network Time Protocol: Reference RFC1305) or the like.
Step 302 is processing for initializing records in the numbered ticket DB 109 in the DB device 107.
Step 303 is a method in which, in the contact terminal device 103, the person in charge inputs the contact number where each contact terminal device 103 is installed among the contact numbers assigned to individual contacts in the agency in advance through the keyboard. This is a process of registering the information and storing the window number on a hard disk or the like.
In step 304, information such as the IP address of the DB device 107 is stored in the log reference device 117 in advance, and the log DB 108 and the numbered ticket DB 109 in the DB device 107 can be referred to from the log reference device 117. .
The initialization from step 301 to step 304 can be performed in any order. For example, step 304 to step 301 may be performed in reverse order.

Also, FIG. 4 shows an outline of the initialization processing flow for each business break such as every day.
Step 401 is processing for adjusting the clock in each processing device using NTP or the like in each processing device.
Step 402 is a process in which the DB device 107 clears the record in the numbered ticket DB 109 or changes an incomplete record to absence completion or the like.
Step 403 is processing in which the numbered ticket issuing device 102 makes an inquiry to the DB device 107 to obtain the last numbered ticket number used, and stores it in the memory as the numbered ticket number.
The initialization from step 401 to step 403 can be performed in any order. For example, step 403 to step 401 may be performed in reverse order.

  Next, in this embodiment, each of the numbered ticket issuing device 102, the reception program 104 in the window terminal device 103, the insurance explanation support program 105, the insurance manual printing program 106, and the numbered ticket number calling device 110 or A processing flow of log recording performed by the program will be described together. FIG. 5 shows an outline of a processing flow when each apparatus or program performs log recording. FIG. 5 shows a processing sequence between the DB apparatus 107 and the apparatus or program that performs log recording.

  Here, reference numeral 501 denotes a log creation source, which is the numbered ticket issuing device 102, the reception program 104 in the window terminal device 103, the insurance explanation support program 105, the insurance manual printing program 106, and the numbered ticket number calling device 110. Each device or program is applicable. First, the log creation source 501 transmits a program name or device name, a numbered ticket number, and a log message to the DB device 107. The details of the log will be described in detail when each device is described. Next, the DB device 107 performs processing 504 for acquiring the date and time using the clock in the DB device 107. Finally, the DB device 107 performs processing 505 for registering the program name or device name, numbered ticket number, log message, and date / time in the log DB.

  An example of the log DB is illustrated in FIG. In FIG. 6, reference numeral 601 is a device name field, reference numeral 602 is a date / time field, reference numeral 603 is a numbered ticket number field, and reference numeral 604 is a log message. The device name field 601 is a field for recording the recording source that recorded the log. The time field 602 is a field for recording the time when the log is recorded, and the recorded date and time is the date and time measured by the clock of the DB device 107. The numbered ticket number field 603 is a field for recording the numbered ticket number. A log message 604 is a field for recording the contents of the log.

  Reference numerals 605 to 609 are examples of log records. In this example, at 605, the numbered ticket issuing device 102 printed the numbered ticket number 123 at time 10:23 and the numbered ticket 123 printed at time 10:23 on the numbered ticket issuing device 102 as a log. Has been. In 606, it is left as a log that the reception program 104 called the numbered ticket number 123 at time 10:26 and called the numbered ticket number 123 from the first window. In 607, it is left as a log that the numbered ticket number calling device 110 calls the numbered ticket number 123 to the first window at time 10:26 as the numbered ticket number 123. In 608, it is left as a log that the insurance explanation support program 105 started at time 10:28 with the numbered ticket number being 123. In 609, the insurance explanation support program 105 registers the name and address of the customer holding the numbered ticket number 123 at time 10:29.

Hereinafter, description will be made according to the operation of the system of the present embodiment. First, the operation when a customer visits the store will be described.
FIG. 7 is a diagram showing a processing flow of the numbered ticket issuing device. This is a sequence diagram showing an outline of the processing flow of the numbered ticket issuing process in the numbered ticket issuing apparatus.
Here, reference numeral 701 is a customer, reference numeral 102 is a numbered ticket issuing apparatus, and reference numeral 107 is a DB apparatus.
First, the customer 701 visits the store (704), and the customer 701 pushes down the numbered ticket issuing button (705). Then, the numbered ticket issuing apparatus 102 performs processing 706 for incrementing the numbered ticket number by one. Next, the numbered ticket issuing apparatus 102 performs a process 707 for acquiring the date and time. Next, the numbered ticket issuing apparatus 102 performs processing 708 for printing the numbered ticket, and issues a numbered ticket 709 to the customer 701. Next, the numbered ticket issuing device 102 transmits the device name, the numbered ticket number, the date and time, and the numbered ticket print log 710 to the DB device 107. Finally, the DB device 107 performs a log registration process 711 to update the log DB 108 and the numbered ticket DB 109.
As a result of the above processing, the numbered ticket issuance log for the customer is registered in the log DB 108 and the numbered ticket DB 109. The numbered ticket DB 109 is illustrated in FIG. 9 and will be described later.

Next, the processing flow of the reception program will be described. FIG. 8 is a sequence diagram illustrating the processing flow of the reception program.
Here, reference numeral 801 is a counter person in charge, reference numeral 104 is a reception program, reference numeral 110 is a numbered ticket number calling device, and reference numeral 107 is a DB device. An example of the processing screen of the reception program 104 is shown in FIG.
First, the contact person 801 transmits a process start command 805 to the reception program 104. Next, the reception program 104 requests an incomplete record in the numbered ticket DB from the numbered ticket number calling device 110 (806). Next, the numbered ticket number calling device 110 searches for an incomplete record in the numbered ticket DB (807), and transmits it to the reception program 104. Next, if there is an incomplete record, the reception program 104 displays that the customer is waiting (808).

Reference numeral 1001 in FIG. 10 is an example of an initial screen. A queue information display unit 1003 in this figure is a part that displays queue information, and information displayed at 808 is displayed here. In addition to the customer waiting, the number of waiting people and the waiting time of the longest waiting person may be displayed.
If the customer is not waiting, the contact person 801 may wait until the customer comes.
If the customer is waiting, the contact person 801 clicks the customer call button 1004 displayed by the reception program 104 (809). Then, the reception program 104 transmits the numbered ticket number to be called and the window number to the numbered ticket number calling device 110, requests a call (810), and transmits the numbered ticket number and the call log to the DB device 107. The DB device 107 updates the log DB 108 accordingly (812).
The numbered ticket number calling device 110 requested to be called performs a process (813) of calling and displaying the numbered ticket number and window number to be called and / or announcement / displayed by voice reproduction. Further, the numbered ticket number calling device 110 transmits the numbered ticket number, window number, and announcement / display log to be called to the DB device 107, and the DB device 107 updates the log DB 108 and the numbered ticket DB 109 accordingly (815). ).

If the customer does not appear at the window of the contact person 801 after waiting for a predetermined time or more, the contact person 801 may click the customer recall button 1005 to make a call request again. When the customer recall button 1005 is clicked, the reception program 104 requests the numbered ticket number calling device 110 to call again the numbered ticket number that was just called.
If the customer does not appear at the window of the contact person 801 even after making several call requests, the contact person 801 estimates that the customer will not come, and clicks the customer absence completion button 1007. The processing may be terminated as completion due to the absence of the customer. In this case, the reception program 104 transmits the program name, numbered ticket number, and absence completion log to the DB device 107, and the DB device 107 updates the log DB 108 and the numbered ticket DB 109 accordingly.

  If the visitor comes, the contact person 801 clicks the visitor button 1006 (816). Then, the reception program 104 transmits the numbered ticket number and customer visit log to the DB device 107. Then, the DB device 107 updates the log DB 108 (818). Next, the reception program 104 transmits the numbered ticket number and call termination to the numbered ticket number calling device 110 (819). Then, the numbered ticket number calling device 110 transmits information indicating completion of the calling to the DB device 107, and the DB device 107 updates the numbered ticket DB 109 accordingly (820). Next, the reception program 104 displays a customer visit screen 1002, and causes the window staff 801 to select a process to be performed (821).

The customer visit screen 1002 includes a numbered ticket number display unit 1008, a deposit service button 1009, a loan consultation button 1010, an insurance consultation button 1011, and the like. The numbered ticket number display unit 1008 is a part for displaying the numbered ticket number of the calling customer. A deposit service button 1009, a loan consultation button 1010, and an insurance consultation button 1011 are buttons for selecting a process to be actually performed. Note that this button is not limited to deposit business, loan consultation, and insurance consultation, and other buttons may exist according to other business programs. Further, when the number of these buttons increases, a hierarchical structure may be adopted in which the programs activated by the buttons are classified, and the programs are first selected after selecting the classification.
The contact person 801 determines the process to be performed next after listening to the customer's wish, and selects a process by clicking one of the deposit service button 1009, the loan consultation button 1010, and the insurance consultation button 1011 (822). . The reception program 104 performs processing for starting a program for performing processing selected using the numbered ticket number as a parameter (823).

An example of the numbered ticket DB touched above is shown in FIG.
In this figure, reference numeral 901 is the store visit time, reference numeral 902 is the numbered ticket number, reference numeral 903 is the calling time, reference numeral 904 is the result, and reference numerals 905 to 908 are examples of records in the numbered ticket DB.
The store visit time 901 is a field for recording the time when the customer visited the store. The numbered ticket number 902 is a field for recording the numbered ticket number issued to the customer. The call time 903 is a field for recording the time when the customer is called. A result 904 is a field for recording a call result.
For example, in the record denoted by reference numeral 905, a numbered ticket with numbered ticket number 123 is issued to a customer at 10:23, the customer is called at 10:26, and it is recorded that the customer has come to the window and the processing is completed. Has been.
In the record with reference numeral 906, a numbered ticket with numbered ticket number 124 is issued to a certain customer at 10:28, and the customer is called at 10:32. However, the customer does not appear at the window and is processed as absence completion. Has been recorded.
In the record of reference numeral 907, a numbered ticket with numbered ticket number 125 is issued to a certain customer at 10:35, and the customer is called at 10:38. It is recorded that the processing has not ended.
Further, in the record of reference numeral 908, it is recorded that a numbered ticket with numbered ticket number 126 is issued to a certain customer at 10:39, but the customer has not been called yet and the processing has not been completed. Yes.
In this example, only one field of the call time 903 is illustrated. However, for example, by preparing three fields of the call time 1, the call time 2, and the call time 3, it is possible to record up to three call times. You may extend to. In this case, if a customer appears in the first call, the values of the call time 2 and the call time 3 may be set as “uncalled”.

Next, the explanation of the insurance explanation support program 105 is started.
The programs started in 823 include, for example, those related to deposit business, those related to loan consultation, and those related to insurance consultation. Among these, when insurance consultation is selected, the insurance explanation support program 105 is activated.
FIG. 11 is a diagram showing an outline of the processing flow of the insurance explanation support program. Step 1101 is a process of starting the insurance explanation support program and recording the numbered ticket number in a log. Log recording is performed as described with reference to FIG.
Step 1102 is a process for displaying an insurance product list screen and selecting an insurance product to be described.

  FIG. 12 is a diagram showing an example of the insurance explanation support program screen. Among these, reference numeral 1201 in FIG. 12A is an example of the insurance product list screen. The insurance product list screen 1201 is a screen for displaying a list of insurance products, and includes an insurance selection button 1202. The insurance selection button 1202 is a button for selecting an insurance product to be described, and a plurality of insurance selection buttons 1202 may exist. In step 1102, the insurance product to be described can be selected by clicking these insurance selection buttons 1202.

Step 1103 is processing for extracting each explanation screen from the explanation screen designated in advance. If there is an element, go to Step 1104. After processing for each element, the process proceeds to step 1107.
Step 1104 is a process of recording operation information indicating the fact that the explanation screen is displayed and explanation contents in a log. The information to be recorded is the operation information indicating the fact that a certain explanation screen is displayed and the contents of the explanation in addition to the name and numbered ticket number of the insurance explanation support program.
Step 1105 is a process of displaying an explanation screen and waiting for the operation of the person in charge of the window. For example, reference numeral 1203 in the insurance explanation support program screen of FIG. 12 is an example of the explanation screen. In this example, “Life Insurance A course is a course that guarantees death due to illness. Insurance is not paid in case of injury”. When the explanation is finished, the person in charge of the window clicks the next screen button 1204 to notify the insurance explanation support program 105 that the explanation screen is finished. Note that there may be a plurality of explanation screens. In this case, when the next screen button 1204 is clicked, the next screen is displayed.

Step 1106 is a process of recording operation information indicating the fact that the explanation screen has ended in a log. The information to be recorded is operation information indicating the fact that the explanation on a certain explanation screen is finished, in addition to the name and numbered ticket number of the insurance explanation support program. After step 1106 is completed, the process returns to step 1103.
Step 1107 is a process for displaying a question screen. For example, (c) of the insurance explanation support program screen in FIG. 12, reference numeral 1205 is an example of a question screen, which includes a button 1206 for selecting a question, an other question button 1207, and a question end button 1208. The button 1206 for selecting a question and the other question button 1207 are both buttons for making a transition to the question answer screen, and the question end button 1208 is a button for notifying the insurance explanation support program 105 of the end of question acceptance.
Step 1108 is a process for checking whether or not the question button has been clicked. If one of the button 1206 for selecting a question and the other question button 1207 is clicked, the process proceeds to step 1109. If question end button 1208 is clicked on, it proceeds to step 1111.

  Step 1109 is a process for displaying a question answer screen. For example, on the question screen 1205, as a button 1206 for selecting a question, an assumed question 1: concurrent injuries and illnesses, an assumed question 2: a cancellation refund, and a button are shown. Click on the appropriate button if the customer is asking about the insurance in the event of both injury and illness, and click on the appropriate button if the customer asks about the surrender value. When these buttons are clicked, an answer screen for the assumed question is displayed, and the answer content is displayed on the screen. If there is a question other than the assumed question, the other question button 1207 is clicked. Then, the screen changes to a question answer screen. For example, reference numeral 1209 in the insurance explanation support program screen of FIG. 12 is an example of a question answer screen. The question answer screen 1209 is a screen for answering questions, and includes a question content input box 1210, an answer input box 1211, and an answer end button 1212. The question content input box 1210 is a place where the person in charge of the window inputs the question content of the customer. The answer input box 1211 is a place where the person in charge of the window inputs the content of the answer made to the question. The answer end button 1212 is a button for notifying the insurance explanation support program of the answer end.

Step 1110 is a process of recording operation information indicating the fact of transition to the question answer screen in a log. The information to be recorded is operation information indicating the fact that the screen has changed to a certain question answer screen in addition to the name and numbered ticket number of the insurance explanation support program.
Step 1111 is a process of recording the question contents and the question answer contents in a log after the answer is completed. The information to be recorded includes the contents of the question and the answer to the question in addition to the name and numbered ticket number of the insurance explanation support program.
Step 1112 is a process for checking whether the insurance manual printing button has been clicked. If the insurance manual print button is clicked, the process proceeds to step 1113. If the insurance instruction print button is not clicked and the end button of the insurance explanation support program is clicked, the process proceeds to step 1114.
Step 1113 is a process for starting the insurance manual printing program using the numbered ticket number as a parameter.
Step 1114 is processing for recording the end of the insurance explanation support program and the numbered ticket number in a log.
Usually, after the insurance explanation is completed, the person in charge of the window clicks the insurance instruction print button to print the insurance instruction manual and gives it to the customer for consideration of insurance participation.

FIG. 13 is a diagram showing an outline of the processing flow of the insurance manual printing program.
Step 1301 is a process for starting the insurance manual printing program and recording the numbered ticket number in a log. The information to be recorded is operation information indicating the fact that the insurance manual printing program has been started in addition to the name and numbered ticket number of the insurance manual printing program.
Step 1302 is a process of searching the log DB from the numbered ticket number and loading the explanation log into the memory. Here, the explanation log is a log relating to explanation acquired in each process of the outline of the processing flow of the insurance explanation support program in FIG.
Step 1303 is a process for printing the contents of the explanation log using the printing apparatus 111.

FIG. 14 is a diagram illustrating an example of a printed insurance manual.
In this figure, reference numeral 1401 is an example of an insurance manual, reference numeral 1402 is an explanation history column, and reference numeral 1403 is a signature column.
The insurance manual 1401 includes an explanation history column 1402 and a signature column 1403. An explanation log is printed in the explanation history column 1402. The signature column 1403 is a column for clearly indicating that the customer has approved the explanation history written in the explanation history column 1402 and has signed and stamped that the explanation has been accepted. As described in the insurance manual 1401, an insurance manual with a different description history column 1402 is issued for each individual and explanation, and the customer approves it, so that trouble can be prevented. The customer's address, name, and date of visit can be printed on the insurance manual. The date and time can also be printed by separating the date and time.

Finally, the log reference processing flow will be described.
FIG. 15 is a sequence diagram showing an outline of the log reference processing flow.
Here, reference numeral 1501 is a log reference source, and reference numeral 107 is a DB device. The log reference source 1501 is, for example, the insurance manual printing program 106 or the log reference device 117.
First, the log reference source 1501 transmits to the DB device 107 the name of the program that created the log to be referred to and the numbered ticket number as a log reference request. Next, the DB device 107 performs processing 1504 for searching for a log that matches the program name and numbered ticket number. Finally, the DB device 107 transmits a log response 1505 to the log reference source 1501.
Further, a search condition may be specified, and a log that matches the search condition may be specified. The DB device can be implemented using general database software, and log reference can also be realized using general database software.
In this case, for example, before transmitting the log reference request, the log reference source 1501 transmits information specifying the date and time range of the store and / or the address and name of the visitor to the DB device 107, and the DB device 107 searches the numbered ticket number corresponding to the transmitted information, and transmits the numbered ticket number and the like of the search result to the log reference source 1501. This search can be repeated to narrow down the corresponding numbered ticket number.
The agent system 101 has been described above.

Next, the insurance company system 115 will be described.
The insurance instruction input device 116 is an apparatus including a scanner 207, for example, and is an apparatus that saves an insurance instruction in the contract DB 119. The log reference device 117 is a device for referring to the log DB 108. The log is referred to through the network 113, and the actual processing is as described with reference to FIG.
The contract DB device 118 is a device for managing the contract DB 119, and is a general DB device.
In the first embodiment, after the customer signs and seals the insurance manual, the customer sends the insurance manual to the insurance company by mailing it to the insurance company together with a separately prepared insurance application form.
The insurance company confirms the explanation content, signature and seal in the insurance manual, and if it is confirmed that the explanation has been received properly, it starts the insurance underwriting examination according to the insurance application form. In the insurance underwriting examination, the insurance manual is stored in the contract DB 119 using the insurance manual input device 116, the underwriting examination is performed, and the contract DB 119 is updated.
When it is desired to know the details of the explanation process written in the insurance manual during the underwriting examination or thereafter, the log DB 108 is referred to using the log reference device 117. For log reference, the log reference method shown in FIG. 15 is used.

Next, a second embodiment of the present invention will be described.
In the second embodiment, compared to the first, third, and fourth embodiments, the time stamp assigning program 1601 further operates in the DB device 107, and the time stamp station 1602 is connected to the network 113. Is different.
FIG. 16 is a diagram illustrating a part added to the first embodiment in the system configuration diagram according to the second embodiment of the present invention.
In this figure, reference numeral 1601 denotes a time stamp assigning program, and reference numeral 1602 denotes a time stamp station.
The time stamp giving program 1601 is a program for giving a time stamp. The time stamp authority 1602 is an organization that certifies that digital information such as documents existed at a certain time based on the time stamp.
In the second embodiment, the log recording processing flow is different from the first, third, and fourth embodiments. An outline of this processing flow is shown in FIG.

FIG. 17 is a sequence diagram illustrating an outline of a processing flow when log recording is performed in the second embodiment.
Here, reference numeral 1701 is a log creation source, reference numeral 107 is a DB apparatus, and reference numeral 1602 is a time stamp station. First, the log creation source 1701 transmits the program name or device name + numbered ticket number + log message 1704 to the DB device 107. Next, the DB device 107 performs processing 1705 for acquiring date and time. Next, the DB device 107 transmits the program name or device name, numbered ticket number, log message, date and time 1706 to the time stamp station 1602. Next, the time stamp station 1602 performs a process 1707 for stamping the program name or device name, numbered ticket number, log message, date and time. Next, the time stamp station 1602 transmits the time stamp stamped information 1708 to the DB device 107. Finally, the DB device 107 performs processing 1709 for registering time stamped information in the log DB. However, the program name or device name, numbered ticket number, and date / time portion are registered in the same manner as in the first embodiment, the third embodiment, or the fourth embodiment, and a time stamp is added to the log message portion.
As a result, a log with a time stamp is left in the log DB, and time evidence can be improved.
Note that a process such as limiting the process of stamping the time stamp to a predetermined log message may be performed. In this case, it is possible to reduce the cost for stamping the time stamp.

Next, a third embodiment of the present invention will be described.
The third embodiment is different from the first embodiment, the second embodiment, or the fourth embodiment in that the operation of the insurance manual printing program 106 is different and that an insurance manual verification device is added. Is different.
FIG. 18 is a diagram showing an outline of a changed part of the system configuration in the third embodiment.
In this figure, reference numeral 1801 denotes an insurance manual verification device.
In addition to the case of the first embodiment, the second embodiment, or the fourth embodiment, the insurance company system 115 further includes an insurance manual verification device 1801.
The insurance manual verification device 1801 is a device for verifying the insurance manual.
First, the processing flow of the insurance manual printing program 106 according to the third embodiment will be described. FIG. 19 is a diagram showing an outline of the processing flow of the insurance manual printing program in the third embodiment.
Step 1901 is a process of starting the insurance manual printing program and recording the numbered ticket number in a log. The information to be recorded is the fact that the insurance manual printing program has been started in addition to the name and numbered ticket number of the insurance manual printing program.
Step 1902 is processing for searching the log DB from the numbered ticket number and loading the explanation log into the memory. Here, the explanation log is a log relating to explanation acquired in each process of the outline of the processing flow of the insurance explanation support program in FIG.

  Step 1903 is processing for creating falsification detection information from the contents of the explanation log, and step 1904 is processing for printing the contents of the explanation log and falsification detection information using the printing apparatus 111. These two processes are different from those in the first embodiment, the second embodiment, or the fourth embodiment. Here, the process of creating the falsification detection information from the explanation log contents is to use the acquired explanation log contents as the falsification detection information, or compress the acquired explanation log contents into the falsification detection information, or Either the acquired explanation log content is encrypted to be falsification detection information, or the acquired explanation log content is compressed and then encrypted to be falsification detection information. In step 1904, the information embedding device disclosed in Japanese Patent Laid-Open No. 2005-096782 can be used to print the contents of the explanation log and the falsification detection information. Alternatively, a two-dimensional code or the like may be used.

Next, the insurance manual verification device 1801 will be described.
FIG. 20 is a diagram showing an outline of a processing flow in the insurance manual verification device.
Step 2001 is a process for reading the insurance manual using the insurance manual input device 116.
Step 2002 is a process of transferring the read insurance instruction image to the insurance instruction verification device 1801 using the insurance company network 114.
Step 2003 is a process of reading the tampering detection information using the information reading device disclosed in Japanese Patent Laid-Open No. 2005-096782. If tamper detection information is embedded using a two-dimensional code in step 1904, a two-dimensional code reader is used.
Step 2004 is processing for detecting falsification using the falsification detection information. If the read information has been encrypted or compressed, it is displayed on the screen after it is released, and the operator is allowed to detect the presence or absence of tampering by visual comparison with the page.

Next, a fourth embodiment of the present invention will be described.
The fourth embodiment is different from the first embodiment, the second embodiment, or the third embodiment in that a remote consultation is added between the agency and the insurance company.
FIG. 21 is a schematic diagram illustrating changes in the system configuration according to the fourth embodiment.
In this figure, reference numeral 2101 denotes a remote consultation program, reference numeral 2102 denotes an insurance company remote consultation apparatus, reference numeral 2103 denotes an insurance company DB apparatus, and reference numeral 2104 denotes an insurance company log DB.
The window terminal device 103 is installed at the window of the agency and is mainly operated by the person in charge of the agency, and a remote consultation program 2101 is further added. The remote consultation program 2101 is a program for performing remote consultation with a person in charge in the insurance company.
The insurance company system 115 is an insurance company system. An insurance company remote consultation device 2102 and an insurance company DB device 2103 are further added and connected to the insurance company network 114. The insurance company remote consultation device 2102 is a device for receiving a remote consultation of a person in charge in the agency. The insurance company DB device 2103 is a device that manages the insurance company log DB 2104. The insurance company log DB 2104 is a log for recording a remote consultation log in the insurance company.
Teleconsultation is conducted when the agent's contact person at the agent determines that the customer's question cannot be answered when the agent is explaining the insurance product to the customer or accepting a question about the insurance product. . This remote consultation is performed in such a manner that the agent's contact person asks the insurance company and the insurance company answers it.
However, since a simple question / answer is likely to cause a trouble of not saying later, a remote consultation log is recorded in this embodiment.

The remote consultation process will be described with reference to FIG. FIG. 22 is a sequence diagram showing an outline of a remote consultation processing flow.
Here, reference numeral 107 denotes a DB apparatus, reference numeral 2101 denotes a remote consultation program, reference numeral 2102 denotes an insurance company remote consultation apparatus, and reference numeral 2103 denotes an insurance company DB apparatus.
First, an agent name is input to the remote consultation program 2101 as an initial setting. In addition, a window name may be entered.
Next, as a pre-process, the agent's contact person operates the remote consultation program 2101 to call the insurance company remote consultation apparatus 2102. The insurance company remote consultation device 2102 notifies the person in charge of the insurance company that a consultation has been received by sound or screen. Further, the agent's counter person in charge inputs the numbered ticket number of the current customer to the remote consultation program 2101.
The following consultation sequence is executed when the person in charge at the insurance company is ready to answer.

First, the person in charge at the agency inputs the contents of the consultation into the remote consultation program 2101 (2201). FIG. 23 summarizes the screens related to the remote consultation. Among them, reference numeral 2301 of (a) illustrates an outline of the consultation content input screen. In FIG. 23A, reference numeral 2302 denotes a consultation content input field, reference numeral 2303 denotes a contact person name field, and reference numeral 2304 denotes a send button. The consultation content input screen 2301 includes a consultation content input field 2302, a contact person name field 2303, and a send button 2304. The consultation content input field 2302 is a field in which the person in charge at the agency inputs the consultation content. The contact person name field 2303 is a field for inputting the contact person name of the agency contact. A transmission button 2304 is a button for transmitting the consultation content to the insurance company.
When the field to be entered is entered, the agent's contact person clicks the send button 2304. Then, the remote consultation program 2101 transmits the agent name, the contact person name, and the consultation content to the DB device 107. In response to this, the DB apparatus 107 performs processing 2206 for recording a log. The recorded log includes the program name of the remote consultation program 2101, the numbered ticket number, and the contents of the consultation.
Next, the remote consultation program 2101 transmits the agent name, the contact person name, and the consultation content to the insurance company remote consultation apparatus 2102 (2207).
The insurance company remote consultation device 2102 receives the agent name, the contact person name, and the content of the consultation, and transmits it to the insurance company DB device 2103 (2208). The insurance company DB apparatus 2103 performs processing 2209 for recording a log accordingly. The log to be recorded includes the device name of the remote consultation device 2102 in the insurance company, the agent name, the name of the person in charge of the window, and the content of the consultation, which is recorded with time.
Next, the insurance company remote consultation device 2102 displays the contents of the consultation (2210).

(B) of the screen relating to remote consultation in FIG. 23 is a diagram exemplifying an outline of the screen displayed on 2210 by the remote consultation apparatus 2102 within the insurance company. Here, the insurance company remote consultation device 2102 displays the contents of the consultation and inputs an answer to the person in charge in the insurance company. In this figure, reference numeral 2305 is an answer input screen, reference numeral 2306 is a consultation content display section, reference numeral 2307 is a consultant name display section, reference numeral 2308 is an answer input field, reference numeral 2309 is an answerer name input field, and reference numeral 2310 is a reply button. is there.
The answer input screen 2305 includes a consultation content display unit 2306, a consultant name display unit 2307, an answer input field 2308, an answerer name input field 2309, and a reply button 2310. The consultation content display unit 2306 is a part for displaying the consultation content. The consultant name display unit 2307 is a part that displays a consultant name. An answer input field 2308 is a field for inputting an answer. An answerer name input field 2309 is a field for inputting an answerer name. A reply button 2310 is a button for returning an answer to the agency.
Using this screen, the person in charge in the insurance company performs processing 2211 for creating an answer. When the person in charge in the insurance company clicks the reply button 2310, the insurance company remote consultation device 2102 transmits a response to the insurance company DB device 2103 (2212). In response to this, the insurance company DB apparatus 2103 performs processing 2213 for log recording. Logs to be recorded are the device name of the insurance company remote consultation device 2102, the name of the person in charge within the insurance company, the contents of the consultation, and the answer 2212, which are recorded with time.
Next, the insurance company remote consultation device 2102 transmits the name of the person in charge within the insurance company and the answer to the remote consultation program 2101 (2214).
The remote consultation program 2101 transmits the received person-in-charge name and answer in the insurance company to the DB device 107 (2215). In response to this, the DB device 107 performs processing 2216 for recording a log. The log to be recorded includes the program name of the remote consultation program 2101, the numbered ticket number, the name of the person in charge within the insurance company, and the answer.
Finally, the remote consultation program 2101 performs processing 2217 for displaying an answer.

(C) of the screen related to remote consultation in FIG. 23 is a diagram exemplifying an outline of the screen displayed in processing 2217 in which the remote consultation program 2101 displays an answer.
Reference numeral 2311 is an answer display screen, reference numeral 2312 is a consultation content display section, reference numeral 2313 is an answer display section, reference numeral 2314 is an answerer name display section, reference numeral 2315 is a button for returning to consultation, and reference numeral 2316 is an end button.
The answer display screen 2311 is a screen for displaying an answer from the insurance company, and includes a consultation content display unit 2312, an answer display unit 2313, an answerer name display unit 2314, a return to consultation button 2315, and an end button 2316. . The consultation content display unit 2312 is a portion for displaying the consultation content. The answer display unit 2313 is a part for displaying an answer. The respondent name display unit 2314 is a part for displaying the respondent name. A consultation return button 2315 is a button for returning to the consultation content input screen 2301. An end button 2316 is a button for ending the remote consultation program 2101.
If the person in charge in the insurance company clicks a return button 2315 for consultation, the remote consultation program 2101 returns to the consultation content input screen 2301 and accepts another consultation. If the person in charge in the insurance company clicks the end button 2316, the remote consultation program 2101 ends the process.

FIG. 24 is a diagram showing an example of the insurance company log DB.
In this figure, reference numeral 2401 denotes a device name field of the insurance company log DB, reference numeral 2402 denotes a time field of the insurance company log DB, and reference numeral 2403 denotes a log message field of the insurance company log DB.
Reference numerals 2404 and 2405 are examples of log records.
In the record 2404, a message is recorded in the remote consultation device within the insurance company at 10:48 at the time of XX agency XX Hanako consultation "Do you need to be notified even if you are injured in the hospital?"
In addition, in the record 2405, at the insurance company's remote consultation device, at 10:50, there will be a message “No need” for △ □ Taro ’s response to “X × agency ○ × Hanako consultation“ Do you need to be notified even if you are injured? ” What has been recorded remains.
As described above, according to the fourth embodiment, it is possible to leave a log of a portion that may cause a trouble without manpower.
Taking the log and letting the customer approve it can be expected to be less likely to cause trouble.

  The embodiments of the present invention have been described above. However, the present invention is not limited to the above-described embodiments. For example, the face-to-face explanation may be recorded or recorded, and the recording or recording may be left as a log. The voice exchanged during the face-to-face explanation may be converted into a sentence by voice recognition software and left as a log. Further, these logs may be compressed or encrypted.

  In addition, although each said Example demonstrated as an insurance agency system and insurance product sales support method of selling insurance products, the sales agent system and sales product explanation support method of this invention are careful at the time of solicitation and sales. It can be widely applied to the sale of products that require or are required to be explained. For example, the sale of financial products such as stocks and investment trusts under the Financial Instruments and Exchange Act that came into effect on September 30, 2007, jewelry, It can be applied to sales of a wide range of products that require careful explanation at the time of solicitation and sales, such as sales of paintings and art antiques, sales of new houses and home renovations, sales / repair / inspection of cars, etc. .

1 is a diagram illustrating an example of a system configuration of Embodiment 1. FIG. It is a figure which shows an example of the internal structure of a general PC. It is the figure which showed the outline of the initialization process flow at the time of system installation. It is the figure which showed the outline of the daily initialization process flow. It is a figure which shows the outline of the processing flow at the time of performing log recording. It is the figure which illustrated an example of log DB. It is the figure which showed the outline of the processing flow of the numbered ticket issuing process in a numbered ticket issuing apparatus. It is the figure which showed an example of the processing flow of a reception program. It is the figure which illustrated an example of numbered ticket DB. It is a figure which shows an example of the screen of a reception program. It is a figure which shows the outline of the processing flow of an insurance explanation assistance program. It is a figure which shows an example of the screen of an insurance explanation assistance program. It is a figure which shows the outline of the processing flow of an insurance manual printing program. It is the figure which illustrated an example of the insurance description. It is a figure which shows the outline of a log reference processing flow. It is a part added to Example 1 among the system block diagrams in Example 2 of this invention. FIG. 10 is a diagram illustrating an outline of a processing flow when log recording is performed in the second embodiment. FIG. 10 is a diagram illustrating an outline of a changed part of a system configuration in a third embodiment. It is a figure which shows the outline of the processing flow of the insurance description printing program in Example 3. FIG. It is the figure which showed the outline of the processing flow in an insurance manual verification apparatus. FIG. 10 is a diagram illustrating an outline of changes in a system configuration according to a fourth embodiment. It is the figure which showed the outline of the processing flow of a remote consultation. It is the figure which illustrated the outline of the screen in connection with a remote consultation. It is the figure which showed an example of insurance company log DB.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 Agent system 102 Numbered ticket issuing device 103 Window terminal device 104 Reception program 105 Insurance explanation support program 106 Insurance manual printing program 107 DB device 108 Log DB
109 Numbered Ticket DB
110 Numbered ticket number calling device 111 Printing device 112 Network in agency 113 Network 114 Network in insurance company 115 System in insurance company 116 Insurance manual input device 117 Log reference device 118 Contract DB device 119 Contract DB
201 CPU
202 Memory 203 Interface 204 Network Interface 205 Keyboard 206 Screen 207 Scanner 208 Printer 209 Hard Disk 210 Clock 601 Device Name Field 602 Time Field 603 Numbered Ticket Number Field 604 Log Message 901 Visit Time 902 Numbered Ticket Number 903 Call Time 904 Result 1001 Initial Screen 1002 Customer visit screen 1003 Queue information display section 1004 Customer call button 1005 Customer recall button 1006 Customer visit button 1007 Customer absence completion button 1008 Numbered ticket number display section 1009 Deposit service button 1010 Loan consultation button 1011 Insurance consultation button 1201 Insurance product list screen 1202 Insurance selection button 1203 Explanation screen 1
1204 Next screen button 1205 Question screen 1206 Button to select question 1207 Other question button 1208 Question end button 1209 Question answer screen 1210 Question content input box 1211 Answer input box 1212 Answer end button 1401 Example of insurance description 1402 Description history 1403 Signature field 1601 Time stamp giving program 1602 Time stamp authority 1801 Insurance manual verification device 2101 Remote consultation program 2102 Insurance company remote consultation device 2103 Insurance company DB device 2104 Insurance company log DB
2301 Consultation contents input screen 2302 Consultation contents input field 2303 Contact person name field 2304 Send button 2305 Answer input screen 2306 Consultation contents display section 2307 Consultant name display section 2308 Answer input field 2309 Answerer name input field 2310 Reply button 2311 Answer display Screen 2312 Consultation content display section 2313 Answer display section 2314 Respondent name display section 2315 Return to consultation button 2316 Exit button 2401 Device name field 2402 Time field 2403 Log message

Claims (9)

A system in a sales agent used when selling a product through a sales agent, including a window terminal means, a database management means for managing a database, and a printing means,
The window terminal means includes sales product description support means for supporting sales product explanation, and sales product description printing means for printing a sales product description from the printing means,
The sales merchandise explanation support means supports sales merchandise explanation using the counter terminal means by a counter person in charge, and records operation information indicating the fact of explanation of the sales merchandise in the database using the database management means. And
The sales product description printing means prints operation information indicating the fact of the description of the sales product recorded in the database on the sales product description.
A sales agent system characterized by that. In the sales agent system according to claim 1,
In addition to the operation information indicating the fact of the description of the sales product in the sales product description, the description content of the sales product corresponding to the operation is recorded in the database and printed on the sales product certificate. In-sales agent system. The in-sales agent system according to claim 1 or 2, wherein
The system in the sales agent further includes a numbered ticket issuing means for issuing a numbered ticket to a customer visiting the sales agent,
Numbered ticket number calling means for signaling a customer who has received a numbered ticket by reproducing and / or displaying the information printed on the numbered ticket surface issued by the voice,
Including
Information on the issuance of the numbered ticket and a signal to the customer who has received the numbered ticket is recorded in the database and printed on the sales merchandise certificate.
A sales agent system characterized by that. The in-sales agent system according to any one of claims 1 to 3,
The in-sales system further includes a time stamp giving means,
The in-sales system according to claim 1, wherein the time stamp assigning means assigns a time stamp to information recorded in the database managing means. The in-sales agent system according to any one of claims 1 to 4,
The sales merchandise manual printing means prints using a means capable of detecting falsification of the sales merchandise manual on which the explanation operation of the sales merchandise is printed,
A sales agent system characterized by that. A sales product explanation support method in a sales agent system for selling sales products,
A step of supporting the explanation of the sales product using the window terminal means by the window person in charge when the window person explains the sales product;
Recording a log of operation of the window terminal means in a database using database management means;
A sales product explanation support method comprising a step in which the window terminal means prints information reflecting the contents of the log on a sales product description in response to an instruction to print a sales product description from the contact person in charge. The sales product explanation support method according to claim 6,
Issuing a numbered ticket to those who wish to sell products;
A sales product explanation support method, comprising: a step of recording the log in a database management means when the numbered ticket is issued and called. The sales product explanation support method according to claim 6 or 7,
A sales product explanation support method, wherein the log is further given a time stamp. A sales product explanation support method according to any one of claims 6 to 8,
The sales product explanation support method, further comprising: printing the falsification detection information on the sales product description.

Images