Outbound task scheduling method and device

Abstract

The invention provides an outbound task scheduling method and device, and the method comprises the steps: determining a list type of a list according to the first feature information of the list; storing the list into a first list warehouse according to the list category of the list; wherein the category of the first name list warehouse corresponds to the name list category of the name list, different categories of name lists correspond to different categories of name list warehouses, and the priorities of the different categories of name list warehouses are different; obtaining a to-be-dialed list from the first list warehouse according to the priority of the first list warehouse; and storing the list to be dialed into a number sending pool. Through the call-out task scheduling method provided by the invention, differentiated scheduling of call-out based on the granularity of the to-be-dialed list can be realized, the pertinence and flexibility of call-out scheduling are improved, and the call-out effect is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method and device for scheduling outbound call tasks. Background Art

[0002] Outbound calling refers to dialing numbers based on a waiting list to market to the target customer group or provide customer service. Among them, intelligent outbound calling is an outbound calling method that uses voice dialogue robots as the carrier. This outbound calling method is not only highly efficient but also saves labor costs, and is therefore becoming more and more widely used.

[0003] Currently, the scheduling of outbound call tasks usually involves directly assigning each waiting-to-call list to the scheduling task without distinction, and then starting the scheduling task to retrieve the waiting-to-call list in turn for sending the number for outbound call. This outbound call scheduling method has poor flexibility and leads to poor outbound call results. Summary of the Invention

[0004] The embodiments of the present application provide an outbound call task scheduling method and device to solve the problem of poor outbound call effect caused by the poor flexibility of the existing outbound call scheduling method.

[0005] In order to solve the above technical problems, this application is implemented as follows:

[0006] In a first aspect, an embodiment of the present application provides a method for scheduling outbound call tasks. The method includes:

[0007] determining a list category of the list according to the first characteristic information of the list;

[0008] According to the list category of the list, the list is stored in a first list warehouse; wherein the category of the first list warehouse corresponds to the list category of the list, different categories of lists correspond to different categories of list warehouses, and different categories of list warehouses have different priorities;

[0009] Obtaining a to-be-dialed list from the first list warehouse according to the priority of the first list warehouse;

[0010] The to-be-dialed list is stored in a number pool.

[0011] In a second aspect, an embodiment of the present application further provides an outbound call task scheduling device. The outbound call task scheduling device includes:

[0012] A first determining module, configured to determine a list category of the list according to first characteristic information of the list;

[0013] A first storing module is configured to store the list into a first list warehouse according to the list category of the list; wherein the category of the first list warehouse corresponds to the list category of the list, different categories of lists correspond to different categories of list warehouses, and different categories of list warehouses have different priorities;

[0014] an acquisition module, configured to acquire a to-be-dialed list from the first list warehouse according to the priority of the first list warehouse;

[0015] The second storing module is used to store the to-be-dialed list into the number sending pool.

[0016] In a third aspect, an embodiment of the present application further provides an outbound call task scheduling device, comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the above-mentioned outbound call task scheduling method when executed by the processor.

[0017] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned outbound call task scheduling method are implemented.

[0018] In a fifth aspect, an embodiment of the present application further provides a computer program product, which is stored in a storage medium and implements the steps of the above-mentioned outbound call task scheduling method when the computer program product is executed by at least one processor.

[0019] In an embodiment of the present application, the list category of the list is determined according to the first characteristic information of the list; the list is stored in a first list warehouse according to the list category of the list; wherein the category of the first list warehouse corresponds to the list category of the list, and lists of different categories correspond to list warehouses of different categories, and list warehouses of different categories have different priorities; according to the priority of the first list warehouse, the list to be dialed is obtained from the first list warehouse; the obtained list to be dialed is stored in the number sending pool, that is, the embodiment of the present application schedules the list according to the first characteristic information of the list, so that differentiated scheduling of outbound calls based on the granularity of the list can be achieved, which improves the pertinence and flexibility of outbound call scheduling, and is conducive to improving the outbound call effect; in addition, by setting up list warehouses of different categories to store lists of different categories, and list warehouses of different categories have different priorities, it is convenient to schedule lists of different categories separately, which is relatively simple to implement. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1 This is one of the flow charts of the outbound call task scheduling method provided in an embodiment of the present application;

[0022] Figure 2 This is a schematic diagram of the interaction between the outbound call system and the upstream business system provided in an embodiment of the present application;

[0023] Figure 3a This is the second flowchart of the outbound call task scheduling method provided in the embodiment of the present application;

[0024] Figure 3b This is a schematic diagram of a list of different dialing methods using different scheduling channels provided in an embodiment of the present application;

[0025] Figure 3c This is a schematic diagram of splitting scheduling tasks based on dialing methods provided in an embodiment of the present application;

[0026] Figure 4 is a schematic diagram of a list warehouse and a list queue provided in an embodiment of the present application;

[0027] Figure 5 This is a schematic diagram of obtaining a list and sending it to a number pool according to an embodiment of the present application;

[0028] Figure 6 This is one of the structural diagrams of the outbound call task scheduling device provided in an embodiment of the present application;

[0029] Figure 7 This is the second structural diagram of the outbound call task scheduling device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0031] For ease of understanding, some terms involved in the embodiments of this application are explained below:

[0032] Waiting list: the list or number that needs to be dialed out, for example, the list that needs to be dialed on the same day is entered into the waiting list table (including the first round and repeat calls).

[0033] Dialing method: Different dialing methods can correspond to different number delivery rates. For example, the above dialing methods can include a speed-limited dialing method and a regular dialing method. The speed-limited dialing method is used to indicate that the number is delivered and dialed according to the specified number of queries per second (QPS) under the configured resources. For example, within the specified QPS limit, the number is delivered and dialed at full capacity according to the configured number of AI seats. The regular dialing method is used to indicate that the number is delivered and dialed as quickly as possible under the configured resources. For example, the number is delivered and dialed at full capacity according to the configured number of AI seats. There is no speed limit in this dialing method.

[0034] List warehouse: Each list warehouse can include one or more list queues. By setting up different categories of list warehouses, you can process different categories of lists.

[0035] List queue: used to store lists. By setting different list queues, you can process lists with different characteristics.

[0036] Number delivery pool: a buffer zone between dispatching warehousing and delivering numbers for dialing.

[0037] Currently, the scheduling of outbound call tasks usually involves directly assigning each to-be-called list to a scheduling task without distinction. Then, by starting the scheduling task, the to-be-called lists are retrieved one by one and the outbound calls are made. This outbound call scheduling method has poor flexibility and poor outbound call effectiveness. Based on this, an embodiment of the present application provides an outbound call task scheduling method that schedules each list based on its characteristic information. This allows for differentiated outbound call scheduling based on the granularity of the list, improves the pertinence and flexibility of outbound call scheduling, and thus helps improve outbound call effectiveness.

[0038] See also Figure 1 , Figure 1 Flowchart of the outbound call task scheduling method provided by the embodiment of the present application. Figure 1 As shown, the following steps are included:

[0039] Step 101: Determine the list category of the list based on the first characteristic information of the list.

[0040] In this embodiment, each list may represent or correspond to a user or number. It is understandable that the number of the above lists may be one or more. In the case of multiple lists, the list category of each list is determined based on the first characteristic information of each list.

[0041] For example, the first characteristic information of the list may include, but is not limited to, one or more of user characteristic information, dialing characteristic information, and service characteristic information. The user characteristic information is used to reflect relevant information about the user represented by the list. The dialing characteristic information is used to reflect dialing-related information about the list. The service characteristic information is used to reflect relevant information about the service associated with the list.

[0042] The list categories of the above lists can be reasonably divided based on actual needs. For example, multiple list categories can be divided based on the dimension of the timeliness of the list, and the timeliness of lists in different list categories is different; or, multiple list categories can be divided based on the dimension of the importance of the users represented by the list, and the importance of users represented by lists in different list categories is different; or, multiple list categories can be divided based on the dimension of the urgency of the business associated with the list, and the urgency of the business associated with lists in different list categories is different.

[0043] In practical applications, the outbound call system can receive a list from an upstream business system. Upon receiving the list pushed by the upstream business system, the system can obtain the first characteristic information of the list and determine the list category based on the first characteristic information. In some optional embodiments, the upstream business system can also push basic data of the list to the outbound call system, such as one or more of user tags, contract tags, marketing campaign information, and dialing strategy information.

[0044] Step 102: store the list into a first list warehouse according to the list category of the list; wherein the category of the first list warehouse corresponds to the list category of the list, different categories of lists correspond to different categories of list warehouses, and different categories of list warehouses have different priorities.

[0045] For example, the categories of the list warehouse can correspond to the list category settings. For example, if the list categories include VIP lists and regular lists, the categories of the list warehouse can include VIP list warehouse and regular list warehouse. The priorities of the list warehouses of different categories are different. For example, the priority of the VIP list warehouse is higher than that of the regular list warehouse.

[0046] Each of the above-mentioned categories of list warehouses may include at least one list warehouse. It should be noted that the number of list warehouses in each category can be reasonably set according to actual needs, and the number of list warehouses in different categories can be the same or different. In some optional embodiments, each list warehouse may include at least one list queue, and the number of list queues included in each list warehouse can also be reasonably set according to actual needs, and the number of list queues included in different list warehouses can be the same or different. It should also be noted that the priorities of multiple list warehouses under the same category can be the same or different.

[0047] Step 103: Obtain the to-be-dialed list from the first list warehouse according to the priority of the first list warehouse.

[0048] It is understood that there may be multiple first list warehouses, with different first list warehouses storing lists of different list categories. For example, to-be-dialed lists may be retrieved from each first list warehouse in descending order of priority until the number of retrieved to-be-dialed lists reaches a preset requirement. Alternatively, to-be-dialed lists may be retrieved from each first list warehouse based on their respective proportions, with the first list warehouse with a higher priority receiving a larger proportion.

[0049] It is understandable that the above-mentioned to-be-dialed list is a list obtained from the first list warehouse. It should be noted that the obtaining of the to-be-dialed list in this embodiment can also be replaced by extracting the to-be-dialed list or obtaining the to-be-dialed list.

[0050] Step 104: store the to-be-dialed list into a number pool.

[0051] The number sending pool is used to cache the waiting list of people waiting for number sending. After the waiting list is put into the number sending pool, the waiting list can be obtained from the number sending pool for number sending and dialing. For example, the number sending pool can be a number sending queue, and the waiting list at the top of the number sending queue can be dialed first.

[0052] The outbound call scheduling method provided in the embodiment of the present application determines the list category of the list according to the first characteristic information of the list; stores the list in a first list warehouse according to the list category of the list; wherein the category of the first list warehouse corresponds to the list category of the list, and different categories of lists correspond to different categories of list warehouses, and different categories of list warehouses have different priorities; according to the priority of the first list warehouse, the list to be dialed is obtained from the first list warehouse; the obtained list to be dialed is stored in the number sending pool, that is, the embodiment of the present application schedules the list according to the first characteristic information of the list, so that differentiated scheduling of outbound calls based on the granularity of the list can be achieved, which improves the pertinence and flexibility of outbound call scheduling, and is conducive to improving the outbound call effect; in addition, by setting up different categories of list warehouses to store different categories of lists, and different categories of list warehouses have different priorities, it is convenient to schedule different categories of lists separately, which is relatively simple to implement.

[0053] Optionally, the first feature information includes at least one of user feature information, dialing feature information, and service feature information.

[0054] In this embodiment, the user characteristic information is used to reflect the relevant information of the users represented by the list. The dialing characteristic information is used to reflect the dialing related conditions of the list. The service characteristic information is used to reflect the relevant information of the service associated with the list.

[0055] Optionally, the user feature information includes at least one of the following: a user tag, user portrait information, and a user evaluation index value; wherein the user evaluation index value is an evaluation index value obtained by evaluating the user using a preset evaluation model;

[0056] and / or,

[0057] The dialing feature information includes at least one of the following: dialing method, estimated dialing time, last dialing time, and redialing interval;

[0058] and / or,

[0059] The service feature information includes at least one of the following: a service contract tag, service activity information, service access information, and identification information of the service system that pushes the list.

[0060] It is understandable that in actual applications, the user feature information to be obtained can be set according to the specific application scenario. The following is an illustration using a marketing scenario as an example.

[0061] Exemplarily, the above-mentioned user tags may include but are not limited to at least one of a new user tag, an old user tag, a price reduction tag, a credit limit increase tag, a marketing campaign type tag, etc.

[0062] The above-mentioned user portrait information may include but is not limited to age, occupation, gender, region, purchase intention level, purchase preference information, whether it is the first time logging into the business system, etc.

[0063] The preset evaluation model may include, but is not limited to, at least one of a credit evaluation model, an overdue risk evaluation model, and a purchase intention evaluation model. The user evaluation index value is the evaluation index value obtained by evaluating the user using the preset evaluation model. For example, user profile information may be input into a purchase intention evaluation model to obtain the user's purchase intention evaluation value; or user profile information may be input into an overdue risk evaluation model to obtain the user's overdue risk evaluation value.

[0064] The above-mentioned dialing methods may include but are not limited to speed-limited dialing methods and regular dialing methods, among which the above-mentioned speed-limited dialing method is used to instruct the number to be delivered and dialed according to the specified QPS under the configured resources. For example, within the specified QPS limit, the number is delivered and dialed with full strength according to the configured number of AI seats; the above-mentioned regular dialing method is used to instruct the number to be delivered and dialed as quickly as possible under the configured resources. For example, the number is delivered and dialed with full strength according to the configured number of AI seats. There is no speed limit under this dialing method.

[0065] The estimated dialing time, illustratively, can be based on at least one of the list's user profile information, service profile information, and the list's historical dialing history, to estimate the dialing time for the list. The last dialing time can refer to the last time a number in the list was dialed. It will be appreciated that for non-recall lists, the dialing profile information does not include the last dialing time. The recall dialing interval can refer to the duration of the interval required to recall a list.

[0066] The above-mentioned business contract label may include but is not limited to at least one of the business contract type label associated with the above-mentioned list, the business contract name associated with the above-mentioned list, and the label of whether the business contract associated with the list is overdue. The above-mentioned business activity information may include but is not limited to at least one of the business activity name, business strategy, business activity time, business product identification, etc. Among them, the above-mentioned business may include but is not limited to marketing business or promotion business. The above-mentioned business access information may include the access information of the user represented by the above-mentioned list to the preset business function (for example, marketing business function). The identification information of the business system that pushes the above-mentioned list may include the identification of the business system that pushes the above-mentioned list, the type of business system, and other information. It should be noted that the above-mentioned preset business function may be a preset business function of the upstream business system of the outbound call system, and the above-mentioned business system that pushes the above-mentioned list may be the upstream business system of the outbound call system.

