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, they obtain information about the property through various media, such as the real estate company's own website, external websites, model rooms, etc., and each property sales representative approaches the customer based on the customer information obtained above. Conventionally, there is a system for managing customers, for example, as disclosed in Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-206253 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 for 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 for sales representatives to manage 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 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 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 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 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] Furthermore, according to one aspect of the present invention, the predetermined integration rule may include a rule that for items in the first category that include project identification information, the main information is adopted, and the items in the first category remain as the main property customer data.

[0009] In addition, according to one aspect of the present invention, the specified integration rule may include a rule that, for items in the second category that include 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.

[0010] Furthermore, according to one aspect of the present invention, the predetermined integration rule may include 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 information of the secondary property customer data is added to the main property customer data as much as will fit.

[0011] In addition, according to one aspect 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 main and secondary property customer data are sorted in ascending order, and the sorted values ​​are updated until the corresponding item of the main 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, characterized in that it includes: a customer registration process executed by the control unit, which registers 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, 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 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 the operator selects a main and a secondary 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 provides a customer information management program to be executed by an information processing device having a control unit and a memory unit, the program comprising: a customer registration process in which the control unit registers 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 an integration process in which, when project identification information and registration date are specified by an operator on an integration processing screen, customers are extracted from the property customer data in the memory unit using the specified 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 specified 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 specified matching conditions are displayed in an integration candidate list, and when the operator selects primary and secondary property customer data in the integration candidate list, the program integrates the primary and secondary property customer data in accordance with specified integration rules. [Effects of the Invention]

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

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

[0016] Hereinafter, embodiments 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 accompanying drawings. Note that the present invention is not limited to these embodiments.

[0017] [1. Overview] For example, in the real estate industry, when customers are considering purchasing real estate, they obtain information about the property through various media, such as the real estate company's own website, external websites, and model rooms, and each property sales representative approaches the customer based on the customer information obtained above.

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

[0019] In order for sales representatives to approach customers appropriately, it is important to properly consolidate and manage customer information, and leaking information can lead to complaints. For each sales representative to independently consolidate customer information, 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, 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 sales person in managing customer information and 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. Note that the customer information management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also 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 communicably 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 achieve a pointing device function. Note that, hereinafter, 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. Furthermore, displaying on the screen of the output device (monitor) 114 by a user and operating the input device 112 may be referred to as a "user operation via a UI."

[0027] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 also stores property customer data, etc.

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

[0029] The control unit 102 is a CPU or the like that performs overall control of 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, etc., and executes various information processing operations 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 stored 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 the 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 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 in a list of integration candidates, and when the operator selects a main and secondary property customer data in the list of integration candidates, integrates the main 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 predetermined integration rule may include a rule that for items in the first category that include project identification information (items with function No. "01" in Figure 9A), 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 that, for items in the second category that include addresses (items with function No. "02" in Figure 9A), when the main property customer data is NULL or blank, the secondary property customer data is adopted and added to the corresponding second category item of the main property customer data.

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

[0038] The specified integration rule may include a rule that, for items in the fourth category (items with function number "07" in Figure 9B) that include 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 until 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] 1 to 14, a specific example of the processing of the control unit 102 of the customer information management device 100 in this embodiment will be described. Fig. 2 is a diagram for explaining an example of the overall processing of the control unit 102 of the customer information management device 100 in this embodiment.

[0042] An example of the overall processing of the control unit 102 of the 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, 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 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 integrating unit 102b executes customer integration processing (step S2). Specifically, in the customer integration processing, for example, when the operator specifies project identification information and the registration date on the integration processing screen displayed on the monitor, the integrating 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 the extracted customers in the integration target data list, displays whether there are any candidate customers in the property customer data linked by predetermined matching conditions, displays the customers selected by the operator in the integration target data list and the customers in the property customer data linked by predetermined matching conditions in the integration candidate list, and when the operator selects a primary and secondary data in the integration candidate list, integrates the primary and secondary property customer data according to predetermined rules.

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

[0046] Figure 3 shows an image of the customer integration process. The following explains the case where Taro Obic (husband) and Hanako Obic (wife) visit property A separately on 5 / 1 and 6 / 1, and property customer data is created for each of them, and then the customer property data for both is integrated.

