WO2019056462A1

WO2019056462A1 - Name list distribution method, apparatus and device, and computer readable storage medium

Info

Publication number: WO2019056462A1
Application number: PCT/CN2017/107422
Authority: WO
Inventors: 徐恺; 王刚
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-09-19
Filing date: 2017-10-24
Publication date: 2019-03-28
Also published as: CN107679718A; CN107679718B

Abstract

A name list distribution method, apparatus and device, and a computer readable storage medium. The method comprises the steps of: when a name list distribution request is detected, extracting, according to the list distribution request, a client list from a name list pool according to a preset rule, and adding the client list into a name list (S10); determining agent groups in the name list pool, and searching the agent groups for a target agent that meets a preset condition (S20); if the target agent is found, distributing the client list in the name list to the target agent (S30); and if the target agent is not found, distributing the client list in the name list in an ascending order of the count values corresponding to agents in the agent groups (S40). During distribution of the client list, the client list is distributed according to a certain rule, instead of being randomly distributed, and therefore, corresponding client lists can be preferentially distributed to the agents meeting certain conditions, and the intelligence of name list distribution is improved.

Description

List allocation method, device, device, and computer readable storage medium

This application claims the priority of the Chinese Patent Application filed on Sep. 19, 2017, the Chinese Patent Application No. PCT Application No. PCT Application No. In the application.

Technical field

The present application relates to the field of Internet technologies, and in particular, to a list allocation method, apparatus, device, and computer readable storage medium.

Background technique

In recent years, customer service call centers have not only been widely used in communication operations, but also the major small and medium-sized enterprises have gradually raised their demand for customer service call centers. Provide support for your own corporate customers by self-built or leased call centers. At present, the distribution lists of various agents in the customer service system are randomly assigned, and the current workload of each agent will not be taken into consideration, nor will the work ability of each agent be considered, that is, the existing customer service system list allocation method is not intelligent enough. Chemical.

Summary of the invention

The main purpose of the present application is to provide a list distribution method, apparatus, device, and computer readable storage medium, aiming at solving the technical problem that the existing list allocation method is not intelligent enough.

To achieve the above objective, the present application provides a list allocation method, and the list allocation method includes the following steps:

When the list allocation request is detected, according to the list allocation request, the customer list is extracted from the list pool according to a preset rule and added to the list;

Determining each agent group in the list pool, and finding a target agent that meets a preset condition in the agent group;

If the target agent is found, the customer list in the list is allocated to the target agent;

If the target agent is not found, the customer list in the list is allocated according to the count value corresponding to each agent in the agent group.

In addition, in order to achieve the above object, the present application further provides a list distribution device, where the list distribution device includes:

The extracting module is configured to: when the list allocation request is detected, extract the customer list in the list pool according to the preset rule according to the list allocation request, and add the list to the list;

a searching module, configured to determine each agent group in the list pool, and find, in the agent group, a target agent that meets a preset condition;

An allocation module, configured to: if the target agent is found, assign a customer list in the list to the target agent; if the target agent is not found, corresponding to each agent in the agent group The count value is assigned from a small to a large list of customers in the list of lists.

In addition, in order to achieve the above object, the present application further provides a list distribution device including a memory, a processor, and a list distribution program stored on the memory and operable on the processor, The list allocation procedure implements the steps of the list allocation method as described above when executed by the processor.

In addition, in order to achieve the above object, the present application further provides a computer readable storage medium having a list allocation program stored thereon, and the list allocation program is executed by a processor to implement list allocation as described above. The steps of the method.

The application adds a client list to the list in the list pool according to the preset rule when the list allocation request is detected, and determines the agent groups in the list pool. The agent group finds a target agent that meets the preset condition; if the target agent is found, the customer list in the list is assigned to the target agent; if the target agent is not found, The count value corresponding to each agent in the agent group is assigned from the smallest to the largest. When the customer list is allocated, the customer list is allocated according to a certain rule, instead of being randomly allocated, so that the agent who satisfies certain conditions is preferentially assigned to the corresponding customer list, thereby improving the intelligence of the list allocation.

DRAWINGS

1 is a schematic structural diagram of a system of a hardware operating environment involved in an embodiment of the present application;