[0067] Optionally, storing the list in a first list warehouse according to the list category of the list includes:

[0068] If the list category of the list is not a real-time list, placing the list into a first list warehouse according to the list category of the list;

[0069] The method further comprises:

[0070] When the list category of the list is a real-time list, the list is stored in a number sending pool.

[0071] In this embodiment, real-time lists may be placed directly into the number pool instead of the list warehouse to achieve real-time triggering. In some optional embodiments, real-time lists may be placed directly at the top of the number pool so that the real-time lists are prioritized for number sending and dialing. During the number sending and dialing process, the top of the waiting-to-dial list is prioritized for dialing. For lists not classified as real-time, they may be placed into the corresponding first list warehouse based on their list category. Subsequently, the waiting-to-dial list may be retrieved from the first list warehouse and added to the number sending pool.

[0072] Specifically, whether the list type of the list is a real-time list can be determined based on preset rules. For example, if the first characteristic information of the list meets any of the following conditions, the list type is determined to be a real-time list; otherwise, the list type is determined not to be a real-time list:

[0073] The user portrait information includes a first preset portrait tag;

[0074] The user tag includes a first preset tag;

[0075] The user's evaluation index value is greater than or equal to a first preset value;

[0076] The marketing activity information includes first preset marketing information.

[0077] Among them, the above-mentioned first preset portrait label, first preset label, first preset value and first preset marketing information can be reasonably set according to actual needs. For example, the above-mentioned first preset portrait label may include a high level of user purchase intention, the above-mentioned first preset label may include a price reduction label, the above-mentioned first preset value may be 90, and the above-mentioned first preset marketing information may include a real-time marketing strategy.

[0078] In this embodiment, when the list category of the list is not a real-time list, the list is placed in the first list warehouse according to the list category of the list; when the list category of the list is a real-time list, the list is placed in the number delivery pool. In this way, while achieving flexible scheduling of lists with lower real-time requirements, it is ensured that lists with higher real-time requirements can be reached in real time, thereby reducing outbound call delays.

[0079] Optionally, storing the list in a first list warehouse according to the list category of the list includes:

[0080] determining a first list warehouse according to the second characteristic information of the list, wherein the category of the first list warehouse corresponds to the list category of the list;

[0081] In a case where the first list warehouse includes at least two list queues, determining a first list queue corresponding to the list in the first list warehouse according to the third characteristic information of the list;

[0082] placing the list into the first list queue according to the sorting information of the list; wherein the sorting information of the list is determined according to the fourth characteristic information of the list;

[0083] The first feature information, the second feature information, the third feature information and the fourth feature information are all different.

[0084] The above-mentioned first characteristic information, the second characteristic information, the third characteristic information and the fourth characteristic information are all different, which can be understood as at least part of the information in the above-mentioned first characteristic information, the second characteristic information, the third characteristic information and the fourth characteristic information is different.

[0085] For example, the first characteristic information may include, but is not limited to, at least one of user characteristic information, dialing characteristic information, and service characteristic information. The second characteristic information may include, but is not limited to, at least one of user characteristic information, dialing characteristic information, and service characteristic information. The third characteristic information may include, but is not limited to, at least one of user characteristic information, dialing characteristic information, and service characteristic information. The fourth characteristic information may include, but is not limited to, at least one of user characteristic information, dialing characteristic information, and service characteristic information. Among them, the above-mentioned first feature information, the second feature information, the third feature information and the fourth feature information may include different feature items in the above-mentioned user feature information, dialing feature information and service feature information. For example, the above-mentioned first feature information may include user feature information, dialing feature information and service feature information, the above-mentioned second feature information may include dialing feature information and service feature information, the above-mentioned third feature information may include dialing feature information, and the above-mentioned fourth feature information may include service feature information; or, the above-mentioned first feature information, the second feature information, the third feature information and the fourth feature information may include different sub-features in the same feature items in the above-mentioned user feature information, dialing feature information and service feature information. For example, the above-mentioned first feature information and the second feature information both include the above-mentioned user feature information, dialing feature information and service feature information, and the user feature information included in the first feature information is a user label, and the user feature information included in the second feature information is an evaluation index value of the user.

[0086] The categories of the above-mentioned list warehouse can be set in one-to-one correspondence with the list categories of the list. For example, if the list categories of the above-mentioned list include VIP lists and regular lists, the categories of the above-mentioned list warehouse can include VIP list warehouse and regular list warehouse, wherein the above-mentioned VIP list warehouse is used to store VIP lists, and the above-mentioned regular list warehouse is used to store regular lists.

[0087] The first list warehouse is determined based on the second characteristic information of the list. For example, if there are multiple list warehouses whose categories correspond to the list category of the list, if the multiple list warehouses respectively correspond to different business contract tags, then the list warehouse to which the list belongs, that is, the first list warehouse, can be determined based on the business contract tag of the list; or, if the multiple list warehouses respectively correspond to different user tags, then the list warehouse to which the list belongs, that is, the first list warehouse, can be determined based on the user tag of the list.

[0088] It should be noted that the list warehouses included in each list warehouse category can be reasonably preset according to actual needs. For example, if the above-mentioned regular list warehouse is preset to include a credit limit increase list warehouse and a new customer list warehouse, then in this case, if the user tag associated with the list includes a credit limit increase tag, then the list warehouse to which the list belongs (i.e., the above-mentioned first list warehouse) is determined to be a credit limit increase list warehouse, and if the user portrait information associated with the list includes a tag for the first login to the business system, then the list warehouse to which the list belongs is determined to be a new customer list warehouse. If the above-mentioned VIP list warehouse is preset to include a first VIP list warehouse and a second VIP list warehouse, the first VIP list warehouse is used to store lists associated with a preset product number, and the second VIP list warehouse is used to store lists other than lists associated with a preset product number, then in this case, if the product number associated with the list is the preset product number, then the list warehouse to which the list belongs is determined to be the first VIP list warehouse, and if the product number associated with the list is not the preset product number, then the list warehouse to which the list belongs is determined to be the second VIP list warehouse.

[0089] It should also be noted that, in the case where the list warehouse corresponding to the list category of the list includes only one list warehouse, the list warehouse can be directly used as the first list warehouse.

[0090] The above-mentioned first list queue corresponding to the list in the first list warehouse is determined based on the third characteristic information of the list. For example, when multiple list queues in the above-mentioned first list warehouse respectively correspond to different value ranges of evaluation index values, the list queue to which the list belongs, that is, the first list queue, can be determined according to the evaluation index value associated with the list; when multiple list queues in the above-mentioned first list warehouse respectively correspond to different value ranges of estimated calling times, the list queue to which the list belongs, that is, the first list queue, can be determined according to the estimated calling time associated with the list.

[0091] It should be noted that the list queues included in each list warehouse can be reasonably preset according to actual needs. For example, if the preset new customer list warehouse includes list queue a and list queue b, where list queue a is used to store lists whose purchase intention index value is greater than or equal to the preset intention index value, and list queue b is used to store lists whose purchase intention index value is less than the preset intention index value, then in this case, if the intention index value associated with the list is greater than or equal to the preset intention index value, then the list is determined to belong to list queue a, that is, the first list warehouse is determined to be list queue a; otherwise, the list is determined to belong to list queue b, that is, the first list warehouse is determined to be list queue b.

[0092] It should also be noted that, when the first list warehouse includes only one list queue, the list queue can be directly used as the first list queue.

[0093] The sorting information of the above-mentioned list is determined based on the fourth characteristic information of the list. For example, the sorting number of the list can be calculated based on the fourth characteristic information of the above-mentioned list, wherein the value range of the sorting number can be 1 to P, wherein P is the maximum number of lists that can be stored in the above-mentioned first list queue. Then, the arrangement position of the above-mentioned list in the first list queue can be determined based on the sorting number of the above-mentioned list; alternatively, the sorting score of the list can be calculated based on the fourth characteristic information of the above-mentioned list, wherein the larger the sorting score, the closer the arrangement position in the first list queue can be to the end of the first list queue, and the list is preferentially drawn from the end of the first list queue during the process of retrieving the list. For example, the sorting score of the above-mentioned list can be determined based on the purchase intention index value of the list, wherein the larger the purchase intention index value, the larger the sorting score.

[0094] This embodiment divides the list warehouse based on the second characteristic information of the list, divides the list queue based on the third characteristic information of the list, and sorts the lists within the list queue based on the fourth characteristic information of the list. This facilitates more fine-grained and accurate list scheduling, which in turn helps improve the effectiveness of outbound calls.

[0095] In some optional embodiments, before determining the list category of the list based on the first characteristic information of the list, the method may further include: filtering the above-mentioned list based on the first filter, wherein, in the case that the above-mentioned list is not filtered out, the list category of the list is determined based on the first characteristic information of the list, and in the case that the above-mentioned list is filtered out, the list can be processed according to preset rules, such as removing it from the waiting-to-dial record table, or delaying outbound calls, or pausing outbound calls, etc. Exemplarily, the above-mentioned list not being filtered out can be understood as the above-mentioned list not being hit by any filtering rule of the first filter, and the above-mentioned list not being filtered out can be understood as the above-mentioned list being hit by the filtering rule of the first filter. The above-mentioned first filter may include but is not limited to at least one of a blacklist filter, a graylist filter, a dialing time limit filter, a call frequency control filter, an outbound call number limit filter, and a holiday limit filter.

[0096] Optionally, obtaining the to-be-dialed list from the first list warehouse according to the priority of the first list warehouse includes:

[0097] When N to-be-dialed lists need to be obtained, the to-be-dialed lists are obtained from the first list warehouse in descending order of priority of the first list warehouse until the total number of the obtained to-be-dialed lists is N.

[0098] Exemplarily, the value of N can be determined based on the capacity of the number sending pool and the current number of names in the number sending pool, for example, N=1.2*(capacity of the number sending pool-current number of names in the number sending pool).

[0099] The present embodiment is described below with reference to examples:

[0100] If the first list warehouse includes list warehouse-1, list warehouse-2 and list warehouse-3, among which the priority of list warehouse-1 is higher than that of list warehouse-2, and the priority of list warehouse-2 is higher than that of list warehouse-3, then the to-be-dialed list can be obtained from the list queue of list warehouse-1 first. If the number of to-be-dialed lists obtained from the list queue of list warehouse-1 reaches N, the process of obtaining the to-be-dialed list can be ended; if the number of to-be-dialed lists obtained from the list queue of list warehouse-1 is less than N, then the to-be-dialed list is obtained from the list queue of list warehouse-2; if the number of to-be-dialed lists obtained from the list queue of list warehouse-1 reaches N, then the process of obtaining the to-be-dialed list is ... reaches N, then the process of obtaining the to-be-dialed list is ended; if the number of to-be-dialed lists obtained from the list queue of list warehouse-2 reaches N, then the process of obtaining the to-be-dialed list is ended; When the sum of the number of to-be-dialed lists obtained and the number of to-be-dialed lists pulled up from the list queue of List Warehouse-2 reaches N, the process of obtaining the to-be-dialed lists can be terminated; if the sum of the number of to-be-dialed lists obtained from the list queue of List Warehouse-1 and the number of to-be-dialed lists pulled up from the list queue of List Warehouse-2 is less than N, the to-be-dialed lists are obtained from the list queue of List Warehouse-3 until the sum of the number of to-be-dialed lists obtained from the list queue of List Warehouse-1, the number of to-be-dialed lists pulled up from the list queue of List Warehouse-2, and the number of to-be-dialed lists obtained from the list queue of List Warehouse-3 reaches N.

[0101] It should be noted that, when the total number of lists in all first list warehouses is less than N, the process of obtaining the to-be-dialed list can be ended when all the lists in the first list warehouse are obtained.

[0102] For example, when there are multiple list warehouses with the same priority, lists can be obtained from the list queues of multiple list warehouses. For example, lists can be obtained from the list queues of multiple list warehouses according to the target acquisition ratio between the multiple list warehouses, wherein the above-mentioned target acquisition ratio can be reasonably set according to actual needs.

[0103] This embodiment obtains the lists from the list queue of the first list warehouse in sequence according to the priority of the first list warehouse and puts them into the number sending pool. This is conducive to ensuring that the lists in the list queue of the first list warehouse with higher priority can be sent and dialed first.

[0104] Optionally, obtaining the to-be-dialed list from the first list repository includes:

[0105] When there are at least two list queues in the first list warehouse, obtaining the to-be-dialed list from the at least two list queues according to a preset acquisition ratio between the at least two list queues;

[0106] When the total number of to-dial lists obtained is less than M, the to-dial lists are obtained from the remaining lists of the at least two list queues according to the priorities of the at least two list queues, where M is less than or equal to N, and M is the number of to-dial lists that need to be obtained from the first list warehouse.

[0107] In this embodiment, the above-mentioned preset acquisition ratio can be reasonably set according to actual needs. For example, if the first list warehouse includes list queue a and list queue b, the above-mentioned preset acquisition ratio can be 40%:60%, that is, M*40% of the to-be-dialed lists are obtained from the above-mentioned list queue a, and M*60% of the to-be-dialed lists are obtained from the above-mentioned list queue b.

[0108] The present embodiment is described below with reference to examples:

[0109] For example, if the first list repository includes list queue a, list queue b, and list queue c, and list queue a has a higher priority than list queue b, which in turn has a higher priority than list queue c, the preset acquisition ratio may be 40%:30%:30%, and M is 1000. In this case, 400 to-be-dialed lists may be acquired from list queue a, 300 to-be-dialed lists may be acquired from list queue b, and 300 to-be-dialed lists may be acquired from list queue c, respectively. If only 200 to-be-dialed lists are acquired from list queue a, to-be-dialed lists may be preferentially acquired from the remaining to-be-dialed lists in list queue b. If 200 to-be-dialed lists are acquired from the remaining to-be-dialed lists in list queue b, the process of acquiring to-be-dialed lists from the first list repository may be terminated. If the number of to-be-dialed lists acquired from the remaining to-be-dialed lists in list queue b is less than 200, to-be-dialed lists may continue to be acquired from the remaining to-be-dialed lists in list queue c, until the total number of to-be-dialed lists acquired from the first list repository reaches M.

