Customer relationship information management method of distributed customer information system and related application device

Abstract

The application discloses a customer relationship information management method of a distributed customer information system and related application equipment. After determining each customer and the corresponding relationship person of each customer, the main information of the customer and the copy information of the corresponding relationship person of the customer are maintained for each customer, so that the main information of each customer and the copy information of the corresponding relationship person thereof are kept consistent. That is, the customer relationship information is updated only once, and the corresponding relationship information between the customer and the related relationship person thereof is updated at the same time. The problem that the customer information is stored in different databases due to the fact that the customer number is used as the primary key in the existing distributed customer information system, and the relationship persons of different customers may exist in different databases, so that the customer relationship information is difficult to maintain and data disorder is prone to occur is solved.

Description

Technical Field

[0001] This application relates to the field of data management technology, and in particular to a method for managing customer relationship information in a distributed customer information system and related application equipment. Background Technology

[0002] A distributed database system consists of several database systems distributed across multiple computer nodes. It provides efficient access methods to manipulate these sub-databases on these nodes. While a distributed database can be viewed as a single, complete database in use, it is actually distributed across geographically dispersed nodes. Of course, the sub-databases distributed across these nodes are logically related.

[0003] The principle of a distributed customer information system is similar to that of a distributed database system. Most existing distributed customer information systems use the customer number as the primary key to shard and store customer information. Relatives of different customers may exist in different databases, making it difficult to maintain customer relationship information and prone to data disorder. Summary of the Invention

[0004] In view of the shortcomings of the prior art, this application provides a customer relationship information management method and related application equipment for a distributed customer information system, so as to solve the problem that most existing distributed customer information systems use customer number as the primary key to store customer information in fragments, and the relationships of different customers may exist in different databases, which makes it difficult to maintain customer relationship information and easy to cause data disorder.

[0005] To achieve the above objectives, this application provides the following technical solution:

[0006] The first aspect of this application provides a method for managing customer relationship information in a distributed customer information system, including:

[0007] Identify each customer in the distributed customer information management system and the corresponding related person for each customer; each customer corresponds to at least one related person.

[0008] For each customer, the master information of the customer and the copy information of the customer's related persons are maintained separately to ensure that the master information of each customer and the copy information of its corresponding related persons are consistent.

[0009] Optionally, in the above-described method for managing customer relationship information in a distributed customer information system, determining the related parties for each customer includes:

[0010] Input the customer number of each customer into the preset relationship query interface to obtain the relationship information sequence number corresponding to each customer number;

[0011] Based on the customer number and the corresponding relationship information sequence number, the related person corresponding to each customer is determined.

[0012] Optionally, in the above-described method for managing customer relationship information in a distributed customer information system, the preset relationship query interface is a multi-information query interface.

[0013] Optionally, in the above-described customer relationship information management method for a distributed customer information system, for each customer, the primary information of the customer and the copy information of the customer's corresponding related persons are maintained separately, so as to ensure that the primary information of each customer is consistent with the copy information of its corresponding related persons, including:

[0014] The target information that needs to be maintained, namely the primary information of the customer and the copy information of the customer's related persons, is determined respectively;

[0015] Based on the target information, the corresponding information in the customer's master information and the copy information of the customer's related persons is modified and / or deleted.

[0016] Optionally, the customer relationship information management method for the above-mentioned distributed customer information system further includes:

[0017] In the distributed customer information management system, customers whose relationships are to be created are identified from all customers, as well as the related customers of the customers whose relationships are to be created.

[0018] Create corresponding master information for the customer to be created and corresponding copy information for the related customers of the customer to be created, and generate a relationship information sequence number corresponding to the copy information created for the related customers of the customer to be created; the master information created for the customer to be created and the copy information created for the related customers of the customer to be created are consistent.

[0019] Optionally, in the above-described method for managing customer relationship information in a distributed customer information system, identifying customers from all customers in the distributed customer information management system who are to have a relationship created, and identifying the related customers of those customers, includes:

[0020] Obtain the customer ID of the customer whose relationship with the customer to be created is also obtained, along with the customer ID of the related customer of the customer whose relationship with the customer to be created is also obtained.

[0021] Based on the customer number of the customer to be created and the customer number of the related customer of the customer to be created, the customer to be created and the related customer of the customer to be created are determined respectively.

[0022] A second aspect of this application provides a customer relationship information management device for a distributed customer information system, comprising:

[0023] The first determining unit is used to determine each customer in the distributed customer information management system and the related person corresponding to each customer; each customer corresponds to at least one related person.

[0024] The maintenance unit is used to maintain the master information of each customer and the copy information of the customer's corresponding related persons for each customer, so as to ensure that the master information of each customer is consistent with the copy information of its corresponding related persons.

[0025] Optionally, the customer relationship information management device of the aforementioned distributed customer information system further includes:

[0026] The second determining unit is used to determine, from all customers in the distributed customer information management system, the customer to be created as a relationship, and the related customers of the customer to be created as a relationship.

[0027] The creation unit is used to create corresponding master information for the customer to be created and corresponding copy information for the customer to be created's related customers, and generate a relationship information sequence number corresponding to the copy information created for the customer to be created's related customers; wherein, the master information created for the customer to be created and the copy information created for the customer to be created's related customers are consistent.

[0028] A third aspect of this application provides an electronic device for running a program, wherein the program, when running, executes a customer relationship information management method for a distributed customer information system as disclosed in any of the first aspects.

[0029] A fourth aspect of this application provides a computer storage medium including a stored program, wherein, when the program is executed, it controls the device where the storage medium is located to perform a customer relationship information management method of any of the distributed customer information systems disclosed in the first aspect.

[0030] This application provides a method for managing customer relationship information in a distributed customer information system. After identifying each customer and its corresponding related parties, the method maintains the primary information of the customer and the copy information of its corresponding related parties for each customer. This ensures that the primary information of each customer is consistent with the copy information of its corresponding related parties. In other words, this application only needs to perform one operation to update the customer relationship information, which can simultaneously update the corresponding relationship information between the customer and its related parties. This solves the problem that most existing distributed customer information systems use the customer number as the primary key to store customer information in shards, and the related parties of different customers may exist in different databases, making it difficult to maintain customer relationship information and prone to data disorder. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0032] Figure 1 A flowchart illustrating a customer relationship information management method for a distributed customer information system provided in this application embodiment;

[0033] Figure 2 A flowchart for determining the related parties of a customer is provided in an embodiment of this application;

[0034] Figure 3 A flowchart illustrating the maintenance of master and copy information is provided for embodiments of this application.

[0035] Figure 4 A flowchart illustrating another method for managing customer relationship information in a distributed customer information system provided in this application embodiment;

[0036] Figure 5 A flowchart for determining a customer to be created and a customer with a relationship to be created, provided in an embodiment of this application;

[0037] Figure 6 This is a schematic diagram of the structure of a customer relationship information management device for a distributed customer information system provided in an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0039] In this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0040] This application provides a method for managing customer relationship information in a distributed customer information system to solve the problem that most existing distributed customer information systems use customer number as the primary key to segment and store customer information, and the related customers of different customers may exist in different databases, which makes it difficult to maintain customer relationship information and easily leads to data disorder.

[0041] Please see Figure 1 The customer relationship information management method of this distributed customer information system mainly includes the following steps:

[0042] S101. Identify each customer in the distributed customer information management system and the corresponding related persons for each customer.

[0043] Each customer corresponds to at least one person with whom they have a relationship.

[0044] In practical applications, a customer can be a customer within a distributed customer information management system, and the related party of that customer can be another customer within the distributed customer information management system who has some connection with that customer. For example, a kinship relationship or a colleague relationship; of course, it is not limited to these, and can also be other existing relationships, all of which are within the scope of protection of this application.

[0045] It should be noted that the distributed customer information management system can be applied to customer relationship management in banks. Of course, it is not limited to this. It can also be applied to other systems that need to manage customer information. This application does not make specific limitations on them, and they are all within the scope of protection of this application.