2 is a schematic flowchart of a first embodiment of a method for allocating a list according to the present application;

FIG. 3 is a schematic flowchart of allocating a client list in the list to the target agent if the target agent is found in the embodiment of the present application;

4 is a schematic flowchart of a third embodiment of a method for allocating a list according to the present application;

FIG. 5 is a schematic flowchart diagram of a fourth embodiment of a method for allocating a list of the present application.

The implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings.

Detailed ways

It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

As shown in FIG. 1 , FIG. 1 is a schematic structural diagram of a system of a hardware operating environment involved in an embodiment of the present application.

The list distribution device in the embodiment of the present application may be a PC, or may be a terminal device such as a smart phone, a tablet computer, or a portable computer.

As shown in FIG. 1, the list distribution device may include a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. Among them, the communication bus 1002 is used to implement connection communication between these components. The user interface 1003 can include a display, an input unit such as a keyboard, and the optional user interface 1003 can also include a standard wired interface, a wireless interface. The network interface 1004 can optionally include a standard wired interface, a wireless interface (such as a WI-FI interface). The memory 1005 may be a high speed RAM memory or a stable memory (non-volatile) Memory), such as disk storage. The memory 1005 can also optionally be a storage device independent of the aforementioned processor 1001.

Optionally, the list distribution device may further include a camera, RF (Radio) Frequency, RF) circuits, sensors, audio circuits, WiFi modules, and more.

Those skilled in the art will appreciate that the list distribution device structure illustrated in FIG. 1 does not constitute a limitation to the terminal, and may include more or fewer components than those illustrated, or some components may be combined, or different component arrangements.

As shown in FIG. 1, an operating system and a list allocation program may be included in the memory 1005 as a computer storage medium. Among them, the operating system is a program that manages and controls the list to allocate device hardware and software resources, and supports the operation of the list distribution program and other software or programs.

In the list distribution device shown in FIG. 1, the network interface 1004 is mainly used to access the network and is connected to other systems; the user interface 1003 is mainly used for detecting a list allocation request and the like. The processor 1001 can be used to call the list allocation program stored in the memory 1005 and perform the following operations:

Further, if the target agent is found, the step of assigning the customer list in the list to the target agent includes:

If the target agent is found, determining whether there is an associated agent associated with the client in the list in the target agent;

If the associated agent exists in the target agent, assigning a client list associated with the associated agent to the associated agent;

If the associated agent does not exist in the target agent, acquiring a count value corresponding to each target agent;

The client list in the list of lists is assigned to each target agent according to the count value from small to large.

Further, the processor 1001 may further be configured to call the list allocation program stored in the memory 1005, and execute the following, before the step of allocating the client list in the list to each target agent according to the count value from small to large. step:

Determining whether there is an equal count value in the count value of each target agent;

If there is no equal count value, the step of allocating the client list in the list of lists to each target agent according to the count value is performed.

Further, after the step of determining whether there is an equal count value in the count values of the respective target agents, the processor 1001 may further be configured to call the list allocation program stored in the memory 1005, and perform the following steps:

If there are equal count values, the target seats with the same count value are recorded as conflicting seats;

Determine the level of each conflicting seat;

If the levels of the conflicting parties are inconsistent, the customer list in the list is preferentially assigned to the conflicting seat with a high level;

If the levels of the conflicting parties are the same, the client list in the list is randomly assigned to the conflicting agents with the same level.

Further, when the list allocation request is detected, the processor 1001 may be further used before the step of extracting the client list into the list list according to the preset rule according to the preset rule. The list allocation program stored in the memory 1005 is called and the following steps are performed:

Obtaining attribute information of the customer list when receiving the customer list;

The customer list is allocated to the corresponding list pool according to the attribute information.

Set corresponding threads for each list pool, so that each list pool corresponds to one thread;

When the list allocation request is detected, the step of extracting the customer list into the list list according to the preset rule according to the preset rule includes:

When the list allocation request is detected, the thread corresponding to each list pool is started according to the list allocation request;

Based on the thread, the customer list is extracted in each list pool according to a preset rule and added to the list.

Further, the step of extracting the customer list in the list pool according to the preset rule and adding it to the list includes:

Determining a storage time of each customer list in the list pool;

Adding a preset number of customer lists in the list pool from front to back according to the storage time is added to the list.

Further, the step of searching for the target agent that meets the preset condition in the agent group includes:

Detecting a status of each agent in the agent group;

If the status of the agent is the logged in state, and the count value corresponding to the agent is less than a preset threshold, determining to find the target agent in the agent group;

If the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined that the agent group is not found in the agent group. The target agent.

Based on the hardware configuration described above, various embodiments of the list assignment method are proposed.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of a first embodiment of a method for allocating a list of applications.

In this embodiment, an embodiment of a list allocation method is provided. It should be noted that although the logical order is shown in the flowchart, in some cases, the illustrated may be performed in a different order than here. Or the steps described.

The list allocation method includes:

In step S10, when the list allocation request is detected, according to the list allocation request, the customer list is extracted from the list pool according to a preset rule and added to the list.

When the list distribution device detects the list allocation request, the list distribution device adds the customer list in each list pool to the list according to the preset rule according to the preset rule. In the embodiment of the present application, the time distribution task is preset in the list distribution device. If the current time of the list distribution device is equal to the time corresponding to the timed task or the time period corresponding to the timed task, the list allocation request is triggered. If the time corresponding to the scheduled task is 9:00 in the morning, the list allocation request is triggered at 9:00 in the morning. Further, the list allocation request can also be manually triggered by a user of the list distribution device. It can be understood that, in a day time, multiple timing tasks can be set, and the list allocation request can be triggered multiple times. The time corresponding to the timed task can be set to a time point or a time period. The list pool allocates storage space for storing the customer list set in the device for the list. The list in the list is the list of customers to be assigned.

Step a: determining a storage time of each customer list in the list pool.

Step b: Select a preset number of customer lists in the list pool from front to back according to the storage time to add to the list.

When the list distribution device detects the list allocation request, the list distribution device determines the storage time of each client list in the list pool according to the list allocation request, determines the order of storage time of each client list, and follows the order of storage time of each client list. After that, select a preset number of customer lists to add to the list. The preset number can be set according to specific needs, for example, 1000 pieces, or 500 pieces, or 3400 pieces can be set.

Further, when the list distribution device detects the list allocation request, the list distribution device determines the priority of each list pool, and preferentially obtains the customer list that satisfies the condition from the high priority list pool and adds it to the list. For example, the customer list whose storage time is before July 20, 2017 is added to the list of the list from the priority pool. The priority of the list pool can be set according to specific needs. For example, the priority of the list pool can be determined according to factors such as the list level of the stored client list and the type of the dialing of the list.

In step S20, each agent group corresponding to the list pool is determined, and the target agent meeting the preset condition is found in the agent group.

The list distribution device determines each agent group corresponding to the list pool, and searches for a target agent that meets the preset condition in each agent group corresponding to the list pool. It should be noted that one list pool corresponds to at least two agent groups, and one agent group includes at least one agent. One agent group may correspond to only one list pool, or may correspond to multiple list pools.

Further, the step of searching, in the agent group, the target agent that meets the preset condition comprises:

Step c: detecting the status of each agent in the agent group.

After the list distribution device determines the respective agent groups corresponding to the list pool, the list distribution device detects the status of each agent in the agent group. The status of the agent includes two types, one is the logged in state, and the other is the logged in state. In this embodiment, the status of each agent can be determined by detecting whether the login identifier corresponding to each agent is a login identifier or a non-login identifier. When it is detected that the login ID corresponding to the agent is the registered ID, the agent is confirmed to be in the logged-in state. When the login ID corresponding to the agent is detected as the unregistered ID, the agent is confirmed to be in the unlogged state. If the login ID can be set to 01, the non-login ID can be set to 00.

In step d, if the status of the agent is the logged in state, and the counter corresponding to the agent is less than the preset threshold, it is determined that the target agent is found in the agent group.

If the status of the agent is confirmed to be the registered state, the list distribution device obtains the count value corresponding to the agent and determines whether the count value corresponding to the agent is less than a preset threshold. If the counter value corresponding to the agent is less than the preset threshold, the list distribution device determines that the target agent is found in the agent group, and the target agent is the agent whose counter value is less than the preset threshold in the agent group. The preset threshold may be set according to specific needs. In this embodiment, there is only one preset threshold, that is, the preset thresholds corresponding to all the seats are consistent. In other embodiments, different preset thresholds may be set for different agents, and different preset thresholds and the like may be set for each agent group in the list pool. In this embodiment, each agent corresponds to a counter through which the counter value corresponding to each agent can be obtained. The preset threshold can be set according to specific needs, such as 20, 50 or 100.

In step e, if the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined in the agent group. The target agent was not found.

If the status of the agent is confirmed to be logged in, but the counter corresponding to the counter is greater than or equal to the preset threshold, or the status of the agent is not logged in, the list distribution device determines that the target agent is not found in the agent group. It can be understood that if the status of the agent is confirmed to be the registered state, but the corresponding value of the agent is greater than or equal to the preset threshold, it indicates that the agent list need not be allocated for the agent.

It can be understood that, as long as there is an agent in the agent group in the logged-in state, and the corresponding value of the agent is greater than or equal to the preset threshold, it indicates that the target agent is found in the agent group.

Step S30: If the target agent is found, the customer list in the list is assigned to the target agent.

If the target agent is found in the agent group, the list distribution device assigns the customer list in the list to the target agent.

Further, referring to FIG. 3, step S30 includes:

Step S31: If the target agent is found, it is determined whether there is an associated agent associated with the client in the list in the target agent.

If the target agent is found in each agent group corresponding to the list pool, the list distribution device determines whether there is an associated agent associated with the client in the list in the target agent. It should be noted that the associated agent is an agent in the previously processed client list that belongs to the same client as the client list in the current list. If the A agent in the target agent has previously processed the D customer list, and the current list list also has a D customer list, then the A agent is recorded as the D customer's associated agent. It should be noted that each customer list has an identity identifier, and the identity identifier can uniquely identify a client, that is, through the identity identifier corresponding to the client list, it can be determined whether there is an associated agent associated with the client in the list in the target agent. If the identity can be a phone number and/or an ID number, and the like.

Step S32: If the associated agent exists in the target agent, assign a client list associated with the associated agent to the associated agent.

In step S33, if the associated agent does not exist in the target agent, the count value corresponding to each target agent is obtained.

If there is an associated agent in the target agent, the list distribution device assigns the list belonging to the customer in the list to the associated agent. If there is no associated agent in the target agent, the list distribution device obtains the count value corresponding to each target agent.

In step S34, the client list in the list is allocated to each target agent according to the count value from small to large.

After the count value corresponding to each target agent is obtained, the list distribution device determines the size relationship of the corresponding target value of each target agent, and allocates the customer list in the list of each target agent according to the count value from small to large. For example, when the count value of the A agent is 2 and the count value of the B agent is 5, the priority is the list of customers in the A agent allocation list. Specifically, three client lists can be assigned to the A agent first, and then the A and A seats can be evenly distributed, so that the agent A and the agent B have the same number of client lists.

Further, the list allocation method further includes:

In step f, when a client list is assigned to the target agent, the count value is incremented by one.

After assigning a client list to the target agent, the list distribution device adds one to the count value corresponding to the target agent, and determines whether the count value corresponding to the target agent is greater than or equal to a preset threshold.

Step g, if the count value is equal to or greater than a preset threshold, suspending the allocation of the customer list for the target agent.

If the corresponding value of the target agent is greater than or equal to the preset threshold, the list distribution device suspends the allocation of the client list for the target agent; if the count value corresponding to the target agent is less than the preset threshold, the list distribution device continues to serve the target agent. Assign the customer list until the list of customers in the list is assigned.

In step S40, if the target agent is not found, the customer list in the list is allocated according to the count value corresponding to each agent in the agent group.

If the target agent is not found in each agent group, the list distribution device determines the count value corresponding to each agent in the agent group, and allocates the customer list in the list according to the count value corresponding to each agent from small to large.

Further, the priority of each agent group corresponding to the list pool may be determined. In the process of assigning the client list in the list to the agents in the same pool, the list allocation device is preferentially assigned to the agent group with higher priority. The agent assigns a list of customers. When the count value corresponding to each agent in the high-priority agent group is equal to or greater than the preset threshold, the agent list is assigned to the agent in the agent group with lower priority. The priority of each agent group is preset by the list distribution device.

Further, the priority of each list pool is determined. When assigning a client list in the list, the list distribution device preferentially assigns the client list to the agent group corresponding to the high priority list pool.

In this embodiment, when the list allocation request is detected, according to the list allocation request, the customer list is extracted into the list in the list pool according to the preset rule; and each agent group in the list pool is determined. The agent group finds a target agent that meets a preset condition; if the target agent is found, assigns a customer list in the list to the target agent; if the target agent is not found, The count value corresponding to each agent in the agent group is allocated from the smallest to the largest in the list of clients in the list. When the customer list is allocated, the customer list is allocated according to a certain rule, instead of being randomly allocated, so that the agent who satisfies certain conditions is preferentially assigned to the corresponding customer list, thereby improving the intelligence of the list allocation.

Further, a second embodiment of the method for assigning a list of the present application is proposed.

The difference between the second embodiment of the list allocation method and the first embodiment of the list allocation method is that the list allocation method further includes:

Step h, determining whether there is an equal count value in the count value of each target agent;

If there is no equal count value, step S34 is performed.

When the count value corresponding to each target agent is obtained, the list distribution device determines whether there is an equal count value among the count values corresponding to the respective target agents. If there is no equal count value in the count value corresponding to each target agent, the customer list in the list of each target agent is allocated according to the count value corresponding to each target agent from small to large.

In step i, if there are equal count values, the target seats with the same count value are recorded as conflict seats.

In step j, the rank of each conflicting seat is determined.

If there is an equal count value among the count values corresponding to the target agents, the list distribution device records the target seats with the same count value as conflicting seats, and determines the rank of each conflicting agent. The level corresponding to each conflict agent is preset by the list distribution device. It can be understood that the higher the work ability, the higher the agent level.

Step k: If the levels of the conflicting agents are inconsistent, the customer list in the list is preferentially assigned to the conflicting agent with a high level.

In step 1, if the levels of the conflicting agents are the same, the client list in the list is randomly assigned to the conflicting agents with the same level.

If the level of each conflicting agent is inconsistent, the list distribution device determines the level of each conflicting agent level, and preferentially assigns the customer list in the list to the high-level conflicting seat; if the level of each conflicting agent is the same, the list distribution device will The list of customers in the list is randomly assigned to conflicting agents of the same level.

In this embodiment, when there is a conflicting agent in the target agent, the level of each conflicting agent is determined, and the client list is preferentially assigned to the conflicting agent with a high level, so that the agent with strong working ability can be preferentially assigned to the client list.

Further, a third embodiment of the method for assigning a list of the present application is proposed.

The third embodiment of the method for assigning a list differs from the first embodiment of the method for assigning a list in that, according to FIG. 4, the method for assigning a list further includes:

In step S50, when the client list is received, the attribute information of the client list is obtained.

When the list distribution device receives the client list, the attribute information of the client list is obtained. The list of clients received by the list distribution device is sent by other systems connected to the list distribution device. Other systems mentioned in this embodiment may be a service system, a sales system, and the like. The attribute information of the customer list includes the service line, the service type, the list level, the area to which the list belongs, the usage method of the list, the type of the activity corresponding to the list, the type of the dialing of the list, the effective time and the expiration time of the corresponding rules of the list. Among them, the business line includes but is not limited to the wealth management business line and the channel business line; the business types include but are not limited to securities account opening, trust financing and public wealth management; the list level can be set according to specific needs, specifically, according to the client list corresponding funds The list level is determined; the list usage method includes but is not limited to the test list and the capacity list; the types of activities corresponding to the list include, but are not limited to, short messages, emails, and online sales; the list types include the first call and the return call.

Step S60, the customer list is allocated to the corresponding list pool according to the attribute information.

When the attribute information of the customer list is obtained, the list distribution device allocates the customer list to the corresponding list pool according to the attribute information of the customer list. In this embodiment, the type of the client list that can be stored in each list pool can be set. For example, a list of customers whose storage list is greater than a certain level can be set, or only a list of customers whose service type is trust financing and whose use method is a test list is stored. The list of customers that can be stored in each list pool can be set according to specific needs, and will not be described here.

