Customer information management device, customer information management method, and customer information management program

Abstract

To reduce efforts and input errors of sales representatives to manage customer information and to conduct sales activities with appropriate customer information.SOLUTION: A customer information management device, when an operator designates project identification information and registration date on an integration processing screen, extracts customers from property customer data in a storage unit using the designated project identification information and registration date as keys, and displays the same in a list of data to be integrated. When displaying the list, the presence or absence of candidate customers in the property customer data associated with prescribed matching conditions is displayed, customers selected by the operator in the list of data to be integrated and customers of the property customer data associated with the prescribed matching conditions are displayed in an integration candidate list, and primary and secondary property customer data are integrated in accordance with prescribed integration rules when the operator selects the primary and secondary at the integration candidate list.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a customer information management device, a customer information management method, and a customer information management program. [Background technology]

[0002] For example, in the real estate industry, when a customer considers purchasing real estate, the customer obtains information about the property through various media such as the real estate company's own website, external websites, model rooms, etc., and each property salesperson approaches the customer based on the customer information obtained above. Conventionally, there is a system for managing customers, for example, Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2004-206253 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above-mentioned Patent Document 1 does not state anything about mechanically integrating customer information, deleting duplicate data of customer information for the same household, and supplementing information by setting predetermined rules for each item, thereby reducing the effort and input errors required by sales representatives to manage customer information and conducting sales activities using appropriate customer information.

[0005] The present invention has been made in consideration of the above, and aims to provide a customer information management device, a customer information management method, and a customer information management program that can reduce the effort and input errors required by sales representatives in managing customer information, and support sales activities using appropriate customer information. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention is characterized in that the control unit comprises a customer registration means for registering property customer data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date in a memory unit, and when project identification information and registration date are specified by an operator on an integration processing screen, an integration means for extracting customers from the property customer data in the memory unit using the specified project identification information and registration date as keys and displaying them in a list of data to be integrated, displaying the presence or absence of candidate customers in the property customer data linked by specified matching conditions, displaying the customers selected by the operator in the list of data to be integrated and the customers in the property customer data linked by the specified matching conditions in an integration candidate list, and when a main and secondary are selected by the operator in the integration candidate list, integrating the main and secondary property customer data in accordance with specified integration rules.

[0007] According to another aspect of the present invention, the predetermined matching conditions may include, for example, a kana name match, an email address match, a telephone number match, an address match, or a mobile phone number match.

[0008] In addition, according to one embodiment of the present invention, the specified integration rule may include a rule that, for items in the first category that include project identification information, main information is adopted and the items in the first category remain as main property customer data.

[0009] In addition, according to one embodiment of the present invention, the specified integration rule may include a rule that, for a second category item including an address, when the main property customer data is NULL or blank, the secondary property customer data is adopted and added to the second category item of the main property customer data.

[0010] In addition, according to one embodiment of the present invention, the specified integration rule may include a rule that, for items in the third category including telephone numbers, the information of the primary property customer data is adopted in ascending order, and then as much information of the secondary property customer data as will fit into the primary property customer data.

[0011] In addition, according to one embodiment of the present invention, the specified integration rule may include a rule that, for items in the fourth category including the date of visit, all values ​​of the primary and secondary property customer data are sorted in ascending order, and the sorted values ​​are updated to the extent that the corresponding item of the primary property customer data is filled.

[0012] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a customer information management method executed by an information processing device equipped with a control unit, comprising: a customer registration process executed by the control unit for registering property customer data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date in a memory unit; and an integration process for, when project identification information and registration date are specified by an operator on an integration processing screen, extracting customers from the property customer data in the memory unit using the specified project identification information and registration date as keys and displaying them in a list of data to be integrated, displaying whether or not there are any candidate customers in the property customer data linked by specified matching conditions, displaying the customers selected by the operator in the list of data to be integrated and the customers in the property customer data linked by the specified matching conditions in an integration candidate list, and, when main and secondary are selected by the operator in the integration candidate list, integrating the main and secondary property customer data in accordance with specified integration rules.

