JP2010238014A - System and program for supporting customer examination - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a customer examination support system and customer examination support program for information exchange between a sales company and a finance company which reduce the number of examination requests and examinations that will not finally lead to sales contracts. <P>SOLUTION: An outstanding debt reference subsystem 210 stores customer outstanding debt information 20 including customer ID, searchable information and outstanding debt information. A customer information list 21 including the customer ID and searchable information is created from the customer outstanding debt information 20 and is sent to a customer reference subsystem 120. The customer reference subsystem 120 searches the customer information list 21 on search key information in input customer information 51 to refer to corresponding customer ID. The outstanding debt reference subsystem 210 returns the outstanding debt information about the customer ID referred to. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a customer examination support system and a customer examination support program, and more particularly to an apparatus for transmitting and receiving information between a sales company and a finance company.

When buying and selling automobiles, there are cases where customers use credits at sales companies. At that time, the sales company sends the vehicle information and the customer information to the finance company, and the finance company performs a credit examination based on the information.
This credit examination may be performed using a system as shown in FIG. In the system shown in FIG. 13, a data linkage subsystem using a Web system is used as a means for transmitting information between a sales company and a finance company.

The sales subsystem of the sales company encrypts negotiation information such as vehicle information and customer information, and creates a linkage file. Next, the data linkage subsystem captures the linkage file, and adds customer attribute information such as office and annual income as supplementary information. The linked file is then sent to the finance company's customer review subsystem. The employees of the finance company make a review / estimate based on the contents of the collaborative file and answer the review results. The salesperson of the sales company browses the examination results answered by the finance company and determines the accuracy of the business negotiation with the customer.
An example of a customer examination support system having such a configuration is also disclosed in Patent Document 1.

  In general, information related to credit examination (credit information) includes information that is not preferably disclosed more than necessary. For example, the customer's product purchase history, information indicating the amount of the remaining bonds, and the like correspond to this. For this reason, finance companies do not provide credit information to sales companies uniformly for all customers, but only as a result of credit review.

JP 2001-266023 A

However, the conventional system has a problem that the number of examination requests and examinations that are not ultimately connected to the sales contract is large, and the work of the sales company and the finance company is inefficient.
When a finance company provides credit information to a sales company, it is provided only as a result of credit examination as described above. For this reason, in a conventional system, a sales company cannot obtain information such as a customer's residual bonds unless it conducts a screening request for all business negotiations. Therefore, even in business negotiations where the amount of residual bonds is actually large and clearly does not pass credit screening, the sales company must input supplementary information necessary for the screening request and make a screening request. Finance companies will also review and estimate all business negotiations. This has the problem that it takes extra time and costs, and the efficiency becomes poor.

  The present invention has been made to solve such problems, and provides a customer examination support system and a customer examination support program capable of suppressing the number of examination requests and examinations that are not ultimately linked to a sales contract. The purpose is to do.

  A customer examination support system according to the present invention is a customer examination support system comprising a customer inquiry subsystem and a residual bond inquiry subsystem, wherein the residual bond inquiry subsystem is configured to receive a residual bond inquiry subsystem for each of a plurality of customers. Stores the customer ID information for identifying the customer in the system, the search target information for searching for the customer, and the customer balance information related to the balance information of the customer and the balance reference sub The system transmits a customer information list including customer IDs and search target information of a plurality of customers to the customer inquiry subsystem, the customer inquiry subsystem obtains search key information, and the residual bond inquiry subsystem receives search key information. The remaining bond information associated with the search target information searched based on is sent to the customer inquiry subsystem.