In this embodiment, the received customer list is allocated to the corresponding list pool according to the attribute information of the customer list, so that the list of the customer list generation list that satisfies the condition can be quickly obtained in the process of generating the list of the customer list in the list pool. , improve the efficiency of list allocation.

Further, a fourth embodiment of the method for assigning a list of the present application is proposed.

The difference between the fourth embodiment of the list allocation method and the first embodiment of the list allocation method is that, with reference to FIG. 5, the list allocation method further includes:

In step S70, a corresponding thread is set for each list pool, so that each list pool corresponds to one thread.

The list distribution device sets a corresponding thread for each list pool, so that each list pool corresponds to one thread. Specifically, the list allocation device can call the API (Application Programming Interface, the application programming interface) sets the thread according to the number of list pools.

Step S10 includes:

In step S11, when the list allocation request is detected, the thread corresponding to each list pool is started according to the list allocation request.

Step S12, based on the thread, extracting a customer list in each list pool according to a preset rule and adding it to the list list.

When the list distribution device detects the list allocation request, the list distribution device starts the threads corresponding to the respective list pools according to the detected list allocation request, and extracts the threads corresponding to each list pool according to the preset rules. The customer list is added to the list of listings.

In this embodiment, a corresponding thread is set for each of the list pools, so that the client list can be added to the list list in each list pool at the same time, which improves the generation speed of the list list and further improves the speed of list allocation.

In addition, the embodiment of the present application further provides a list distribution device, where the list distribution device includes:

Further, the allocation module includes:

a determining unit, configured to determine, if the target agent is found, whether the associated agent associated with the client in the list is present in the target agent;

And an allocating unit, configured to: if the associated agent exists in the target agent, assign a client list associated with the associated agent to the associated agent;

An obtaining unit, configured to acquire a count value corresponding to each target agent if the associated agent does not exist in the target agent;

The allocating unit is further configured to allocate the customer list in the list of the lists to each target agent according to the count value from small to large.

Further, the determining unit is further configured to determine whether an equal count value exists in the count value of each target agent;

The allocating unit is further configured to allocate a customer list in the list of the names to each target agent according to the count value, if there is no equal count value.

Further, the allocating module further includes:

a marking unit, if there is an equal counting value, the target agent with the same counting value is recorded as a conflicting seat;

a first determining unit, configured to determine a level of each conflicting agent;

The allocation unit is further configured to: if the levels of the conflicting agents are inconsistent, the customer list in the list is preferentially assigned to the conflicting seat with a higher level; if the levels of the conflicting agents are the same, the list in the list is The customer list is randomly assigned to conflicting agents of the same level.

Further, the list distribution device further includes:

An obtaining module, configured to acquire attribute information of the customer list when receiving a customer list;

The allocating module is further configured to allocate the customer list to a corresponding list pool according to the attribute information.

Further, the list distribution device further includes:

Setting a module, configured to set a corresponding thread for each list pool, so that each list pool corresponds to one thread;

The extraction module includes:

a startup unit, configured to start, according to the list allocation request, a thread corresponding to each list pool when the list allocation request is detected;

The extracting unit is configured to extract the customer list in each of the list pools into the list according to the thread according to the preset rule.

Further, the extracting module further includes:

a second determining unit, configured to determine a storage time of each customer list in the list pool;

And a selecting unit, configured to select, in the list pool, a preset number of customer lists to be added to the list according to the storage time from front to back.

Further, the lookup module includes:

a detecting unit, configured to detect a state of each agent in the agent group;

a third determining unit, configured to: if the status of the agent is a logged-in state, and the count value corresponding to the agent is less than a preset threshold, determine that the target agent is found in the agent group; If the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined that the target agent is not found in the agent group. .

The specific implementation manners of the application list allocation device are basically the same as the foregoing embodiment of the list allocation method, and details are not described herein again.

In addition, the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium stores a list allocation program, and when the list allocation program is executed by the processor, the following steps are implemented:

Further, before the step of allocating the client list in the list list to each target agent according to the counting value from small to large, the list allocation program is executed by the processor to implement the following steps:

Further, after the step of determining whether there is an equal count value in the count values of the respective target agents, the list distribution program is executed by the processor to implement the following steps:

Determine the level of each conflicting seat;

Further, when the list allocation request is detected, the list allocation program is processed according to the list allocation request, before the step of extracting the customer list into the list list according to the preset rule in the list pool. The following steps are implemented when the device is executed:

Determining a storage time of each customer list in the list pool;

Detecting a status of each agent in the agent group;

The specific embodiment of the computer readable storage medium of the present application is substantially the same as the embodiment of the foregoing list allocation method, and details are not described herein again.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of 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 methods described in various embodiments of the present application.

The above is only a preferred embodiment of the present application, and is not intended to limit the scope of the patent application, and the equivalent structure or equivalent process transformations made by the specification and the drawings of the present application, or directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of this application.

Claims

A list allocation method, characterized in that the list allocation method comprises the following steps:

When the list allocation request is detected, according to the list allocation request, the customer list is extracted from the list pool according to a preset rule and added to the list;

Determining each agent group in the list pool, and finding a target agent that meets a preset condition in the agent group;

If the target agent is found, the customer list in the list is allocated to the target agent;

If the target agent is not found, the customer list in the list is allocated according to the count value corresponding to each agent in the agent group.
The method for assigning a list according to claim 1, wherein the step of assigning a list of customers in the list to the target agent if the target agent is found includes:

If the target agent is found, determining whether there is an associated agent associated with the client in the list in the target agent;

If the associated agent exists in the target agent, assigning a client list associated with the associated agent to the associated agent;

If the associated agent does not exist in the target agent, acquiring a count value corresponding to each target agent;

The client list in the list of lists is assigned to each target agent according to the count value from small to large.
The method for assigning a list according to claim 2, wherein the step of allocating the client list in the list of the objects to the target agents according to the count value from the small to the large value includes:

Determining whether there is an equal count value in the count value of each target agent;

If there is no equal count value, the step of allocating the client list in the list of lists to each target agent according to the count value is performed.
The method for assigning a list according to claim 3, wherein the step of determining whether there is an equal count value in the count value of each target agent further comprises:

If there are equal count values, the target seats with the same count value are recorded as conflicting seats;

Determine the level of each conflicting seat;

If the levels of the conflicting parties are inconsistent, the customer list in the list is preferentially assigned to the conflicting seat with a high level;

If the levels of the conflicting parties are the same, the client list in the list is randomly assigned to the conflicting agents with the same level.
The method for assigning a list according to claim 1, wherein when the list allocation request is detected, according to the list allocation request, the customer list is extracted from the list pool according to a preset rule and added to the list. Before the steps in the middle, it also includes:

Obtaining attribute information of the customer list when receiving the customer list;

The customer list is allocated to the corresponding list pool according to the attribute information.
The method for assigning a list according to claim 1, wherein when the list allocation request is detected, according to the list allocation request, the customer list is extracted from the list pool according to a preset rule and added to the list. Before the steps in the middle, it also includes:

Set corresponding threads for each list pool, so that each list pool corresponds to one thread;

When the list allocation request is detected, the step of extracting the customer list into the list list according to the preset rule according to the preset rule includes:

When the list allocation request is detected, the thread corresponding to each list pool is started according to the list allocation request;

Based on the thread, the customer list is extracted in each list pool according to a preset rule and added to the list.
The method for assigning a list to the list according to claim 1, wherein the step of extracting a customer list in the list pool according to a preset rule and adding it to the list includes:

Determining a storage time of each customer list in the list pool;

Adding a preset number of customer lists in the list pool from front to back according to the storage time is added to the list.
The method for assigning a list according to claim 1, wherein the step of searching for a target agent that satisfies a preset condition in the agent group comprises:

Detecting a status of each agent in the agent group;

If the status of the agent is the logged in state, and the count value corresponding to the agent is less than a preset threshold, determining to find the target agent in the agent group;

If the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined that the agent group is not found in the agent group. The target agent.
The method for assigning a list according to claim 2, wherein the step of searching for a target agent that satisfies a preset condition in the agent group comprises:

Detecting a status of each agent in the agent group;