[0013] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention is a customer information management program to be executed by an information processing device having a control unit and a memory unit, the control unit comprising: a customer registration process for registering property customer data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date in the memory unit; and, when project identification information and registration date are specified by an operator on an integration processing screen, extracting customers from the property customer data in the memory unit using the specified project identification information and registration date as keys and displaying them in a list of data to be integrated, displaying whether or not there are any candidate customers in the property customer data linked by specified matching conditions, displaying the customers selected by the operator in the list of data to be integrated and the customers in the property customer data linked by the specified matching conditions in an integration candidate list, and, when a primary and secondary are selected by the operator in the integration candidate list, integrating the primary and secondary property customer data in accordance with specified integration rules. Effect of the Invention

[0014] According to the present invention, it is possible to reduce the effort required for sales representatives to manage customer information and input errors, and to support sales activities using appropriate customer information. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram showing an example of a configuration of a customer information management device according to the present embodiment. [Diagram 2] FIG. 2 is a diagram for explaining an example of the overall processing of the customer information management device in this embodiment. [Diagram 3] FIG. 3 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 4] FIG. 4 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Diagram 5]FIG. 5 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 9A] FIG. 9A is a diagram for explaining a specific example of the process of the customer information management device in the present embodiment. [Figure 9B] FIG. 9B is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. [Figure 14] FIG. 14 is a diagram for explaining a specific example of the process of the customer information management device in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, an embodiment of a customer information management device, a customer information management method, and a customer information management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiment.

[0017] [1. Overview] For example, in the real estate industry, when a customer is considering purchasing real estate, they obtain information about the property through various media, such as the real estate company's own website, external sites, model rooms, etc., and each property salesperson uses the information they have obtained to approach the customer.

[0018] However, for example, customers obtain information from various media, and in the case of a married couple, for example, the wife may visit the store as the clerk, so it is often not possible to consolidate and manage information for the same household.

[0019] In order for salespeople to approach customers appropriately, it is important to consolidate and manage customer information correctly, and leaking information can lead to complaints. For each salesperson to consolidate customer information at their own discretion, a high level of accuracy is required, which can lead to mistakes and a lot of work, which is an issue.

[0020] Therefore, in this embodiment, the customer information is mechanically integrated, duplicate data of customer information of the same household is deleted, and information is complemented by setting predetermined rules for each item. To reduce the labor and input errors of a salesperson in managing customer information and to enable sales activities to be carried out using appropriate customer information.

[0021] The customer information management device of this embodiment is applicable to a wide range of industries such as the real estate sales industry.

[0022] [2. Configuration] The configuration of customer information management device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of customer information management device 100 according to this embodiment.

[0023] The customer information management device 100 is a commercially available desktop personal computer. The customer information management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0024] 1, the customer information management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the customer information management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0025] The communication interface unit 104 communicatively connects the customer information management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the customer information management device 100 and the bank website 400 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0026] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. In addition, the operation by the user using the input device 112 to display on the screen of the output device (monitor) 114 may be referred to as a "user operation via a UI."

[0027] The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106. The storage unit 106 also stores property customer data, and the like.

[0028] The property customer data may include items shown in Figures 9A and 9B, and may include, for example, project identification information (PJ code and / or project name), SEQ, customer number, registration date, customer name (written in kanji), customer's kana name, address, telephone number, mobile phone number, email address, date of visit, desired area, name of the nearest train line, nearest station, unavailable FLG, NC flag, etc.

[0029] The control unit 102 is a CPU or the like that comprehensively controls the customer information management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, and the like, and executes various information processing based on these stored programs.

[0030] The control unit 102 is configured to be able to access property customer data, etc., stored in the storage unit 106. Note that the property customer data, etc., may be provided in another location (e.g., the server 200) as long as the control unit 102 is able to access it.

[0031] The control unit 102 conceptually includes a customer registration unit 102a, an integration unit 102b, and a screen display control unit 102c.

[0032] The customer registration unit 102a inputs property customer data in response to, for example, an operator's operation on a customer registration screen (not shown) displayed on a monitor, and registers the data in the storage unit 106.