[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 the following are registered 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", ...

[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", and ...

[0050] (S2: Customer integration processing) A specific example of customer integration processing will be described with reference to Figures 5 to 14. For example, when the operator specifies project identification information and registration date on an integration processing screen displayed on a monitor, the integration unit 102b extracts property customer data from the storage unit 106 using the specified project identification information and registration date as keys, displays the extracted property customer data in a list of data to be integrated, and indicates whether there are any candidate customers in the property customer data linked by predetermined matching conditions. The integration unit 102b displays the customers selected by the operator in the list of data to be integrated and the customers in the property customer data linked by predetermined matching conditions in a list of integration candidates. When the operator selects a primary and secondary property customer data in the list of integration candidates, the integration unit 102b integrates the primary and secondary property customer data in accordance with predetermined integration rules.

[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 customer integration processing. Fig. 7 is a diagram showing an image of property customer data after integration.

[0052] As shown in Figure 5, the integration processing screen 500 displays fields for specifying 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 list of data to be integrated displays a selection box for selecting the data to be integrated, the customer name, address, whether or not there is an integration candidate (yes or no), etc. The list of integration candidates 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 list of integration candidates is integrated according to predetermined integration rules.

[0054] The flow of the customer integration process will be described with reference to Figure 6. When the operator enters the project code and customer registration date of the operator and presses the display button 501 (step S11). The integration unit 102b extracts customers from the property customer data from the storage unit 106 using the project code and customer registration date as keys, and displays them in a 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 in the property customer data that is linked by a predetermined matching condition. The predetermined matching condition is, for example, a match in kana name, a match in email address, a match in telephone number (landline), a match in address, or a match in mobile phone number.

[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 pops up the customer input screen and displays the registered property customer data for that customer, allowing the operator to check the property customer data of the integration candidate (step S14).

[0057] When the operator selects the "main" customer and the "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, PJ code "0001" and registration date "6 / 1" are entered and display button 501 is pressed (step S11 in Fig. 6), and using PJ code "0001" and 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 based on the matching conditions), so "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 matches the matching criteria, are displayed (step S13 in FIG. 6). The display order can be, for example, by customer number. By pressing the target customer button 502, you can check the property customer data for "Obic Taro" and "Obic Hanako."

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

[0061] Figure 7 shows an example of integrating property customer data, with "Obic Taro" as the "primary" and "Obic Hanako" as the "secondary." As shown in Figure 7, the "secondary" information is integrated into the "primary," and the "unusable" flag for the "secondary" is updated to "1." If the "unusable" flag is set to "1," the customer's property registration data is considered unusable, and sales activities are conducted, for example, toward the "primary" customer. In this example, "Obic Taro" is integrated with "Obic Hanako's" telephone number (080-XXX-XXXX), visit date (6 / 1), and desired area (Suginami Ward). The link between the primary and secondary property customer data is managed by storing the primary customer number in the secondary property customer data. Specifically, when integrating the secondary property customer data, (1) the primary customer number is updated (set), and (2) the "unusable" flag is set to "1 (ON)."

[0062] Next, the rules for integration will be explained with reference to Figures 8 to 14. Figure 8 is a diagram for explaining the rules for integration, showing the rules for integration by function number. Figures 9A and 9B show a list of property customer data items and their function numbers. Figures 10 to 14 show examples of integrating property customer data by 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 rules, as follows:

[0064] In Function No. "01: Main Customer Recruitment", the data is always integrated with the main customer data, regardless of whether it is the main customer or secondary customer data. In other words, for items with Function No. "01", the data remains the main customer data.

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

[0066] Function No. "03': Maximum classification value adopted" compares the target classification or flag and adopts the larger attribute data. NULL values ​​are considered to be 0.

[0067] Function No. "07: Information Integration (1)" integrates the information of the main customer and secondary customer, sorts all the values ​​of the main customer and secondary customer in ascending order, and updates the main customer field until it is filled up.

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

[0069] Figures 9A and 9B show Table 2, which lists property customer data items and links them to update rules, and show the correspondence between property customer data items and the above-mentioned function numbers. Property customer data items are integrated according to the integration rules for function numbers in Figure 8. The data in Figures 9A and 9B can be implemented by directly coding them in the integration unit 102b. They may also be made into a master. In Figure 9A, the item with function number "01" corresponds to the "item in the first division," the item with function number "02" corresponds to the "item in the second division," and the item with function number "08" corresponds to the "item in the third division." In Figure 9B, the item with function number "03'" corresponds to the "item in the fifth division," and the item with function number "07" corresponds to the "item in the fourth division."

[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 Recruitment will be explained. Here, we will explain using an example of the PJ code and SEQ (see Figure 9A) with function number "01". 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 Figures 10(A) and 10(B), the PJ code and SEQ are updated using 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: Sub-customer merge will be explained. Here, we will explain using as an example the name of the nearest train line and the name of the nearest station, which have 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] If the primary field is NULL or blank, the secondary information is used to update the field. As shown in Figure 11(A), the primary field contains the blank nearest station name, and the secondary field contains the nearest station name "Kyobashi." Therefore, as shown in Figure 11(B), the secondary nearest station name "Kyobashi" is set as the primary field.

[0075] (Function No. "08: Information Integration (2)") The case of 08: Information Integration (2) will be explained with reference to Figure 12. Here, we will explain using an example of a telephone number (see Figure 9A) with function number "08". 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 primary customer is taken in ascending order, and then as much secondary customer data as possible is added. Adding as much as possible means breaking (ending the update) when the last item in the field is filled in. For example, in the case of phone numbers, there are three fields (phone number 1 to phone number 3), and breaking occurs when the last phone number, number 3, is filled in.

[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, we will explain the case of 03': adopting the maximum classification value. Here, we will explain using as an example the NC (no count) classification (see Figure 9B) with function number "03'". The NC classification 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 category or flag is compared and the larger attribute data is adopted. NULL values ​​are considered to be 0. As shown in Figure 13(A), the main NC flag is "0" and the sub NC flag is "1", so as shown in Figure 13(B), the main NC flag is updated to the sub 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 is integrated, and all primary and secondary values ​​are sorted in ascending order and updated until the primary field is filled. The visit dates are 1 to 10, so sort them in ascending order and cut off the 11th and subsequent visit 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 the operator specifies project identification information and registration date on the 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 a list of data to be integrated, and at that time, displaying whether 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 specified matching conditions in a list of integration candidates, and, when the operator selects a primary and secondary property customer data in the list of integration candidates, integrating the primary and secondary property customer data in accordance with specified integration rules. This makes 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 the achievement of SDGs Goals 8 and 9.

[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, which can contribute to the achievement of Goal 16 of the SDGs.

[0086] 5. Other Embodiments The present invention may be implemented 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] Furthermore, 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 can be changed as desired unless otherwise specified.

[0089] Furthermore, with regard to the customer information management device 100, the components shown in the drawings are functional concepts, and do not necessarily have to be physically configured as shown in the drawings.

[0090] For example, all or any part of the processing functions of the customer information management device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing 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 needed. That is, a computer program for providing 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). The computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0091] This computer program may also be stored in an application program server connected to the customer information management device 100 via any network, and all or part of it may be downloaded as needed.

[0092] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "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] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. 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, can use well-known configurations and procedures.

[0094] The various databases 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 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 workstation, or may be configured as the information processing device to which any peripheral device is connected. The customer information management device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processes 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 configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or 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 unit 106 Storage section 108 Input / Output Interface Section 112 Input Device 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 a customer registration means for registering property customer data in a storage unit, the data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date; 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, and displaying whether or not there are candidate customers in the property customer data linked by a predetermined 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 predetermined matching condition in a list of integration candidates; and, when the operator selects a main property customer data that is the main property customer data and a sub property customer data that is the sub property customer data in the list of integration candidates, integrating the main and sub property customer data in accordance with a predetermined integration rule that prioritizes the main over the sub; 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 corresponding second category item of the main property customer data.

5. 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 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 described in 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 until 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 in a storage unit, the data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date; an integration process in which, when the operator specifies project identification information and registration date on the integration processing screen, customers are extracted from the property customer data in the storage unit using the specified project identification information and registration date as keys, and displayed in a list of data to be integrated, and 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 a list of integration candidates, and when the operator selects a main property customer data that is the main property customer data and a sub property customer data that is the sub property customer data in the list of integration candidates, the main and sub property customer data are integrated in accordance with a predetermined integration rule that prioritizes the main over the sub; 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 in a storage unit, the data including project identification information, customer number, registration date, customer name, kana name, address, telephone number, mobile phone number, email address, and visit date; an integration process in which, when the operator specifies project identification information and registration date on the integration processing screen, customers are extracted from the property customer data in the storage unit using the specified project identification information and registration date as keys, and displayed in a list of data to be integrated, and 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 a list of integration candidates, and when the operator selects a main property customer data that is the main property customer data and a sub property customer data that is the sub property customer data in the list of integration candidates, the main and sub property customer data are integrated in accordance with a predetermined integration rule that prioritizes the main over the sub; A customer information management program for executing the above on a computer.

Images