If the status of the agent is the logged in state, and the count value corresponding to the agent is less than a preset threshold, determining to find the target agent in the agent group;

If the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined that the agent group is not found in the agent group. The target agent.
The method for assigning a list according to claim 3, wherein the step of searching for a target agent that satisfies a preset condition in the agent group comprises:

Detecting a status of each agent in the agent group;

If the status of the agent is the logged in state, and the count value corresponding to the agent is less than a preset threshold, determining to find the target agent in the agent group;

If the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined that the agent group is not found in the agent group. The target agent.
The method for assigning a list according to claim 4, wherein the step of searching for a target agent that satisfies a preset condition in the agent group comprises:

Detecting a status of each agent in the agent group;

If the status of the agent is the logged in state, and the count value corresponding to the agent is less than a preset threshold, determining to find the target agent in the agent group;

If the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined that the agent group is not found in the agent group. The target agent.
The method for assigning a list according to claim 5, wherein the step of searching for a target agent that satisfies a preset condition in the agent group comprises:

Detecting a status of each agent in the agent group;

If the status of the agent is the logged in state, and the count value corresponding to the agent is less than a preset threshold, determining to find the target agent in the agent group;

If the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined that the agent group is not found in the agent group. The target agent.
The method for assigning a list according to claim 6, wherein the step of searching for a target agent that satisfies a preset condition in the agent group comprises:

Detecting a status of each agent in the agent group;

If the status of the agent is the logged in state, and the count value corresponding to the agent is less than a preset threshold, determining to find the target agent in the agent group;

If the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined that the agent group is not found in the agent group. The target agent.
The method for assigning a list according to claim 7, wherein the step of searching for a target agent that satisfies a preset condition in the agent group comprises:

Detecting a status of each agent in the agent group;

If the status of the agent is the logged in state, and the count value corresponding to the agent is less than a preset threshold, determining to find the target agent in the agent group;

If the status of the agent is the logged in state, but the count value corresponding to the agent is greater than or equal to the preset threshold, or the status of the agent is not logged in, it is determined that the agent group is not found in the agent group. The target agent.
A list distribution device, wherein the list distribution device comprises:

The extracting module is configured to: when the list allocation request is detected, extract the customer list in the list pool according to the preset rule according to the list allocation request, and add the list to the list;

a searching module, configured to determine each agent group in the list pool, and find, in the agent group, a target agent that meets a preset condition;

An allocation module, configured to: if the target agent is found, assign a customer list in the list to the target agent; if the target agent is not found, corresponding to each agent in the agent group The count value is assigned from a small to a large list of customers in the list of lists.
The list distribution device according to claim 15, wherein the distribution module comprises:

a determining unit, configured to determine, if the target agent is found, whether the associated agent associated with the client in the list is present in the target agent;

And an allocating unit, configured to: if the associated agent exists in the target agent, assign a client list associated with the associated agent to the associated agent;

An obtaining unit, configured to acquire a count value corresponding to each target agent if the associated agent does not exist in the target agent;

The allocating unit is further configured to allocate the customer list in the list of the lists to each target agent according to the count value from small to large.
The list distribution device according to claim 16, wherein the determining unit is further configured to determine whether there is an equal count value among the count values of the respective target agents;

The allocating unit is further configured to allocate a customer list in the list of the names to each target agent according to the count value, if there is no equal count value.
The list distribution device according to claim 17, wherein the distribution module further comprises:

a marking unit, if there is an equal counting value, the target agent with the same counting value is recorded as a conflicting seat;

a first determining unit, configured to determine a level of each conflicting agent;

The allocation unit is further configured to: if the levels of the conflicting agents are inconsistent, the customer list in the list is preferentially assigned to the conflicting seat with a higher level; if the levels of the conflicting agents are the same, the list in the list is The customer list is randomly assigned to conflicting agents of the same level.
A list distribution device, characterized in that the list distribution device comprises a memory, a processor, and a list allocation program stored on the memory and operable on the processor, the list distribution program being processed The steps of the list allocation method of claim 1 are implemented when the device is executed.
A computer readable storage medium, wherein the computer readable storage medium stores a list allocation program, and the list distribution program is executed by a processor to implement the steps of the list allocation method according to claim 1.