CN117217448A - Customer relationship distribution method, device, equipment and readable storage medium - Google Patents
Customer relationship distribution method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN117217448A CN117217448A CN202311101800.8A CN202311101800A CN117217448A CN 117217448 A CN117217448 A CN 117217448A CN 202311101800 A CN202311101800 A CN 202311101800A CN 117217448 A CN117217448 A CN 117217448A
- Authority
- CN
- China
- Prior art keywords
- client
- enterprise
- customer
- target
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 55
- 238000001514 detection method Methods 0.000 claims description 38
- 230000004044 response Effects 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 27
- 238000010586 diagram Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 6
- 239000008186 active pharmaceutical agent Substances 0.000 description 5
- 238000011156 evaluation Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000012015 optical character recognition Methods 0.000 description 2
- 238000012552 review Methods 0.000 description 2
- 238000009736 wetting Methods 0.000 description 2
- BQCADISMDOOEFD-UHFFFAOYSA-N Silver Chemical compound [Ag] BQCADISMDOOEFD-UHFFFAOYSA-N 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000007788 liquid Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000004801 process automation Methods 0.000 description 1
- 229910052709 silver Inorganic materials 0.000 description 1
- 239000004332 silver Substances 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Abstract
The application discloses a client relationship distribution method, a device, equipment and a readable storage medium, which relate to the technical field of financial management and comprise the following steps: responding to a service access request sent by a client, and acquiring client information according to the service access request, wherein the client information at least comprises a client identifier and an enterprise identifier; acquiring a client allocation rule according to the service access request, and allocating a target client manager account based on the client allocation rule and the client information, wherein the client allocation rule comprises allocation according to a management relationship, allocation according to a park relationship and flow balance allocation; and acquiring an identification code associated with the target customer manager account and displaying the identification code. The application realizes the intelligent automatic distribution of the client relationship.
Description
Technical Field
The present application relates to the field of financial management technologies, and in particular, to a method, an apparatus, a device, and a readable storage medium for distributing a customer relationship.
Background
Typically, banks distribute customers with customer managers to provide related services such as financial product consultation services, investment financial scheme recommendation services, etc. However, at present, when a bank distributes a customer manager for a customer, the customer manager is manually distributed for the customer to provide services, the distribution mode of manually distributing the customer relationship consumes labor cost, the workload of distributing the customer relationship is huge, the adjustment of the customer relationship can be related every day, the service is heavy, and the labor cost and the time cost are extremely high.
In summary, how to implement intelligent automatic distribution of customer relationships has become a major technical problem to be solved in the art.
Disclosure of Invention
The application mainly aims to provide a client relationship distribution method, equipment and a readable storage medium, which aim to solve the technical problem of how to realize intelligent automatic distribution of client relationships.
To achieve the above object, the present application provides a method for distributing customer relations, comprising the steps of:
responding to a service access request sent by a client, and acquiring client information according to the service access request, wherein the client information at least comprises a client identifier and an enterprise identifier;
acquiring a client allocation rule according to the service access request, and allocating a target client manager account based on the client allocation rule and the client information, wherein the client allocation rule comprises allocation according to a management relationship, allocation according to a park relationship and flow balance allocation;
and acquiring an identification code associated with the target customer manager account and displaying the identification code.
Optionally, the step of assigning the target customer manager account based on the customer assignment rule and the customer information includes:
If the client allocation rule comprises allocation according to a management relationship, detecting whether a target enterprise identifier matched with the enterprise identifier exists in a preset legal enterprise service table or not;
if the target enterprise identifier exists, determining a first customer manager account associated with the target enterprise identifier;
and taking the first customer manager account as a target customer manager account.
Optionally, the client information further includes a current geographic location and a current time, and the step of assigning a target client manager account based on the client assignment rule and the client information includes:
if the client allocation rule includes allocation according to a park relation, determining a target service node meeting preset conditions in all preset service nodes, wherein the preset conditions include: the distance between the network point position of the service network point and the current geographic position is smaller than the preset distance, and the current time is within the business time of the service network point;
and determining a second customer manager account number associated with the target service network point, and taking the second customer manager account number as a target customer manager account number.
Optionally, the step of assigning the target customer manager account based on the customer assignment rule includes:
If the client allocation rule comprises balanced allocation according to the flow, acquiring the added client quantity of each preset default client manager account;
and determining the minimum added client quantity in the added client quantities, and taking a preset default client manager account corresponding to the minimum added client quantity as a target client manager account.
Optionally, after the step of displaying the identification code, the method further includes:
if the client monitors a friend adding request sent by the client based on the identification code, carrying out validity detection on the client information according to the friend adding request to obtain a validity detection result;
and if the validity detection result is that the detection is passed, storing the client identifier and the enterprise identifier in a preset client enterprise table in a correlation way.
Optionally, the step of performing validity detection on the client information according to the friend adding request to obtain a validity detection result includes:
detecting whether a target enterprise identifier matched with the enterprise name identifier exists in a preset legal enterprise service table;
if the target enterprise identifier does not exist, detecting whether an account opening enterprise identifier matched with the enterprise identifier exists in a preset account opening enterprise list;
If the account opening enterprise identifier exists, detecting the account opening enterprise identifier as a validity detection result corresponding to the client information.
Optionally, after the step of storing the customer identifier and the enterprise identifier in a preset customer enterprise table, the method further includes:
inquiring whether a task to be pushed exists in a task list to be pushed, and if the task to be pushed exists, acquiring a pushing enterprise identifier and pushing content of the task to be pushed;
determining a target pushing enterprise identifier matched with the pushing enterprise identifier in a preset client enterprise list, and determining a target client identifier corresponding to the target pushing enterprise identifier in the preset client enterprise list;
and determining a target client corresponding to the target client identifier, and pushing the push content to the target client.
In addition, to achieve the above object, the present application also provides a customer relationship distribution apparatus, including:
the response module is used for responding to a service access request sent by the client and acquiring client information according to the service access request, wherein the client information at least comprises a client identifier and an enterprise identifier;
the distribution module is used for acquiring a client distribution rule according to the service access request, and distributing a target client manager account based on the client distribution rule and the client information, wherein the client distribution rule comprises distribution according to a management relationship, distribution according to a park relationship and flow balance distribution;
And the display module is used for acquiring the identification code associated with the target customer manager account and displaying the identification code.
In addition, to achieve the above object, the present application also provides a customer relationship allocation apparatus, including: the system comprises a memory, a processor and a client relationship allocation program stored in the memory and capable of running on the processor, wherein the client relationship allocation program realizes the steps of the client relationship allocation method when being executed by the processor.
In addition, in order to achieve the above object, the present application provides a readable storage medium, on which a client relationship allocation program is stored, which when executed by a processor, implements the steps of the client relationship allocation method as described above.
According to the method, the client information is obtained according to the service access request sent by the client, wherein the client information at least comprises a client identifier and an enterprise identifier; acquiring a client allocation rule according to the service access request, and allocating a target client manager account based on the client allocation rule and the client information, wherein the client allocation rule comprises allocation according to a management relationship, allocation according to a park relationship and flow balance allocation; and acquiring an identification code associated with the target customer manager account and displaying the identification code. In this way, compared with the client relationship distribution mode of manually distributing client managers in the prior art, in the embodiment of the application, the account number of the client manager is automatically distributed according to the client information and the client distribution rule by acquiring the client information and the client distribution rule, and the identification code associated with the account number is displayed, so that the client corresponding to the client is distributed to the client manager corresponding to the identification code, and the intelligent automatic distribution of the client relationship is realized.
Drawings
The achievement of the objects, functional features and advantages of the present application will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
FIG. 1 is a schematic diagram of a terminal/device structure of a hardware operating environment according to an embodiment of the present application;
FIG. 2 is a flowchart of a first embodiment of a client relationship allocation method according to the present application;
FIG. 3 is a schematic diagram of the overall architecture of the service architecture of the present application;
FIG. 4 is a schematic diagram of a service scenario of the service architecture of the present application;
FIG. 5 is a schematic diagram of a single-code customer relationship assignment flow in accordance with the present application;
FIG. 6 is a schematic diagram of a group code customer relationship assignment flow in accordance with the present application;
FIG. 7 is a flow chart of a customer relationship assignment method according to the present application;
FIG. 8 is a schematic diagram of a login authorization process in the client relationship assignment method of the present application;
FIG. 9 is a schematic diagram of an active hosting flow in a customer relationship distribution method according to the present application;
FIG. 10 is a schematic diagram of a device module of the customer relationship assignment device of the present application.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a customer relationship allocation device of a hardware running environment according to an embodiment of the present application.
As shown in fig. 1, the customer relationship assignment apparatus may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a high-speed random access Memory (Random Access Memory, RAM) Memory or a stable nonvolatile Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
Those skilled in the art will appreciate that the structure shown in fig. 1 is not limiting of the customer relationship dispensing apparatus and may include more or fewer components than shown, or may combine certain components, or may be a different arrangement of components.
As shown in fig. 1, an operating system, a data storage module, a network communication module, a user interface module, and a customer relationship assignment program may be included in the memory 1005 as one type of storage medium.
In the customer relationship assignment apparatus shown in fig. 1, the network interface 1004 is mainly used for data communication with other apparatuses; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the customer relationship allocation apparatus of the present application may be provided in the customer relationship allocation apparatus, which calls the customer relationship allocation program stored in the memory 1005 through the processor 1001 and executes the customer relationship allocation method provided by the embodiment of the present application.
Referring to fig. 2, fig. 2 is a flowchart illustrating a first embodiment of a client relationship allocation method according to the present application. It should be noted that although a logical order is depicted in the flowchart, in some cases the steps depicted or described may be performed in a different order than presented herein.
In this embodiment, the client relationship allocation method of the present application is applied to the terminal device described above. It should be understood that the client relationship allocation method of the present application may of course be applied specifically to other terminal devices in different possible embodiments, based on different design requirements of the actual application.
As shown in fig. 2, in this embodiment, the client relationship allocation method includes the following steps:
step S10, responding to a service access request sent by a client, and acquiring client information according to the service access request, wherein the client information at least comprises a client identifier and an enterprise identifier;
referring to fig. 3, a service architecture is constructed based on enterprise WeChat and service capability, and the service architecture is composed of personal WeChat, enterprise WeChat of other enterprises, enterprise WeChat management system of the present line and wholesale CRM+ (Customer Relationship Management ). The roles of accessing the service architecture include accessing and managing wholesale CRM for clients, client manager, manager and CRM, wherein CRM can access and manage wholesale CRM, including enterprise micro-platform management and basic service functions, client manager and manager can log in an enterprise micro-letter management system in a row, including log-in authentication, communication management, application management, session data management and other work functions, after the secondary authentication of the enterprise micro-letter management system in the row passes, the enterprise micro-letter can be logged in, enterprise micro-API (Application Program Interface) and enterprise micro-basic application can be called after the enterprise micro-letter is logged in, third party application (such as Tengyin provider) and self-built application (such as CRM self-built developed application) can be further called through enterprise micro-API, and the self-built application can access enterprise micro-API. The service architecture can provide corresponding services through personal or enterprise WeChat of the client. The third party application includes saas (Software-as-a-service) service of deep ploughing scene, and the self-built application meets the requirement of enterprise personalized development and can be communicated with an internal system of the enterprise. In terms of data layers, data within the service architecture, such as Tengyin return data, enterprise micro return data, CRM self-building application data, etc., may be stored in a data warehouse and/or platform, such as a fire eye platform.
The service architecture focuses on the construction of customer operation capability and channel service capability, realizes the closed-loop construction of five links from customer expansion, customer portraits, marketing content and service support to customer operation of relation evaluation, supports channel capability such as unified login authentication, application access service, customer manager access, customer access and the like, and enables the power-assisted service scene to be accessed efficiently. Referring to fig. 4, the service architecture includes a channel layer, a business service, an external service and a cloud studio management and control specification, the channel layer includes a client (such as personal WeChat of the client), a client manager (such as enterprise WeChat of the client manager), a comprehensive manager (such as wholesale crm+ of the comprehensive manager), and the business service includes client expansion, client portrait, marketing content, service support and relationship evaluation, cloud studio basic service and the like. The client expansion supports the functions of personal studio, client authentication, batch adding (batch client adding enterprise WeChat), welcome push, inheritance management and the like. Customer portrayal includes portrayal content such as customer information, customer (identification), contact view, customer tag, etc. Customer marketing supports active service, activity management, node care and other functions, and can also provide business treasure boxes, talk files and the like. The service support comprises intelligent questions and answers, business notification, enterprise new knowledge, product click through and the like. The relationship evaluation can be performed based on data such as a fire hole source, a fire hole report, background statistics and the like, and the evaluation result can be stored in the relationship evaluation. The cloud stem studio base services comprise services such as unified login authentication, customer contact support, customer manager contact, application access service and the like. External services are provided through enterprise micro-server APIs, enterprise micro-client APIs, weChat services, tengyinsaas, enterprise WeChat management systems and the like. The cloud studio management and control specifications comprise management and control of various specifications such as user access specifications, application access specifications, development access specifications and the like.
In an actual scene, corresponding service two-dimension codes can be posted or placed in corresponding areas of the actual scene, such as a bank gate, a bank counter, a customer waiting area and the like, and when a customer has a service requirement, a service access request can be initiated by scanning the service two-dimension codes, wherein the service two-dimension code types comprise single codes, group codes and multi-person codes.
Optionally, each single code is associated with a customer manager account, where the customer manager account may be a corporation's WeChat account of the customer manager, each customer manager account uniquely corresponds to a customer manager identifier, such as a customer manager name, and each customer manager account uniquely associates an identification code, such as a corporation's WeChat two-dimensional code. Referring to fig. 5, a single code of an active person is generated based on an enterprise WeChat [ contact me ] interface, and when a client scans the single code, a request type of a service access request sent by the client is a single service access request, and the client can be a handheld terminal of the client, such as a mobile phone, a tablet, and the like. After the client scans the single code, the identification code of the client manager account associated with the single code, such as an enterprise Wednesday two-dimensional code associated with the client manager account, is displayed, whether the client scans the initiation friend adding event of the identification code adding service personnel is monitored, namely whether the client initiates the friend adding event based on the identification code is monitored, and when the client scans the identification code, the enterprise micro friend adding event is triggered. And calling a bank registration interface to monitor an enterprise micro-friend adding event, analyzing enterprise micro-encryption data after the enterprise micro-friend adding event is monitored, and sending welcome to a client and processing summarized micro-addition data after the friend adding is successful, wherein the micro-addition data can comprise data such as a client manager identifier and the like, wherein the client name corresponds to a client manager account added by a client, and the data can be obtained through an enterprise micro-interface.
The group code is similar to a single code, but the monitoring process of the group code adopts a timing synchronization strategy, and the condition that clients in enterprises and micro are in the group is identified and processed. Referring to fig. 6, an enterprise micro interface may be called to generate a group two-dimensional code, after a customer scans the group code, the customer is pulled into the enterprise micro group to realize enterprise micro group entry of the customer, and synchronous enterprise micro group information of the group entry condition is scheduled to be acquired, personnel entering the group by the system group code are identified, and summary group entry data is processed.
When it is detected that the client scans the multi-person code, step S10 is executed, and the client can fill in the enterprise information of the enterprise where the client is located after scanning the multi-person code, where the enterprise information includes, but is not limited to, enterprise identification, for example, an enterprise address, an enterprise unified credit code, whether the enterprise has been opened, and the like, where the enterprise identification is used for uniquely identifying an enterprise, and may be an enterprise name. After the client is filled, the enterprise information filled by the client can be obtained, specifically, the enterprise identifier (i.e. the enterprise identifier of the enterprise where the client is located) can be obtained, and the client information includes, but is not limited to, the enterprise identifier and the client identifier, for example, the client identifier can also include the current geographic position, the current time, the micro signal, the mobile phone number and the like, and the client identifier is used for uniquely identifying a client and can be a client name.
Step S20, acquiring a client allocation rule according to the service access request, and allocating a target client manager account based on the client allocation rule and the client information, wherein the client allocation rule comprises allocation according to a management relationship, allocation according to a park relationship and allocation according to flow balance;
the client allocation rule can be preset and stored, and the client allocation rule can be obtained after the client scans the multi-person code to initiate the service access request. The allocation rule can include one or more of allocation according to a management relationship, allocation according to a residence relationship and allocation according to flow balance, when a plurality of allocation modes exist, the allocation priority of each allocation mode can be preset, after the allocation of the allocation mode with high priority fails, the allocation is performed in the allocation mode with low priority, namely, when the allocation of the client relationship is successful, the allocation is finished, and when the allocation of the client relationship fails, the allocation of the client relationship is performed again according to the priority sequence. The client relationship allocation generation means that the target client manager account is successfully allocated, otherwise, the client relationship allocation fails.
It should be noted that, the customer manager account may be a unique system account pre-assigned to each customer manager, where each customer manager account uniquely corresponds to a customer manager identifier, where the customer manager identifier is used to uniquely identify a customer manager, for example, may be a customer manager name, and each customer manager account uniquely associates an identification code, such as a dynamic code, an enterprise WeChat two-dimensional code, or the like.
In a possible embodiment, the step of allocating the target customer manager account to the customer allocation rule and the customer information includes:
step A10, if the client allocation rule comprises allocation according to a management relationship, detecting whether a target enterprise identifier matched with the enterprise identifier exists in a preset legal enterprise service table;
step A20, if the target enterprise identifier exists, determining a first customer manager account associated with the target enterprise identifier;
and step A30, taking the first customer manager account as a target customer manager account.
In this embodiment, the allocation flow according to the management relationship may be as follows: detecting whether a target enterprise identifier matched with the enterprise identifier exists in a preset legal enterprise service table, wherein the preset legal enterprise service table is enterprise identifiers of all enterprises which provide services for the enterprise service table and comprises silver behaviors, if the target enterprise identifier exists, executing step S30, if the target enterprise identifier does not exist, further detecting whether the enterprise identifier exists an enterprise list with preset account opening, and if the preset account opening enterprise list is the enterprise identifier of all enterprises which have performed account opening at a bank, determining that allocation according to a management relationship fails. If the enterprise identifier exists in the preset account opening enterprise list, whether the enterprise (enterprise corresponding to the enterprise identifier) is associated with a customer manager account for providing service for the enterprise is detected, if the enterprise is associated with the customer manager account for providing service for the enterprise, the customer manager account is used as a target customer manager account, and if the enterprise is not associated with the customer manager account for providing service for the enterprise, the allocation failure according to the management relationship is determined.
Further, if there are multiple first customer manager accounts associated with the target enterprise identifier, a wetting proportion of each first customer manager account may be obtained, and one customer manager account with the highest wetting proportion is selected as the target customer manager account.
In this embodiment, the enterprise identifier according to the client information is automatically allocated to the target client manager account, so that the client manager account is allocated to the enterprise identifier according to the enterprise identifier, and compared with a private allocation mode of a client relationship pair in which an individual client identifier is used as a direct allocation main body, the embodiment allocates the client manager by using the enterprise identifier as the direct allocation main body, thereby realizing public allocation of the client relationship.
In a possible embodiment, the client information further includes a current geographic location and a current time, and the step of assigning a target client manager account based on the client assignment rule and the client information includes:
step B10, if the client allocation rule includes allocation according to a park relation, determining target service nodes meeting preset conditions in all preset service nodes, wherein the preset conditions include: the distance between the network point position of the service network point and the current geographic position is smaller than the preset distance, and the current time is within the business time of the service network point;
And step B20, determining a second customer manager account number associated with the target service network point, and taking the second customer manager account number as a target customer manager account number.
In one possible embodiment, the allocation flow for allocation by park relationship may be as follows: the method comprises the steps of obtaining the current geographic position of a client, determining first service nodes which are smaller than a preset distance from the current geographic position of the client, identifying whether each first service node is currently open and in specific business hours, selecting a target service node which is in the business hours of the service nodes at the current time from the first service nodes, if a plurality of target service nodes exist, selecting a target service node which is closest to the target service node, determining a second client manager account which is associated with the target service node, and taking the second client manager account as a target client manager account.
It should be noted that, if one or more customer manager accounts are associated with each service website, if a target service website is associated with a plurality of customer manager accounts, the client may select whether to display the identification codes of some or all of the customer manager accounts, or may set the identification codes of some or all of the customer manager accounts in advance, and the user may select which customer manager is specifically added as a friend to perform the consultation service.
In this embodiment, if the client allocation rule includes allocation according to a park relation, determining a target service node that satisfies a preset condition in each preset service node, where the preset condition includes: the distance between the site position of the service site and the current geographic position is smaller than the preset distance, the current time is within the business hours of the service site, a second customer manager account number associated with the target service site is determined, and the second customer manager account number is used as a target customer manager account number, so that the customer manager account number which is closest to the customer and is associated with the target service site in the service time is distributed to the customer terminal, the effective distribution of the customer manager account number is ensured, and the customer experience is improved.
In a possible embodiment, the step of assigning the target customer manager account based on the customer assignment rule includes:
step C10, if the client allocation rule comprises balanced allocation according to the flow, acquiring the added client quantity of each preset default client manager account;
and step C20, determining the minimum adding client quantity in the adding client quantities, and taking a preset default client manager account corresponding to the minimum adding client quantity as a target client manager account.
In one possible embodiment, the flow of the allocation by flow balancing may be as follows: which customer manager accounts can be set in advance as preset default customer manager accounts, and the corresponding preset default customer manager accounts can be different when the enterprise identifications are different. Initially, the added client quantity of each client manager account is zero, after each client added client manager account corresponds to a client manager, the added client quantity of the client manager account corresponding to the client manager is added by one, and the added client quantity of each client manager account is stored in real time, so that the added client quantity of each preset client manager account can be obtained, and the preset default client manager account corresponding to the minimum added client quantity is selected as a target client manager account. In another possible embodiment, the client quantity added can be sorted from small to large, the identification codes of the default manager account numbers arranged in the first n (such as 1, 2, 3, 4, 5, etc.) bits are selected for display, and the user selects which client manager to add specifically as the friend for consulting service.
Step S30, acquiring an identification code associated with the target customer manager account and displaying the identification code.
When the identification code associated with the account number of the client manager is displayed, the client corresponding to the client is distributed to the client manager corresponding to the identification code, and the client can add the client manager associated with the identification code as friends through scanning the identification code. The identification code can be a dynamic code, an enterprise WeChat two-dimensional code and the like.
To facilitate understanding of the technical concept or technical principle of the present application, a specific embodiment is listed:
referring to fig. 7, the customer relationship allocation flow in this embodiment is:
1) Customer scans multi-person code picture and fills in enterprise information
2) And according to the client allocation rules, allocating a household manager to the client according to the management relationship or the residence relationship or the flow balance.
And (3) managing household allocation: searching in-line enterprise library information in a preset database according to enterprise business registration names, if the in-line enterprise library information is matched, finding corresponding client managers in the management relationship, and if a single enterprise has a plurality of client managers, recommending the client managers according to the in-line client relationship and the distribution relationship according to the priority of high distribution proportion; if no manager relationship exists, the customer manager of the service is selected according to the data of the account opening in the middle.
Dot allocation: the method comprises the steps of obtaining current position information of a client, obtaining a network point list in the nearby 10km in a network point library in a row according to the position information, identifying whether the current business and the specific business hours exist, supporting a user to adjust the network point, and recommending the client manager of the network point to serve after determining the network point.
Flow distribution: the customer manager with least customer added by the active personnel can be selected to be added preferentially in the channel activities.
3) After the customer manager is assigned, the assigned customer manager's dynamic code is presented.
In this embodiment, by responding to a service access request sent by a client, client information is obtained according to the service access request, where the client information at least includes a client identifier and an enterprise identifier; acquiring a client allocation rule according to the service access request, and allocating a target client manager account based on the client allocation rule and the client information, wherein the client allocation rule comprises allocation according to a management relationship, allocation according to a park relationship and flow balance allocation; and acquiring an identification code associated with the target customer manager account and displaying the identification code. In this way, compared with the client relationship distribution mode of manually distributing client managers in the prior art, in the embodiment, the client manager account is automatically distributed according to the client information and the client distribution rule by acquiring the client information and the client distribution rule, and the identification code associated with the account is displayed, so that the client corresponding to the client is distributed to the client manager corresponding to the identification code, and intelligent automatic distribution of the client relationship is realized.
Further, based on the above first embodiment of the present application, a second embodiment of the client relationship allocation method of the present application is provided, and the same or similar contents as those of the above first embodiment can be referred to the above description, and will not be repeated. In this embodiment, after the step of displaying the identification code in the steps of the foregoing embodiment, the method further includes:
step D10, if the client-side monitors a friend adding request sent by the client-side based on the identification code, carrying out validity detection on the client information according to the friend adding request to obtain a validity detection result;
in this embodiment, a client corresponding to the client may initiate a friend adding request by scanning the displayed identifier. And after the client side is monitored to initiate a friend adding request, carrying out validity detection on the client information of the client side. Alternatively, the legal condition of each piece of customer information may be preset, for example, the legal condition of the customer information such as the mobile phone number may be set to include an 11-bit numerical value, the legal condition of the customer information such as the customer identification may be set to include an arabic number, and the legal condition of the customer information such as the micro signal may be set to be not null. Therefore, the validity detection is carried out on the client information according to the legal conditions of each client information, when each client information meets the corresponding legal conditions, the validity detection result is determined to be the detection success, and any client information does not meet the corresponding legal conditions, the validity detection result can be determined to be the detection failure. Further, for the client information which is not passed by the validity detection, the client information can be sent to the account of the client manager, the client manager corresponding to the account of the client manager carries out manual check back, after the client manager passes the manual check back, the detection is used as a result of the validity detection of the client information, and if the client manager does not pass the manual check back, prompt information can be output to remind the client.
And step D20, if the validity detection result is that the detection is passed, storing the client identifier and the enterprise identifier in a preset client enterprise table in a correlation way.
When the validity detection result is that the detection is passed, the added client quantity of the target client manager account, namely the added client quantity of the target client manager account is increased by one, the client identifier and the enterprise identifier are associated and stored in a preset enterprise table, and further, the client enterprise WeChat account of the client can be obtained according to the friend adding request, and the client identifier, the enterprise identifier and the client enterprise WeChat account are associated and stored in the preset client enterprise table. In another possible embodiment, each enterprise may create a corresponding enterprise client table, and use the enterprise identifier of the enterprise as the table identifier of the enterprise client table, so after the client initiates the friend adding request and the validity of the client information is detected, it may be matched whether there is a target table identifier matched with the enterprise identifier in the table identifiers of the enterprise client tables, if there is the target table identifier, the client identifier is associated with the enterprise identifier (or the client identifier, the enterprise identifier and the client enterprise WeChat account number) and stored in the enterprise client table corresponding to the target table identifier, if there is no target table identifier, a new blank table is created, the enterprise identifier is set as the table identifier of the new blank table, and the client identifier is associated with the enterprise identifier (or the client identifier, the enterprise identifier and the client enterprise WeChat account number) and stored in the new blank table. Therefore, at least the mode of storing the client identifications and the enterprise identifications in a table in an associated mode can realize statistics and recording of enterprise staff in each enterprise, and targeted data pushing, concentrated consultation and other services are carried out on the enterprise staff of each enterprise, so that client experience is improved.
In an embodiment, the step of performing validity detection on the client information according to the friend adding request to obtain a validity detection result includes:
step E10, detecting whether a target enterprise identifier matched with the enterprise name identifier exists in a preset legal enterprise service table;
step E20, if the target enterprise identifier does not exist, detecting whether an account opening enterprise identifier matched with the enterprise identifier exists in a preset account opening enterprise list;
and E30, if the account opening enterprise identifier exists, detecting the passing of the detection result as a validity detection result corresponding to the client information.
In this embodiment, only the validity detection of the enterprise identifier in the client information is taken as an example, whether a target enterprise identifier matched with the enterprise identifier exists in the preset legal enterprise service table is detected, if the target enterprise identifier does not exist, whether an account opening enterprise identifier matched with the enterprise identifier exists in the preset account opening enterprise table is detected; if the account opening enterprise identifier exists, the detection is passed as a legal detection result corresponding to the client information. If the account opening enterprise identification does not exist, the detection is not passed as a validity detection result corresponding to the client information. When the enterprise identifier does not exist in the preset legal enterprise service table, whether the enterprise identifier exists in the preset account opening enterprise table is further determined, so that whether the enterprise identifier is legal or not is comprehensively detected, and the situation that the enterprise identifier cannot be matched in enterprise library information in a row, but the enterprise corresponding to the enterprise identifier is in account opening, and the enterprise identifier is erroneously detected to be failed to be detected is avoided.
To facilitate understanding of the technical concept or technical principle of the present embodiment, a specific embodiment is listed:
referring to fig. 7, the process of adding friends by the client in this embodiment is:
1) Monitoring enterprise micro-friend adding event
2) After monitoring the micro-friend day adding event of the enterprise, analyzing the micro-encryption data of the enterprise
3) Sending welcome to clients
4) Acquiring information such as a customer manager, a customer, an enterprise binding two-dimensional codes and the like
5) Querying an in-line enterprise library based on enterprise name
6) After the enterprise name is queried by the enterprise library in the enterprise, the relationship between the client added this time and the enterprise is associated
7) Optionally, when the enterprise name is not queried by the enterprise library in the row, the client information can be sent to a client manager for manual review, or the associated information in the step 6) can also be sent to the client manager for manual review, so that the accuracy of the relationship between the associated client and the enterprise is further improved.
In an embodiment, after the step of storing the customer identifier and the enterprise identifier in a preset customer enterprise table, the method further includes:
step F10, inquiring whether a task to be pushed exists in a task list to be pushed, and if the task to be pushed exists, acquiring a pushing enterprise identifier and pushing content of the task to be pushed;
The active service with the help of RPA (Robotic process automation) capability requires a client manager to authorize account rights of enterprise WeChat to the robot, so that the robot can replace the client manager to serve clients, thereby saving the time of the client manager and laying a foundation for subsequent intelligent service.
Before executing step F10, it may be detected whether the client manager has authorized the RPA robot to log on to its enterprise WeChat account, and if the client manager has authorized the RPA robot to log on to its enterprise WeChat account, step F10 is executed. If not, the customer manager may first authorize. The authorization process may be shown in fig. 8, where the RPA hosting robot is connected to a middle platform (PC end), the RPA hosting robot is connected to a client manager (enterprise WeChat mobile end), the middle platform starts a hosting task first, after the hosting task is started, it detects whether the client manager has authorized to log in to the RPA, if yes, the middle platform generates a task list to be pushed by the client manager, if not, the middle platform may output a reminding message to the client manager (enterprise WeChat mobile end), the enterprise WeChat mobile end jumps to the RPA assistant, if the client manager clicks a login button, it invokes a login interface to log in to the RPA hosting robot, the RPA hosting robot simulates and opens the enterprise client, and location intercepts a login two-dimensional code, uploads the two-dimensional code to a preset database, and pushes the two-dimensional code to the enterprise WeChat mobile end, after the enterprise WeChat mobile end obtains the login two-dimensional code, the client manager authorizes the RPA hosting robot, after the RPA client detects that the client normally logs in, captures the login action and pushes the state to the middle platform, and updates the state of the client manager.
The task to be pushed can be generated by a middle platform and stored in a task list to be pushed, each task to be pushed comprises a pushing object and pushing content, the pushing object can be a pushing enterprise identifier or can also be a target client directly, the step F20 is executed when the pushing object is the pushing enterprise identifier, and the pushing content is pushed to the target client directly when the pushing object is the target client. That is, step F10 may be to query whether a task to be pushed exists in the task list to be pushed, if yes, obtain a pushing object and a pushing content of the task to be pushed, if the pushing object is a pushing enterprise identifier, execute step F20, and if the pushing object is a target client, push the pushing content to the target client.
Taking a pushing object for generating a task to be pushed as a target client as an example, the generating process of generating the task to be pushed by a middle platform can refer to fig. 9, label identification is performed according to a timing strategy or an organization activity, such as identifying birth date of an enterprise, opening date of enterprise and liquid, opening time of 7 days, opening balance condition of various products, etc., identifying an enterprise list hitting a certain label, identifying a target client to be sent, including identifying an individual authenticating the enterprise (obtained in the executable step F20), identifying a tiny client manager, selecting the client manager according to the client/latest adding time, etc., wherein each label is associated with pushing content, and the identified target client is taken as a pushing object according to the pushing content associated with the hit label, so as to assemble the task to be pushed into a task list to be pushed.
Step F20, determining a target pushing enterprise identifier matched with the pushing enterprise identifier in a preset client enterprise list, and determining a target client identifier corresponding to the target pushing enterprise identifier in the preset client enterprise list;
and step F30, determining a target client corresponding to the target client identifier, and pushing the push content to the target client.
The mobile phone or the enterprise dimension signal of the corresponding client can be identified, and the push content is pushed to the target client through the short message or the enterprise dimension signal.
In this embodiment, whether a task to be pushed exists in a task list to be pushed is queried, if the task to be pushed exists, a pushing enterprise identifier and a pushing content of the task to be pushed are obtained, a target pushing enterprise identifier matched with the pushing enterprise identifier in a preset client enterprise list is determined, a target client identifier corresponding to the target pushing enterprise identifier in the preset client enterprise list is determined, a target client corresponding to the target client identifier is determined, and the pushing content is pushed to the target client, so that content pushing is automatically performed on clients in an intelligent manner by using an RPA technology, manual pushing by a client manager is not needed, and content pushing efficiency and comprehensiveness are improved.
To facilitate understanding of the technical concept or technical principle of the present embodiment, a specific embodiment is listed:
referring to fig. 9, the content pushing process in this embodiment is:
1) Acquiring tasks to be pushed
2) Identifying push content and push object in task to be pushed, and downloading enterprise WeChat materials based on push content notification application
3) Simulation opens a public RPA dialog box to inform the middlebox to push the required material to the RPA hosting robot
4) Forwarding of full selection dialog box content
5) Searching by target clients in push objects
6) OCR (Optical Character Recognition ) recognition of a searched target customer
7) Judging whether the searched client is a target client needing pushing aiming at the identified file so as to improve the pushing accuracy
8) If yes, pushing the pushing content to the target client; if not, pushing is not performed, and prompt information can be output.
Further, referring to fig. 10, the present application also provides a customer relationship distribution apparatus, including:
the response module 10 is configured to respond to a service access request sent by a client, and obtain client information according to the service access request, where the client information at least includes a client identifier and an enterprise identifier;
The allocation module 20 is configured to obtain a client allocation rule according to the service access request, and allocate a target client manager account based on the client allocation rule and the client information, where the client allocation rule includes allocation according to a manager relationship, allocation according to a park relationship, and allocation according to a flow balance;
and the display module 30 is configured to obtain an identification code associated with the target customer manager account, and display the identification code.
In addition, the embodiment of the application also provides a client relationship distribution device, which comprises a memory, a processor and a client relationship distribution program stored in the memory and executable on the processor, wherein the client relationship distribution program realizes the steps of the client relationship distribution method when being executed by the processor.
The specific implementation manner of the customer relationship allocation device of the present application is basically the same as the above-mentioned examples of the customer relationship allocation method, and will not be repeated here.
In addition, in order to achieve the above object, the present application provides a readable storage medium, on which a client relationship allocation program is stored, which when executed by a processor, implements the steps of the client relationship allocation method as described above.
The specific implementation manner of the readable storage medium of the present application is basically the same as the above embodiments of the client relationship allocation method, and will not be repeated here.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.
The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the application, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (10)
1. A method of customer relationship allocation, the method comprising the steps of:
responding to a service access request sent by a client, and acquiring client information according to the service access request, wherein the client information at least comprises a client identifier and an enterprise identifier;
acquiring a client allocation rule according to the service access request, and allocating a target client manager account based on the client allocation rule and the client information, wherein the client allocation rule comprises allocation according to a management relationship, allocation according to a park relationship and flow balance allocation;
and acquiring an identification code associated with the target customer manager account and displaying the identification code.
2. The customer relationship assignment method as claimed in claim 1, wherein the step of assigning a target customer manager account based on the customer assignment rule and the customer information comprises:
If the client allocation rule comprises allocation according to a management relationship, detecting whether a target enterprise identifier matched with the enterprise identifier exists in a preset legal enterprise service table or not;
if the target enterprise identifier exists, determining a first customer manager account associated with the target enterprise identifier;
and taking the first customer manager account as a target customer manager account.
3. The customer relationship assignment method as claimed in claim 1, wherein the customer information further comprises a current geographic location and a current time, the step of assigning a target customer manager account based on the customer assignment rule and the customer information comprising:
if the client allocation rule includes allocation according to a park relation, determining a target service node meeting preset conditions in all preset service nodes, wherein the preset conditions include: the distance between the network point position of the service network point and the current geographic position is smaller than the preset distance, and the current time is within the business time of the service network point;
and determining a second customer manager account number associated with the target service network point, and taking the second customer manager account number as a target customer manager account number.
4. The customer relationship assignment method as claimed in claim 1, wherein said step of assigning a target customer manager account based on said customer assignment rule comprises:
If the client allocation rule comprises balanced allocation according to the flow, acquiring the added client quantity of each preset default client manager account;
and determining the minimum added client quantity in the added client quantities, and taking a preset default client manager account corresponding to the minimum added client quantity as a target client manager account.
5. A customer relationship allocation method according to any one of claims 1 to 4, wherein after the step of presenting the identification code, the method further comprises:
if the client monitors a friend adding request sent by the client based on the identification code, carrying out validity detection on the client information according to the friend adding request to obtain a validity detection result;
and if the validity detection result is that the detection is passed, storing the client identifier and the enterprise identifier in a preset client enterprise table in a correlation way.
6. The method for assigning client relationships according to claim 5, wherein the step of performing validity detection on the client information according to the friend adding request to obtain a result of validity detection includes:
detecting whether a target enterprise identifier matched with the enterprise name identifier exists in a preset legal enterprise service table;
If the target enterprise identifier does not exist, detecting whether an account opening enterprise identifier matched with the enterprise identifier exists in a preset account opening enterprise list;
if the account opening enterprise identifier exists, detecting the account opening enterprise identifier as a validity detection result corresponding to the client information.
7. The customer relationship assignment method as set forth in claim 5, wherein after the step of storing the customer identification and the enterprise identification in association with a predetermined customer enterprise table, the method further comprises:
inquiring whether a task to be pushed exists in a task list to be pushed, and if the task to be pushed exists, acquiring a pushing enterprise identifier and pushing content of the task to be pushed;
determining a target pushing enterprise identifier matched with the pushing enterprise identifier in a preset client enterprise list, and determining a target client identifier corresponding to the target pushing enterprise identifier in the preset client enterprise list;
and determining a target client corresponding to the target client identifier, and pushing the push content to the target client.
8. A customer relationship distribution apparatus, the customer relationship distribution apparatus comprising:
the response module is used for responding to a service access request sent by the client and acquiring client information according to the service access request, wherein the client information at least comprises a client identifier and an enterprise identifier;
The distribution module is used for acquiring a client distribution rule according to the service access request, and distributing a target client manager account based on the client distribution rule and the client information, wherein the client distribution rule comprises distribution according to a management relationship, distribution according to a park relationship and flow balance distribution;
and the display module is used for acquiring the identification code associated with the target customer manager account and displaying the identification code.
9. A customer relationship distribution apparatus, the customer relationship distribution apparatus comprising: memory, a processor and a customer relationship assignment program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the customer relationship assignment method of any of claims 1 to 7.
10. A readable storage medium, wherein a customer relationship assignment program is stored on the readable storage medium, which when executed by a processor, implements the steps of the customer relationship assignment method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311101800.8A CN117217448A (en) | 2023-08-29 | 2023-08-29 | Customer relationship distribution method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311101800.8A CN117217448A (en) | 2023-08-29 | 2023-08-29 | Customer relationship distribution method, device, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117217448A true CN117217448A (en) | 2023-12-12 |
Family
ID=89041656
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311101800.8A Pending CN117217448A (en) | 2023-08-29 | 2023-08-29 | Customer relationship distribution method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117217448A (en) |
-
2023
- 2023-08-29 CN CN202311101800.8A patent/CN117217448A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9053136B2 (en) | Systems and methods for identifying contacts as users of a multi-tenant database and application system | |
| US20080133657A1 (en) | Karma system | |
| US8671114B2 (en) | Search results weighted by real-time sharing activity | |
| US8266127B2 (en) | Systems and methods for directed forums | |
| US8332760B2 (en) | Dynamically mapping chat session invitation history | |
| CN101263483B (en) | Sharing a port with multiple processes | |
| EP3788582A1 (en) | System for controlling user interaction via an application with remote servers | |
| US9325849B1 (en) | Customer service routing | |
| US20100088187A1 (en) | System and method for localized and/or topic-driven content distribution for mobile devices | |
| US8615550B2 (en) | Client-side data scraping for open overlay for social networks and online services | |
| US20080133658A1 (en) | Auto-shared photo album | |
| US20060004869A1 (en) | System and method for mapping relationship management intelligence | |
| US20100299617A1 (en) | Identity management for open overlay for social networks and online services | |
| US20140201292A1 (en) | Digital business card system performing social networking commonality comparisions, professional profile curation and personal brand management | |
| US20070027915A1 (en) | Method and system for processing a workflow using a publish-subscribe protocol | |
| US8838803B2 (en) | Methods and apparatus for management of user presence in communication activities | |
| US20110066470A1 (en) | System and method for providing context based remote advisor capabilities to users of web applications | |
| CN109657899B (en) | Item processing method, device, equipment and readable storage medium | |
| US20110119276A1 (en) | Submission capture, auto-response and processing system | |
| CN109669718A (en) | System permission configuration method, device, equipment and storage medium | |
| US7912930B1 (en) | System and method for resource provisioning | |
| CN111583023A (en) | Service processing method, device and computer system | |
| US20100211674A1 (en) | Community generation support system, community generation support method, and community generation support program | |
| US11689481B2 (en) | Automated, extensible natural-language conversational system | |
| US8190746B2 (en) | Explicit casualty control in a client/server system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |