Method, apparatus, storage medium and computer device for allocating outbound call list

Abstract

The embodiments of the present application disclose a method, device, storage medium, and computer device for allocating outbound call lists. The method includes: obtaining the remaining outbound call lists in the current outbound call resource pool; predicting the first target list that can be outbound called by the current outbound call resource pool based on the remaining outbound call time and historical outbound call experience; determining the second target list that cannot be outbound called by the current outbound call resource pool according to the remaining outbound call lists and the first target list; determining the target outbound call resource pool from other outbound call resource pools based on the busy degree corresponding to each other outbound call resource pool, and allocating the second target list to the target outbound call resource pool for outbound calling, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool. By means of support for outbound calling from other outbound call resource pools, it is avoided that some users in the outbound call list of the current resource pool cannot be reached, and the situation that the outbound call list cannot be completely called on the same day is avoided.

Description

Technical Field

[0001] The present application relates to the field of computers, and particularly to a method and device for allocating outbound call lists, a computer-readable storage medium, and a computer device. Background Art

[0002] In recent years, with the development and popularization of computer device technology, in some sales promotion scenarios, intelligent outbound calls are used. The core of intelligent outbound calls is the basic technology of AI, which endows products with the capabilities of speech recognition, semantic understanding, and speech synthesis. Simply put, it is about accurately identifying the meaning expressed by customers, generally referred to as intent recognition. On the other hand, the call service built by Fs and sip endows products with the ability to make external calls, and can dial customers' mobile phones for communication.

[0003] In the process of researching and practicing the existing technology, the inventors of the present application found that in the existing technology, when the list volume is large, some users who should have been fully outbound called on the same day cannot be outbound called due to the problem of too low concurrent utilization rate of the resource pool, resulting in waste of the list. Summary of the Invention

[0004] Embodiments of the present application provide a method and device for allocating outbound call lists, which can avoid the situation that the outbound call list cannot be fully dialed on the same day and cause no waste of the list.

[0005] To solve the above technical problems, the embodiments of the present application provide the following technical solutions:

[0006] An outbound call list allocation method, applied to a distributed outbound call resource pool, includes:

[0007] Obtain the remaining outbound call list in the current outbound call resource pool;

[0008] Based on the remaining outbound call time and historical outbound call experience, predict a first target list that can be outbound called by the current outbound call resource pool from the remaining outbound call list;

[0009] According to the remaining outbound call list and the first target list, determine a second target list that cannot be outbound called by the current outbound call resource pool;

[0010] Based on the busy degree corresponding to each other outbound call resource pool, determine a target outbound call resource pool from the other outbound call resource pools, and allocate the second target list to the target outbound call resource pool for outbound calling, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool.

[0011] An outbound call list allocation device, includes:

[0012] An obtaining module, configured to obtain the remaining outbound call list in the current outbound call resource pool;

[0013] A prediction module, configured to predict a first target list that can be called by the current outbound call resource pool from the remaining outbound call list based on the remaining outbound call time and historical outbound call experience;

[0014] A determination module, configured to determine a second target list that cannot be called by the current outbound call resource pool according to the remaining outbound call list and the first target list;

[0015] An allocation module, configured to determine a target outbound call resource pool from other outbound call resource pools based on the busy degree corresponding to each other outbound call resource pool, and allocate the second target list to the target outbound call resource pool for outbound call, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool.

[0016] In some embodiments, the prediction module includes:

[0017] A first acquisition sub-module, configured to acquire the remaining sub-outbound call list corresponding to each outbound call scenario in the remaining outbound call list, and determine the scenario weight coefficient of each outbound call scenario;

[0018] A first prediction sub-module, configured to predict a first target list that can be called by the current outbound call resource pool from the remaining outbound call list based on the remaining outbound call time, the scenario weight coefficient of each outbound call scenario, and historical outbound call experience.

[0019] In some embodiments, the first prediction sub-module is configured to:

[0020] Sort the outbound call scenarios according to the scenario weight coefficients of each outbound call scenario in descending order of the scenario weight coefficients to obtain an outbound call scenario sorting;

[0021] Based on the remaining outbound call time, the outbound call scenario sorting, and historical outbound call experience, predict candidate sub-lists that can be called by the current resource pool in the remaining outbound call sub-lists corresponding to each outbound call scenario in the outbound call scenario sorting;

[0022] Determine a first target list that can be called by the current outbound call resource pool from the remaining outbound call list according to the candidate sub-lists corresponding to each outbound call scenario.

[0023] In some embodiments, the first acquisition sub-module is configured to:

[0024] Acquire the banking business type corresponding to each outbound call scenario and the current time period;

[0025] Determine the priority parameter corresponding to each outbound call scenario based on a preset priority determination rule, the banking business type, and the current time period, and calculate the total priority parameter of multiple outbound call scenarios;

[0026] Calculate the ratio of the priority parameter corresponding to each outbound call scenario to the total priority parameter to obtain the scenario weight coefficient of each outbound call scenario.

[0027] In some embodiments, the determining module includes:

[0028] The first determining sub-module is configured to determine, from the remaining outbound call list, the other outbound call lists except the first target list as the second target list that cannot be outbound called by the current outbound call resource pool.

[0029] In some embodiments, the allocating module includes:

[0030] The second determining sub-module is configured to determine the busy degree corresponding to each other outbound call resource pool, and determine the other outbound call resource pool with the lowest busy degree as the target outbound call resource pool.

[0031] In some embodiments, the second determining sub-module is configured to:

[0032] Determine the remaining outbound call list and the remaining outbound call time corresponding to each other outbound call resource pool;

[0033] Calculate the ratio of the remaining outbound call list to the remaining outbound call time corresponding to each other outbound call resource pool to obtain the busy degree corresponding to each other outbound call resource pool.

[0034] A computer-readable storage medium stores multiple instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the above-mentioned outbound call list allocation method.

[0035] A computer device includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the steps in the above-mentioned outbound call list allocation method.

[0036] In the embodiment of the present application, the remaining outbound call list in the current outbound call resource pool is obtained; based on the remaining outbound call time and historical outbound call experience, the first target list that can be outbound called by the current outbound call resource pool in the remaining outbound call list is predicted; according to the remaining outbound call list and the first target list, the second target list that cannot be outbound called by the current outbound call resource pool is determined; based on the busy degree corresponding to each other outbound call resource pool, a target outbound call resource pool is determined from the other outbound call resource pools, and the second target list is allocated to the target outbound call resource pool for outbound call, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool. In this way, by means of support for outbound calls from other outbound call resource pools, it is avoided that some users in the outbound call list of the current resource pool cannot be outbound called, and further, the situation that the outbound call list cannot be completely called on the same day, resulting in waste of the list, is avoided. Brief Description of the Drawings

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative efforts.

[0038] Figure 1a It is a system schematic diagram of the method for allocating an outbound call list provided by the embodiment of the present application.

[0039] Figure 1b It is a flowchart of the method for allocating an outbound call list provided by the embodiment of the present application.

[0040] Figure 2 It is a structural schematic diagram of the device for allocating an outbound call list provided by the embodiment of the present application.

[0041] Figure 3 It is a structural schematic diagram of the computer device provided by the embodiment of the present application. Detailed Embodiments

[0042] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative efforts belong to the scope of protection of the present application.

[0043] Please refer to Figure 1a , Figure 1aSystem schematic diagram of the outbound call list allocation method provided by the embodiments of the present application. The system may include at least one client 1000, at least one computer device 2000, at least one database 3000, and a network 4000. The computer devices 2000 can be directly connected by wire or indirectly connected wirelessly to form a distributed structure, and the client 1000 can be a terminal device such as a mobile phone, a computer, or a personal digital assistant. The computer device 2000 makes network calls to the client 1000 through the network 4000. Among them, the network 4000 can be a wireless network or a wired network. For example, the wireless network is a wireless local area network (WLAN), a local area network (LAN), a cellular network, a 2G network, a 3G network, a 4G network, a 5G network, etc. In addition, the system may include a database 3000, and the database 3000 can be used to store the preferences of multiple users, as well as the outbound call list, etc.

[0044] Embodiments of the present application provide a method for allocating an outbound call list, and this method can be executed by a computer device. As Figure 1a shown, the computer device 2000 obtains the remaining outbound call list in the current outbound call resource pool; based on the remaining outbound call time and historical outbound call experience, predicts the first target list that can be outbound called by the current outbound call resource pool from the remaining outbound call list; determines the second target list that cannot be outbound called by the current outbound call resource pool according to the remaining outbound call list and the first target list; based on the busy degree corresponding to each other outbound call resource pool, determines the target outbound call resource pool from other outbound call resource pools, and allocates the second target list to the target outbound call resource pool for outbound calling. The other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool. Based on this, by calculating the weighted average total outbound call duration corresponding to the outbound call scenario, the outbound call concurrency is obtained, so as to dynamically allocate outbound call resources, avoid the situation that the outbound call list cannot be completely called on the same day, and does not cause waste of the list.

[0045] It should be noted that Figure 1a The scenario schematic diagram of the outbound call list allocation method shown is only an example. The outbound call list allocation system and scenario described in the embodiments of the present application are for more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art know that with the evolution of the outbound call list allocation system and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0046] In this embodiment, the description will be made from the perspective of the outbound call list allocation device. The outbound call list allocation device can be specifically integrated in a computer device with a storage unit and installed with a microprocessor and having computing capabilities.

[0047] Please refer to Figure 1b , Figure 1b which is a schematic flowchart of the method for allocating outbound call lists provided by an embodiment of this application. The method for allocating outbound call lists includes:

[0048] In step 101, obtain the remaining outbound call lists in the current outbound call resource pool.

[0049] Among them, the distributed outbound call resource pool is the resource pool referred to by the central processing unit in each computer device in the distributed structure. Each outbound call resource pool will be configured with outbound call lists by business personnel for outbound calls. The remaining outbound call lists are the lists that remain un-called by the current outbound call resource pool among the outbound call lists as of the current time point.

[0050] For example, if the current outbound call resource pool is allocated a total of 1000 outbound call lists, and there are 500 lists that have not been called by the current outbound call resource pool at 12:00, then these 500 lists are the remaining outbound call lists.

[0051] Specifically, the scenario weight coefficient can be set by business personnel based on the importance or priority of different outbound call scenarios.

[0052] In step 102, based on the remaining outbound call time and historical outbound call experience, predict the first target list among the remaining outbound call lists that can be called by the current outbound call resource pool.

[0053] Among them, the outbound call system generally closes at 6:00 pm. Therefore, the remaining outbound call time can be determined according to the current time and the closing time. Then, based on the remaining outbound call time and historical outbound call experience, predict the first target list among the remaining outbound call lists that can be successfully called by the current outbound call resource pool within the remaining outbound call time.

[0054] In some embodiments, the step of predicting the first target list among the remaining outbound call lists that can be called by the current outbound call resource pool based on the remaining outbound call time and historical outbound call experience includes:

[0055] (1) Obtain the remaining sub-outbound call lists corresponding to each outbound call scenario in the remaining outbound call lists, and determine the scenario weight coefficient of each outbound call scenario;

[0056] (2) Based on the remaining outbound call time, the scenario weight coefficient of each outbound call scenario, and historical outbound call experience, predict the first target list among the remaining outbound call lists that can be called by the current outbound call resource pool.

[0057] Among them, different outbound call services correspond to different outbound call scenarios. For example, the outbound call scenario corresponding to the credit card recommendation service is the credit card recommendation scenario, and the outbound call scenario corresponding to the insurance recommendation service is the insurance recommendation scenario. Moreover, for different outbound call scenarios, an outbound call list will be configured for each outbound call scenario. The outbound call list can determine the purchase tendency of users based on historical outbound calls, so as to determine whether a specific service is hit in the purchase tendency of users. If it is hit, the user will be assigned to the list of the specific outbound call scenario corresponding to the specific service. For example: In the historical outbound call with user A, user A indicates that they need to purchase an insurance. Then, the number of user A can be assigned to the outbound call list corresponding to the insurance recommendation outbound call scenario for subsequent outbound calls for insurance business to user A.

[0058] Specifically, the remaining sub-outbound call list is the outbound call volume that has not been made for each outbound call scenario currently remaining. Due to the different importance levels of business scenarios, according to historical outbound call experience, the list that can be successfully outbound called by the current outbound call resource pool within the remaining outbound call time can be determined first from the business scenarios with higher importance levels by determining the scenario weight coefficient of each outbound call scenario.

[0059] In some embodiments, the step of predicting the first target list that can be outbound called by the current outbound call resource pool from the remaining outbound call list based on the remaining outbound call time, the scenario weight coefficient of each outbound call scenario, and historical outbound call experience includes:

[0060] (1.1) Sort the outbound call scenarios according to the scenario weight coefficient of each outbound call scenario in descending order of the scenario weight coefficient to obtain the outbound call scenario sorting;

[0061] (1.2) Based on the remaining outbound call time, the outbound call scenario sorting, and historical outbound call experience, predict the candidate sub-lists that can be outbound called by the current resource pool in the remaining outbound call sub-lists corresponding to each outbound call scenario in the outbound call scenario sorting;

[0062] (1.3) Determine the first target list that can be outbound called by the current outbound call resource pool from the remaining outbound call list according to the candidate sub-lists corresponding to each outbound call scenario.

[0063] Among them, the magnitude of the scenario weight coefficient indicates the importance level of the outbound call scenario. The larger the scenario weight coefficient, the higher the importance level of the outbound call scenario, and the smaller the scenario weight coefficient, the lower the importance level of the outbound call scenario. Therefore, the outbound call scenarios can be sorted in descending order of the scenario weight coefficient to obtain the outbound call scenario sorting. For example, the scenario weight coefficient of outbound call scenario A is 3, and the scenario weight coefficient of outbound call scenario B is 2. Then, the importance level of outbound call scenario A is higher than that of outbound call scenario B, and outbound call scenario A is in front of outbound call scenario B after the outbound call scenario sorting.

[0064] Specifically, after sorting the outbound call scenarios, by combining the remaining outbound call sub-lists corresponding to each outbound call scenario and the remaining outbound call time, a candidate sub-list that can be outbound called by the current resource pool can be preferentially determined from the remaining outbound call sub-lists corresponding to the outbound call scenarios ranked ahead.

[0065] For example, outbound call scenario A is ranked ahead of outbound call scenario B in the sorting. There are 50 remaining outbound call sub-lists corresponding to outbound call scenario A and 100 remaining outbound call sub-lists corresponding to outbound call scenario B. Historical outbound call experience can be used to determine that one call in outbound call scenario A takes 2 minutes and one call in outbound call scenario B takes 10 minutes. The remaining outbound call duration is 2 hours. First, calculate 50 * 2 = 100 minutes, which is less than 2 hours. Then it is determined that all 50 of the remaining outbound call sub-lists corresponding to outbound call scenario A can be outbound called by the current outbound call resource pool. Only 20 minutes are left, which can only be used to make outbound calls to 2 sub-lists in outbound call scenario B. Then, the 2 sub-lists in outbound call scenario B are determined as the candidate sub-lists.

[0066] In some embodiments, the step of determining the scenario weight coefficient for each outbound call scenario includes:

[0067] (1) Obtain the banking business type corresponding to each outbound call scenario and the current time period;

[0068] (2) Based on a preset priority determination rule, the banking business type, and the current time period, determine the priority parameter corresponding to each outbound call scenario, and calculate the total priority parameter of multiple outbound call scenarios;

[0069] (3) Calculate the ratio of the priority parameter corresponding to each outbound call scenario to the total priority parameter to obtain the scenario weight coefficient for each outbound call scenario.

[0070] Among them, the scenario weight parameter can also be calculated. The calculation method is as follows: Obtain the current time period and the banking business type corresponding to each outbound call scenario. For example, there are a credit card recommendation outbound call scenario and a loan collection outbound call scenario, and the current time period is 8:00 - 10:00. Based on a preset priority determination rule, the banking business type, and the current time period, determine the priority parameter corresponding to each outbound call scenario, and calculate the total priority parameter of multiple outbound call scenarios. Since 8:00 - 10:00 is generally the working time of users, according to the preset priority determination rule, the loan collection outbound call scenario has a higher priority, and the priority parameter can be set to 2; the credit card recommendation outbound call scenario has a lower priority, and the priority parameter can be set to 1; the total priority parameter is 1 + 2 = 3. Calculate the ratio of the priority parameter corresponding to each outbound call scenario to the total priority parameter to obtain the scenario weight coefficient for each outbound call scenario. Then, the scenario weight coefficient of the loan collection outbound call scenario is 2 / 3, and the scenario weight coefficient of the credit card recommendation outbound call scenario is 1 / 3.

[0071] In step 103, according to the remaining outbound call list and the first target list, determine a second target list that cannot be outbound called by the current outbound call resource pool.

[0072] Among them, after predicting the first target list that can be successfully outbound called by the current outbound call resource, the second target list that cannot be outbound called by the current outbound call resource pool can be determined according to the remaining outbound call list and the first target list.

[0073] In some embodiments, the step of determining a second target list that cannot be outbound called by the current outbound call resource pool according to the remaining outbound call list and the first target list includes:

[0074] Determine the other outbound call lists in the remaining outbound call list except the first target list as the second target list that cannot be outbound called by the current outbound call resource pool.

[0075] Among them, determine the other outbound call lists in the remaining outbound call list except the first target list as the second target list that cannot be outbound called by the current outbound call resource pool. For example, if it is determined that all 50 of the remaining outbound call sub-lists corresponding to outbound call scenario A can be outbound called by the current outbound call resource pool, then 2 in outbound call scenario B are determined as candidate sub-lists, and the remaining 48 in outbound call scenario B are determined as the second target list.

[0076] In step 104, based on the busy degree corresponding to each other outbound call resource pool, determine a target outbound call resource pool from the other outbound call resource pools, and allocate the second target list to the target outbound call resource pool for outbound calling. The other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool.

[0077] Among them, when it is determined that there is a second target list in the remaining outbound call list, determine a target outbound call resource pool from the other outbound call resource pools based on the busy degree corresponding to each other outbound call resource pool, and allocate the second target list to the target outbound call resource pool for outbound calling. The other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool.

[0078] Specifically, the allocation method can be TCP transmission, or gateway protocol transmission, etc., which is not limited here.

[0079] In some embodiments, the step of determining a target outbound call resource pool from the other outbound call resource pools based on the busy degree corresponding to each other outbound call resource pool includes:

[0080] Determine the busy degree corresponding to each other outbound call resource pool, and determine the other outbound call resource pool with the lowest busy degree as the target outbound call resource pool.

[0081] Among them, since other outbound call resource pools may also be performing outbound call operations, it is necessary to determine the busy degree corresponding to each other outbound call resource pool, and determine the other outbound call resource pool with the lowest busy degree (that is, the one with the ability of additional processing resources) as the target outbound call resource pool.

[0082] In some embodiments, the step of determining the busy degree corresponding to each other outbound call resource pool includes:

[0083] (1.1) Determine the remaining outbound call list and the remaining outbound call time corresponding to each other outbound call resource pool;

[0084] (1.2) Calculate the ratio of the remaining outbound call list to the remaining outbound call time corresponding to each other outbound call resource pool to obtain the busy degree corresponding to each other outbound call resource pool.