[0033] For example, when the operator specifies project identification information and registration date on an integration processing screen displayed on the monitor, the integration unit 102b extracts customers from the property customer data in the memory unit 106 using the specified project identification information and registration date as keys, and displays them in a list of data to be integrated, displaying whether there are any candidate customers in the property customer data that are linked by specified matching conditions, and displays in a list of integration candidates the customers selected by the operator in the list of data to be integrated and the customers in the property customer data that are linked by specified matching conditions, and when the operator selects a primary and secondary data in the list of integration candidates, integrates the primary and secondary property customer data in accordance with specified rules.

[0034] The predetermined matching conditions may include, for example, a kana name match, an email address match, a telephone number match, an address match, or a mobile phone number match.

[0035] The specified integration rule may include a rule that for items in the first category (items with function number "01" in Figure 9A) that include project identification information, the main information is adopted and the items in the first category remain as the main property customer data.

[0036] The specified integration rule may include a rule for a second category item including an address (item with function No. "02" in Figure 9A) that adopts secondary property customer data and adds it to the second category item of the primary property customer data when the primary property customer data is NULL or blank.

[0037] The specified integration rule may include a rule that, for items in the third category including telephone numbers (items with function number "08" in Figure 9A), the information of the main property customer data is adopted in ascending order, and then as much information from the secondary property customer data as will fit into the main property customer data.

[0038] The specified integration rule may include a rule that, for items in the fourth category (item with function No. "07" in Figure 9B) that includes the date of visit, all values ​​of the main and secondary property customer data are sorted in ascending order, and the sorted values ​​are updated to the extent that the corresponding item of the main property customer data is filled.

[0039] The specified integration rule may include a rule that, for items in the fifth category including the NC category (items with function No. "03'" in Figure 9B), the target categories or flags of the main and secondary property customer data are compared, and the larger attribute data is adopted as the main property customer data.

[0040] The screen display control unit 102c controls the display of various screens (for example, a customer registration screen, an integrated processing screen, etc.) displayed on the monitor 114 and the reception of inputs.

[0041] [3. Specific Examples] A specific example of the processing of control unit 102 of customer information management device 100 in this embodiment will be described with reference to Fig. 1 to Fig. 14. Fig. 2 is a diagram for explaining an example of the overall processing of control unit 102 of customer information management device 100 in this embodiment.

[0042] An example of the overall processing of control unit 102 of customer information management device 100 in this embodiment will be described with reference to FIG.

[0043] (Overall processing) 2, the customer registration unit 102a executes a customer registration process (step S1). Specifically, in the customer registration process, the customer registration unit 102a inputs property customer data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date in response to, for example, an operator's operation on a customer registration screen (not shown) displayed on a monitor, and registers the data in the storage unit 106.

[0044] The integration unit 102b executes a customer integration process (step S2). Specifically, in the customer integration process, for example, when the operator specifies project identification information and the registration date on the integration process screen displayed on the monitor, the integration unit 102b extracts customers from the property customer data in the storage unit 106 using the specified project identification information and the registration date as keys, displays them in an integration target data list, and displays the presence or absence of a candidate for a customer in the property customer data linked by a predetermined matching condition, displays the customer selected by the operator in the integration target data list and the customer in the property customer data linked by a predetermined matching condition in an integration candidate list, and when the operator selects a main and a secondary in the integration candidate list, integrates the main and secondary property customer data according to a predetermined rule.

[0045] (3-2. Sample data) 3 to 17 are diagrams showing sample data for explaining a specific example of the processing by control unit 102 of customer information management device 100 in the present embodiment. A specific example of the processing by control unit 102 of customer information management device 100 in the present embodiment will be explained with reference to Figs. 3 to 17.

[0046] Figure 3 is a diagram showing the processing image of customer integration. In the following, we will explain the case where Taro Obic (husband) and Hanako Obic (wife) visit property A separately on 5 / 1 and 6 / 1, and then create property customer data for each of them, and then integrate the customer property data of both.

[0047] (S1: Customer registration process) A specific example of the customer registration process will be described with reference to Fig. 4. The customer registration unit 102a inputs property customer data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date in response to, for example, an operator's operation on a customer registration screen (not shown) displayed on a monitor, and registers the data in the storage unit 106.

[0048] Figure 4 shows an example of customer property data. Figure 4(A) shows an example of customer property data updated when Obic Taro visited property A (5 / 1), and in the first line, PJ code "A001", project name "Property A", SEQ "0001", customer number "K001", registration date "5 / 1", customer name "Obic Taro", kana name "Obic Taro", address "Tokyo...", TEL1 "090-XXXX-XXXX", visit date 1 "5 / 1", desired area 1 "Koto-ku",... are registered.

[0049] Figure 4 (B) shows an example of customer property data updated when Obic Hanako visited property A (6 / 1). On the second line, the following are registered: PJ code "A001", project name "Property A", SEQ "0002", customer number "K002", registration date "6 / 1", customer name "Obic Hanako", kana name "Obic Hanako", address "Tokyo...", TEL1 "080-XXXX-XXXX", visit date 1 "6 / 1", desired area 1 "Suginami-ku", ...

[0050] (S2: Customer integration processing) A specific example of the customer integration process will be described with reference to Figures 5 to 14. For example, when the operator specifies project identification information and the registration date on the integration process screen displayed on the monitor, the integration unit 102b extracts property customer data from the storage unit 106 using the specified project identification information and the registration date as keys, displays the presence or absence of candidate customers of the property customer data linked by a predetermined matching condition, displays the customer selected by the operator in the integration target data list and the customer of the property customer data linked by a predetermined matching condition in the integration candidate list, and when the operator selects a main and a secondary in the integration candidate list, integrates the main and secondary property customer data according to a predetermined integration rule.

[0051] Fig. 5 is a diagram showing a display example of the integration processing screen 500. Fig. 6 is a diagram showing a flow of the customer integration processing. Fig. 7 is a diagram showing an image of the property-customer data after integration.

[0052] As shown in Figure 5, the integration processing screen 500 displays fields for entering the PJ code and registration date, an area for displaying a list of data to be integrated, an area for displaying a list of integration candidates, a display button 501 for displaying the list of data to be integrated, a customer button 502 for inquiring about property customer data, and a registration button 503 for integrating property customer data.

[0053] The integration target data list displays a selection box for selecting the data to be integrated, the customer name, address, whether there is an integration candidate (yes or no), etc. The integration candidate list displays a selection box for selecting "primary" and "secondary" for integration, the customer name, address, a customer button 502 for inquiring about the property customer data of the customer, etc. When the register button 503 is pressed, the property customer data of the primary and secondary customers selected in the integration candidate list is integrated according to a predetermined integration rule.

[0054] The flow of the customer integration process will be described with reference to FIG. 6. When the operator inputs the project code and customer registration date of the person in charge and presses the display button 501 (step S11). The integration unit 102b extracts customers of the property customer data from the storage unit 106 using the project code and customer registration date as keys, and displays them in the list of data to be integrated (step S12). At this time, the integration unit 102b displays "Yes" in the "Candidate" item of the list of data to be integrated if there is a customer of property customer data that is linked by a predetermined matching condition. The predetermined matching condition is, for example, a match of kana names, a match of email addresses, a match of telephone numbers (landline), a match of addresses, or a match of mobile phone numbers.

[0055] When the operator selects (checks) the data to be integrated in the list of data to be integrated, the integration unit 102b displays the selected customers to be integrated and the customers of the property customer data that match the matching conditions as candidates in the list of integration candidates (step S13).

[0056] When the operator presses the customer button 502 for the customer he / she wishes to inquire about in the list of integration candidates, the integration unit 102b launches a pop-up customer input screen to display the registered property customer data for that customer, and the operator can check the property customer data of the integration candidate (step S14).

[0057] When the operator selects a "main" customer and a "secondary" customer in the list of integration candidates and presses the registration button 503, the integration unit 102b integrates the selected main and secondary property customer data in accordance with predetermined integration rules (step S15).

[0058] In the example of integration processing screen 500 shown in Fig. 5, a project code "0001" and a registration date "6 / 1" are entered and display button 501 is pressed (step S11 in Fig. 6), and using the project code "0001" and the registration date "6 / 1" as keys, Obic Hanako, customer A, customer B, and customer C are extracted as customers of the property customer data from memory unit 106 and displayed in the list of data to be integrated (step S12 in Fig. 6). In this example, Obic Hanako has an address that matches Obic Taro (a hit on the matching condition), and "Yes" is displayed in the "Candidate" field.

[0059] "Obic Hanako" is selected as the data to be integrated in the list of data to be integrated, and is added to the list of integration candidates. "Obic Hanako", selected as the integration target, and "Obic Taro", who was found based on the matching conditions, are displayed (step S13 in FIG. 6). The display order can be, for example, by customer number. By pressing the target customer button 502, the property customer data for "Obic Taro" and "Obic Hanako" can be confirmed.

[0060] In the list of integration candidates, when "OBIC Taro" is selected as the "main" customer and "OBIC Hanako" is selected as the "secondary" customer and the register button 503 is pressed, the property customer data with "OBIC Taro" as the "main" customer and "OBIC Hanako" as the "secondary" customer is integrated according to the specified integration rules.

[0061] FIG. 7 is a diagram showing an example of integration of property customer data with "OBIC Taro" as the "main" and "OBIC Hanako" as the "secondary". As shown in FIG. 7, the information of the "secondary" is integrated into the "main", and the unavailable FLG for the "secondary" is updated to "1". When the unavailable FLG is "1", the property registration data of the customer is unusable, and sales activities are conducted, for example, for the "main" customer. In this example, the telephone number "080-XXX-XXXX", the visit date "6 / 1", and the desired area "Suginami-ku" of "OBIC Hanako" are integrated into "OBIC Taro". The link between the main and secondary property customer data is managed by storing the main customer number in the secondary property customer data. Specifically, when integrating the secondary property customer data, (1) the main customer number is updated (set), and (2) the unavailable FLG is set to "1 (ON)".

[0062] Next, the rules for integration will be described with reference to Figures 8 to 14. Figure 8 is a diagram for explaining the rules for integration, showing the rules for integration for each function number. Figures 9A and 9B show a list of property customer data items and their function numbers. Figures 10 to 14 show an example of integration of property customer data for each function number.

[0063] The property customer data to be integrated is updated by using the integration rules in Figure 8 for the primary and secondary customer data selected on the screen. Figure 8 shows Table 1 of the integration rules when updating items, and shows the function number and an explanation of the integration rule, as follows:

[0064] In the function number "01: Main customer recruitment", regardless of whether the data is for the main customer or sub-customer, the data is always integrated with the data for the main customer. In other words, the items in the function number "01" will remain as the data for the main customer.

[0065] In function number "02: Sub-customer Merge", if the data of the main customer is NULL or blank, the data of the sub-customer is adopted. Otherwise, the data of the main customer is adopted. In other words, if all the data of the main customer is NULL or blank and even one of the data of the sub-customer is not NULL or blank, the data of the sub-customer is adopted.

[0066] Function No. "03': Maximum division value adopted" compares the target division or flag and adopts the larger attribute data. NULL value is regarded as 0.

[0067] In function number "07: Information integration (1)", the information of the main customer and secondary customer is integrated, the values ​​of the main customer and secondary customer are all arranged in ascending order, and the main customer field is updated until it is filled.

[0068] In function number "08: Information integration (2)", the information of the primary customers is adopted in ascending order, and then the data of the secondary customers is added as much as possible.

[0069] 9A and 9B show Table 2 of the link between the property customer data item list and the update rules, and show the correspondence between the property customer data items and the above-mentioned function numbers. The property customer data items are integrated according to the integration rules of function numbers in FIG. 8. The data in FIG. 9A and FIG. 9B can be directly coded and implemented in the integration unit 102b. It may also be made into a master. In FIG. 9A, the item with function number "01" corresponds to the "first division item", the item with function number "02" corresponds to the "second division item", and the item with function number "08" corresponds to the "third division item". In FIG. 9B, the item with function number "03'" corresponds to the "fifth division item", and the item with function number "07" corresponds to the "fourth division item".

[0070] Next, a specific example of integration of property customer data for each function number will be described with reference to FIGS.

[0071] (Function No. "01: Main Customer Recruitment") With reference to Figure 10, the case of 01: Main customer adoption will be explained. Here, the PJ code and SEQ (see Figure 9A) with function number "01" will be explained as an example. Figure 10(A) shows an example of property customer data before updating, and Figure 10(B) shows an example of property customer data after updating.

