Data processing method and device for customer relationship management

Abstract

The present application discloses a data processing method and device for customer relationship management. The method responds to a user's rule configuration operation, sends a rule configuration file indicated by the rule configuration operation to a server, so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file; responds to a user's scenario configuration operation, determines multiple business relationship scenarios; sends multiple business relationship scenarios to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer. Since multiple business relationship scenarios representing the corresponding relationship between multiple trigger rule pools and multiple processing rule pools are configured, the target customer relationship can be determined according to the processing rule pool indicated by the target business relationship scenario corresponding to the target customer, without the need for manual judgment and manual configuration of the customer relationship, thereby reducing the cost of customer relationship management and improving the efficiency of customer relationship management.

Description

Technical Field

[0001] The present application relates to the field of information processing technology, and in particular to a data processing method and device for customer relationship management. Background Art

[0002] Currently, enterprises need to record and manage customers' personal information, corresponding business information and business personnel information, so as to facilitate the acquisition, follow-up, service and maintenance of customers. In the prior art, customer relationships are manually configured by business personnel and uploaded to the server, so as to be presented on the customer relationship management system. However, since the business and management requirements of enterprises often need to be flexibly adjusted, the manual configuration of customer relationships is difficult and risky, resulting in high cost and low efficiency of customer relationship management. Therefore, how to reduce the cost of customer relationship management and improve the efficiency of customer relationship management has become a technical problem that needs to be further solved. Summary of the invention

[0003] The present application proposes a data processing method and device for customer relationship management to solve the problems of high cost and low efficiency of customer relationship management, reduce the cost of customer relationship management, and improve the efficiency of customer relationship management.

[0004] In a first aspect, an embodiment of the present application provides a data processing method for customer relationship management, which is applied to a terminal device in a customer relationship management system, wherein the customer relationship management system includes the terminal device and a server, and the method includes:

[0005] In response to a rule configuration operation of a user, a rule configuration file indicated by the rule configuration operation is sent to the server, so that the server determines a plurality of trigger rule pools and a plurality of processing rule pools according to the rule configuration file, wherein the rule configuration operation includes an input operation for a rule configuration operation box in the first interface, a plurality of trigger rules in the plurality of trigger rule pools are used to classify business relationships for customers, and a plurality of processing rules in the plurality of processing rule pools are used to process business relationships for customers;

[0006] receiving the multiple trigger rule pools and the multiple processing rule pools sent by the server;

[0007] In response to a scenario configuration operation of the user, determining a plurality of business relationship scenarios, wherein the scenario configuration operation includes an input operation for a scenario configuration operation box in the second interface, and the plurality of business relationship scenarios are used to characterize a correspondence between the plurality of trigger rule pools and the plurality of processing rule pools;

[0008] The multiple business relationship scenarios are sent to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, and the target customer relationship is used to characterize the association relationship between the target customer and the corresponding target-related personnel.

[0009] In a second aspect, an embodiment of the present application provides a data processing device for customer relationship management, which is applied to a terminal device in a customer relationship management system. The customer relationship management system includes the terminal device and a server. The device includes:

[0010] A first processing unit is configured to respond to a rule configuration operation of a user and send a rule configuration file indicated by the rule configuration operation to the server, so that the server determines a plurality of trigger rule pools and a plurality of processing rule pools according to the rule configuration file, wherein the rule configuration operation includes an input operation for a rule configuration operation box in the first interface, a plurality of trigger rules in the plurality of trigger rule pools are used to classify business relationships of customers, and a plurality of processing rules in the plurality of processing rule pools are used to process business relationships of customers;

[0011] A first receiving unit, configured to receive the multiple trigger rule pools and the multiple processing rule pools sent by the server;

[0012] The second processing unit is used to respond to the user's scenario configuration operation, determine multiple business relationship scenarios, the scenario configuration operation includes an input operation on the scenario configuration operation box in the second interface, and the multiple business relationship scenarios are used to characterize the correspondence between the multiple trigger rule pools and the multiple processing rule pools; send the multiple business relationship scenarios to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, and the target customer relationship is used to characterize the association relationship between the target customer and the corresponding target-related personnel.

[0013] In a third aspect, an embodiment of the present application provides a terminal device, comprising a processor, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the program includes instructions for executing the steps in the method described in any one of the first aspects.

[0014] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program / instruction stored thereon, wherein the computer program / instruction, when executed by a processor, implements the steps of the method described in any one of the first aspects.

[0015] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements part or all of the steps of the method described in any one of the first aspects of the embodiments of the present application.

[0016] It can be seen that in the present application, the terminal device responds to the user's rule configuration operation and sends the rule configuration file indicated by the rule configuration operation to the server, so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file, and the rule configuration operation includes an input operation for the rule configuration operation box in the first interface, and the multiple trigger rules in the multiple trigger rule pools are used to classify the business relationship of the customer, and the multiple processing rules in the multiple processing rule pools are used to perform business relationship processing on the customer; receiving multiple trigger rule pools and multiple processing rule pools sent by the server; responding to the user's scenario configuration operation, determining multiple business relationship scenarios, the scenario configuration operation includes an input operation for the scenario configuration operation box in the second interface, and the multiple business relationship scenarios are used to characterize the correspondence between multiple trigger rule pools and multiple processing rule pools; sending multiple business relationship scenarios to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, and the target customer relationship is used to characterize the association relationship between the target customer and the corresponding target-related personnel. Since multiple business relationship scenarios representing the correspondence between multiple trigger rule pools and multiple processing rule pools are configured through the terminal device, the server can determine the target customer relationship corresponding to the target customer according to the processing rule pool indicated by the target business relationship scenario corresponding to the target customer. Therefore, when the business and management requirements of the enterprise are adjusted, it is only necessary to reconfigure multiple business relationship scenarios to obtain customer relationships that meet the latest requirements. There is no need for business personnel to manually configure customer relationships based on manual judgment according to the latest business and management requirements, thereby reducing the cost of customer relationship management and improving the efficiency of customer relationship management. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1 It is a structural diagram of a customer relationship management system provided by an embodiment of the present application;

[0019] Figure 2 It is a structural diagram of a terminal device in a customer relationship management system provided by an embodiment of the present application;

[0020] Figure 3 It is a structural schematic diagram of a terminal device in another customer relationship management system provided by an embodiment of the present application;

[0021] Figure 4 It is a flowchart of a data processing method for customer relationship management provided by an embodiment of the present application;

[0022] Figure 5 It is a scenario diagram of a data processing method for customer relationship management provided by an embodiment of the present application;

[0023] Figure 6 It is a scenario diagram of another data processing method for customer relationship management provided by an embodiment of the present application;

[0024] Figure 7 This is a scenario diagram of another data processing method for customer relationship management provided by an embodiment of the present application;

[0025] Figure 8 This is a block diagram of the functional units of a data processing device for customer relationship management provided by an embodiment of the present application;

[0026] Fig. 9 It is a block diagram of the functional units of another data processing device for customer relationship management provided by an embodiment of the present application;

[0027] Fig.10 It is a structural block diagram of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0029] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0030] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0031] In the embodiments of the present application, "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent the following three situations: A exists alone; A and B exist at the same time; B exists alone. Among them, A and B can be singular or plural.

[0032] In the embodiment of the present application, the symbol " / " can indicate that the objects associated with each other are in an "or" relationship. In addition, the symbol " / " can also indicate a division sign, that is, performing a division operation. For example, A / B can indicate A divided by B.

[0033] In the embodiments of the present application, "at least one item" or similar expressions refer to any combination of these items, including any combination of single items or plural items, and refer to one or more, and multiple refers to two or more. For example, at least one item of a, b, or c can represent the following seven situations: a, b, c, a and b, a and c, b and c, a, b, and c. Among them, each of a, b, and c can be an element or a set containing one or more elements.

[0034] In the embodiments of the present application, "equal to" can be used in conjunction with greater than, and is applicable to the technical solution adopted when greater than, and can also be used in conjunction with less than, and is applicable to the technical solution adopted when less than. When equal to is used in conjunction with greater than, it is not used in conjunction with less than; when equal to is used in conjunction with less than, it is not used in conjunction with greater than.

[0035] In order to better understand the solutions of the embodiments of the present application, the terminal devices, related concepts and backgrounds that may be involved in the embodiments of the present application are first introduced below.

[0036] (1) Customer Relationship Management: Customer Relationship Management, or CRM, refers to the process by which an enterprise uses relevant information technology and Internet technology to coordinate the interaction between the enterprise and its customers in sales, marketing, and services in order to improve its core competitiveness, thereby improving its management methods and providing customers with innovative, personalized customer interactions and services.

[0037] (2) Customer relationship management system: Customer relationship management system, referred to as CRM system, refers to the use of software, hardware and network technology to establish an information system for enterprises to collect, manage, analyze and utilize customer information.

[0038] Currently, enterprises need to record and manage customers' personal information, corresponding business information and business personnel information, so as to facilitate the acquisition, follow-up, service and maintenance of customers. In the prior art, customer relationships are manually configured by business personnel and uploaded to the server, so as to be presented on the customer relationship management system. However, since the business and management requirements of enterprises often need to be flexibly adjusted, the manual configuration of customer relationships is difficult and risky, resulting in high cost and low efficiency of customer relationship management. Therefore, how to reduce the cost of customer relationship management and improve the efficiency of customer relationship management has become a technical problem that needs to be further solved.

[0039] To solve the above problems, an embodiment of the present application provides a data processing method and device for customer relationship management, in which multiple business relationship scenarios representing the correspondence between multiple trigger rule pools and multiple processing rule pools are configured through a terminal device, so that the server can update the customer relationship corresponding to each customer based on the processing rules indicated by the business relationship scenario corresponding to each customer. Therefore, when the business and management requirements of the enterprise are adjusted, it is only necessary to reconfigure multiple business relationship scenarios to obtain customer relationships that meet the latest requirements. There is no need for business personnel to manually configure customer relationships based on the latest business and management requirements through manual judgment, thereby reducing the cost of customer relationship management and improving the efficiency of customer relationship management.

[0040] See also Figure 1 , Figure 1 Schematic diagram of the structure of a customer relationship management system provided by the embodiment of the present application. Figure 1 As shown, the customer relationship management system 100 includes a server 110 and a terminal device 120, the server 110 and the terminal device 120 are in communication connection, the server 110 can be a server, or a server group composed of multiple servers. The terminal device 120 can be a mobile phone, a tablet computer, etc.

[0041] The terminal device 120 specifically refers to an operation terminal used by management personnel.

[0042] In daily use of the customer relationship management system 100, the terminal device 120 responds to the user's rule configuration operation and sends the rule configuration file indicated by the rule configuration operation to the server, so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file, the rule configuration operation includes an input operation for the rule configuration operation box in the first interface, the multiple trigger rules in the multiple trigger rule pools are used to classify the business relationship of the customer, and the multiple processing rules in the multiple processing rule pools are used to process the business relationship of the customer; receiving multiple trigger rule pools and multiple processing rule pools sent by the server; responding to the user's scenario configuration operation, determining multiple business relationship scenarios, the scenario configuration operation includes an input operation for the scenario configuration operation box in the second interface, and the multiple business relationship scenarios are used to characterize the corresponding relationship between the multiple trigger rule pools and the multiple processing rule pools; sending multiple business relationship scenarios to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, and the target customer relationship is used to characterize the association relationship between the target customer and the corresponding target-related personnel.

[0043] See also Figure 2 , Figure 2 Schematic diagram of the structure of a terminal device in a customer relationship management system provided by an embodiment of the present application. Figure 2 As shown, the terminal device 120 includes a rule configuration module 210 and a scene configuration module 220 , the rule configuration module 210 is communicatively connected to the scene configuration module 220 , the rule configuration module 210 is communicatively connected to the server 110 , and the scene configuration module 220 is communicatively connected to the server 110 .

[0044] Among them, the rule configuration module is used to respond to the user's rule configuration operation, and send the rule configuration file indicated by the rule configuration operation to the server, so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file, and the rule configuration operation includes an input operation for the rule configuration operation box in the first interface, and the multiple trigger rules in the multiple trigger rule pools are used to classify business relationships for customers, and the multiple processing rules in the multiple processing rule pools are used to process business relationships for customers.

[0045] Among them, the scenario configuration module is used to receive the multiple trigger rule pools and the multiple processing rule pools sent by the server; respond to the user's scenario configuration operation, determine multiple business relationship scenarios, the scenario configuration operation includes an input operation for the scenario configuration operation box in the second interface, and the multiple business relationship scenarios are used to characterize the correspondence between the multiple trigger rule pools and the multiple processing rule pools; send the multiple business relationship scenarios to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, and the target customer relationship is used to characterize the association relationship between the target customer and the corresponding target-related personnel.

[0046] See also Figure 3 , Figure 3 Schematic diagram of the structure of another terminal device in a customer relationship management system provided by an embodiment of the present application. Figure 3 As shown, the terminal device 120 includes a processor 310 and a memory 320, and the processor 310 is in communication with the memory 320. The memory 320 stores one or more programs, and the one or more programs are configured to be executed by the processor 310. The function of the one or more programs is to respond to the user's rule configuration operation, send the rule configuration file indicated by the rule configuration operation to the server, so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file, the rule configuration operation includes an input operation for the rule configuration operation box in the first interface, the multiple trigger rules in the multiple trigger rule pools are used to classify the business relationship of the customer, and the multiple processing rules in the multiple processing rule pools are used to process the business relationship of the customer; receive multiple trigger rule pools and multiple processing rule pools sent by the server; respond to the user's scenario configuration operation, determine multiple business relationship scenarios, the scenario configuration operation includes an input operation for the scenario configuration operation box in the second interface, and the multiple business relationship scenarios are used to characterize the correspondence between the multiple trigger rule pools and the multiple processing rule pools; send multiple business relationship scenarios to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, and the target customer relationship is used to characterize the association relationship between the target customer and the corresponding target-related personnel.

[0047] The following describes a data processing method for customer relationship management provided by an embodiment of the present application.

[0048] See also Figure 4 , Figure 4 is a flow chart of a data processing method for customer relationship management provided by an embodiment of the present application, which is applied to Figure 1The terminal device 120 in the customer relationship management system 100 shown in the figure comprises a server 110 and a terminal device 120, and the server 110 and the terminal device 120 are in communication connection; Figure 4 As shown, the method comprises the following steps:

[0049] Step S401, in response to a rule configuration operation of a user, sending a rule configuration file indicated by the rule configuration operation to the server, so that the server determines a plurality of trigger rule pools and a plurality of processing rule pools according to the rule configuration file.

[0050] Among them, the rule configuration operation includes an input operation for the rule configuration operation box in the first interface, the multiple trigger rules in the multiple trigger rule pools are used to classify business relationships of customers, and the multiple processing rules in the multiple processing rule pools are used to process business relationships of customers.

[0051] Among them, the response to the user's rule configuration operation, sending the rule configuration file indicated by the rule configuration operation to the server, so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file, includes: responding to the user's upload operation on the rule configuration operation box, displaying a first confirmation button in the rule configuration operation box, the upload operation is used to upload the rule configuration file, and the first confirmation button is used to obtain the user's first confirmation operation on the rule configuration file; in response to the first confirmation operation, sending the rule configuration file to the server.

[0052] Among them, see Figure 5 , Figure 5 Schematic diagram of a scenario of a data processing method for customer relationship management provided by an embodiment of the present application. Figure 5 As shown, the terminal device displays a first interface 500 , which includes a rule configuration operation box 510 . When the user performs the upload operation on the rule configuration operation box 510 , a first confirmation button 511 is displayed in the rule configuration operation box 510 .

[0053] In a possible embodiment, the rule configuration file includes sample customer information of multiple sample customers and sample personnel information and sample customer relationships of sample personnel corresponding to each sample customer among the multiple sample customers, the sample customer relationship being used to indicate an association relationship between a corresponding sample customer and a relevant personnel in each relationship level in at least one corresponding relationship level, and the step of responding to a rule configuration operation of a user, sending a rule configuration file indicated by the rule configuration operation to the server so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file, including: responding to a rule configuration operation of a user, sending a rule configuration file indicated by the rule configuration operation to the server so that the server performs the following operations: receiving the rule configuration file; determining a trigger rule pool and a processing rule pool according to each sample customer; The sample customer information and the corresponding sample personnel information of the customer determine multiple atomic-level elements corresponding to each trigger dimension in at least one trigger dimension; determine the trigger rule pool corresponding to each sample customer according to the multiple atomic-level elements corresponding to each trigger dimension in the at least one trigger dimension, and obtain the multiple trigger rule pools, each of the multiple trigger rule pools includes at least one trigger rule, and the at least one trigger rule corresponds one-to-one to the at least one trigger dimension; determine the processing rule pool corresponding to each sample customer according to the sample customer relationship corresponding to each sample customer, and obtain the multiple processing rule pools, each of the multiple processing rule pools includes at least one processing rule, and the at least one processing rule corresponds one-to-one to at least one relationship level corresponding to each sample customer.

[0054] The sample customer information of each sample customer includes a sample customer type and a sample channel type, and the sample personnel information of the sample personnel corresponding to each sample customer includes a sample personnel type and a sample personnel qualification.

[0055] The at least one relationship level includes a first relationship level, a second relationship level and a third relationship level.

[0056] Among them, the sample customer relationship may specifically include a first-level relationship between the corresponding sample customer and a first-level relevant personnel in the corresponding first relationship level, a second-level relationship with a second-level relevant personnel in the corresponding second relationship level, and a third-level relationship with a third-level relevant personnel in the corresponding third relationship level, the first-level relationship being used to indicate the share ratio of the first-level relevant personnel for the business handled by the customer and the effective date of the hierarchical relationship, the second-level relationship being used to indicate the share ratio of the second-level relevant personnel for the business handled by the customer and the effective date of the hierarchical relationship, and the third-level relationship being used to indicate the share ratio of the third-level relevant personnel for the business handled by the customer and the effective date of the hierarchical relationship. For example, the sample customer information of sample customer X in the rule configuration file includes: sample customer type: individual customer, sample channel type: offline, and the corresponding sample personnel information of sample personnel a (specifically, the personnel who handles business for sample customer X) includes: sample personnel type: first-level salesperson, sample personnel qualification: general securities practitioner qualification, and the first-level relationship corresponding to sample customer X is: customer: X, first-level related personnel: A, sharing ratio: 0.1, effective date: account opening date; the corresponding second-level relationship is: customer: X, second-level related personnel: B, sharing ratio: 0.2, effective date: account opening date; the corresponding third-level relationship is: customer: X, third-level related personnel: a, sharing ratio: 0.7, effective date: account opening date.

[0057] Wherein, the at least one triggering dimension includes a customer type dimension, a channel type dimension, a personnel type dimension and a personnel qualification dimension.

[0058] Among them, the server determines multiple atomic-level elements corresponding to each trigger dimension in at least one trigger dimension according to the sample customer information of each sample customer and the corresponding sample personnel information. Specifically, the sample customer information of each sample customer and the corresponding sample personnel information are divided into atomic-level elements by rule classification to obtain the multiple atomic-level elements, wherein the customer type atomic-level element corresponds to the customer type dimension, the channel type atomic-level element corresponds to the channel type dimension, the personnel type atomic-level element corresponds to the personnel type dimension, and the personnel qualification atomic-level element corresponds to the personnel qualification dimension. For example, the multiple atomic-level elements determined according to the sample customer information of the sample customer X and the corresponding sample personnel information of the sample personnel a include: individual customer, offline, first-level salesperson, and general securities practitioner qualification.

[0059] Among them, the server determines the trigger rule pool corresponding to each sample customer according to the multiple atomic-level elements corresponding to each trigger dimension in the at least one trigger dimension, and obtains the multiple trigger rule pools. For example, at least one trigger rule in the trigger rule pool corresponding to the sample customer X includes: the first trigger rule corresponding to the customer type dimension: individual customer, the second trigger rule corresponding to the channel type dimension: offline, the third trigger rule corresponding to the personnel type dimension: first-level salesperson, and the fourth trigger rule corresponding to the personnel qualification dimension: general securities practitioner qualification.

[0060] Among them, the processing rule pool corresponding to each sample customer is determined according to the sample customer relationship corresponding to each sample customer, and the multiple processing rule pools are obtained. For example, at least one processing rule in the processing rule pool corresponding to sample customer X includes: first-level relationship: customer: X, first-level related personnel: A, sharing ratio: 0.1, effective date: account opening day; second-level relationship: customer: X, second-level related personnel: B, sharing ratio: 0.2, effective date: account opening day; third-level relationship: customer: X, third-level related personnel: a, sharing ratio: 0.7, effective date: account opening day.

[0061] It can be seen that in this example, the terminal device sends the rule configuration file uploaded by the user to the server, and then receives multiple trigger rule pools and multiple processing rule pools sent by the server, thereby configuring multiple business relationship scenarios that characterize the correspondence between the multiple trigger rule pools and the multiple processing rule pools, so that the server can determine the target customer relationship corresponding to the target customer according to the processing rule pool indicated by the target business relationship scenario corresponding to the target customer, so that when the business and management requirements of the enterprise are adjusted, it is only necessary to reconfigure multiple business relationship scenarios to obtain customer relationships that meet the latest requirements, and there is no need for business personnel to manually configure customer relationships based on the latest business and management requirements. This reduces the cost of customer relationship management and improves the efficiency of customer relationship management.

[0062] Step S402: receiving the multiple trigger rule pools and the multiple processing rule pools sent by the server.

[0063] After receiving the multiple trigger rule pools and the multiple processing rule pools, the terminal device displays a second interface.

[0064] Step S403: In response to the scenario configuration operation of the user, a plurality of business relationship scenarios are determined.

[0065] The scenario configuration operation includes an input operation on a scenario configuration operation box in the second interface, and the multiple business relationship scenarios are used to characterize the corresponding relationship between the multiple trigger rule pools and the multiple processing rule pools.

[0066] In a possible embodiment, the scenario configuration operation box includes multiple scenario name input boxes, multiple trigger rule pool configuration boxes and multiple processing rule pool configuration boxes, the multiple scenario name input boxes correspond one-to-one to the multiple trigger rule pool configuration boxes, and the multiple scenario name input boxes correspond one-to-one to the multiple processing rule pool configuration boxes. The determination of multiple business relationship scenarios in response to the user's scenario configuration operation includes: determining multiple business relationship scenario names in response to the user's input operation on the multiple scenario name input boxes; determining trigger rule pools corresponding to the multiple business relationship scenario names in response to the user's input operation on the multiple trigger rule pool configuration boxes; determining processing rule pools corresponding to the multiple business relationship scenario names in response to the user's input operation on the multiple processing rule pool configuration boxes; and determining the multiple business relationship scenarios based on the multiple business relationship scenario names and the trigger rule pools and processing rule pools corresponding to the multiple business relationship scenario names.

[0067] Among them, see Figure 6 , Figure 6 FIG. 1 is a schematic diagram of another scenario of a data processing method for customer relationship management provided by an embodiment of the present application. Figure 6As shown, the terminal device displays a second interface 600, which includes the rule configuration operation box 510 and the scenario configuration operation box 610. The rule configuration operation box 510 displays a first confirmation button 511. The scenario configuration operation box 610 includes multiple scenario name input boxes 611, multiple trigger rule pool configuration boxes 612, multiple processing rule pool configuration boxes 613, multiple scenario confirmation buttons 614, and a new scenario button 615. The multiple scenario name input boxes 611 correspond to the multiple trigger rule pool configuration boxes 612, the multiple processing rule pool configuration boxes 613, and the multiple scenario confirmation buttons 614, respectively. Specifically, the scenario name input box in each row corresponds to one trigger rule pool configuration box, one processing rule trigger pool configuration box, and one scenario confirmation button. The multiple scenario name input boxes 611 are used to obtain multiple business relationship scenario names. When any one of the multiple trigger rule pool configuration boxes 612 detects a user's click operation, a first drop-down form will be displayed. The first drop-down form displays the multiple trigger rule pools for the user to select from the multiple trigger rule pools. The trigger rule pool selected by the user will be displayed in the trigger rule pool configuration box. When any one of the multiple processing rule pool configuration boxes 613 detects a user's click operation, a second drop-down form will be displayed. The second drop-down form displays the multiple processing rule pools for the user to select from the multiple processing rule pools. The processing rule pool selected by the user will be displayed in the processing rule pool configuration box. Each of the multiple scenario confirmation buttons 614 is used to obtain the user's second confirmation operation for the trigger rule pool and processing rule pool corresponding to the corresponding business relationship scenario. The new scene button 615 is used to obtain the user's new scene operation. Specifically, when the user clicks the new scene button 615 once, a new scene name input box is added to the scene configuration operation box 610, and a trigger rule pool configuration box, a processing rule trigger pool configuration box and a scene confirmation button corresponding to the newly added scene name input box are added.

[0068] Among them, determining the multiple business relationship scenarios according to the multiple business relationship scenario names and the trigger rule pool and the processing rule pool corresponding to the multiple business relationship scenario names can specifically be: binding the corresponding business relationship scenario name with the corresponding trigger rule pool and the processing rule pool according to the second determination operation obtained by each confirmation button in the multiple scenario confirmation buttons to obtain the multiple business relationship scenarios.

[0069] It can be seen that in this example, multiple business relationship scenarios are configured through multiple scenario name input boxes, multiple trigger rule pool configuration boxes and multiple processing rule pool configuration boxes in the second interface of the terminal device, so that the server can determine the target customer relationship corresponding to the target customer according to the processing rule pool indicated by the target business relationship scenario corresponding to the target customer. Therefore, when the business and management requirements of the enterprise are adjusted, it is only necessary to reconfigure multiple business relationship scenarios to obtain customer relationships that meet the latest requirements. There is no need for business personnel to manually configure customer relationships based on the latest business and management requirements through manual judgment, thereby reducing the cost of customer relationship management and improving the efficiency of customer relationship management.

[0070] Step S404: sending the multiple business relationship scenarios to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer.

[0071] The target customer relationship is used to represent the association relationship between the target customer and the corresponding target-related personnel.

[0072] In a possible embodiment, sending the multiple business relationship scenarios to the server so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer includes: sending the multiple business relationship scenarios to the server so that the server performs the following operations: obtaining target customer information of the target customer and target personnel information of the target personnel corresponding to the target customer; determining a target business relationship scenario according to the target customer information, the target personnel information and the multiple business relationship scenarios, the target business relationship scenario being used to characterize the business relationship scenario corresponding to the target customer; determining a target customer relationship according to the target customer information, the target personnel information and the target business relationship scenario; and updating a customer relationship storage table according to the target customer relationship so that the target customer relationship is stored in the customer relationship storage table, the customer relationship storage table being used to store the association relationship between all customers and all personnel.

[0073] The business terminal responds to the information input operation of the business personnel, determines the initial customer information of the target customer and the initial personnel information of the target personnel corresponding to the target customer, and sends the initial customer information and the initial personnel information to the server. The business terminal is connected to the server in communication, and the business terminal specifically refers to the operation terminal used by the business personnel.

[0074] Among them, the target customer information and the target personnel information are obtained by the server performing the following operations: receiving the initial customer information and the initial personnel information sent by the business terminal; performing information cleaning on the initial customer information to obtain first customer information, including: screening out the customer affiliation branch, customer type, customer status, customer assets, customer business tags, customer drainage channel information, and customer account opening referral information in the initial customer information to obtain the first customer information; performing information cleaning on the initial personnel information to obtain first personnel information, including: screening out the personnel mobile phone number, personnel qualifications, personnel type, and personnel team in the initial personnel information to obtain the first personnel information; performing data detection, data repair, and data filling on the first customer information and the first personnel information to obtain second customer information and second personnel information; performing information format and data type unification processing on the second customer information and the second personnel information to obtain the target customer information and the target personnel information.

[0075] It can be seen that in this example, multiple business relationship scenarios representing the correspondence between multiple trigger rule pools and multiple processing rule pools are configured through the terminal device, so that the server can determine the target customer relationship corresponding to the target customer according to the processing rule pool indicated by the target business relationship scenario corresponding to the target customer. Therefore, when the business and management requirements of the enterprise are adjusted, it is only necessary to reconfigure multiple business relationship scenarios to obtain customer relationships that meet the latest requirements. There is no need for business personnel to manually configure customer relationships based on manual judgment according to the latest business and management requirements, thereby reducing the cost of customer relationship management and improving the efficiency of customer relationship management.

[0076] In a possible embodiment, the target business relationship scenario is obtained by the server performing the following operations: determining a target trigger rule corresponding to the target customer information and the target personnel information, the target trigger rule being a trigger rule in a pool of multiple trigger rules corresponding to the multiple business relationship scenarios hit by the target customer information and the target personnel information; and determining the target business relationship scenario based on the target trigger rule.

[0077] The server determines the target trigger rules corresponding to the target customer information and the target personnel information by specifically determining the trigger rules that the target customer information and the target personnel information match in each trigger dimension to obtain the target trigger rules.

[0078] Among them, see Figure 7 , Figure 7 FIG. 1 is a schematic diagram of another scenario of a data processing method for customer relationship management provided by an embodiment of the present application. Figure 7As shown, the atomic elements in the customer type dimension include: individual customers, institutional customers, product customers; the atomic elements in the channel type dimension include: offline, company app, company website, company community; the atomic elements in the personnel type dimension include: third-level salesperson, second-level salesperson, first-level salesperson, zero-level salesperson; the atomic elements in the personnel qualification dimension include: general securities qualification, fund qualification, securities investment consulting qualification, futures qualification. When the target customer is determined to be customer A among customers A, B, C, and D, the target customer information of customer A obtained includes customer type: individual customer, channel type: company app, and the corresponding target personnel information includes personnel type: first-level salesperson, personnel qualification: fund qualification. The target customer information of customer A and the corresponding target personnel information hit the first trigger rule in the customer type dimension: individual customer, hit the second trigger rule in the channel type dimension: company app, hit the third trigger rule in the personnel type dimension: first-level salesperson, and hit the fourth trigger rule in the personnel qualification dimension: fund practitioner qualification. Therefore, the target trigger rules corresponding to the target customer information of customer A and the corresponding target personnel information include: the first trigger rule: individual customer, the second trigger rule: company app, the third trigger rule: first-level salesperson, and the fourth trigger rule: fund practitioner qualification. The multiple business relationship scenarios include the first business relationship scenario, the second business relationship scenario, the third business relationship scenario, and the fourth business relationship scenario. At least one trigger rule in the trigger rule pool corresponding to the third business relationship scenario includes: the first trigger rule: individual customer, the second trigger rule: company app, the third trigger rule: first-level salesperson, and the fourth trigger rule: fund practitioner qualification. Therefore, the target business relationship scenario determined according to the target trigger rules corresponding to the target customer information of customer A and the corresponding target personnel information is the third business relationship scenario.

[0079] It can be seen that in this example, multiple business relationship scenarios representing the correspondence between multiple trigger rule pools and multiple processing rule pools are configured through the terminal device, so that the server can determine the corresponding target business relationship scenario from multiple business relationship scenarios according to the target trigger rule corresponding to the target customer information and the target personnel information, and thus determine the target customer relationship corresponding to the target customer according to the processing rule pool indicated by the target business relationship scenario. Therefore, when the business and management requirements of the enterprise are adjusted, it is only necessary to reconfigure multiple business relationship scenarios to obtain customer relationships that meet the latest requirements. There is no need for business personnel to manually configure customer relationships based on manual judgment according to the latest business and management requirements, thereby reducing the cost of customer relationship management and improving the efficiency of customer relationship management.

[0080] In a possible embodiment, the target business relationship scenario is obtained by the server performing the following operations according to the target trigger rule: determining at least one business relationship scenario corresponding to the target customer according to the target trigger rule; and determining the relationship scenario with the highest corresponding scenario priority among the at least one business relationship scenario as the target business relationship scenario.

[0081] Among them, at least one trigger rule in the trigger rule pool corresponding to each business relationship scenario in the at least one business relationship scenario includes the target trigger rule.

[0082] Wherein, the scenario priority corresponding to each business relationship scenario in the at least one business relationship scenario is preconfigured.

[0083] It can be seen that in this example, multiple business relationship scenarios representing the correspondence between multiple trigger rule pools and multiple processing rule pools are configured through the terminal device, so that the server can determine at least one corresponding business relationship scenario from multiple business relationship scenarios according to the target trigger rules corresponding to the target customer information and the target personnel information, and then determine the target business relationship scenario from at least one business relationship scenario, so as to determine the target customer relationship corresponding to the target customer according to the processing rule pool indicated by the target business relationship scenario. Therefore, when the business and management requirements of the enterprise are adjusted, it is only necessary to reconfigure multiple business relationship scenarios to obtain customer relationships that meet the latest requirements, and there is no need for business personnel to manually configure customer relationships based on manual judgment according to the latest business and management requirements, thereby reducing the cost of customer relationship management and improving the efficiency of customer relationship management.

[0084] In a possible embodiment, the target customer relationship is obtained by the server performing the following operations: determining at least one target relationship processing logic according to a target processing rule pool, wherein the target processing rule pool is a processing rule pool corresponding to the target business relationship scenario, and at least one target processing rule in the target processing rule pool corresponds one-to-one to the at least one target relationship processing logic; generating a target relationship processing flow according to the at least one target relationship processing logic and the target customer information; and executing the target relationship processing flow to obtain the target customer relationship.

[0085] The at least one target processing rule corresponds one-to-one to at least one target relationship level, and the at least one target relationship level is at least one relationship level corresponding to the target customer in the target business relationship scenario.

[0086] Before the server generates a target relationship processing flow according to the at least one target relationship processing logic and the target customer information, the server also performs the following operations: generating at least one down-linking flow according to the at least one target relationship processing logic and the target customer information, wherein the at least one down-linking flow corresponds to the at least one relationship level one-to-one; executing the at least one down-linking flow so that each target relationship level in the at least one target relationship level is associated with a corresponding relevant person. Specifically, the first relationship level of customer A is associated with the first-level relevant person Q, the second relationship level is associated with the second-level relevant person W, and the third relationship level is associated with the third-level relevant person Y. The first-level relevant person Q, the second-level relevant person W, and the third-level relevant person Y can be public accounts with different permissions, and they can all view the customer relationship of customer A.

[0087] Wherein, before the server executes the target relationship processing flow and obtains the target customer relationship, the server also performs the following operations: S1: sending the target relationship processing flow to the business terminal device, so that the business terminal receives the approval operation of the business personnel on the target relationship processing flow and determines the approval result, and the approval result is pass or fail and the reason for failure; S2: receiving the approval result sent by the business terminal device; S3: when the approval result is fail, updating the target relationship processing flow according to the approval result, and repeatedly executing S1-S2 until the approval result is pass; when the approval result is pass, executing the target relationship processing flow to obtain the target customer relationship.

[0088] It can be seen that in this example, multiple business relationship scenarios representing the correspondence between multiple trigger rule pools and multiple processing rule pools are configured through the terminal device, so that the server can generate a target relationship processing process according to the processing rule pool indicated by the target business relationship scenario, thereby determining the target customer relationship corresponding to the target customer according to the target relationship processing process. Therefore, when the business and management requirements of the enterprise are adjusted, it is only necessary to reconfigure multiple business relationship scenarios to obtain customer relationships that meet the latest requirements. There is no need for business personnel to manually configure customer relationships based on the latest business and management requirements through manual judgment, thereby reducing the cost of customer relationship management and improving the efficiency of customer relationship management.

[0089] It can be seen that in the present application, the terminal device responds to the user's rule configuration operation and sends the rule configuration file indicated by the rule configuration operation to the server, so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file, and the rule configuration operation includes an input operation for the rule configuration operation box in the first interface, and the multiple trigger rules in the multiple trigger rule pools are used to classify the business relationship of the customer, and the multiple processing rules in the multiple processing rule pools are used to perform business relationship processing on the customer; receiving multiple trigger rule pools and multiple processing rule pools sent by the server; responding to the user's scenario configuration operation, determining multiple business relationship scenarios, the scenario configuration operation includes an input operation for the scenario configuration operation box in the second interface, and the multiple business relationship scenarios are used to characterize the correspondence between multiple trigger rule pools and multiple processing rule pools; sending multiple business relationship scenarios to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, and the target customer relationship is used to characterize the association relationship between the target customer and the corresponding target-related personnel. Since multiple business relationship scenarios representing the correspondence between multiple trigger rule pools and multiple processing rule pools are configured through the terminal device, the server can determine the target customer relationship corresponding to the target customer according to the processing rule pool indicated by the target business relationship scenario corresponding to the target customer. Therefore, when the business and management requirements of the enterprise are adjusted, it is only necessary to reconfigure multiple business relationship scenarios to obtain customer relationships that meet the latest requirements. There is no need for business personnel to manually configure customer relationships based on manual judgment according to the latest business and management requirements, thereby reducing the cost of customer relationship management and improving the efficiency of customer relationship management.

[0090] The above mainly introduces the scheme of the embodiment of the present application from the perspective of the execution process on the method side. It is understandable that, in order to realize the above functions, the controller includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiment provided herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

[0091] In accordance with the above-mentioned embodiment, please refer to Figure 8 , Figure 8 is a block diagram of the functional units of a data processing device for customer relationship management provided by an embodiment of the present application, such as Figure 8As shown, the data processing device 800 for customer relationship management includes: a first processing unit 801, which is used to respond to the user's rule configuration operation and send the rule configuration file indicated by the rule configuration operation to the server, so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file, wherein the rule configuration operation includes an input operation for the rule configuration operation box in the first interface, the multiple trigger rules in the multiple trigger rule pools are used to classify the business relationship of the customer, and the multiple processing rules in the multiple processing rule pools are used to process the business relationship of the customer; a first receiving unit 802, which is used to receive the multiple trigger rule pools sent by the server. A trigger rule pool and the multiple processing rule pools; a second processing unit 803, used to respond to the user's scenario configuration operation, determine multiple business relationship scenarios, the scenario configuration operation includes an input operation for the scenario configuration operation box in the second interface, and the multiple business relationship scenarios are used to characterize the correspondence between the multiple trigger rule pools and the multiple processing rule pools; send the multiple business relationship scenarios to the server, so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, and the target customer relationship is used to characterize the association relationship between the target customer and the corresponding target-related personnel.

[0092] In a possible embodiment, the rule configuration file includes sample customer information of multiple sample customers and sample personnel information and sample customer relationships of sample personnel corresponding to each sample customer in the multiple sample customers, the sample customer relationships are used to indicate the association relationship between the corresponding sample customer and the relevant personnel in each relationship level in the corresponding at least one relationship level, and in response to the user's rule configuration operation, in sending the rule configuration file indicated by the rule configuration operation to the server so that the server determines multiple trigger rule pools and multiple processing rule pools according to the rule configuration file, the first processing unit 801 is specifically used to: respond to the user's rule configuration operation, send the rule configuration file indicated by the rule configuration operation to the server so that the server performs the following operations: receive the rule configuration file; Determine a plurality of atomic-level elements corresponding to each trigger dimension in at least one trigger dimension based on the sample customer information and the corresponding sample personnel information of each sample customer; determine a trigger rule pool corresponding to each sample customer based on the plurality of atomic-level elements corresponding to each trigger dimension in the at least one trigger dimension, and obtain the plurality of trigger rule pools, each of the plurality of trigger rule pools including at least one trigger rule, and the at least one trigger rule corresponds one-to-one to the at least one trigger dimension; determine a processing rule pool corresponding to each sample customer based on the sample customer relationship corresponding to each sample customer, and obtain the plurality of processing rule pools, each of the plurality of processing rule pools including at least one processing rule, and the at least one processing rule corresponds one-to-one to at least one relationship level corresponding to each sample customer.

[0093] In a possible embodiment, the scenario configuration operation box includes multiple scenario name input boxes, multiple trigger rule pool configuration boxes and multiple processing rule pool configuration boxes, the multiple scenario name input boxes correspond one-to-one to the multiple trigger rule pool configuration boxes, and the multiple scenario name input boxes correspond one-to-one to the multiple processing rule pool configuration boxes. In terms of responding to the user's scenario configuration operation and determining multiple business relationship scenarios, the second processing unit 803 is specifically used to: respond to the user's input operation on the multiple scenario name input boxes to determine multiple business relationship scenario names; respond to the user's input operation on the multiple trigger rule pool configuration boxes to determine the trigger rule pools corresponding to the multiple business relationship scenario names; respond to the user's input operation on the multiple processing rule pool configuration boxes to determine the processing rule pools corresponding to the multiple business relationship scenario names; determine the multiple business relationship scenarios according to the multiple business relationship scenario names and the trigger rule pools and processing rule pools corresponding to the multiple business relationship scenario names.

[0094] In a possible embodiment, in terms of sending the multiple business relationship scenarios to the server so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenarios corresponding to the target customer, the second processing unit 803 is specifically used to: send the multiple business relationship scenarios to the server so that the server performs the following operations: obtain target customer information of the target customer and target personnel information of the target personnel corresponding to the target customer; determine a target business relationship scenario according to the target customer information, the target personnel information and the multiple business relationship scenarios, the target business relationship scenario is used to characterize the business relationship scenario corresponding to the target customer; determine a target customer relationship according to the target customer information, the target personnel information and the target business relationship scenario; update a customer relationship storage table according to the target customer relationship, so that the target customer relationship is stored in the customer relationship storage table, and the customer relationship storage table is used to store the association relationship between all customers and all personnel.