The customer inquiry subsystem may transmit search key information to the remaining debt inquiry subsystem, and the remaining debt inquiry subsystem may retrieve the search target information based on the search key information.
The residual bond inquiry subsystem transmits a customer information list including customer IDs and search target information of a plurality of customers to the customer inquiry subsystem, and the customer inquiry subsystem searches the search target information of the customer information list based on the search key information. The customer ID associated with the relevant search target information is acquired and transmitted to the residual bond inquiry subsystem, and the residual bond inquiry subsystem receives the transmitted customer ID and associates it with the received customer ID. The remaining balance information may be sent to the customer inquiry subsystem.
The customer inquiry subsystem outputs information related to the customer ID for all the customer IDs associated with the search target information corresponding to the search key information, and the customer inquiry subsystem outputs at least one of the output customer IDs. The customer inquiry subsystem may receive only the selected customer ID when transmitting the customer ID to the balance inquiry subsystem.
The customer inquiry subsystem and the residual bond inquiry subsystem may be composed of different computers owned by different companies.

  The customer examination support program according to the present invention causes a computer to function as the above-described customer examination support system.

  According to the customer examination support system and the customer examination support program according to the present invention, the salesperson can obtain credit information about the customer who is the subject of the negotiation before making a request for examination to the finance company. Therefore, the accuracy associated with the sales contract can be determined before the examination request is made, and the work efficiency can be improved by suppressing the number of examination requests that are not finally tied to the sales contract. This also helps finance companies to reduce the number of reviews that are not ultimately linked to sales contracts, thereby improving work efficiency.

It is a figure showing composition of a customer examination support system concerning this invention. It is a figure which shows the example of a structure of the customer remainder bond information of FIG. It is a figure which shows the example of a structure of the customer information list of FIG. It is a figure which shows the example of a structure of the vehicle estimation data of FIG. It is a figure which shows the example of a structure of the inquiry cooperation file of FIG. It is a figure which shows the example of a structure of the cooperation file for examination requests | requirements of FIG. It is a figure which shows the example of a structure of the examination result cooperation file of FIG. It is a flowchart showing the flow of processing in a residual bond inquiry subsystem. It is a flowchart which shows the flow of the process which a sales subsystem performs with generation | occurrence | production of the negotiation with a customer. It is a flowchart which shows the flow of the process which a customer inquiry subsystem and a residual bond inquiry subsystem perform regarding transmission / reception of customer residual bond information. It is a figure explaining the flow of processing in Drawing 10 using an example of data. It is a flowchart which shows the flow of the process which a customer inquiry subsystem and a customer examination subsystem perform regarding the customer examination which a salesperson asks the person in charge of examination of a finance company. It is a figure which shows the structure of the system used for the conventional credit examination.

Embodiments of the present invention will be described below with reference to the accompanying drawings.
Embodiment 1 FIG.
FIG. 1 shows a configuration of a customer examination support system 10 according to the present invention. The customer examination support system 10 is a system that supports examination performed in relation to customer credit when selling using credit to a customer. The customer examination support system 10 includes a sales company terminal 100 and a finance company server 200. The sales company terminal 100 and the finance company server 200 are composed of different computers. The sales company terminal 100 is a computer owned and managed by a sales company that sells products to customers, and is operated by a sales person who is an employee of the sales company. In this embodiment, an automobile sales company is taken as an example, but this may be a sales company for other products as long as the sales are performed using credit.
The finance company server 200 is a computer owned and managed by a finance company having credit information related to the use of a customer's credit card, etc., and is operated by an examiner who is an employee of the finance company.

The sales company terminal 100 and the finance company server 200 have a configuration as a well-known computer.
The sales company terminal 100 and the finance company server 200 include an input device used by a user to input information. This input device is, for example, a mouse or a keyboard. Further, the sales company terminal 100 and the finance company server 200 include an output device that outputs information to the user. The output device is, for example, a display device such as a liquid crystal display or a printing device such as a printer.

  The sales company terminal 100 and the finance company server 200 include a calculation device that performs calculation. The arithmetic unit is, for example, a CPU (Central Processing Unit). Further, the sales company terminal 100 and the finance company server 200 include a memory and an HDD (hard disk drive) as storage means for storing information. Further, the sales company terminal 100 and the finance company server 200 include network interfaces for transmitting and receiving information to and from other computers and the like, and are connected to the communication network 300 via the respective network interfaces. The sales company terminal 100 and the finance company server 200 can communicate with each other via the communication network 300. The communication network 300 is a public communication line such as the Internet, but may be a dedicated communication line.

The storage means of the sales company terminal 100 and the finance company server 200 store part or all of the customer support program. The sales company terminal 100 and the finance company server 200 implement the function as the customer examination support system 10 by executing this customer support program.
The sales company terminal 100 includes a sales subsystem 110 and a customer inquiry subsystem 120. That is, the sales company terminal 100 functions as the sales subsystem 110 and the customer inquiry subsystem 120 by executing the corresponding portions of the customer support program. The sales subsystem 110 is a subsystem used when a salesperson sells a car to a customer. Further, the customer inquiry subsystem 120 is a subsystem for a salesperson to inquire about a customer who has visited the store using information held by the finance company.

The customer inquiry subsystem 120 functions as a data linkage system that links sales companies and finance companies. That is, the exchange of information is mediated between the sales company terminal 100 and the sales subsystem 110 of the sales company, and the finance company server 200, the residual bond inquiry subsystem 210 and the customer examination subsystem 220 of the finance company, and these Realize cooperation.
The customer inquiry subsystem 120 can be constructed by the sales company terminal 100 executing a Web browser program. That is, the customer inquiry subsystem 120 can be constructed by the sales company terminal 100 functioning as a so-called Web system. In this case, a web server is provided on the finance company side correspondingly. That is, the residual bond inquiry subsystem 210 and the customer examination subsystem 220 are connected to the communication network 300 via a Web server, and the customer inquiry subsystem 120 including the Web browser program is connected via the communication network 300 and the Web server. Communicate with the residual bond inquiry subsystem 210 and the customer review subsystem 220. The finance company server 200 may function as a Web server, and a computer different from the finance company server 200 may be prepared as a Web server.

  The finance company server 200 includes a residual bond inquiry subsystem 210 and a customer examination subsystem 220. That is, the finance company server 200 functions as a residual bond inquiry subsystem 210 and a customer examination subsystem 220 by executing the corresponding portions of the customer support program. The residual bond inquiry subsystem 210 is a subsystem that stores information related to the customer's residual bonds and transmits a part thereof to the outside periodically or upon request. The customer review subsystem 220 is a subsystem that is used in connection with the review by the reviewer.

  The sales subsystem 110, the customer inquiry subsystem 120, the residual bond inquiry subsystem 210, and the customer examination subsystem 220 store the following information in their respective storage means. Here, each subsystem may include a part of the storage unit of the sales company terminal 100 or the finance company server 200 as a storage unit dedicated to each subsystem, and the storage of the sales company terminal 100 or the finance company server 200. The means may be shared with other subsystems.

The remaining bond inquiry subsystem 210 stores the customer remaining bond information 20 and the customer information list 21 in the storage means.
FIG. 2 shows an example of the structure of the customer balance information 20. The customer balance information 20 is created in the finance company and includes a customer ID, which is information for identifying the customer in the balance bond inquiry subsystem 210 for each customer of the finance company. Further, the customer balance information 20 associates each customer ID with other information related to the customer. Information associated with the customer ID includes the customer's name, zip code, address, and date of birth. Further, the information associated with the customer ID includes the remaining bond information of the customer. The residual bond information includes a residual bond and a transaction history.

  The name, postal code, address, and date of birth are search target information for searching for customers. For example, as will be described later, the customer inquiry subsystem 120 searches for a customer using the name and date of birth of a specific customer as search key information. Alternatively, a salesperson, reviewer, other user, or other computer or system may search for a customer using the name, zip code, address, and date of birth as search key information. It is good also as a structure which can be performed.

  The remaining debt is a gradual evaluation regarding the amount of the remaining debt of the customer, and is represented by any one of, for example, five ranks A to E. In this example, rank A represents the highest level, i.e., the state where the remaining bonds are zero or the least amount of remaining bonds, and rank E represents the lowest stage, i.e., the state where there are the most remaining bonds. In other words, the customer whose residual debt is rank A has the highest credit, the customer whose residual debt is rank E has the lowest credit, and the customer whose residual debt is rank C is in the middle. The finance company will determine the appropriate stage for each customer, taking into account the amount of residual bonds and other information.

  The transaction history includes the date of last use and the total number of uses. The last use date represents the date when the customer last used the finance company, and the total use count represents the number of times the customer used the finance company in the past. The transaction history represents, for example, the transaction history of all products including automobiles without distinguishing the products, but this may represent the transaction history of only cars. The transaction histories of the products may be distinguished from each other, or the transaction histories of a plurality of products including automobiles may be expressed individually for each product.

  FIG. 3 shows an example of the configuration of the customer information list 21. The customer information list 21 is created by the residual bond inquiry subsystem 210 based on the customer residual bond information 20, for example. This customer information list 21 is referred to by the customer inquiry subsystem 120 to search for customers. The customer information list 21 associates search target information with each customer ID. The customer information list 21 is obtained by extracting the customer ID, name, postal code, address, and date of birth from the customer balance information 20. In other words, the customer information list 21 is obtained by removing the residual bond information from the customer residual bond information 20.