[0085] Among them, the determination method of the busy degree can be obtained by determining the ratio of the remaining outbound call list to the remaining outbound call time corresponding to the other outbound call resource pool. For example, the remaining outbound call list corresponding to the other outbound call resource pool A is 180, and the remaining outbound call time is 1 hour. The remaining outbound call list corresponding to the other outbound call resource pool B is 120, and the remaining outbound call time is 1 hour. Then the busy degree of the other outbound call resource pool A is 180 / 60 = 3, and the busy degree of the other outbound call resource pool B is 120 / 60 = 2. It can be seen that the greater the result, the higher the busy degree.

[0086] As can be seen from the above, in the embodiment of the present application, the remaining outbound call list in the current outbound call resource pool is obtained; based on the remaining outbound call time and historical outbound call experience, the first target list that can be outbound called by the current outbound call resource pool in the remaining outbound call list is predicted; according to the remaining outbound call list and the first target list, the second target list that cannot be outbound called by the current outbound call resource pool is determined; based on the busy degree corresponding to each other outbound call resource pool, the target outbound call resource pool is determined from the other outbound call resource pools, and the second target list is allocated to the target outbound call resource pool for outbound call. The other outbound call resource pool is other resource pools in the distributed resource pool except the current outbound call resource pool. In this way, by the method of supporting outbound calls by other outbound call resource pools, it is avoided that some users in the outbound call list of the current resource pool cannot be outbound called, and further avoided that the situation that the outbound call list cannot be completely called on the same day occurs, resulting in waste of the list.

[0087] To facilitate better implementation of the outbound call list allocation method provided by the embodiment of the present application, the embodiment of the present application also provides a device based on the above outbound call list allocation method. The meanings of the nouns are the same as those in the above outbound call list allocation method, and the specific implementation details can refer to the description in the method embodiment.

[0088] Please refer toFigure 2 , Figure 2 is a schematic structural diagram of an outbound call list allocation device provided by an embodiment of the present application, where the outbound call list allocation device may include an acquisition module 201, a prediction module 202, a determination module 203, an allocation module 204, etc.

[0089] The acquisition module 201 is used to acquire the remaining outbound call lists in the current outbound call resource pool;

[0090] The prediction module 202 is used to predict a first target list that can be outbound called by the current outbound call resource pool from the remaining outbound call lists based on the remaining outbound call time and historical outbound call experience;

[0091] The determination module 203 is used to determine a second target list that cannot be outbound called by the current outbound call resource pool according to the remaining outbound call lists and the first target list;

[0092] The allocation module 204 is used to determine a target outbound call resource pool from other outbound call resource pools based on the busy degree corresponding to each other outbound call resource pool, and allocate the second target list to the target outbound call resource pool for outbound calling, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool.

[0093] In some embodiments, the prediction module includes:

[0094] A first acquisition sub-module, which is used to acquire the remaining sub-outbound call lists corresponding to each outbound call scenario in the remaining outbound call lists and determine the scenario weight coefficient of each outbound call scenario;

[0095] A first prediction sub-module, which is used to predict a first target list that can be outbound called by the current outbound call resource pool from the remaining outbound call lists based on the remaining outbound call time, the scenario weight coefficient of each outbound call scenario, and historical outbound call experience.

[0096] In some embodiments, the first prediction sub-module is used to:

[0097] Sort the outbound call scenarios according to the scenario weight coefficients of each outbound call scenario in descending order of the scenario weight coefficients to obtain an outbound call scenario sorting;

[0098] Based on the remaining outbound call time, the outbound call scenario sorting, and historical outbound call experience, predict candidate sub-lists that can be outbound called by the current resource pool in the remaining outbound call sub-lists corresponding to each outbound call scenario in the outbound call scenario sorting;

[0099] Determine a first target list that can be outbound called by the current outbound call resource pool from the candidate sub-lists corresponding to each outbound call scenario.

[0100] In some embodiments, the first acquisition sub-module is configured to:

[0101] Acquire the banking business types corresponding to each outbound call scenario and the current time period;

[0102] Determine the priority parameters corresponding to each outbound call scenario based on a preset priority determination rule, the banking business type, and the current time period, and calculate the total priority parameter of multiple outbound call scenarios;

[0103] Calculate the ratio of the priority parameter corresponding to each outbound call scenario to the total priority parameter to obtain the scenario weight coefficient of each outbound call scenario.

[0104] In some embodiments, the determination module includes:

[0105] The first determination sub-module is configured to determine the other outbound call lists in the remaining outbound call list except the first target list as the second target list that cannot be outbound called by the current outbound call resource pool.

[0106] In some embodiments, the allocation module includes:

[0107] The second determination sub-module is configured to determine the busy degree corresponding to each other outbound call resource pool, and determine the other outbound call resource pool with the lowest busy degree as the target outbound call resource pool.

[0108] In some embodiments, the second determination sub-module is configured to:

[0109] Determine the remaining outbound call list and the remaining outbound call time corresponding to each other outbound call resource pool;

[0110] Calculate the ratio of the remaining outbound call list to the remaining outbound call time corresponding to each other outbound call resource pool to obtain the busy degree corresponding to each other outbound call resource pool.