[0046] In practical applications, the individual customers in a distributed customer information management system can be identified by aggregating the customers in the system.

[0047] Specifically, if the application environment of distributed customer information management is a bank, then the customer is the bank's customer, and the customer relationship person is other bank customers who have some connection relationship with the bank's customer.

[0048] It should be noted that the specific process of executing step S101, identifying the relevant parties for each customer, can be as follows: Figure 2 As shown, it mainly includes:

[0049] S201. Input the customer number of each customer into the preset relationship query interface to obtain the relationship information sequence number corresponding to each customer number.

[0050] In practical applications, the preset relationship query interface can be a multi-information query interface; of course, it is not limited to this, and can be determined according to the specific application environment and user needs. This application does not limit the specific type of the preset relationship query interface, and all of them are within the protection scope of this application.

[0051] It should be noted that a distributed customer information system can provide an interface that supports querying multiple relationship information entries. Then, the customer number of each customer can be entered into the interface to query the relationship information sequence number corresponding to each customer number.

[0052] S202. Based on the customer number and the corresponding relationship information sequence number, determine the related person for each customer.

[0053] In practical applications, since each of a customer's related persons has a corresponding relationship information number, the related persons of each customer can be determined based on the customer number and the corresponding relationship information number.

[0054] Of course, in addition to the above methods, other existing methods can also be used to determine the related persons of each customer. This application does not specifically limit them, and they are all within the scope of protection of this application.

[0055] S102. For each customer, maintain the customer's master information and the copy information of the customer's corresponding related persons to ensure that the master information of each customer is consistent with the copy information of the corresponding related persons.

[0056] In practical applications, the specific process of executing step S102, which involves maintaining the master information of each customer and the copy information of the customer's corresponding related persons for each customer, to ensure that the master information of each customer is consistent with the copy information of their corresponding related persons, can be as follows: Figure 3 As shown, it mainly includes:

[0057] S301. Identify the target information that needs to be maintained, including the customer's master information and the copy information of the customer's corresponding related persons.

[0058] Among them, the master information of the customer is the relationship information stored in the master customer data table. The master can be the currently maintained record; the copy information of the related person is the relationship information of the related person customer stored in the data table where the related person customer is located. The copy is a record with the related person as the primary key to satisfy the query of the person with whom the relationship was established.

[0059] In practical applications, the target information may be a piece of information that needs to be maintained in both the master information and / or the copy information.

[0060] S302. Based on the target information, modify and / or delete the corresponding information in the customer's master information and the copy information of the customer's related persons.

[0061] In practical applications, after identifying the target information that needs to be maintained, including the customer's master information and the copy information of the customer's corresponding related persons, the corresponding information in the customer's master information and the copy information of the customer's corresponding related persons can be modified and / or deleted based on the target information.

[0062] It should be noted that if a certain piece of information in a customer's master copy needs to be modified, after identifying the information to be modified, the information in the customer's master copy should be verified and modified first, and then the corresponding information in the copy information of all related persons of the customer should be modified to ensure that the information on the master copy remains consistent.

[0063] If it is necessary to delete a certain piece of information in the client's master information, after identifying the information to be deleted, first verify and delete that piece of information in the client's master information, and then delete the corresponding information in the copy information of all the client's related persons to ensure that the information on the master copy remains consistent.

[0064] In summary, it is understood that this application can utilize an external call method based on the characteristics of a distributed system. That is, the background automatically assembles message information based on the replica information, calls the internal interface to route it to the database where the related party is located, and simultaneously updates the main replica information of the customer and its corresponding related party.

[0065] Based on the above principles, the customer relationship information management method for a distributed customer information system provided in this embodiment determines each customer and its corresponding related parties. For each customer, the method maintains the customer's master information and the copy information of the customer's corresponding related parties to ensure that the master information of each customer is consistent with the copy information of its corresponding related parties. In other words, this application only needs to perform one operation to update the customer relationship information, which can simultaneously update the corresponding relationship information between the customer and its related parties. This solves the problem that most existing distributed customer information systems use the customer number as the primary key to store customer information in shards, and the related parties of different customers may exist in different databases, making it difficult to maintain customer relationship information and prone to data disorder.