[0072] As shown in Figure 10(A) and (B), the PJ code and SEQ are updated by adopting the main information. In other words, the main information remains the same, and the PJ code "A001" and SEQ "0001" of the main property customer data remain unchanged.

[0073] (Function No. "02: Sub-customer Merge") With reference to Figure 11, the case of 02: secondary customer merge will be explained. Here, the explanation will be given by taking as an example the name of the nearest train line and the name of the nearest station, which are set to function number "02" (although not shown in Figure 9A, the name of the nearest train line and the name of the nearest station are set to "02"). Figure 11(A) shows an example of property customer data before updating, and Figure 11(B) shows an example of property customer data after updating.

[0074] When the primary field is NULL or blank, the secondary information is used to update. As shown in Figure 11(A), the primary field contains the blank closest station name, and the secondary field contains the closest station name "Kyobashi", so the secondary closest station name "Kyobashi" is set as the primary field, as shown in Figure 11(B).

[0075] (Function No. "08: Information Integration (2)") The case of 08: information integration (2) will be described with reference to Figure 12. Here, a telephone number (see Figure 9A) with function number "08" will be used as an example for explanation. Figure 12(A) shows an example of property customer data before updating, and Figure 12(B) shows an example of property customer data after updating.

[0076] The information for the main customer is taken in ascending order, and then as much data for secondary customers is added as it will fit. Adding as much as it can means that the system breaks (ends updating) when the last item in the field is filled. For example, in the case of phone numbers, there are three items (phone number 1 to phone number 3), and the system breaks when the last phone number 3 is filled.

[0077] As shown in Figures 12(A) and (B), the secondary telephone number 1, "080-XXXX-XX2", is added to the primary telephone number 2.

[0078] (Function No. "03': Maximum division value adopted") With reference to Figure 13, the case of 03': adopting the maximum category value will be explained. Here, the NC (no count) category (see Figure 9B) with function number "03'" will be explained as an example. The NC category is used when sorting data, for example, to exclude items with NC checked. Figure 13(A) shows an example of property customer data before updating, and Figure 13(B) shows an example of property customer data after updating.

[0079] The target categories or flags are compared and the larger attribute data is adopted. NULL values ​​are considered to be 0. As shown in Figure 13(A), the primary NC flag is "0" and the secondary NC flag is "1", so as shown in Figure 13(B), the primary NC flag is updated to the secondary NC flag "1".

[0080] (Function No. "07: Information Integration (1)") The case of 07: Information integration (1) will be explained with reference to Figure 14. Here, the visit date (see Figure 9B) with function number "07" will be explained as an example. Figure 14(A) shows an example of property customer data before updating, and Figure 14(B) shows an example of property customer data after updating.

[0081] The primary and secondary information are integrated, and all primary and secondary values ​​are sorted in ascending order, and updated until the primary item is filled. The visit dates are 1 to 10, so sort them in ascending order and cut off the 11th and subsequent dates. In Figure 14(A), if the secondary visit dates are sorted in ascending order, they become 5 / 1 (primary), 5 / 10 (primary, secondary), 5 / 20 (secondary), and 6 / 1 (secondary). As shown in Figure 14(B), the primary visit dates are updated in chronological order to 5 / 1, 5 / 10, 5 / 20, and 6 / 1 (secondary).

[0082] As described above, according to this embodiment, there is provided a customer registration means for registering property customer data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date in a storage unit, and an integration means for, when project identification information and registration date are specified by an operator on an integration processing screen, extracting customers from the property customer data in the storage unit 106a using the specified project identification information and registration date as keys and displaying them in an integration target data list, displaying whether there are any candidate customers in the property customer data linked by a specified matching condition, displaying the customers selected by the operator in the integration target data list and the customers in the property customer data linked by a specified matching condition in an integration candidate list, and, when a primary and secondary are selected by the operator in the integration candidate list, integrating the primary and secondary property customer data in accordance with a specified integration rule, thereby making it possible to reduce the effort and input errors required for sales representatives to manage customer information and to support sales activities using appropriate customer information.

[0083] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to goals 8 and 9 of the SDGs.

[0084] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0085] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0086] 5. Other embodiments The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0087] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0088] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

[0089] Moreover, with regard to the customer information management device 100, each of the components shown in the drawings is merely a functional concept, and does not necessarily have to be physically configured as shown in the drawings.