[0111] As can be seen from the above, in the embodiment of the present application, the obtaining module 201 obtains the remaining outbound call list in the current outbound call resource pool; the prediction module 202 predicts a first target list that can be outbound called by the current outbound call resource pool based on the remaining outbound call time and historical outbound call experience; the determination module 203 determines a second target list that cannot be outbound called by the current outbound call resource pool according to the remaining outbound call list and the first target list; the allocation module 204 determines a target outbound call resource pool from other outbound call resource pools based on the busy degree corresponding to each other outbound call resource pool, and allocates the second target list to the target outbound call resource pool for outbound call, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool. In this way, by means of supporting outbound calls by other outbound call resource pools, it is avoided that some users in the outbound call list of the current resource pool cannot be outbound called, and further, the situation that the outbound call list cannot be completely called on the same day is avoided, resulting in waste of the list.

[0112] For the specific implementation of each of the above operations, reference may be made to the foregoing embodiments, which will not be elaborated herein.

[0113] Correspondingly, the embodiment of the present application further provides a computer device, which may be a terminal or a server. The terminal may be a smart phone, a tablet computer, a notebook computer, a touch screen, a game console, a personal computer (PC), a personal digital assistant (PDA), and other terminal devices. As Figure 3 shown, Figure 3 is a schematic structural diagram of the computer device provided by the embodiment of the present application. The computer device 2000 includes a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, and a computer program stored on the memory 402 and executable on the processor. Among them, the processor 401 is electrically connected to the memory 402. Those skilled in the art can understand that the structural diagram of the computer device shown in the figure does not constitute a limitation on the computer device, and it may include more or fewer components than shown in the figure, or combine some components, or arrange different components.

[0114] The processor 401 is the control center of the computer device 2000, connects various parts of the entire computer device 2000 through various interfaces and lines, executes various functions of the computer device 2000 and processes data by running or loading software programs and / or modules stored in the memory 402, and calling data stored in the memory 402, so as to monitor the computer device 2000 as a whole.

[0115] In an embodiment of the present application, the processor 401 in the computer device 2000 will load the instructions corresponding to the processes of one or more application programs into the memory 402 according to the following steps, and the processor 401 will run the application programs stored in the memory 402 to implement various functions:

[0116] Obtain the remaining outbound call list in the current outbound call resource pool; based on the remaining outbound call time and historical outbound call experience, predict a first target list in the remaining outbound call list that can be outbound called by the current outbound call resource pool; according to the remaining outbound call list and the first target list, determine a second target list that cannot be outbound called by the current outbound call resource pool; based on the busy degree corresponding to each other outbound call resource pool, determine a target outbound call resource pool from other outbound call resource pools, and allocate the second target list to the target outbound call resource pool for outbound calling, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool.

[0117] In some embodiments, the step of predicting a first target list in the remaining outbound call list that can be outbound called by the current outbound call resource pool based on the remaining outbound call time and historical outbound call experience includes:

[0118] Obtain the remaining sub-outbound call list corresponding to each outbound call scenario in the remaining outbound call list, and determine the scenario weight coefficient of each outbound call scenario;

[0119] Based on the remaining outbound call time, the scenario weight coefficient of each outbound call scenario, and historical outbound call experience, predict a first target list in the remaining outbound call list that can be outbound called by the current outbound call resource pool.

[0120] In some embodiments, the step of predicting a first target list in the remaining outbound call list that can be outbound called by the current outbound call resource pool based on the remaining outbound call time, the scenario weight coefficient of each outbound call scenario, and historical outbound call experience includes:

[0121] Sort the outbound call scenarios according to the scenario weight coefficient from large to small according to the scenario weight coefficient of each outbound call scenario to obtain an outbound call scenario sorting;

[0122] Based on the remaining outbound call time, the outbound call scenario sorting, and historical outbound call experience, predict a candidate sub-list in the remaining outbound call sub-lists corresponding to each outbound call scenario in the outbound call scenario sorting that can be outbound called by the current resource pool;

[0123] According to the candidate sub-lists corresponding to each outbound call scenario, determine a first target list in the remaining outbound call list that can be outbound called by the current outbound call resource pool.

[0124] In some embodiments, the step of determining the scenario weight coefficient for each outbound call scenario includes:

[0125] Obtain the banking business type corresponding to each outbound call scenario and the current time period;

[0126] Based on a preset priority determination rule, the banking business type, and the current time period, determine the priority parameter corresponding to each outbound call scenario, and calculate the total priority parameter of multiple outbound call scenarios;

[0127] Calculate the ratio of the priority parameter corresponding to each outbound call scenario to the total priority parameter to obtain the scenario weight coefficient of each outbound call scenario.

[0128] In some embodiments, the step of determining the second target list that cannot be called by the current outbound call resource pool according to the remaining outbound call list and the first target list includes:

[0129] Determine the other outbound call lists in the remaining outbound call list except the first target list as the second target list that cannot be called by the current outbound call resource pool.

[0130] In some embodiments, the step of determining the target outbound call resource pool from other outbound call resource pools based on the busy degree corresponding to each other outbound call resource pool includes:

[0131] Determine the busy degree corresponding to each other outbound call resource pool, and determine the other outbound call resource pool with the lowest busy degree as the target outbound call resource pool.

[0132] In some embodiments, the step of determining the busy degree corresponding to each other outbound call resource pool includes:

[0133] Determine the remaining outbound call list and the remaining outbound time corresponding to each other outbound call resource pool;

[0134] Calculate the ratio of the remaining outbound call list to the remaining outbound time corresponding to each other outbound call resource pool to obtain the busy degree corresponding to each other outbound call resource pool.

[0135] For the specific implementation of each of the above operations, reference may be made to the previous embodiments and will not be elaborated herein.

[0136] Optionally, as Figure 3 shown, the computer device 2000 further includes: a touch display screen 403, an input unit 404, and a power supply 405. Among them, the processor 401 is electrically connected to the touch display screen 403, the input unit 404, and the power supply 405 respectively. Those skilled in the art can understand, Figure 3The computer device structure shown does not constitute a limitation on the computer device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0137] The touch display screen 403 can be used to display a graphical user interface and receive operation instructions generated by a user acting on the graphical user interface. The touch display screen 403 can include a display panel and a touch panel. Among them, the display panel can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of the computer device. These graphical user interfaces can be composed of graphics, text, icons, videos, and any combination thereof. Optionally, the display panel can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. The touch panel can be used to collect touch operations of the user on or near it (such as operations of the user using any suitable object or accessory such as a finger or a stylus on the touch panel or near the touch panel), and generate corresponding operation instructions, and the operation instructions execute the corresponding program. Optionally, the touch panel can include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the touch orientation of the user, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the processor 401, and can receive and execute the commands sent by the processor 401. The touch panel can cover the display panel. When the touch panel detects a touch operation on or near it, it transmits it to the processor 401 to determine the type of touch event. Subsequently, the processor 401 provides a corresponding visual output on the display panel according to the type of touch event. In the embodiments of the present application, the touch panel and the display panel can be integrated into the touch display screen 403 to implement input and output functions. However, in some embodiments, the touch panel and the touch panel can be implemented as two independent components to implement input and output functions. That is, the touch display screen 403 can also be used as part of the input unit 404 to implement the input function.

[0138] In the embodiments of the present application, by executing a game application through the processor 401, a graphical user interface is generated on the touch display screen 403. The virtual scene on the graphical user interface includes at least one skill control area, and the skill control area includes at least one skill control. The touch display screen 403 is used to present the graphical user interface and receive operation instructions generated by a user acting on the graphical user interface.

[0139] The input unit 404 can be used to receive input digital, character information or user feature information (such as fingerprints, irises, facial information, etc.), and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.

[0140] The power supply 405 is used to supply power to each component of the computer device 2000. Optionally, the power supply 405 can be logically connected to the processor 401 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system. The power supply 405 can also include any components such as one or more DC or AC power supplies, a recharge system, a power failure detection circuit, a power converter or inverter, and a power status indicator.

[0141] Although Figure 3 not shown in the figure, the computer device 2000 can also include a Wi-Fi module, a Bluetooth module, etc., which will not be elaborated here.

[0142] In the above embodiments, the descriptions of each embodiment have their own emphases. For parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0143] As can be seen from the above, the computer device provided in this embodiment obtains the remaining outbound call list in the current outbound call resource pool; predicts the first target list that can be outbound called by the current outbound call resource pool based on the remaining outbound call time and historical outbound call experience; determines the second target list that cannot be outbound called by the current outbound call resource pool according to the remaining outbound call list and the first target list; determines a target outbound call resource pool from other outbound call resource pools based on the busy degree corresponding to each other outbound call resource pool, and allocates the second target list to the target outbound call resource pool for outbound calling, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool. In this way, by means of supporting outbound calls by other outbound call resource pools, it is avoided that some users in the outbound call list of the current resource pool cannot be outbound called, and further, the situation that the outbound call list cannot be completely dialed on the same day, resulting in waste of the list, is avoided.

[0144] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructions, or by controlling relevant hardware through instructions. The instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0145] Therefore, an embodiment of the present application provides a computer-readable storage medium, in which multiple computer programs are stored. The computer programs can be loaded by a processor to execute the steps in any one of the control methods of the skills provided by the embodiments of the present application. For example, the computer program can execute the following steps:

[0146] Obtain the remaining outbound call list in the current outbound call resource pool; predict a first target list that can be outbound called by the current outbound call resource pool based on the remaining outbound call time and historical outbound call experience; determine a second target list that cannot be outbound called by the current outbound call resource pool according to the remaining outbound call list and the first target list; determine a target outbound call resource pool from other outbound call resource pools based on the busy degree corresponding to each other outbound call resource pool, and allocate the second target list to the target outbound call resource pool for outbound calling, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool.

[0147] For the specific implementation of each of the above operations, reference may be made to the previous embodiments and will not be elaborated here.

[0148] Among them, the storage medium may include: read only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc.