[0066] Alternatively, in another embodiment provided in this application, please refer to Figure 4 The customer relationship information management method of this distributed customer information system may also include:

[0067] S401. In the distributed customer information management system, identify the customers whose relationships need to be created, as well as the related customers of the customers whose relationships need to be created.

[0068] Among them, "customers whose relationships need to be established" are customers who need to establish relationships with other customers but have not yet done so. "Relationship customers of customers whose relationships need to be established" are customers who need to establish relationships with the customers whose relationships need to be established.

[0069] In practical applications, the specific process of executing step S401—identifying the customers to be created as relationships among all customers in the distributed customer information management system, and identifying the related customers of those customers—can be as follows: Figure 5 As shown, it mainly includes:

[0070] S501. Obtain the customer number of the customer to be created and the customer number of the related customer of the customer to be created.

[0071] Specifically, the customer number selected by the user by triggering the selection button can be used as the customer number of the customer to be created in the relationship, and the customer number of the customer to be created in the relationship can be used as the customer number of the related customer of the customer to be created in the relationship, or the customer number of the customer to be created in the relationship can be used as the customer number of the related customer of the customer to be created in the relationship, or the customer number of the related customer can be used as the customer number ...

[0072] S502. Based on the customer number of the customer to be created and the customer number of the related customer of the customer to be created, respectively, determine the customer to be created and the related customer of the customer to be created.

[0073] Since each customer in the distributed customer information system has a corresponding customer number, the customer to be created can be identified by the customer number of the customer to be created, and the related customer of the customer to be created can be identified by the customer number of the related customer of the customer to be created.

[0074] S402. Create the corresponding primary information for the client to be created and the corresponding copy information for the client to be created, and generate the relationship information sequence number corresponding to the copy information created for the client to be created.

[0075] The master information created for the client to be creating a relationship is consistent with the copy information created for the client to be creating a relationship.

[0076] In practical applications, when it is necessary to create master and copy information for customers with relationships to be created and their related customers, the customer relationship information required to create the master information for the customer with relationships to be created can be obtained first, and the customer relationship information can be verified. Then, the master information for the customer with relationships to be created and the copy information for their related customers can be created, thereby ensuring that the master information created for the customer with relationships to be created is consistent with the copy information created for their related customers.

[0077] In this embodiment, a single creation operation can also create the primary information corresponding to the customer with the relationship to be created and the copy information corresponding to the related customers of the customer with the relationship to be created, and keep the two information consistent. This also solves the problem that most existing distributed customer information systems use the customer number as the primary key to store customer information in shards, and the related persons of different customers may exist in different databases, which makes it difficult to maintain customer relationship information and easy to cause data disorder.

[0078] Optionally, based on the customer relationship information management method for a distributed customer information system provided in the above embodiments, another embodiment of this application also provides a customer relationship information management device for a distributed customer information system. Please refer to [link to relevant documentation]. Figure 6 The device mainly includes:

[0079] The first determining unit 101 is used to determine each customer in the distributed customer information management system and the related person corresponding to each customer; each customer corresponds to at least one related person.

[0080] The maintenance unit 102 is used to maintain the master information of each customer and the copy information of the customer's corresponding related persons for each customer, so as to ensure that the master information of each customer is consistent with the copy information of its corresponding related persons.

[0081] Optionally, the first determining unit 101 is specifically used to determine the related party for each customer when determining the related party:

[0082] Input each customer's customer number into the preset relationship query interface to obtain the relationship information sequence number corresponding to each customer number.

[0083] Based on the customer number and the corresponding relationship information sequence number, the related person for each customer is determined.

[0084] Optionally, the preset relationship query interface is a multi-information query interface.

[0085] Optionally, the maintenance unit 102 is specifically used for:

[0086] The target information that needs to be maintained, namely the customer's master information and the copy information of the customer's corresponding related persons, is determined separately;