[0090] For example, the processing functions of the customer information management device 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the customer information management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form a control unit.

[0091] In addition, this computer program may be stored in an application program server connected to the customer information management device 100 via any network, and it is also possible to download all or part of it as necessary.

[0092] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0093] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0094] The various databases etc. stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.

[0095] The customer information management device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device to which any peripheral device is connected. The customer information management device 100 may be realized by installing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

[0096] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Explanation of symbols]

[0097] 100 Customer information management device 102 Control section 102a Customer Registration Department 102b Integration Department 102c Screen display control unit 104 Communication interface section 106 Storage section 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network 500 Integrated Processing Screen 501 Display button 502 Customer Button 503 Registration button

Claims

1. A customer information management device including a control unit, The control unit is a customer registration means for registering property customer data including project identification information, a customer number, a registration date, a customer name, a kana name, an address, a telephone number, a mobile phone number, an email address, and a visit date in a storage unit; an integration means for, when an operator specifies project identification information and a registration date on an integration processing screen, extracting customers from the property customer data in the storage unit using the specified project identification information and registration date as keys and displaying them in a list of data to be integrated, displaying whether there are any candidate customers in the property customer data linked by a specified matching condition, displaying the customers selected by the operator in the list of data to be integrated and the customers in the property customer data linked by the specified matching condition in a list of integration candidates, and integrating the main and secondary property customer data in accordance with a specified integration rule when the operator selects a main and secondary property customer data in the list of integration candidates; A customer information management device comprising:

2. 2. The customer information management device according to claim 1, wherein the predetermined matching conditions include a match of a kana name, a match of an email address, a match of a telephone number, a match of an address, or a match of a mobile phone number.

3. The customer information management device described in claim 1 or 2, characterized in that the specified integration rule includes a rule that for items in the first category including project identification information, main information is adopted and the items in the first category remain as main property customer data.

4. The customer information management device described in claim 1 or 2, characterized in that the specified integration rule includes a rule that, for items in the second category including addresses, when the main property customer data is NULL or blank, the secondary property customer data is adopted and added to the second category item of the main property customer data.

5. The customer information management device according to claim 1 or 2, characterized in that the specified integration rule includes a rule that, for items in the third category including telephone numbers, the information of the main property customer data is adopted in ascending order, and then the information of the secondary property customer data is added to the main property customer data as much as it will fit.

6. The customer information management device of claim 1 or 2, characterized in that the specified integration rule includes a rule that, for items in the fourth category including the date of visit, all values ​​of the main and secondary property customer data are sorted in ascending order, and the sorted values ​​are updated to the extent that the corresponding item of the main property customer data is filled.

7. A customer information management method executed by an information processing device having a control unit, Executed in the control unit: a customer registration process for registering property customer data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date in a storage unit; an integration process in which, when project identification information and registration date are designated by an operator on an integration processing screen, customers are extracted from the property customer data in the storage unit using the designated project identification information and registration date as keys, and displayed in a list of data to be integrated, and at that time, the presence or absence of candidate customers in the property customer data linked by predetermined matching conditions is displayed, and the customers selected by the operator in the list of data to be integrated and the customers in the property customer data linked by the predetermined matching conditions are displayed in an integration candidate list, and when a primary and secondary are selected by the operator in the integration candidate list, the primary and secondary property customer data are integrated in accordance with predetermined integration rules; A customer information management method comprising:

8. A customer information management program to be executed by an information processing device having a control unit and a storage unit, In the control unit, a customer registration process for registering property customer data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date in a storage unit; an integration process in which, when project identification information and registration date are designated by an operator on an integration processing screen, customers are extracted from the property customer data in the storage unit using the designated project identification information and registration date as keys, and displayed in a list of data to be integrated, and at that time, the presence or absence of candidate customers in the property customer data linked by predetermined matching conditions is displayed, and the customers selected by the operator in the list of data to be integrated and the customers in the property customer data linked by the predetermined matching conditions are displayed in an integration candidate list, and when a primary and secondary are selected by the operator in the integration candidate list, the primary and secondary property customer data are integrated in accordance with predetermined integration rules; A customer information management program for causing a computer to execute the above.

Images