[0149] Since the computer program stored in the storage medium can execute the steps in any of the outbound call list allocation methods provided in the embodiments of the present application, the beneficial effects achievable by any of the outbound call list allocation methods provided in the embodiments of the present application can be achieved. For details, refer to the previous embodiments and will not be elaborated here.

[0150] The above has introduced in detail an outbound call list allocation method, device, storage medium and computer device provided by the embodiments of the present application. Specific examples are used in this article to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those skilled in the art, according to the idea of the present application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present application.

Claims

1. A method for allocating an outbound call list, characterized in that Applied to a distributed outbound resource pool, including: Obtain the remaining outbound list in the current outbound resource pool, where the remaining outbound list is the list of remaining outbound calls in the outbound list of the current outbound resource pool that have not been called by the current outbound resource pool as of the current time point; Obtain the remaining sub-outbound list corresponding to each outbound scenario in the remaining outbound list, and determine the scenario weight coefficient for each outbound scenario; Based on the remaining outbound time, the scenario weight coefficient of each outbound scenario, and historical outbound experience, predict the first target list that can be called by the current outbound resource pool from the remaining outbound list; According to the remaining outbound list and the first target list, determine the second target list that cannot be called by the current outbound resource pool; Based on the busy degree corresponding to each other outbound resource pool, determine the target outbound resource pool from the other outbound resource pools, and allocate the second target list to the target outbound resource pool for outbound calls. The other outbound resource pools are other resource pools in the distributed resource pool except the current outbound resource pool.

2. The distribution method of the outbound call list according to claim 1, characterized in that, The step of predicting the first target list that can be called by the current outbound resource pool from the remaining outbound list based on the remaining outbound time, the scenario weight coefficient of each outbound scenario, and historical outbound experience includes: Sort the outbound scenarios according to the scenario weight coefficient of each outbound scenario from large to small to obtain the outbound scenario sorting; Based on the remaining outbound time, the outbound scenario sorting, and historical outbound experience, predict the candidate sub-lists that can be called by the current resource pool from the remaining outbound sub-lists corresponding to each outbound scenario in the outbound scenario sorting; According to the candidate sub-lists corresponding to each outbound scenario, determine the first target list that can be called by the current outbound resource pool from the remaining outbound list.

3. The distribution method of the outbound call list according to claim 1, characterized in that The step of determining the scenario weight coefficient for each outbound scenario includes: Obtain the banking business type corresponding to each outbound scenario and the current time period; Based on a preset priority determination rule, the banking business type, and the current time period, determine the priority parameter corresponding to each outbound scenario, and calculate the total priority parameter of multiple outbound scenarios; Calculate the ratio of the priority parameter corresponding to each outbound scenario to the total priority parameter to obtain the scenario weight coefficient for each outbound scenario.

4. The distribution method of the outbound call list according to claim 1, characterized in that The step of determining the second target list that cannot be called by the current outbound resource pool according to the remaining outbound list and the first target list includes: Determine the other outbound lists in the remaining outbound list except the first target list as the second target list that cannot be called by the current outbound resource pool.

5. The distribution method of the outbound call list according to claim 1, wherein The step of determining the target outbound resource pool from the other outbound resource pools based on the busy degree corresponding to each other outbound resource pool includes: Determine the busy degree corresponding to each other outbound resource pool, and determine the other outbound resource pool with the lowest busy degree as the target outbound resource pool.

6. The distribution method of the outbound call list according to claim 5, characterized in that, The step of determining the busy degree corresponding to each other outbound resource pool includes: Determine the remaining outbound list and the remaining outbound time corresponding to each other outbound resource pool; Calculate the ratio of the remaining outbound call list to the remaining outbound call time corresponding to each other outbound call resource pool to obtain the busyness level corresponding to each other outbound call resource pool.

7. An allocation device for an outbound call list, characterized in that Applied to a distributed outbound call resource pool, including: An acquisition module, configured to acquire the remaining outbound call list in the current outbound call resource pool, where the remaining outbound call list is the list of the remaining outbound call list in the outbound call list of the current outbound call resource pool that has not been outbound called by the current outbound call resource pool as of the current time point; A prediction module, configured to acquire the remaining sub-outbound call list corresponding to each outbound call scenario in the remaining outbound call list, determine the scenario weight coefficient of each outbound call scenario, and predict the first target list that can be outbound called by the current outbound call resource pool based on the remaining outbound call time, the scenario weight coefficient of each outbound call scenario, and historical outbound call experience; A determination module, configured to determine a second target list that cannot be outbound called by the current outbound call resource pool according to the remaining outbound call list and the first target list; An allocation module, configured to determine a target outbound call resource pool from other outbound call resource pools based on the busyness level corresponding to each other outbound call resource pool, and allocate the second target list to the target outbound call resource pool for outbound calling, where the other outbound call resource pools are other resource pools in the distributed resource pool except the current outbound call resource pool.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores multiple instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the outbound call list allocation method according to any one of claims 1 to 6.

9. A computer device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the outbound call list allocation method according to any one of claims 1 to 6.

Images