[0110] In this embodiment, the to-be-dialed lists are first obtained from the at least two list queues under the first list warehouse according to a preset acquisition ratio between the at least two list queues; when the total number of to-be-dialed lists obtained from the at least two list queues according to the preset acquisition ratio is less than M, the to-be-dialed lists are then obtained from the remaining to-be-dialed lists in the at least two list queues according to the priorities of the at least two list queues. This is beneficial for ensuring the priority of obtaining lists between list queues while taking into account the fairness of obtaining lists between list queues.

[0111] Optionally, before determining the list category of the list based on the first characteristic information of the list, the method further includes:

[0112] Determining a dialing method for the list from at least two preset dialing methods based on fifth characteristic information of the list, wherein the fifth characteristic information includes at least one of the following: user characteristic information, service characteristic information, number delivery status corresponding to each preset dialing method, and a recommended dialing method;

[0113] Among them, lists with different dialing methods are scheduled using different list scheduling channels, and lists with the same dialing method are scheduled using the same list scheduling channel. Different list scheduling channels correspond to different list warehouses and different number delivery pools.

[0114] The user feature information and service feature information of this embodiment can be found in the relevant description of the aforementioned embodiment and will not be elaborated here. The number delivery status corresponding to each of the above-mentioned preset dialing methods and the recommended dialing method can be used to reflect the number delivery status of each dialing method, for example, busy status, idle status, etc. The above-mentioned recommended dialing method can be the dialing method recommended by the upstream service system. The above-mentioned at least two dialing methods may include but are not limited to a speed-limited dialing method and a regular dialing method.

[0115] For example, when the business strategy associated with the list is real-time marketing, the dialing method of the list is determined to be the regular dialing method, otherwise the dialing method of the list is determined to be the speed-limited dialing method; or, when the recommended dialing method is the regular dialing method, the dialing method of the list is determined to be the regular dialing method, and when the recommended dialing method is the speed-limited dialing method, the dialing method of the list to be dialed is determined to be the speed-limited dialing method.

[0116] It should be noted that, in this embodiment, different list dispatching channels can be pre-set for different dialing methods, and different list dispatching channels can be used to dispatch lists for different dialing methods. Specifically, for each list dispatching channel, the above steps 101 to 104 can be used to dispatch the list. The following examples illustrate this embodiment:

[0117] Exemplarily, if the list of conventional dialing method is scheduled using the first list scheduling channel, and the list of speed-limited dialing method is scheduled using the second list scheduling channel, the first list scheduling channel corresponds to the first list warehouse set and the first number sending pool, and the second list scheduling channel corresponds to the second list warehouse set and the second number sending pool, wherein the first list warehouse set includes at least two list warehouses, the second list warehouse set includes at least two list warehouses, and the list warehouses in the first list warehouse set and the list warehouses in the second list warehouse set are different list warehouses. Then, when it is determined that the dialing method of the list is the conventional dialing method according to the dialing strategy information of the list, the first list scheduling channel can be used to schedule the list, that is, the following steps can be performed: according to the first characteristic information of the list, the list category of the list is determined, and according to the list category of the list, the list is Put it into the first list warehouse in the first list warehouse set; according to the priority of each first list warehouse in the first list warehouse set, obtain the list to be dialed from the first list warehouse in the first list warehouse set, and store the obtained list to be dialed in the first number sending pool; when it is determined according to the dialing strategy information of the list that the dialing method of the list is the speed-limited dialing method, the second list scheduling channel can be used to schedule the list, that is, the following steps can be performed: according to the first characteristic information of the list, determine the list category of the list; according to the list category of the list, put the list into the first list warehouse in the second list warehouse set; according to the priority of each first list warehouse in the second list warehouse set, obtain the list to be dialed from the list queue of the first list warehouse of the second list warehouse set, and store the obtained list to be dialed in the second number sending pool.

[0118] In this embodiment, lists with different dialing methods are scheduled using different list scheduling channels. This allows for independent scheduling of different dialing methods, which in turn facilitates dialing at different rates. In addition, the dialing method of the list is determined from at least two preset dialing methods based on the fifth characteristic information of the list, which helps ensure that the determined dialing method is more in line with the dialing needs of the list.

[0119] Optionally, determining the list category of the list based on the first characteristic information of the list includes:

[0120] When the time from the estimated dialing time of the list is less than or equal to the preset time, obtaining the first characteristic information of the list;

[0121] The list category of the list is determined according to the first characteristic information of the list.

[0122] The preset duration can be set reasonably according to actual needs, for example, 10 seconds or 30 seconds.

[0123] In this embodiment, the list is scheduled based on at least one of the user characteristic information, dialing characteristic information and service characteristic information of the list. Since changes in at least one of the user characteristic information, dialing characteristic information and service characteristic information of the above-mentioned list may affect the scheduling result of the list, this embodiment performs scheduling of the list when it is relatively close to or reaches the estimated dialing time of the list, that is, the first characteristic information of the list is obtained when it is relatively close to or reaches the estimated dialing time of the list, and the list category of the list is determined based on the first characteristic information of the list. According to the list category of the list, the list is placed in the list queue of the corresponding list warehouse in at least two list warehouses. This is conducive to ensuring that the first characteristic information of the list obtained is the latest, thereby improving the accuracy of list scheduling.

[0124] The following examples illustrate the embodiments of the present application:

[0125] Example 1:

[0126] like Figure 2 As shown, upstream business systems such as telemarketing, anti-fraud, anti-electronic fraud, and customer service can push first list data to the call system. This first data may include the list and its basic data, such as at least one of user tags, contract tags, marketing campaign information, source system information, dialing strategy information, and invitation strategy information. The call system includes a list scheduling system and an answering system. The list scheduling system may include a list receiving module, a list scheduling module, and a number delivery module.

[0127] For example, Figure 3a , the above-mentioned receiving list module can receive the first data of the list pushed by the upstream business system, process it, obtain the second data of the list, and push the second data of the list to the scheduling list module. For example, the receiving list module can monitor the list that the upstream business system needs to dial. Once the first data of the dialed list is detected, the first data of the list can be parsed to obtain various basic data such as user identification, user tags, business activity information (such as marketing activity information), source system information and invitation strategy information associated with the list, and determine the dialing method of the current list based on the above-mentioned basic data and at least two preset dialing methods. It should be noted that this example supports the configuration or adjustment of the above-mentioned dialing methods, for example, it supports adding dialing methods or reducing dialing methods or changing dialing methods, etc. Furthermore, the receiving list module can package the basic data of the obtained list and the dialing method of the determined list together to generate the second data of the list, and push it to the scheduling list module.

[0128] The above-mentioned dispatch list module is used to dispatch the second data of the list pushed by the receiving list module according to different dialing methods. Exemplarily, the above-mentioned dispatch list module can be used to perform persistent lists and list scheduling, wherein the above-mentioned list scheduling can include list warehousing (i.e. calculating the list warehouse and list queue, calculating the list ranking, etc.) and filling the number sending pool. The above-mentioned persistent list and list scheduling are respectively explained below:

[0129] 1. Persistent List

[0130] When the second data of the list pushed by the receiving list module is received, characteristic information (i.e., first characteristic information) including but not limited to user portrait information, user tag, business contract tag, estimated calling time, redial interval and user evaluation index value can be obtained based on the user identifier associated with the list, and the third data of the list can be generated based on the obtained characteristic information and the second data of the list, and the third data of the list can be stored in the list table.