The sales subsystem 110 stores the vehicle estimate data 30 and the inquiry linkage file 40 in the storage means.
FIG. 4 shows an example of the configuration of the vehicle estimate data 30. The vehicle estimate data 30 includes vehicle information 50 and customer information 51. The vehicle information 50 is created by a sales company, and associates data representing the vehicle name, model, age, body price, consumption tax, and accessories for each vehicle to be sold. The vehicle information 50 is stored in advance in the storage means of the sales subsystem 110 according to a vehicle sales plan or the like. Alternatively, the vehicle information 50 may be created by a salesperson with the occurrence of a business negotiation with a customer and input to the sales subsystem 110 using the sales company terminal 100.

  The customer information 51 is created by a salesperson when a business negotiation with a customer occurs, and is input to the sales subsystem 110 using the sales company terminal 100. The customer information 51 associates information related to customers with each other. Information related to the customer includes the customer's name, zip code, address, and date of birth. These pieces of information are search key information for searching for customers, and are used for searching for specific customers in the customer information list 21 of FIG. For example, as will be described later, the customer inquiry subsystem 120 searches for a customer using the name and date of birth as search key information.

  FIG. 5 shows an example of the configuration of the inquiry cooperation file 40. The inquiry cooperation file 40 is created based on the vehicle estimation data 30 of FIG. 4 by encrypting the data included therein. The configuration is the same as that of the vehicle estimate data 30 except that the vehicle information 50 and the customer information 51 are encrypted.

The customer examination subsystem 220 stores the examination request cooperation file 41 and the examination result cooperation file 42 in its storage means.
FIG. 6 shows an example of the configuration of the examination request cooperation file 41. The examination request cooperation file 41 is obtained by adding customer attribute information 52 to the inquiry cooperation file 40 of FIG. These pieces of information are all encrypted in the same manner as the inquiry linkage file 40.
The customer attribute information 52 is created as additional information when the salesperson requests the finance company to examine the customer, and is input to the customer inquiry subsystem 120 using the sales company terminal 100. The customer attribute information 52 associates the work place, the annual income, the joint guarantor, and the transaction history for the customer represented by the customer information 51. The transaction history can be expressed in the same format as the transaction history of the customer balance information 20 shown in FIG. 2, for example.

FIG. 7 shows an example of the configuration of the examination result linkage file 42. The examination result linkage file 42 is obtained by adding examination result information 53 to the examination request linkage file 41 of FIG. These pieces of information are all encrypted in the same manner as the inquiry cooperation file 40 and the examination request cooperation file 41.
The examination result information 53 represents the result of examination for the customer, and is prepared by a person in charge of examination of the finance company and input to the customer examination subsystem 220 using the finance company server 200. is there. The examination result information 53 associates the examination result with the examination reply date for the customer represented by the customer information 51. The examination result indicates whether or not credit from the finance company is available when the vehicle represented by the vehicle information 50 is sold to the customer.

  The customer inquiry subsystem 120 stores the customer information list 21, the inquiry cooperation file 40, the examination request cooperation file 41, and the examination result cooperation file 42 in its storage means. Each of these has the same configuration as described above.

The operation of the customer examination support system 10 having the above configuration will be described below with reference to the flowcharts of FIGS.
FIG. 8 shows a processing flow in the residual bond inquiry subsystem 210. The finance company creates customer residual information 20 in advance, and this customer residual information 20 is stored in the residuals inquiry subsystem 210.