[0087] Based on the target information, the corresponding information in the customer's master information and the copy information of the customer's related persons is modified and deleted respectively.

[0088] It should be noted that the specific principles and execution processes of each unit of the customer relationship information management device of the distributed customer information system disclosed in the above embodiments are the same as those of the customer relationship information management method of the distributed customer information system shown in the above embodiments of the present invention. Please refer to the corresponding parts of the customer relationship information management method of the distributed customer information system disclosed in the above embodiments of the present invention, which will not be repeated here.

[0089] In the customer relationship information management device of the distributed customer information system provided in this embodiment, the first determining unit 101 can be used to determine each customer in the distributed customer information management system and the related person corresponding to each customer; each customer corresponds to at least one related person; the maintenance unit 102 is used to maintain the main information of the customer and the copy information of the related person corresponding to the customer for each customer, so that the main information of each customer and the copy information of the related person corresponding to the customer are consistent. That is, only one operation is needed to update the customer relationship information, and the corresponding relationship information between the customer and its related persons can be updated at the same time. This solves the problem that most existing distributed customer information systems use the customer number as the primary key to store customer information in fragments, and the related persons of different customers may exist in different databases, which makes it difficult to maintain customer relationship information and easy to cause data disorder.

[0090] Optionally, in another embodiment provided in this application, the customer relationship information management device of the distributed customer information system further includes:

[0091] The second determining unit is used to determine, among all customers in the distributed customer information management system, the customers to be created as relationships, and the related customers of the customers to be created as relationships.

[0092] The creation unit is used to create corresponding master information for the customer to be created and corresponding copy information for the customer to be created, and to generate a relationship information sequence number corresponding to the copy information created for the customer to be created; wherein, the master information created for the customer to be created and the copy information created for the customer to be created are consistent.

[0093] It should be noted that the specific principles and execution processes of each unit of the customer relationship information management device of the distributed customer information system disclosed in the above embodiments are the same as those of the customer relationship information management method of the distributed customer information system shown in the above embodiments of the present invention. Please refer to the corresponding parts of the customer relationship information management method of the distributed customer information system disclosed in the above embodiments of the present invention, which will not be repeated here.

[0094] In this embodiment, a second determining unit is used to determine the customer to be created and the related customers of the customer to be created from all customers in the distributed customer information management system; a creating unit is used to create corresponding master information for the customer to be created and corresponding copy information for the related customers of the customer to be created, and generate a relationship information sequence number corresponding to the copy information created for the related customers of the customer to be created; wherein, the master information created for the customer to be created and the copy information created for the related customers of the customer to be created are consistent, that is, the master information created for the customer to be created and the copy information created for the related customers of the customer to be created can be created in one creation operation, and the two information are kept consistent. This also solves the problem that most existing distributed customer information systems use customer number as the primary key to store customer information in shards, and the related people of different customers may exist in different databases, which makes it difficult to maintain customer relationship information and easy to cause data disorder.

[0095] Optionally, embodiments of the present invention also disclose an electronic device for running a program, wherein the program executes the customer relationship information management method of the distributed customer information system described in the above embodiments.

[0096] It should be noted that the relevant explanations of the customer relationship information management method of the distributed customer information system can be found in the corresponding embodiments shown above, and will not be repeated here.

[0097] Optionally, embodiments of the present invention also disclose a computer storage medium, the storage medium including a stored program, wherein, when the program is running, it controls the device where the storage medium is located to execute the customer relationship information management method of the distributed customer information system as described in any of the above embodiments.

[0098] It should be noted that the relevant explanations of the customer relationship information management method of the distributed customer information system can be found in the corresponding embodiments shown above, and will not be repeated here.