[0131] It should be noted that if the currently generated list hits the real-time list rule, it will not wait for the subsequent scheduling operation based on the dialing method, but will directly put the list at the top of the number pool corresponding to its dialing method to achieve the purpose of real-time reach.

[0132] 2. List Scheduling

[0133] like Figure 3b As shown, the scheduling list module will split and generate scheduling tasks for the dialing methods according to the dialing methods, that is, as many different scheduling tasks will be generated as the preset dialing methods are configured, and each scheduling task runs independently without interfering with each other.

[0134] The following takes the pre-configured regular dialing method and flow-limited dialing method as an example. The regular dialing method scheduling task and the flow-limited dialing method scheduling task are generated according to the dialing method, and registered with the scheduling task execution center to wait for resource allocation. The scheduling task execution center will further split the scheduling task into two subtasks: extracting the list and filling the number pool. The scheduling task execution center will assign application instances to the subtasks based on the current application cluster usage. Once the subtask and the application instance are successfully bound, the subtask will reside on the assigned application instance to perform the list calculation until there is no list. It will stop and inform the scheduling task execution center, such as Figure 3c shown.

[0135] (1) List storage

[0136] After the scheduling task execution center distributes the subtask of extracting the list to an application instance, the instance first reads the execution code of the subtask and then starts processing according to the established dialing method. Figure 3bAs shown, the scheduling tasks for the conventional dialing method and the flow-limited dialing method mentioned above both execute the following steps: extracting a list, and after obtaining basic data, filtering the list, determining the list warehouse and list queue, and calculating the ranking score, the list is placed in the corresponding list warehouse and list queue according to the calculated list warehouse and list queue, and queued according to the ranking score. The following describes each of the above processes separately:

[0137] 1) Obtain basic data

[0138] A list represents a user. First, we need to obtain basic data such as user profile information, user tags, contract tags, marketing strategy information, and user evaluation index values ​​associated with the list. Any change in any of these attributes may affect the scheduling of the list.

[0139] 2) Filter list

[0140] Due to upstream business or technical limitations, some lists may have their outbound calls stopped, delayed, or suspended. Therefore, a scalable filter chain is required. This example allows for pre-defined filtering of lists using at least one filter: a blacklist filter, a graylist filter, a call time limit filter, a call frequency control filter, an outbound call limit filter, or a holiday limit filter. The example also supports implementing custom filters through the filter interface. Once a list is filtered by a filter, it is processed according to the filter's rules, for example, being removed from the pending call list, having outbound calls delayed, or having them suspended.

[0141] 3) Determine the list warehouse and list queue

[0142] Calculating the list warehouse and list queue is actually calculating which category of list warehouse the list belongs to and which list queue in the list warehouse of that category. The relationship between the two can be as follows: Figure 4 As shown:

[0143] For example, this example divides the call lists into three categories: real-time, VIP, and regular. The outbound call efficiency for these three categories is as follows: real-time > VIP > regular. The real-time lists don't have a corresponding list repository or queue. Once a list is identified as real-time, it's directly sent to the call pool to ensure real-time reach. The VIP and regular lists have corresponding list repositories and queues, respectively.

[0144] Calculate the list category. In this example, three list categories are preset: real-time list, VIP list, and regular list, and a data structure for determining the list category is defined. For example, the data structure of the list category can be shown in Table 1.

[0145] Table 1

[0146]

[0147]

[0148] It should be noted that the above-mentioned first preset portrait label, first preset label, first preset value, second preset portrait label, second preset label, second preset value, preset product number and preset marketing strategy can all be reasonably set according to actual needs, and this embodiment does not limit this.

[0149] Refer to Table 1. The data structure of the above-mentioned list category includes category name, category division rules, priority and whether to send numbers in real time. Among them, the category name is used as the unique identifier of the category to distinguish the list category; the category division rules are used to define what kind of list can enter what category, and the calculated metadata comes from the basic data obtained previously. For example, the list category of the list can be determined based on the user portrait information, user tags, user evaluation index values, product numbers, marketing strategies and source system information associated with the list; the priority is to classify the list category, and then extract the list into the number sending pool according to the priority when the number is drawn. For example, the above-mentioned priority can include high, upper-middle, medium, lower-middle and low levels; whether to send numbers in real time is to identify whether the list needs to be sent in real time, that is, no matter what the dialing time is, once the list is received, it will be immediately placed in the number sending pool and wait for the number to be sent.

[0150] like Figure 4 As shown, the real-time list does not have a corresponding list warehouse and list queue. This is mainly because the real-time list needs to be reached in real time, so once it is determined to be a real-time list, it needs to be directly placed in the number delivery pool and wait for the number to be delivered. In this way, there is no need for a list warehouse and list queue to further refine the list attribution.

[0151] It should be noted that this example takes three preset list categories as an example. If you need to add a list category, you only need to add a configuration. It will be automatically identified when processing the list, and then the list attribution will be calculated according to the configured classification rules. However, only when the real-time list is configured as yes, there is no need to configure the list warehouse and list queue.

[0152] Determine the list warehouse, and set the category of the list warehouse in correspondence with the list category. For example, the data structure of the list warehouse can be as shown in Table 2.

[0153] Table 2

[0154]

[0155]

[0156] See Table 2. The data structure of the list warehouse includes category name, warehouse name and partition rules. The above category name is used to specify which category the list warehouse belongs to. Once the category is defined, the list of this list warehouse will come from that category; the warehouse name is used as a unique identifier to distinguish the list warehouse and is also used to provide affiliation for the list queue; the partition rules are used to determine the list warehouse to which the list belongs.

[0157] The lists in the list warehouse are derived from the categories defined in the current list warehouse. That is, all lists determined by the warehouse rules are derived from the corresponding categories. For example, the lists in the first and second VIP warehouses can only be derived from the VIP list category, and the lists in the credit limit increase list warehouse and the new customer list warehouse can only be derived from the regular list category.

[0158] Determine the list queue, which belongs to the list warehouse. For example, the data structure of the list queue can be shown in Table 3.

[0159] Table 3

[0160] Warehouse Name Queue Name Queue division rules Get Ratio Priority New Customer List Warehouse High-intent cohort Intention score > first value 70％ high New Customer List Warehouse Low-intent cohort Intention score < second value 30％ Low

[0161] It should be noted that the above-mentioned first value and second value can be reasonably set according to actual needs. For example, the first value and the second value are both 80, or the first value is 90 and the second value is 50, etc.

[0162] See Table 3. The data structure of the list queue includes the warehouse name, queue name, queue division rule, acquisition ratio and priority. The warehouse name is used to specify which list warehouse the list queue belongs to. In other words, it specifies the source of the list for the list queue; the queue name is used as a unique identifier to distinguish list queues; the queue division rule is used to determine the list queue to which the list belongs; the acquisition ratio is used to specify the ratio to be obtained during the stage of obtaining the list to be dialed. The sum of the acquisition ratios of multiple list queues under the same list warehouse should be 100%; the priority is also used during the stage of pulling up the list to be dialed.

[0163] It should be noted that regardless of whether a list queue is configured under the list warehouse, this example will set a default queue as a fallback. This is to prevent the configuration from not covering all scenarios and to prevent the situation where no queue is configured.

[0164] (2) Fill the number pool