First, the residual bond inquiry subsystem 210 creates the customer information list 21 based on the customer residual bond information 20 (step S11). This is performed, for example, by extracting the customer ID, name, zip code, address, and date of birth from the customer balance information 20. Next, the residual bond inquiry subsystem 210 transmits the customer information list 21 to the sales company terminal 100 or to the customer inquiry subsystem 120 of the sales company terminal 100 via the communication network 300 (step). S12). In this step S12, the customer inquiry subsystem 120 receives the transmitted customer information list 21 and stores it in the storage means.
The residual bond inquiry subsystem 210 executes the process of FIG. 8 periodically, for example, every day at a predetermined time.

FIG. 9 shows a flow of processing executed by the sales subsystem 110 when a business negotiation with a customer occurs. This process is started in accordance with, for example, an instruction from a salesperson.
First, the sales subsystem 110 receives input of vehicle information 50 and customer information 51 (step S21). Here, the salesperson selects the appropriate vehicle information 50 prepared in advance for each vehicle, creates customer information 51 for the customer under negotiation, and inputs it to the sales subsystem 110.
Next, the sales subsystem 110 encrypts the input vehicle information 50 and customer information 51, and creates a reference linkage file 40 (step S22). Next, the sales subsystem 110 activates the customer inquiry subsystem 120 and delivers the examination request cooperation file 41 (step S23).

FIG. 10 shows a flow of processing executed by the customer inquiry subsystem 120 and the residual debt inquiry subsystem 210 regarding transmission / reception of information included in the customer residual debt information 20. FIG. 11 is a diagram for explaining the flow of processing in FIG. 10 using an example of data.
The process of FIG. 10 is started in response to the customer inquiry subsystem 120 being activated in step S23 of FIG.

First, the customer inquiry subsystem 120 acquires the inquiry cooperation file 40 delivered from the sales subsystem 110 (step S31). Here, as described above, the customer information 51 included in the inquiry cooperation file 40 includes the name and date of birth as search key information for searching for a customer.
Next, the customer inquiry subsystem 120 compares the acquired inquiry cooperation file 40 with the customer information list 21 periodically received from the remaining bond inquiry subsystem 210 (step S32). Here, since the customer information list 21 includes the name and date of birth as the search target information as described above, the customer information list 21 can be searched based on the name and date of birth.

Next, the customer inquiry subsystem 120 determines whether or not the corresponding customer exists as a result of the search (step S33). If there is no corresponding customer, the fact is displayed and the process is terminated. In the example of FIG. 11, as a result of searching for a customer with a condition of including both the name “○ yama × hus” and the date of birth “19XX year X month X day” included in the customer information 51 for ○ yama × husband. Therefore, it is determined that the customer represented by the customer ID “1002” in the customer information list 21 corresponds to this. In this example, the name and date of birth are used as the search key information. However, other information such as reading or postal code may be used as the search key information. Any information may be used as long as it contains one.
If there is a corresponding customer, the customer inquiry subsystem 120 acquires all the customer IDs of the customer and outputs information associated with each customer ID (step S34). This output is performed, for example, as a display on a liquid crystal display, and the customer ID, name, postal code, address, and date of birth are displayed.

  Next, the customer inquiry subsystem 120 accepts selection of a customer ID to be inquired to the remaining bond inquiry subsystem 210 from the displayed customer IDs (step S35). The customer inquiry subsystem 120 accepts this selection as an input specifying at least one of the displayed customer IDs. In other words, if there is information on two or more customers with the same name and date of birth, the salesperson will check each address and other information, and then select the customer to be referred appropriately. be able to. In the example of FIG. 11, it is assumed that only Mr. Oyama and Mr. Hu are displayed as selection candidates and are selected as customers to be inquired.

Next, the customer inquiry subsystem 120 transmits the customer ID selected to be inquired to the balance inquiry subsystem 210 (step S36), and the balance inquiry subsystem 210 receives the transmitted customer ID. (Step S41).
When receiving the customer ID, the residual bond inquiry subsystem 210 searches the customer residual bond information 20 using the customer ID, acquires the residual bond information associated with the customer ID (step S42), and acquires the acquired residual amount. The bond information is returned to the customer inquiry subsystem 120 (step S43). That is, the residual bond inquiry subsystem 210 transmits the residual bond information associated with the search target information searched based on the search key information to the customer inquiry subsystem 120. The customer inquiry subsystem 120 receives this residual bond information (step S37). In this step S37, the customer inquiry subsystem 120 further outputs the received residual bond information. In the example of FIG. 11, information including ○ yama × Msue's remaining bond information is acquired, returned, and output. This output is performed, for example, as a display on a liquid crystal display, and the customer ID, name, postal code, address, date of birth, remaining debt, and transaction history (last use date and total number of uses) are displayed. From this display, the salesperson can know, for example, that ○ Yayama × Msue's remaining bonds are in rank A, and based on this, can determine the accuracy of the negotiations with ○ Yayama × Ms. ( Step S38).

  Here, since the customer residual bond information 20 including the residual bond information is stored only in the residual bond inquiry subsystem 210, it cannot be browsed from the customer inquiry subsystem 120 until the residual bond information is received in step S37. . In other words, the finance company can disclose credit information that is not preferably disclosed more than necessary until it is inquired, and can disclose only credited information. In other words, in the example of FIG. 11, only the information of Mr. ○ Yama × Huso that was inquired is disclosed to the sales company, and the information of Mr. × River ○ Taro and Mr. Agawa □ is left undisclosed. Therefore, similarly to the conventional system, problems relating to security and privacy protection can be avoided.

  Unlike conventional systems, sales company sales staff can obtain and view the customer's residual bond information as necessary, so that the customers that are the subject of the negotiation are reviewed with the finance company. Credit information can be obtained before making a request. Therefore, it is possible to determine the accuracy associated with the sales contract before making an examination request, and to reduce the number of examination requests that are not ultimately tied to the sales contract, thereby making the work more efficient. This also helps finance companies to reduce the number of reviews that are not ultimately linked to sales contracts, thereby improving work efficiency.

  After step S38, the customer inquiry subsystem 120 accepts the input of the salesperson as to whether or not to inquire about other customer IDs among the customer IDs corresponding in step S34 (step S39). If an input for inquiring another customer ID is made, the process returns to step S35. In addition, the process ends when an input indicating that the inquiry of another customer ID is not performed is made.

  FIG. 12 shows a flow of processing executed by the customer inquiry subsystem 120 and the customer examination subsystem 220 regarding the customer examination requested by the salesperson to the person in charge of examination of the finance company. This process is started in accordance with, for example, an instruction from a salesperson. The salesperson can instruct the start of this process, for example, when it is determined that the probability of the negotiation is high as a result of the determination in step S38 of FIG. Note that the processing in FIG. 12 may be the same processing as the processing related to examination in the conventional system.

  First, the customer inquiry subsystem 120 accepts input of customer attribute information 52 (step S51). Here, the salesperson creates the customer attribute information 52 for the customer in the negotiation and inputs it to the customer inquiry subsystem 120. Next, the customer inquiry subsystem 120 adds the customer attribute information 52 to the inquiry cooperation file 40 and creates the examination request cooperation file 41 (step S52). Next, the customer inquiry subsystem 120 transmits the examination request cooperation file 41 to the customer examination subsystem 220 (step S53), and the customer examination subsystem 220 receives it (step S61).

Upon receiving the examination request cooperation file 41, the customer examination subsystem 220 requests examination by a person in charge of examination (step S62). This request is made by displaying that the examination request cooperation file 41 has been received and that examination / estimation is requested. Here, the person in charge of examination performs examination and estimation based on this request, creates examination result information 53 representing the result, and inputs it to the customer examination subsystem 220. The customer examination subsystem 220 adds examination result information 53 to the examination request cooperation file 41 and creates an examination result cooperation file 42 (step S63).
Next, the customer examination subsystem 220 transmits the examination result linkage file 42 to the customer inquiry subsystem 120 (step S64), and the customer inquiry subsystem 120 receives it (step S54). Next, the customer inquiry subsystem 120 displays the received examination result linkage file 42 (step S55). The salesperson can view the examination result information 53 included in the displayed examination result cooperation file 42 and determine the accuracy of the negotiation based on the examination result of the finance company.

  In the first embodiment described above, the customer inquiry subsystem 120 accepts selection of a customer ID to be inquired after displaying all the customers corresponding to the search key information in steps S34 to S35 of FIG. As a modification, such a selection may not be performed. For example, the customer inquiry subsystem 120 may transmit all the customer IDs of the customers corresponding to the search key information to the residual bond inquiry subsystem 210 as a result of the collation in step S32. In this way, the operation by the salesperson can be omitted, and the work can be made more efficient.

Embodiment 2. FIG.
In the first embodiment, the residual bond inquiry subsystem 210 periodically transmits the customer information list 21 to the customer inquiry subsystem 120, and the customer inquiry subsystem 120 stores the customer information list 21 for all customers. The second embodiment is configured such that the customer inquiry subsystem 120 does not have the customer information list 21 in the first embodiment. Hereinafter, differences from the first embodiment will be described.

The residual bond inquiry subsystem 210 creates the customer information list 21 (corresponding to step S11 in FIG. 8), but does not transmit it to the customer inquiry subsystem 120. That is, the process corresponding to step S12 in FIG. 8 is not executed.
When the customer inquiry subsystem 120 obtains the inquiry cooperation file 40 (corresponding to step S31 in FIG. 10), it transmits it to the residual bond inquiry subsystem 210 as it is. The residual bond inquiry subsystem 210 receives this, and collates with the customer information list 21 (corresponding to steps S32 and S33 in FIG. 10). If there is a corresponding customer as a result of the verification, the residual bond inquiry subsystem 210 acquires all the customer IDs of the customer and transmits information associated with each customer ID to the customer inquiry subsystem 120. The customer inquiry subsystem 120 outputs this (corresponding to step S34 in FIG. 10). The subsequent processing is the same as in the first embodiment.

10 customer examination support system, 20 customer balance information, 21 customer information list,
30 vehicle estimate data, 100 sales company terminal (computer), 110 sales subsystem, 120 customer inquiry subsystem, 200 finance company server (computer), 210 residual bond inquiry subsystem.

Claims (6)

A customer examination support system comprising a customer inquiry subsystem and a residual bond inquiry subsystem,
The residual bond inquiry subsystem is configured for each of a plurality of customers.
A customer ID identifying the customer in the residual bond inquiry subsystem;
Search target information different from the customer ID for searching for the customer;
Storing customer residual information relating to the residual information on the customer's residual debt,
The customer inquiry subsystem obtains search key information,
The said residual bond inquiry subsystem transmits the said residual bond information linked | related with the said search object information searched based on the said search key information to the said customer inquiry subsystem. The customer inquiry subsystem sends search key information to the residual bond inquiry subsystem;
The customer examination support system according to claim 1, wherein the residual bond inquiry subsystem searches the search target information based on the search key information. The residual bond inquiry subsystem transmits a customer information list including the customer IDs of the plurality of customers and the search target information to the customer inquiry subsystem,
The customer inquiry subsystem searches the search target information in the customer information list based on the search key information, acquires the customer ID associated with the corresponding search target information, and acquires the remaining bond reference subsystem. To
2. The customer examination support system according to claim 1, wherein the remaining bond inquiry subsystem receives the transmitted customer ID, and transmits the remaining bond information associated with the received customer ID to the customer inquiry subsystem. . The customer inquiry subsystem outputs information related to the customer ID for all of the customer IDs associated with the search target information corresponding to the search key information,
The customer inquiry subsystem receives an input for selecting at least one of the output customer IDs;
4. The customer examination support system according to claim 3, wherein the customer inquiry subsystem transmits only the selected customer ID when transmitting the customer ID to the remaining bond inquiry subsystem.   The customer examination support system according to any one of claims 1 to 4, wherein the customer inquiry subsystem and the residual bond inquiry subsystem are configured by different computers owned by different companies.   A customer examination support program for causing a computer to function as the customer examination support system according to any one of claims 1 to 5.

Images