[0099] In the context of this disclosure, a computer storage medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0100] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0101] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A customer relationship information management method of a distributed customer information system, characterized by, include: Identify each customer in the distributed customer information system and the corresponding related persons for each customer. Each of the aforementioned customers corresponds to at least one of the aforementioned related persons; The step of determining the related person corresponding to each customer includes: inputting the customer number of each customer into a preset relationship query interface to obtain the relationship information sequence number corresponding to each customer number; and determining the related person corresponding to each customer based on the customer number and the relationship information sequence number corresponding to the customer number. For each customer, the primary information of the customer and the copy information of the customer's corresponding related persons are maintained to ensure that the primary information of each customer and the copy information of its corresponding related persons are consistent. This includes: determining the target information that needs to be maintained for the primary information of the customer and the copy information of the customer's corresponding related persons; modifying and / or deleting the corresponding information in the primary information of the customer and the copy information of the customer's corresponding related persons based on the target information; wherein, when the target information is the information that needs to be maintained in the copy information, this includes: automatically assembling message information according to the copy information, calling the internal interface to route it to the database where the related person is located, and simultaneously updating the primary information of the customer and the copy information of its corresponding related person.

2. The customer relationship information management method of a distributed customer information system according to Claim 1, characterized by, The preset relationship query interface is a multi-information query interface.

3. The customer relationship information management method of a distributed customer information system according to Claim 1, characterized by, Also includes: In the distributed customer information system, customers whose relationships are to be created are identified from all customers, as well as the related customers of the customers whose relationships are to be created. The master information corresponding to the customer to be created and the copy information corresponding to the customer to be created are created respectively, and a relationship information sequence number corresponding to the copy information created for the customer to be created is generated; wherein, the master information created for the customer to be created and the copy information created for the customer to be created are consistent.

4. The customer relationship information management method of a distributed customer information system according to Claim 3, characterized by, In the distributed customer information system, customers from all customers are identified as having relationships to be created, as well as the related customers of those customers, including: Obtain the customer ID of the customer whose relationship with the customer to be created is also obtained, along with the customer ID of the related customer of the customer whose relationship with the customer to be created is also obtained. Based on the customer number of the customer to be created and the customer number of the related customer of the customer to be created, the customer to be created and the related customer of the customer to be created are determined respectively.

5. A customer relationship information management apparatus of a distributed customer information system, characterized by comprising: include: The first determining unit is used to determine each customer in the distributed customer information system and the related person corresponding to each customer; Each of the aforementioned customers corresponds to at least one of the aforementioned related persons; The step of determining the related person corresponding to each customer includes: inputting the customer number of each customer into a preset relationship query interface to obtain the relationship information sequence number corresponding to each customer number; and determining the related person corresponding to each customer based on the customer number and the relationship information sequence number corresponding to the customer number. A maintenance unit is used to maintain the master information of each customer and the copy information of the customer's corresponding related persons for each customer, so as to ensure that the master information of each customer is consistent with the copy information of its corresponding related persons. The unit includes: determining the target information that needs to be maintained for the master information of the customer and the copy information of the customer's corresponding related persons; modifying and / or deleting corresponding information in the master information of the customer and the copy information of the customer's corresponding related persons based on the target information; wherein, when the target information is information that needs to be maintained in the copy information, the unit includes: automatically assembling message information according to the copy information, calling an internal interface to route it to the database where the related person resides, and simultaneously updating the master information of the customer and the copy information of its corresponding related person.

6. The customer relationship information management apparatus of the distributed customer information system according to Claim 5, wherein Also includes: The second determining unit is used to determine, among all customers in the distributed customer information system, the customer to be created as a relationship, and the related customers of the customer to be created as a relationship. The creation unit is used to create corresponding master information for the customer to be created and corresponding copy information for the customer to be created's related customers, and generate a relationship information sequence number corresponding to the copy information created for the customer to be created's related customers; wherein, the master information created for the customer to be created and the copy information created for the customer to be created's related customers are consistent.

7. An electronic device, comprising: The electronic device is used to run a program, wherein the program executes the customer relationship information management method of the distributed customer information system as described in any one of claims 1-4.

8. A computer storage medium, characterized in that The storage medium includes a stored program, wherein, when the program is running, it controls the device where the storage medium is located to execute the customer relationship information management method of the distributed customer information system as described in any one of claims 1-4.

Images