[0165] Similar to the list entry process, filling the number pool can also be triggered by the dispatch center. The data for filling the number pool comes from the list entered into the warehouse. It's understandable that since the real-time list is directly entered into the number pool, this step doesn't retrieve the real-time list. Instead, it only retrieves the VIP and regular lists from the list warehouse.

[0166] Obtaining the to-be-dialed list can be divided into two rounds: the first round is to obtain the VIP list in full, and the second round is to complete the regular list. Among them, obtaining the regular list can be divided into two rounds: the first round is to obtain the to-be-dialed list according to the preset acquisition ratio, and the second round is to obtain the to-be-dialed list in descending order of priority of the list queue. The reason for the two-round acquisition is mainly to ensure the fairness between the list warehouses of each category and the list queues while ensuring the priority between them. For example, Figure 5 shown.

[0167] The above-mentioned number sending module is used to extract the to-be-dialed list in the number sending pool and send and dial the numbers. After passing through the above-mentioned receiving list module and scheduling list module, the to-be-dialed list that needs to be sent and dialed is all in the number sending pool. At this time, a unified number sending scheduling operation will be used to coordinate and obtain the to-be-dialed list of each dialing method. As mentioned above, the purpose of dividing the dialing method is to achieve sending and dialing at different rates. As for how to control the rate, it is the core function of the number sending module. That is, the above-mentioned number sending module can be used to control the rate to obtain the to-be-dialed list, and send and dial the numbers from the to-be-dialed list. It should be noted that how the above-mentioned number sending module controls the rate to obtain the to-be-dialed list, and sends and dials the numbers from the to-be-dialed list, can be referred to the relevant technology, and this embodiment will not elaborate on this.

[0168] It should be noted that once a connection is established with the user, each round of human-computer dialogue can be handled by the answering system.

[0169] Example 2:

[0170] This example shows an outbound call processing process, which may include the following steps:

[0171] Step S1: List receiving.

[0172] This step may specifically include: the upstream business system pushes the circled list to the receiving list module through KAFKA and the message bus; the receiving list module determines whether it is a new schedule. If not, it processes it according to the original list receiving and processing method. If so, it executes the list parsing, monitoring task generation and basic data acquisition in sequence to obtain the list data and store it in the to-be-dialed list table. If the list is a real-time list, the list is directly placed in the number sending pool.

[0173] Step S2: The scheduling subtasks are distributed through the scheduling task execution center. If it is a list warehousing task, the list warehousing process is executed. If it is a number sending pool filling task, the process of obtaining the to-be-dialed list from the list warehouse and sending it to the number sending pool is executed.

[0174] Exemplarily, the process of warehousing the above-mentioned list may include: reading the list of the last hour from the to-be-dial list table, and determining whether the list is in a paused or stopped state. If not, determining whether the list belongs to the black and gray lists. If not, determining whether the list is filtered by the call restriction-related filters. For example, the above-mentioned call restriction-related filters may include at least one of the call time limit filter, call frequency control filter, outbound call limit filter, holiday limit filter, etc. If not, determining the list warehouse and list queue corresponding to the list, and placing the list into the list queue of the corresponding list warehouse.

[0175] It should be noted that in the process of executing the scheduling subtask, they are all run independently according to the dialing mode, and the logical execution between the dialing modes does not interfere with each other.

[0176] Step S3: Schedule and start sending numbers.

[0177] In this step, the number of to-be-dialed lists required for each dialing method is first calculated. The corresponding number of to-be-dialed lists is then retrieved from the corresponding number pool. Finally, the number data is assembled through a post-filter to request the number to be dialed. The post-filters may include, but are not limited to, at least one of the following: list dialing status filtering, blacklist filtering, graylist filtering, dialing time limit filtering, monitoring task pause or stop status filtering, and tenant suspension filtering.

[0178] Step S4: After the user answers the call, the user can have a conversation with the user.

[0179] It should be noted that after the user hangs up, a decision can be made whether to re-call the call. If a re-call is required, the current call list will be returned to the dispatch system for the next round of re-call scheduling. For example, based on the conversation with the user, an intention score, intention level, or user tag can be generated. Based on this intention score, intention level, or user tag, a decision can be made as to whether to re-call the user, or whether to add the user to a blacklist or graylist.

[0180] In summary, the embodiments of the present application can realize the division of various categories, list warehouses and list queues in the list dimension, and also support independent scheduling for different dialing scenarios, as well as rich configuration schemes. It can support the business party to perform fine-grained regulation and precision marketing on the list dimension, and can quickly enable independent scheduling according to different dialing methods, thereby reducing outbound call costs and improving resource utilization.

[0181] See also Figure 6 , Figure 6 This is one of the structural diagrams of the outbound call task scheduling device provided in the embodiment of the present application. Figure 6 As shown, the outbound call task scheduling device 600 includes:

[0182] A first determining module 601 is configured to determine a list category of the list based on first characteristic information of the list;

[0183] A first storing module 602 is configured to store the list into a first list warehouse according to the list category of the list; wherein the category of the first list warehouse corresponds to the list category of the list, and lists of different categories correspond to different list warehouses, and list warehouses of different categories have different priorities;

[0184] An acquisition module 603 is configured to acquire a to-be-dialed list from the first list warehouse according to the priority of the first list warehouse;

[0185] The second storing module 604 is used to store the to-be-dialed list into a number sending pool.

[0186] Optionally, the first storage module is specifically configured to:

[0187] If the list category of the list is not a real-time list, placing the list into a first list warehouse according to the list category of the list;

[0188] The device further comprises:

[0189] The third storing module is used to store the list into the number sending pool when the list category of the list is a real-time list.

[0190] Optionally, the first storage module is specifically configured to:

[0191] determining a first list warehouse according to the second characteristic information of the list, wherein the category of the first list warehouse corresponds to the list category of the list;

[0192] In a case where the first list warehouse includes at least two list queues, determining a first list queue corresponding to the list in the first list warehouse according to the third characteristic information of the list;

[0193] placing the list into the first list queue according to the sorting information of the list; wherein the sorting information of the list is determined according to the fourth characteristic information of the list;

[0194] The first feature information, the second feature information, the third feature information and the fourth feature information are all different.

[0195] Optionally, the first feature information includes at least one of user feature information, dialing feature information, and service feature information.

[0196] Optionally, the user feature information includes at least one of the following: a user tag, user portrait information, and a user evaluation index value; wherein the user evaluation index value is an evaluation index value obtained by evaluating the user using a preset evaluation model;

[0197] and / or,

[0198] The dialing feature information includes at least one of the following: dialing method, estimated dialing time, last dialing time, and redialing interval;

[0199] and / or,

[0200] The service feature information includes at least one of the following: a service contract tag, service activity information, service access information, and identification information of the service system that pushes the list.

[0201] Optionally, the acquisition module is specifically configured to:

[0202] When N to-be-dialed lists need to be obtained, the to-be-dialed lists are obtained from the first list warehouse in descending order of priority of the first list warehouse until the total number of the obtained to-be-dialed lists is N.

[0203] Optionally, the acquisition module is specifically configured to:

[0204] When there are at least two list queues in the first list warehouse, obtaining the to-be-dialed list from the at least two list queues according to a preset acquisition ratio between the at least two list queues;