[0095] In a possible embodiment, the target business relationship scenario is obtained by the server performing the following operations: determining a target trigger rule corresponding to the target customer information and the target personnel information, the target trigger rule being a trigger rule in a pool of multiple trigger rules corresponding to the multiple business relationship scenarios hit by the target customer information and the target personnel information; and determining the target business relationship scenario based on the target trigger rule.

[0096] In a possible embodiment, the target business relationship scenario is obtained by the server performing the following operations according to the target trigger rule: determining at least one business relationship scenario corresponding to the target customer according to the target trigger rule; and determining the relationship scenario with the highest corresponding scenario priority among the at least one business relationship scenario as the target business relationship scenario.

[0097] In a possible embodiment, the target customer relationship is obtained by the server performing the following operations: determining at least one target relationship processing logic according to a target processing rule pool, wherein the target processing rule pool is a processing rule pool corresponding to the target business relationship scenario, and at least one target processing rule in the target processing rule pool corresponds one-to-one to the at least one target relationship processing logic; generating a target relationship processing flow according to the at least one target relationship processing logic and the target customer information; and executing the target relationship processing flow to obtain the target customer relationship.

[0098] It can be understood that since the method embodiment and the device embodiment are different presentation forms of the same technical concept, the content of the method embodiment part in this application should be synchronously adapted to the device embodiment part and will not be repeated here.

[0099] In the case of an integrated unit, such as Fig. 9 As shown, Fig. 9 This is a block diagram of the functional units of another data processing device for customer relationship management provided by an embodiment of the present application. Fig. 9 In the embodiment, the data processing device 800 for customer relationship management includes: a processing module 912 and a communication module 911. The processing module 912 is used to control and manage the actions of the data processing device 800 for customer relationship management, for example, to execute the steps of the first processing unit 801, the first receiving unit 802 and the second processing unit 803, and / or to execute other processes of the technology described herein. The communication module 911 is used to support the interaction between the data processing device 800 for customer relationship management and other devices. Fig. 9 As shown, the data processing device 800 for customer relationship management may further include a storage module 913, and the storage module 913 is used to store program codes and data of the data processing device 800 for customer relationship management.

[0100] Among them, the processing module 912 can be a processor or a controller, for example, a central processing unit (CPU), a general processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements a computing function, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The communication module 911 can be a transceiver, an RF circuit or a communication interface, and the like. The storage module 913 can be a memory.

[0101] All relevant contents of each scenario involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here. Figure 4 The data processing method for customer relationship management is shown.

[0102] The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination thereof. When implemented using software, the above embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media sets. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium may be a solid-state hard disk.

[0103] Fig.10 is a structural block diagram of a terminal device provided in an embodiment of the present application. Fig.10 As shown, the terminal device 120 may include one or more of the following components: a processor 310, and a memory 320 coupled to the processor 310, wherein the memory 320 may store one or more computer programs 321, and the one or more computer programs 321 may be configured to implement the methods described in the above embodiments when executed by one or more processors 310.

[0104] The processor 310 may include one or more processing cores. The processor 310 uses various interfaces and lines to connect various parts of the entire terminal device 120, and executes various functions and processes data of the terminal device 120 by running or executing instructions, programs, code sets or instruction sets stored in the memory 320, and calling data stored in the memory 320. Optionally, the processor 310 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 310 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 310, but may be implemented separately through a communication chip.

[0105] The memory 320 may include a random access memory (RAM) or a read-only memory (ROM). The memory 320 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 320 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc. The data storage area may also store data created by the terminal device 120 during use, etc.

[0106] It is understandable that the terminal device 120 may include more or fewer structural elements than those in the above structural block diagram, which is not limited here. The embodiment of the present application provides a computer-readable storage medium on which a computer program / instruction is stored, and when the computer program / instruction is executed by a processor, the steps of the method described in any possible embodiment are implemented.

[0107] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0108] In the several embodiments provided in the present application, it should be understood that the disclosed methods, devices and systems can be implemented in other ways. For example, the device embodiments described above are merely schematic; for example, the division of the unit is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0109] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0110] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0111] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform some steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a volatile memory or a non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM) and direct RAM bus random access memory (DR RAM), among other media that can store program code.

[0112] Although the present invention is disclosed as above, the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions without departing from the spirit and scope of the present invention, and can make various changes and modifications, including the combination of the above-mentioned different functions and implementation steps, including software and hardware implementation methods, all of which are within the scope of protection of the present invention.

Claims

1. A data processing method for customer relationship management, characterized in that: A terminal device applied to a customer relationship management system, wherein the customer relationship management system comprises the terminal device and a server, and the method comprises: In response to a rule configuration operation of a user, a rule configuration file indicated by the rule configuration operation is sent to the server, so that the server determines a plurality of trigger rule pools and a plurality of processing rule pools according to the rule configuration file, wherein the rule configuration operation includes an input operation for a rule configuration operation box in the first interface, a plurality of trigger rules in the plurality of trigger rule pools are used to classify business relationships for customers, and a plurality of processing rules in the plurality of processing rule pools are used to process business relationships for customers; receiving the multiple trigger rule pools and the multiple processing rule pools sent by the server; In response to a scenario configuration operation of the user, determining a plurality of business relationship scenarios, wherein the scenario configuration operation includes an input operation for a scenario configuration operation box in the second interface, and the plurality of business relationship scenarios are used to characterize a correspondence between the plurality of trigger rule pools and the plurality of processing rule pools; Sending the multiple business relationship scenarios to the server, so that the server determines a target customer relationship corresponding to the target customer according to a processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, wherein the target customer relationship is used to characterize an association relationship between the target customer and a corresponding target-related person; The rule configuration file includes sample customer information of a plurality of sample customers and sample personnel information and sample customer relationships of sample personnel corresponding to each sample customer among the plurality of sample customers, wherein the sample customer relationship is used to indicate the association relationship between the corresponding sample customer and the relevant personnel in each relationship level in the corresponding at least one relationship level, and the rule configuration file indicated by the rule configuration operation is sent to the server in response to the user's rule configuration operation, so that the server determines a plurality of trigger rule pools and a plurality of processing rule pools according to the rule configuration file, including: responding to the user's rule configuration operation, sending the rule configuration file indicated by the rule configuration operation to the server, so that the server performs the following operations: receiving the rule configuration file; determining the trigger rule pools and the processing rule pools according to the sample personnel of each sample customer; Determine multiple atomic-level elements corresponding to each trigger dimension in at least one trigger dimension based on the present customer information and the corresponding sample personnel information; determine the trigger rule pool corresponding to each sample customer based on the multiple atomic-level elements corresponding to each trigger dimension in the at least one trigger dimension, and obtain the multiple trigger rule pools, each of the multiple trigger rule pools including at least one trigger rule, and the at least one trigger rule corresponds one-to-one to the at least one trigger dimension; determine the processing rule pool corresponding to each sample customer based on the sample customer relationship corresponding to each sample customer, and obtain the multiple processing rule pools, each of the multiple processing rule pools including at least one processing rule, and the at least one processing rule corresponds one-to-one to at least one relationship level corresponding to each sample customer; Among them, the method of determining multiple atomic-level elements corresponding to each trigger dimension in at least one trigger dimension based on the sample customer information and the corresponding sample personnel information of each sample customer includes splitting the customer type, channel type, personnel type, and personnel qualification information included in the sample customer information and the corresponding sample personnel information of each sample customer into atomic-level elements through rule classification to obtain the multiple atomic-level elements.

2. The method according to claim 1, characterized in that The scenario configuration operation box includes multiple scenario name input boxes, multiple trigger rule pool configuration boxes and multiple processing rule pool configuration boxes, the multiple scenario name input boxes correspond one-to-one to the multiple trigger rule pool configuration boxes, the multiple scenario name input boxes correspond one-to-one to the multiple processing rule pool configuration boxes, and the multiple business relationship scenarios are determined in response to the scenario configuration operation of the user, including: In response to the user's input operation on the multiple scene name input boxes, determining multiple business relationship scene names; In response to the user's input operation on the multiple trigger rule pool configuration boxes, determining the trigger rule pools corresponding to the multiple business relationship scenario names; In response to the user's input operation on the multiple processing rule pool configuration boxes, determining the processing rule pools corresponding to the multiple business relationship scenario names; The multiple business relationship scenarios are determined according to the multiple business relationship scenario names and the trigger rule pools and processing rule pools corresponding to the multiple business relationship scenario names.

3. The method according to claim 2, characterized in that The sending the multiple business relationship scenarios to the server so that the server determines the target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, includes: Sending the multiple business relationship scenarios to the server so that the server performs the following operations: Acquire target customer information of the target customer and target personnel information of the target personnel corresponding to the target customer; Determine a target business relationship scenario according to the target customer information, the target personnel information and the multiple business relationship scenarios, wherein the target business relationship scenario is used to characterize the business relationship scenario corresponding to the target customer; Determine a target customer relationship according to the target customer information, the target personnel information and the target business relationship scenario; The customer relationship storage table is updated according to the target customer relationship, so that the target customer relationship is stored in the customer relationship storage table, and the customer relationship storage table is used to store the association relationship between all customers and all personnel.

4. The method according to claim 3, characterized in that The target business relationship scenario is obtained by the server performing the following operations: Determine a target trigger rule corresponding to the target customer information and the target personnel information, wherein the target trigger rule is a trigger rule in a plurality of trigger rule pools corresponding to the plurality of business relationship scenarios hit by the target customer information and the target personnel information; The target business relationship scenario is determined according to the target trigger rule.

5. The method according to claim 4, characterized in that The target business relationship scenario is obtained by the server performing the following operations according to the target trigger rule: Determine at least one business relationship scenario corresponding to the target customer according to the target trigger rule; The relationship scenario with the highest corresponding scenario priority among the at least one business relationship scenario is determined as the target business relationship scenario.

6. The method according to claim 5, characterized in that The target customer relationship is obtained by the server performing the following operations: Determine at least one target relationship processing logic according to a target processing rule pool, wherein the target processing rule pool is a processing rule pool corresponding to the target business relationship scenario, and at least one target processing rule in the target processing rule pool corresponds one-to-one to the at least one target relationship processing logic; generating a target relationship processing flow according to the at least one target relationship processing logic and the target customer information; The target relationship processing flow is executed to obtain the target customer relationship.

7. A data processing device for customer relationship management, characterized in that: A terminal device applied to a customer relationship management system, wherein the customer relationship management system comprises the terminal device and a server, and the apparatus comprises: A first processing unit is configured to respond to a rule configuration operation of a user and send a rule configuration file indicated by the rule configuration operation to the server, so that the server determines a plurality of trigger rule pools and a plurality of processing rule pools according to the rule configuration file, wherein the rule configuration operation includes an input operation for a rule configuration operation box in the first interface, a plurality of trigger rules in the plurality of trigger rule pools are used to classify business relationships of customers, and a plurality of processing rules in the plurality of processing rule pools are used to process business relationships of customers; A first receiving unit, configured to receive the multiple trigger rule pools and the multiple processing rule pools sent by the server; a second processing unit, configured to respond to a scenario configuration operation of the user, determine a plurality of business relationship scenarios, wherein the scenario configuration operation includes an input operation for a scenario configuration operation box in the second interface, and the plurality of business relationship scenarios are used to characterize the correspondence between the plurality of trigger rule pools and the plurality of processing rule pools; and send the plurality of business relationship scenarios to the server, so that the server determines a target customer relationship corresponding to the target customer according to the processing rule pool corresponding to the target business relationship scenario corresponding to the target customer, and the target customer relationship is used to characterize the association relationship between the target customer and the corresponding target-related personnel; The rule configuration file includes sample customer information of a plurality of sample customers and sample personnel information and sample customer relationships of sample personnel corresponding to each sample customer among the plurality of sample customers, wherein the sample customer relationship is used to indicate the association relationship between the corresponding sample customer and the relevant personnel in each relationship level in the corresponding at least one relationship level, and the rule configuration file indicated by the rule configuration operation is sent to the server in response to the user's rule configuration operation, so that the server determines a plurality of trigger rule pools and a plurality of processing rule pools according to the rule configuration file, including: responding to the user's rule configuration operation, sending the rule configuration file indicated by the rule configuration operation to the server, so that the server performs the following operations: receiving the rule configuration file; determining the trigger rule pools and the processing rule pools according to the sample personnel of each sample customer; Determine multiple atomic-level elements corresponding to each trigger dimension in at least one trigger dimension based on the present customer information and the corresponding sample personnel information; determine the trigger rule pool corresponding to each sample customer based on the multiple atomic-level elements corresponding to each trigger dimension in the at least one trigger dimension, and obtain the multiple trigger rule pools, each of the multiple trigger rule pools including at least one trigger rule, and the at least one trigger rule corresponds one-to-one to the at least one trigger dimension; determine the processing rule pool corresponding to each sample customer based on the sample customer relationship corresponding to each sample customer, and obtain the multiple processing rule pools, each of the multiple processing rule pools including at least one processing rule, and the at least one processing rule corresponds one-to-one to at least one relationship level corresponding to each sample customer; Among them, the method of determining multiple atomic-level elements corresponding to each trigger dimension in at least one trigger dimension based on the sample customer information and the corresponding sample personnel information of each sample customer includes splitting the customer type, channel type, personnel type, and personnel qualification information included in the sample customer information and the corresponding sample personnel information of each sample customer into atomic-level elements through rule classification to obtain the multiple atomic-level elements.

8. A terminal device, characterized in that: The method comprises a processor, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for executing the steps in the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: A computer program / instruction is stored thereon, and when the computer program / instruction is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images