[0205] When the total number of to-dial lists obtained is less than M, the to-dial lists are obtained from the remaining lists of the at least two list queues according to the priorities of the at least two list queues, where M is less than or equal to N, and M is the number of to-dial lists that need to be obtained from the first list warehouse.

[0206] Optionally, the device further comprises:

[0207] a second determining module configured to determine a dialing method for the list from at least two preset dialing methods based on fifth characteristic information of the list before determining the list category of the list based on the first characteristic information of the list, wherein the fifth characteristic information includes at least one of the following: user characteristic information, service characteristic information, number delivery status corresponding to each preset dialing method, and a recommended dialing method;

[0208] Among them, lists with different dialing methods are scheduled using different list scheduling channels, and lists with the same dialing method are scheduled using the same list scheduling channel. Different list scheduling channels correspond to different list warehouses and different number delivery pools.

[0209] Optionally, the first determining module is specifically configured to:

[0210] When the time from the estimated dialing time of the list is less than or equal to the preset time, obtaining the first characteristic information of the list;

[0211] The list category of the list is determined according to the first characteristic information of the list.

[0212] The outbound call task scheduling device 400 provided in the embodiment of the present application can implement each process in the above method embodiment, and will not be described again here to avoid repetition.

[0213] See also Figure 7 , Figure 7 This is the second structural diagram of the outbound call task scheduling device provided by the present application. Figure 7 As shown, the outbound call task scheduling device 700 includes: a processor 701, a memory 702, and a computer program stored in the memory 702 and executable on the processor. The various components in the outbound call task scheduling device 700 are coupled together via a bus interface 703. When the computer program is executed by the processor 701, the following steps are implemented:

[0214] determining a list category of the list according to the first characteristic information of the list;

[0215] According to the list category of the list, the list is stored in a first list warehouse; wherein the category of the first list warehouse corresponds to the list category of the list, different categories of lists correspond to different categories of list warehouses, and different categories of list warehouses have different priorities;

[0216] Obtaining a to-be-dialed list from the first list warehouse according to the priority of the first list warehouse;

[0217] The obtained waiting-to-dial list is stored in the number pool.

[0218] It should be understood that in the embodiment of the present application, when the computer program is executed by the processor 701, each process in the above-mentioned outbound call task scheduling method embodiment can be implemented. To avoid repetition, it will not be described here.

[0219] An embodiment of the present application also provides an outbound call task scheduling device, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, the various processes of the above-mentioned outbound call task scheduling method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0220] The present application also provides a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program implements the various processes of the above-described outbound call task scheduling method embodiment and achieves the same technical effects. To avoid repetition, the details are not described here. The computer-readable storage medium may be, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0221] An embodiment of the present application also provides a computer program product, which is stored in a storage medium. When the computer program product is executed by at least one processor, it implements the various processes of the above-mentioned outbound call task scheduling method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0222] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0223] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0224] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A method for scheduling outbound call tasks, characterized in that: include: determining a list category of the list according to the first characteristic information of the list; According to the list category of the list, the list is stored in a first list warehouse; wherein the category of the first list warehouse corresponds to the list category of the list, different categories of lists correspond to different categories of list warehouses, and different categories of list warehouses have different priorities; Obtaining a to-be-dialed list from the first list warehouse according to the priority of the first list warehouse; The to-be-dialed list is stored in a number pool.

2. The method according to claim 1, characterized in that The step of storing the list in the first list warehouse according to the list category of the list includes: If the list category of the list is not a real-time list, placing the list into a first list warehouse according to the list category of the list; The method further comprises: When the list category of the list is a real-time list, the list is stored in a number sending pool.

3. The method according to claim 1, characterized in that The step of storing the list in the first list warehouse according to the list category of the list includes: determining a first list warehouse according to the second characteristic information of the list, wherein the category of the first list warehouse corresponds to the list category of the list; In a case where the first list warehouse includes at least two list queues, determining a first list queue corresponding to the list in the first list warehouse according to the third characteristic information of the list; placing the list into the first list queue according to the sorting information of the list; wherein the sorting information of the list is determined according to the fourth characteristic information of the list; The first feature information, the second feature information, the third feature information and the fourth feature information are all different.

4. The method according to any one of claims 1 to 3, characterized in that The first characteristic information includes at least one of user characteristic information, dialing characteristic information, and service characteristic information.

5. The method according to claim 4, characterized in that The user feature information includes at least one of the following: a user tag, user portrait information, and a user evaluation index value; wherein the user evaluation index value is an evaluation index value obtained by evaluating the user using a preset evaluation model; and / or, The dialing feature information includes at least one of the following: dialing method, estimated dialing time, last dialing time, and redialing interval; and / or, The service feature information includes at least one of the following: a service contract tag, service activity information, service access information, and identification information of the service system that pushes the list.

6. The method according to any one of claims 1 to 3, characterized in that The acquiring the to-be-dialed list from the first list warehouse according to the priority of the first list warehouse includes: When N to-be-dialed lists need to be obtained, the to-be-dialed lists are obtained from the first list warehouse in descending order of priority of the first list warehouse until the total number of the obtained to-be-dialed lists is N.

7. The method according to claim 6, characterized in that The step of obtaining the to-be-dialed list from the first list repository includes: When there are at least two list queues in the first list warehouse, obtaining the to-be-dialed list from the at least two list queues according to a preset acquisition ratio between the at least two list queues; When the total number of to-dial lists obtained is less than M, the to-dial lists are obtained from the remaining lists of the at least two list queues according to the priorities of the at least two list queues, where M is less than or equal to N, and M is the number of to-dial lists that need to be obtained from the first list warehouse.

8. The method according to claim 1, characterized in that Before determining the list category of the list based on the first characteristic information of the list, the method further includes: Determining a dialing method for the list from at least two preset dialing methods based on fifth characteristic information of the list, wherein the fifth characteristic information includes at least one of the following: user characteristic information, service characteristic information, number delivery status corresponding to each preset dialing method, and a recommended dialing method; Among them, lists with different dialing methods are scheduled using different list scheduling channels, and lists with the same dialing method are scheduled using the same list scheduling channel. Different list scheduling channels correspond to different list warehouses and different number delivery pools.

9. The method according to claim 1, characterized in that The determining of the list category of the list according to the first characteristic information of the list includes: When the time from the estimated dialing time of the list is less than or equal to the preset time, obtaining the first characteristic information of the list; The list category of the list is determined according to the first characteristic information of the list.

10. An outbound call task scheduling device, characterized in that: include: A first determining module, configured to determine a list category of the list according to first characteristic information of the list; A first storing module is configured to store the list into a first list warehouse according to the list category of the list; wherein the category of the first list warehouse corresponds to the list category of the list, different categories of lists correspond to different categories of list warehouses, and different categories of list warehouses have different priorities; an acquisition module, configured to acquire a to-be-dialed list from the first list warehouse according to the priority of the first list warehouse; The second storing module is used to store the to-be-dialed list into a number sending pool.

11. An outbound call task scheduling device, characterized in that: The method comprises a processor, a memory and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the outbound call task scheduling method according to any one of claims 1 to 9 are implemented.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the outbound call task scheduling method according to any one of claims 1 to 9 are implemented.

13. A computer program product, characterized in that The computer program product is stored in a storage medium, and when the computer program product is executed by at least one processor, the steps of the outbound call task scheduling method according to any one of claims 1 to 9 are implemented.

Images