Outbound call method and device, storage medium and computer device

Abstract

Embodiments of the present application disclose an outbound call method and device, a storage medium and a computer device. The method comprises: obtaining a to-be-called list, the to-be-called list comprising a plurality of to-be-called objects and a potential service handling type of each to-be-called object; selecting a target to-be-called object with a type number of potential service handling types greater than a preset number from the plurality of to-be-called objects; performing outbound call on each to-be-called object in the to-be-called list, when the to-be-called object is a non-target to-be-called object, performing outbound call according to the potential service handling type of the non-target to-be-called object, and recommending a service of one potential service handling type to the non-target to-be-called object each time the outbound call is performed; and when the to-be-called object is a target to-be-called object, recommending services of a plurality of corresponding potential service handling types to the target to-be-called object. The to-be-called object with a plurality of potential service handling types is called once in a comprehensive manner, so that the outbound call time is shortened and the outbound call efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of computers, and specifically to an outbound calling method, apparatus, computer-readable storage medium, and computer device. Background Technology

[0002] Traditional banks typically have a dedicated outbound calling team. Bank operations staff identify target customer groups and distribute this data to agents, who then make calls to reach customers and market bank products. This outbound calling method builds business opportunity data through traditional sales channels to reach users and conduct banking operations and product sales.

[0003] In the process of researching and practicing existing technologies, the inventors of this application discovered that in existing technologies, different product lines select corresponding customer group data according to the current product type, circle the list of outbound customers, and make calls. After the customer is connected, the communication and marketing are carried out through the script matched by the product. If the customer is interested, they fill out a business processing entry form. After the service is completed, a service summary is filled out. Each outbound call is carried out in the above process. This operation method matches all business opportunity data from the customer's perspective, resulting in an expansion of the outbound call scale, but the efficiency has not been effectively improved. Summary of the Invention

[0004] This application provides an outbound calling method and apparatus that can shorten outbound calling time and improve outbound calling efficiency.

[0005] To address the aforementioned technical problems, this application provides the following technical solutions:

[0006] An outbound calling method includes:

[0007] Obtain a list of objects to be called, which includes multiple objects to be called and the potential business processing type for each object;

[0008] Select target outbound call objects from multiple pending call objects, where the number of potential business processing types is greater than a preset number;

[0009] Call each of the pending outbound call objects in the pending outbound call list. When the outbound call object is a non-target pending outbound call object, call outbound according to the potential business handling type of the non-target pending outbound call object, and recommend a potential business handling type to the non-target pending outbound call object for each outbound call.

[0010] When the outbound call recipient is the target recipient, various potential business processing types are recommended to the target recipient.

[0011] An outbound calling device, comprising:

[0012] The first acquisition module is used to acquire a list of objects to be called out of the country, which includes multiple objects to be called out of the country and the potential business processing type of each object to be called out of the country.

[0013] The filtering module is used to filter out target outbound call objects from multiple outbound call objects, where the number of potential business processing types is greater than a preset number;

[0014] The first recommendation module is used to make outbound calls to each outbound object in the outbound call list. When the outbound object is a non-target outbound object, the outbound call is made according to the potential business handling type of the non-target outbound object, and a potential business handling type is recommended to the non-target outbound object for each outbound call.

[0015] The second recommendation module is used to recommend various potential business processing types to the target callee when the outbound callee is the target callee.

[0016] In some embodiments, the apparatus further includes:

[0017] The second acquisition module is used to acquire the user's historical usage information in different business applications, including whether there is any business processing form filling behavior.

[0018] The first determination module is used to determine the business processing type corresponding to the business application where there is a business processing form as the user's potential business processing type, and to determine the users with potential business processing types as the targets to be called, thus obtaining the list of targets to be called.

[0019] In some embodiments, the historical usage information further includes the user's historical browsing time in different business applications, and the device further includes:

[0020] The second determination module is used to determine the historical browsing duration of the target callee in the corresponding potential business processing type of the business application.

[0021] The identification module is used to identify potential business processing types according to the historical browsing duration of the business application for each potential business processing type, and to obtain a list of outbound calls with historical browsing duration.

[0022] In some embodiments, the second recommendation module includes:

[0023] The first acquisition submodule is used to acquire the identifier of the potential business processing type of the target outbound call object, and obtain the historical browsing duration of the business application corresponding to each potential business processing type of the target outbound call object.

[0024] The sorting submodule is used to sort the historical browsing time of the business applications corresponding to each potential business processing type to obtain the sorted potential business processing types.

[0025] The first recommendation submodule is used to recommend various potential business processing types to the non-target outbound call objects in sequence according to the sorted potential business processing types.

[0026] In some embodiments, the first recommendation submodule is configured to:

[0027] Obtain the recommended script for each potential business processing type after sorting;

[0028] The recommended scripts corresponding to each of the sorted potential business processing types are used to sequentially recommend various potential business processing types to the target outbound call recipient.

[0029] In some embodiments, the first recommendation module includes:

[0030] The second acquisition submodule is used to acquire the recommended script corresponding to the current potential business processing type recommended to the non-target outbound call object;

[0031] The second recommendation submodule uses the recommendation script corresponding to the current potential business processing type to recommend the current potential business processing type to the non-target outbound call recipient.

[0032] A computer-readable storage medium storing a plurality of instructions adapted for loading by a processor to perform the steps in the outbound call method described above.

[0033] A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps in the outbound call method described above.

[0034] This application embodiment obtains a list of pending outbound calls, which includes multiple pending call recipients and the potential service types for each recipient. It then selects target pending call recipients from the multiple recipients whose number of potential service types exceeds a preset number. Outbound calls are made to each recipient in the pending call list. When the recipient is not a target recipient, the outbound call is made according to the potential service types of the non-target recipient, and a potential service type is recommended to the non-target recipient during each outbound call. When the recipient is a target recipient, multiple potential service types are recommended to the target recipient. In this way, by making a comprehensive outbound call to recipients with multiple potential service types in a single call, the outbound call time is shortened and outbound call efficiency is improved. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1a This is a system schematic diagram of the outbound calling method provided in the embodiments of this application.

[0037] Figure 1b This is a flowchart illustrating the outbound calling method provided in an embodiment of this application.

[0038] Figure 2 This is a schematic diagram of the outbound calling device provided in an embodiment of this application.

[0039] Figure 3 A schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0040] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0041] Please see Figure 1a , Figure 1aThis is a system diagram illustrating the outbound calling method provided in this application embodiment. The system may include at least one client 1000, at least one computer device 2000, at least one database 3000, and a network 4000. Each application corresponds to at least one computer device 2000, and the client 1000 can be a terminal device such as a mobile phone, computer, or personal digital assistant. The computer device 2000 makes VoIP calls to the client 1000 through the network 4000. The network 4000 can be a wireless network or a wired network, such as a wireless local area network (WLAN), local area network (LAN), cellular network, 2G network, 3G network, 4G network, 5G network, etc. Additionally, the system may include a database 3000, which can be used to store information such as the potential business processing types of multiple outbound call recipients.

[0042] This application provides an outbound calling method, which can be executed by a computer device. For example... Figure 1a As shown, the computer device 2000 acquires a list of objects to be called, which includes multiple objects to be called and the potential service types for each object. It then selects target objects from the multiple objects to be called, where the number of potential service types exceeds a preset number. For each object in the list, an outbound call is made. When the object is not a target object, the call is made according to the potential service types of the non-target object, and a potential service type is recommended to the non-target object during each call. When the object is a target object, multiple potential service types are recommended to the target object. Based on this, by making a comprehensive outbound call to objects with multiple potential service types, the outbound call time is shortened and the outbound call efficiency is improved.

[0043] It should be noted that, Figure 1a The schematic diagram of the outbound calling method shown is merely an example. The outbound calling system and scenario described in this application embodiment are for the purpose of more clearly illustrating the technical solutions of this application embodiment and do not constitute a limitation on the technical solutions provided in this application embodiment. As those skilled in the art will know, with the evolution of outbound calling systems and the emergence of new business scenarios, the technical solutions provided in this application embodiment are also applicable to similar technical problems.

[0044] In this embodiment, the description will be from the perspective of an outbound calling device, which can be integrated into a computer device that has a storage unit and a microprocessor and thus computing power.

[0045] Please see Figure 1b , Figure 1bThis is a flowchart illustrating an outbound calling method provided in an embodiment of this application. The outbound calling method includes:

[0046] In step 101, a list of objects to be called is obtained, which includes multiple objects to be called and the potential business processing type for each object.

[0047] The list of entities to be called includes multiple entities waiting to be called by the outbound calling system, as well as the potential business processing type corresponding to each entity to be called, collected through various means.

[0048] Specifically, please refer to Table 1. Table 1 is a schematic diagram of the first structure of the outbound call list provided in this application embodiment. The outbound call list includes customer names and various business processing types such as the number of credit card interest rate increase opportunities, the number of auto loan opportunities, the number of personal loan opportunities, and the number of wealth management opportunities. If the outbound call recipient has a potential interest in a certain business processing type, then the business processing type with the potential interest is identified as a potential business processing type and marked as 1 in the outbound call list. For example, if Li Si has a potential interest in personal loans and wealth management, then in the outbound call list, Li Si's line for personal loans and wealth management is marked as 1, and the rest are marked as 0.

[0049] Table 1

[0050]

[0051] In some implementations, the method further includes, prior to the step of obtaining the list of calls to be made:

[0052] (1) Obtain the user's historical usage information in different business applications, including whether there is any business processing form filling behavior;

[0053] (2) The business processing type corresponding to the business application with business processing filling behavior is identified as the potential business processing type of the user, and the user with potential business processing type is identified as the target to be called, thus obtaining the target to be called list.

[0054] The collection of each potential callee and their corresponding potential business type can be achieved by pre-setting multiple business applications for different business types. For example, if the business type is auto finance / car owner loan, a car owner loan app can be set up; if the business type is wealth management, a wealth management app can be set up. Users can download different apps from the app store to their phones according to their needs. During app usage, historical usage information is generated, including whether any business application information has been filled out. For example, if someone has filled out information about car owner loans in the car owner loan app, a business application information entry will be generated. If such an entry occurs, it is assumed that the user has a potential interest in applying for a car owner loan, and the user is identified as a potential callee, with car owner loan identified as their corresponding potential business type.

[0055] Specifically, different business applications can connect to the same backend server, allowing the backend server to obtain multiple potential business processing types for a single user, or multiple users with a single potential business processing type.

[0056] In some implementations, the historical usage information also includes the user's historical browsing time in different business applications. Following the steps of determining the business processing type corresponding to the business application where business processing information is filled out as the user's potential business processing type, and determining users with potential business processing types as targets for outbound calls, the method further includes:

[0057] (1) Determine the historical browsing duration of the target callee in the corresponding potential business processing type of the business application;

[0058] (2) Identify potential business processing types according to the historical browsing duration of the business application for each potential business processing type, and obtain a list of outbound calls with historical browsing duration.

[0059] The historical usage information also includes the user's historical browsing time in different business applications. For example, the user's historical browsing time in the Car Owner Loan APP is 30 minutes.

[0060] Specifically, please refer to Table 2, which illustrates the second structure of the outbound call list provided in this application embodiment. After determining the outbound call recipient and the corresponding potential business processing type, the historical browsing time of the outbound call recipient in the corresponding potential business processing type of the business application can also be determined. For example, if the potential business processing type corresponding to the outbound call recipient Wang Wu is car owner loan, and his historical browsing time in the car owner loan APP is 30 minutes, then the part of the outbound call recipient Wang Wu's group related to car owner loan will be marked in the outbound call list as 30 minutes, thus obtaining the outbound call list with historical browsing time.

[0061] Table 2

[0062]

[0063] In step 102, target outbound call objects with a greater than preset number of potential business processing types are selected from multiple outbound call objects.

[0064] To improve outbound calling efficiency, this application stipulates that if a single callee corresponds to multiple potential business processing types, a single outbound call will be made to that single callee, recommending each of the multiple potential business processing types to that callee during the call process. Therefore, to determine which callees require multiple recommendations in a single outbound call, it is necessary to select target callees from the multiple callees whose number of potential business processing types exceeds a preset number. The preset number can be two or more.

[0065] Specifically, referring to Table 2, Zhang San has 4 potential business handling types, Li Si has 1 potential business handling type, Wang Wu has 3 potential business handling types, Zhao Liu has 4 potential business handling types, Qian Qi has 2 potential business handling types, and Liu Ba has 3 potential business handling types. Therefore, the target callees are: Zhang San, Wang Wu, Zhao Liu, Qian Qi, and Liu Ba.

[0066] In step 103, outbound calls are made to each outbound target in the outbound call list. When the outbound target is a non-target outbound target, the outbound call is made according to the potential business processing type of the non-target outbound target, and a potential business processing type is recommended to the non-target outbound target during each outbound call.

[0067] In the process of making outbound calls to each target in the outbound call list, if the target is not a target, the outbound call is made according to the potential business processing type of the non-target target, and a potential business processing type is recommended to the non-target target during each outbound call.

[0068] Specifically, if the outbound call target is not the target to be called, it means that the current outbound call target has only a single potential business processing type, or the number of its potential business processing types is less than the preset number. For such users, outbound calls can be made for a single business processing type.

[0069] For example, if Li Si has two potential business types, namely car owner loan and interest rate increase, and the preset number is three, then Li Si is not a target to be called. Therefore, two outbound calls can be made to Li Si: one call to recommend the car owner loan business and the other call to recommend the interest rate increase business.

[0070] In some implementations, the step of recommending a potential service type to the non-target callee on each outbound call includes:

[0071] (1) Obtain the recommended script corresponding to the current potential business processing type recommended to the non-target outbound call object;

[0072] (2) Recommend the business of the current potential business processing type to the non-target outbound call object using the recommended script corresponding to the current potential business processing type.

[0073] Since outbound calls to non-target recipients involve multiple calls based on different potential service types, different recommended scripts are needed for each type of potential service. Therefore, the recommended script for the current potential service type is obtained and used to recommend the service of that type to the non-target recipients.

[0074] In step 104, when the outbound call target is the target outbound call target, various potential business processing types are recommended to the target outbound call target.

[0075] In the process of making outbound calls to each target in the outbound call list, if the target is the target target, then various potential business processing types are recommended to the target target. In other words, multiple potential business processing types are recommended through a single outbound call.

[0076] Specifically, if the outbound call target is the target to be called, it means that the current outbound call target has only multiple potential business processing types, or the number of its potential business processing types is greater than the preset number. For such users, a single outbound call can be made for multiple potential business processing types.

[0077] For example, if Liu Ba has three potential business types: interest rate increase, car owner loan, and wealth management, and the preset quantity is two, then Liu Ba is the target to be called. A single outbound call can be made to Liu Ba, during which interest rate increase, car owner loan, and wealth management can all be recommended to Liu Ba.

[0078] In some implementations, the step of recommending various potential service types to the target callee when the outbound callee is the target callee includes:

[0079] (1) Obtain the identifier of the potential business processing type of the target outbound call object, and obtain the historical browsing duration of the business application corresponding to each potential business processing type of the target outbound call object;

[0080] (2) Sort the historical browsing duration of the business application corresponding to each potential business processing type to obtain the sorted potential business processing types.

[0081] (3) Recommend the corresponding business processing types to the non-target outbound call objects in sequence according to the sorted potential business processing types.

[0082] In this process, since each potential service type was identified based on the user's usage time of apps for different potential service types when collecting the outbound call list, the identifier of the potential service type for the target outbound call recipient can be obtained, and the historical browsing time of the target outbound call recipient for each potential service type can be obtained. To improve the success rate of handling multiple potential service types, the historical browsing time of the business applications corresponding to each potential service type can be sorted to obtain the sorted potential service types; according to the sorted potential service types, the corresponding services of multiple potential service types are recommended to the non-target outbound call recipients in sequence.

[0083] For example, if Wang Wu's historical usage time on the interest rate increase app is 10 minutes, on the car owner loan app is 30 minutes, and on the wealth management app is 20 minutes, then the potential business types after sorting by usage time would be car owner loan, wealth management, and interest rate increase. When making outbound calls to Wang Wu, the business recommendations would be made in this order: first recommend car owner loan, then wealth management, and finally interest rate increase.

[0084] In some implementations, the step of sequentially recommending various potential business processing types to the target outbound call recipient according to the sorted potential business processing types includes:

[0085] (1.1) Obtain the recommended script for each potential business processing type after sorting;

[0086] (1.2) The recommended scripts corresponding to each of the sorted potential business processing types are used to recommend the corresponding multiple potential business processing types to the target outbound call object in sequence.

[0087] Specifically, the system obtains the recommended scripts for each sorted potential business processing type, and when recommending services to the target outbound call recipient, it can sequentially recommend services of multiple potential business processing types.

[0088] As described above, this application embodiment obtains a list of objects to be called, which includes multiple objects to be called and the potential business processing types for each object. From the multiple objects to be called, target objects to be called are selected where the number of potential business processing types exceeds a preset number. Outbound calls are made to each object in the list. When the object to be called is not a target object, the outbound call is made according to the potential business processing type of the non-target object, and a potential business processing type is recommended to the non-target object during each outbound call. When the object to be called is a target object, multiple corresponding potential business processing types are recommended to the target object. In this way, by making a comprehensive outbound call to objects with multiple potential business processing types in one go, the outbound call time is shortened and the outbound call efficiency is improved.

[0089] Obtain the list of objects to be called, which includes multiple objects to be called and the potential business processing type for each object.

[0090] The list of entities to be called includes multiple entities waiting to be called by the outbound calling system, as well as the potential business processing type corresponding to each entity to be called, collected through various means.

[0091] Specifically, please refer to Table 3. Table 3 is a schematic diagram of the first structure of the outbound call list provided in this application embodiment. The outbound call list includes customer names and various business processing types such as the number of credit card interest rate increase opportunities, the number of auto loan opportunities, the number of personal loan opportunities, and the number of wealth management opportunities. If the outbound call recipient has a potential interest in a certain business processing type, then the business processing type with the potential interest is identified as a potential business processing type and marked as 1 in the outbound call list. For example, if Li Si has a potential interest in personal loans and wealth management, then in the outbound call list, Li Si's line for personal loans and wealth management is marked as 1, and the rest are marked as 0.

[0092] Table 3

[0093]

[0094] In some implementations, the method further includes, prior to the step of obtaining the list of calls to be made:

[0095] (1) Obtain the user's historical usage information in different business applications, including whether there is any business processing form filling behavior;

[0096] (2) The business processing type corresponding to the business application with business processing filling behavior is identified as the potential business processing type of the user, and the user with potential business processing type is identified as the target to be called, thus obtaining the target to be called list.

[0097] The collection of each potential callee and their corresponding potential business type can be achieved by pre-setting multiple business applications for different business types. For example, if the business type is auto finance / car owner loan, a car owner loan app can be set up; if the business type is wealth management, a wealth management app can be set up. Users can download different apps from the app store to their phones according to their needs. During app usage, historical usage information is generated, including whether any business application information has been filled out. For example, if someone has filled out information about car owner loans in the car owner loan app, a business application information entry will be generated. If such an entry occurs, it is assumed that the user has a potential interest in applying for a car owner loan, and the user is identified as a potential callee, with car owner loan identified as their corresponding potential business type.

[0098] Specifically, different business applications can connect to the same backend server, allowing the backend server to obtain multiple potential business processing types for a single user, or multiple users with a single potential business processing type.

[0099] In some implementations, the historical usage information also includes the user's historical browsing time in different business applications. Following the steps of determining the business processing type corresponding to the business application where business processing information is filled out as the user's potential business processing type, and determining users with potential business processing types as targets for outbound calls, the method further includes:

[0100] (1) Determine the historical browsing duration of the target callee in the corresponding potential business processing type of the business application;

[0101] (2) Identify potential business processing types according to the historical browsing duration of the business application for each potential business processing type, and obtain a list of outbound calls with historical browsing duration.

[0102] The historical usage information also includes the user's historical browsing time in different business applications. For example, the user's historical browsing time in the Car Owner Loan APP is 30 minutes.

[0103] Specifically, please refer to Table 4, which illustrates the second structure of the outbound call list provided in this application embodiment. After determining the outbound call recipient and the corresponding potential business processing type, the historical browsing time of the outbound call recipient in the corresponding potential business processing type of the business application can also be determined. For example, if the potential business processing type corresponding to the outbound call recipient Wang Wu is car owner loan, and his historical browsing time in the car owner loan APP is 30 minutes, then the part of the outbound call recipient Wang Wu's group related to car owner loan will be marked in the outbound call list as 30 minutes, thus obtaining the outbound call list with historical browsing time.

[0104] Table 4

[0105]

[0106] Select target outbound call objects from multiple pending call objects whose number of potential business processing types exceeds a preset number.

[0107] To improve outbound calling efficiency, this application stipulates that if a single callee corresponds to multiple potential business processing types, a single outbound call will be made to that single callee, recommending each of the multiple potential business processing types to that callee during the call process. Therefore, to determine which callees require multiple recommendations in a single outbound call, it is necessary to select target callees from the multiple callees whose number of potential business processing types exceeds a preset number. The preset number can be two or more.

[0108] Specifically, referring to Table 4, Zhang San has 4 potential business handling types, Li Si has 1 potential business handling type, Wang Wu has 3 potential business handling types, Zhao Liu has 4 potential business handling types, Qian Qi has 2 potential business handling types, and Liu Ba has 3 potential business handling types. Therefore, the target callees are: Zhang San, Wang Wu, Zhao Liu, Qian Qi, and Liu Ba.

[0109] For each target in the list of targets to be called, make an outbound call. When the target is not a target, make the outbound call according to the potential business processing type of the non-target target and recommend a potential business processing type to the non-target target during each outbound call.

[0110] In the process of making outbound calls to each target in the outbound call list, if the target is not a target, the outbound call is made according to the potential business processing type of the non-target target, and a potential business processing type is recommended to the non-target target during each outbound call.

[0111] Specifically, if the outbound call target is not the target to be called, it means that the current outbound call target has only a single potential business processing type, or the number of its potential business processing types is less than the preset number. For such users, outbound calls can be made for a single business processing type.

[0112] For example, if Li Si has two potential business types, namely car owner loan and interest rate increase, and the preset number is three, then Li Si is not a target to be called. Therefore, two outbound calls can be made to Li Si: one call to recommend the car owner loan business and the other call to recommend the interest rate increase business.

[0113] In some implementations, the step of recommending a potential service type to the non-target callee on each outbound call includes:

[0114] (1) Obtain the recommended script corresponding to the current potential business processing type recommended to the non-target outbound call object;

[0115] (2) Recommend the business of the current potential business processing type to the non-target outbound call object using the recommended script corresponding to the current potential business processing type.

[0116] Since outbound calls to non-target recipients involve multiple calls based on different potential service types, different recommended scripts are needed for each type of potential service. Therefore, the recommended script for the current potential service type is obtained and used to recommend the service of that type to the non-target recipients.

[0117] When the outbound call recipient is the target recipient, various potential business processing types are recommended to the target recipient.

[0118] In the process of making outbound calls to each target in the outbound call list, if the target is the target target, then various potential business processing types are recommended to the target target. In other words, multiple potential business processing types are recommended through a single outbound call.

[0119] Specifically, if the outbound call target is the target to be called, it means that the current outbound call target has only multiple potential business processing types, or the number of its potential business processing types is greater than the preset number. For such users, a single outbound call can be made for multiple potential business processing types.

[0120] For example, if Liu Ba has three potential business types: interest rate increase, car owner loan, and wealth management, and the preset quantity is two, then Liu Ba is the target to be called. A single outbound call can be made to Liu Ba, during which interest rate increase, car owner loan, and wealth management can all be recommended to Liu Ba.

[0121] In some implementations, the step of recommending various potential service types to the target callee when the outbound callee is the target callee includes:

[0122] (1) Obtain the identifier of the potential business processing type of the target outbound call object, and obtain the historical browsing duration of the business application corresponding to each potential business processing type of the target outbound call object;

[0123] (2) Sort the historical browsing duration of the business application corresponding to each potential business processing type to obtain the sorted potential business processing types.

[0124] (3) Recommend the corresponding business processing types to the non-target outbound call objects in sequence according to the sorted potential business processing types.

[0125] In this process, since each potential service type was identified based on the user's usage time of apps for different potential service types when collecting the outbound call list, the identifier of the potential service type for the target outbound call recipient can be obtained, and the historical browsing time of the target outbound call recipient for each potential service type can be obtained. To improve the success rate of handling multiple potential service types, the historical browsing time of the business applications corresponding to each potential service type can be sorted to obtain the sorted potential service types; according to the sorted potential service types, the corresponding services of multiple potential service types are recommended to the non-target outbound call recipients in sequence.

[0126] For example, if Wang Wu's historical usage time on the interest rate increase app is 10 minutes, on the car owner loan app is 30 minutes, and on the wealth management app is 20 minutes, then the potential business types after sorting by usage time would be car owner loan, wealth management, and interest rate increase. When making outbound calls to Wang Wu, the business recommendations would be made in this order: first recommend car owner loan, then wealth management, and finally interest rate increase.

[0127] In some implementations, the step of sequentially recommending various potential business processing types to the target outbound call recipient according to the sorted potential business processing types includes:

[0128] (1.1) Obtain the recommended script for each potential business processing type after sorting;

[0129] (1.2) The recommended scripts corresponding to each of the sorted potential business processing types are used to recommend the corresponding multiple potential business processing types to the target outbound call object in sequence.

[0130] Specifically, the system obtains the recommended scripts for each sorted potential business processing type, and when recommending services to the target outbound call recipient, it can sequentially recommend services of multiple potential business processing types.

[0131] To facilitate better implementation of the outbound calling method provided in the embodiments of this application, the embodiments of this application also provide an apparatus based on the above-described outbound calling method. The meanings of the terms used are the same as in the above-described outbound calling method, and specific implementation details can be found in the descriptions in the method embodiments.

[0132] Please see Figure 2 , Figure 2 This is a schematic diagram of the structure of an outbound calling device provided in an embodiment of this application. The outbound calling device may include a first acquisition module 201, a screening module 202, a first recommendation module 203, and a second recommendation module 204, etc.

[0133] The first acquisition module 201 is used to acquire a list of objects to be called out of the country, which includes multiple objects to be called out of the country and the potential business processing type of each object to be called out of the country.

[0134] The filtering module 202 is used to filter out target outbound call objects from multiple outbound call objects whose number of potential business processing types is greater than a preset number;

[0135] The first recommendation module 203 is used to make outbound calls to each outbound object in the outbound call list. When the outbound object is a non-target outbound object, the outbound call is made according to the potential business handling type of the non-target outbound object, and a potential business handling type is recommended to the non-target outbound object for each outbound call.

[0136] The second recommendation module 204 is used to recommend various potential business processing types to the target callee when the outbound callee is the target callee.

[0137] In some embodiments, the apparatus further includes:

[0138] The second acquisition module is used to acquire the user's historical usage information in different business applications, including whether there is any business processing form filling behavior.

[0139] The first determination module is used to determine the business processing type corresponding to the business application where there is a business processing form as the potential business processing type of the user, and to determine the users with potential business processing types as the targets to be called, thus obtaining the list of users to be called.

[0140] In some embodiments, the historical usage information further includes the user's historical browsing time in different business applications, and the device further includes:

[0141] The second determination module is used to determine the historical browsing duration of the target callee in the corresponding potential business processing type of the business application.

[0142] The identification module is used to identify potential business processing types according to the historical browsing duration of the business application for each potential business processing type, and to obtain a list of outbound calls with historical browsing duration.

[0143] In some embodiments, the second recommendation module includes:

[0144] The first acquisition submodule is used to acquire the identifier of the potential business processing type of the target outbound call object, and obtain the historical browsing time of the business application corresponding to each potential business processing type of the target outbound call object.

[0145] The sorting submodule is used to sort the historical browsing time of the business applications corresponding to each potential business processing type to obtain the sorted potential business processing types.

[0146] The first recommendation submodule is used to recommend various potential business processing types to the non-target outbound call objects in sequence according to the sorted potential business processing types.

[0147] In some embodiments, the first recommendation submodule is configured to:

[0148] Obtain the recommended script for each potential business processing type after sorting;

[0149] The recommended scripts corresponding to each of the sorted potential business processing types are used to sequentially recommend various potential business processing types to the target outbound call recipient.

[0150] In some embodiments, the first recommendation module includes:

[0151] The second acquisition submodule is used to acquire the recommended script corresponding to the current potential business processing type recommended to the non-target outbound call object;

[0152] The second recommendation submodule uses the recommendation script corresponding to the current potential business processing type to recommend the current potential business processing type to the non-target outbound call recipient.

[0153] As described above, this embodiment of the application obtains a list of objects to be called through a first acquisition module 201. The list includes multiple objects to be called and the potential business processing types of each object. A filtering module 202 filters out target objects from the multiple objects to be called, where the number of potential business processing types is greater than a preset number. A first recommendation module 203 makes outbound calls to each object in the list. When the object to be called is not a target object, it makes outbound calls according to the potential business processing types of the non-target object, and recommends a potential business processing type to the non-target object during each outbound call. A second recommendation module 204 recommends multiple potential business processing types to the target object when the object to be called is the target object. In this way, by making a comprehensive outbound call to objects with multiple potential business processing types, the outbound call time is shortened and the outbound call efficiency is improved.

[0154] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0155] Accordingly, this application also provides a computer device, which can be a terminal or a server. The terminal can be a smartphone, tablet computer, laptop computer, touch screen, game console, personal computer (PC), personal digital assistant (PDA), or other terminal device. Figure 3 As shown, Figure 3 This is a schematic diagram of the structure of a computer device provided in an embodiment of this 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. The processor 401 and the memory 402 are electrically connected. Those skilled in the art will understand that the computer device structure shown in the figure 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.

[0156] The processor 401 is the control center of the computer device 2000. It connects various parts of the computer device 2000 through various interfaces and lines. By running or loading software programs and / or modules stored in the memory 402, and calling data stored in the memory 402, it performs various functions of the computer device 2000 and processes data, thereby monitoring the computer device 2000 as a whole.

[0157] In this embodiment, the processor 401 in the computer device 2000 loads the instructions corresponding to the processes of one or more applications into the memory 402 according to the following steps, and the processor 401 runs the applications stored in the memory 402 to achieve various functions:

[0158] Obtain a list of objects to be called, which includes multiple objects to be called and the potential service types for each object. Select target objects from the multiple objects to be called whose number of potential service types exceeds a preset number. Make outbound calls to each object in the list. When the object to be called is not a target object, make outbound calls according to the potential service types of the non-target object, and recommend one potential service type to the non-target object during each outbound call. When the object to be called is a target object, recommend multiple corresponding potential service types to the target object.

[0159] In some embodiments, prior to the step of obtaining the list of calls to be made, the method further includes:

[0160] Obtain users’ historical usage information in different business applications, including whether there is any business processing form filling behavior;

[0161] The business processing type corresponding to the business application where there is a business processing form is identified as the user's potential business processing type, and the users with potential business processing types are identified as the targets to be called, thus obtaining the list of targets to be called.

[0162] In some embodiments, the historical usage information further includes the user's historical browsing time in different business applications. After the steps of determining the business processing type corresponding to the business application where business processing information is filled in as the user's potential business processing type, and determining the user with the potential business processing type as the target for outbound calls, the method further includes:

[0163] Determine the historical browsing duration of the target callee in the corresponding potential business application for the business processing type;

[0164] Potential business processing types are identified by the historical browsing duration of the business applications used for each type, resulting in a list of pending outbound calls with the historical browsing duration.

[0165] In some embodiments, the step of recommending various potential service types to the target callee when the outbound callee is the target callee includes:

[0166] Obtain the identifier of the potential business processing type of the target outbound call object, and obtain the historical browsing duration of the business application corresponding to each potential business processing type for the target outbound call object;

[0167] Sort the historical browsing duration of the business applications corresponding to each potential business processing type to obtain the sorted potential business processing types;

[0168] Based on the sorted potential business processing types, the non-target outbound call recipients are sequentially recommended various corresponding potential business processing types.

[0169] In some embodiments, the step of sequentially recommending services of various potential service types to the target outbound call object according to the sorted potential service types includes:

[0170] Obtain the recommended script for each potential business processing type after sorting;

[0171] The recommended scripts corresponding to each of the sorted potential business processing types are used to sequentially recommend various potential business processing types to the target outbound call recipient.

[0172] In some embodiments, the step of recommending a potential service type to the non-target callee on each outbound call includes:

[0173] Obtain the recommended script corresponding to the current potential business processing type recommended to the non-target outbound call recipient;

[0174] The recommended script corresponding to the current potential business processing type is used to recommend the business of the current potential business processing type to the non-target outbound call recipient.

[0175] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0176] Optional, such as Figure 3 As shown, the computer device 2000 also includes a touch screen display 403, an input unit 404, and a power supply 405. The processor 401 is electrically connected to the touch screen display 403, the input unit 404, and the power supply 405. Those skilled in the art will understand that... Figure 3 The 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.

[0177] The touch display screen 403 can be used to display a graphical user interface (GUI) and receive operation commands generated by the user interacting with the GUI. The touch display screen 403 may include a display panel and a touch panel. 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, video, and any combination thereof. Optionally, the display panel can be configured using a liquid crystal display (LCD), organic light-emitting diode (OLED), or other similar technologies. The touch panel can be used to collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel), generate corresponding operation commands, and execute the corresponding program according to the operation commands. Optionally, the touch panel may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch location and the signal generated by the touch operation, transmitting the signal to the touch controller. The touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 401. It can also receive and execute commands from 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 the information to the processor 401 to determine the type of touch event. Subsequently, the processor 401 provides corresponding visual output on the display panel based on the type of touch event. In this embodiment, the touch panel and the display panel can be integrated into the touch display screen 403 to achieve input and output functions. However, in some embodiments, the touch panel and the touch display screen 403 can be implemented as two independent components to achieve input and output functions. That is, the touch display screen 403 can also be used as part of the input unit 404 to achieve input functions.

[0178] In this embodiment, a game application is executed by processor 401 to generate a graphical user interface (GUI) on touch display screen 403. The virtual scene on the GUI 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 GUI and receive operation commands generated by the user interacting with the GUI.

[0179] The input unit 404 can be used to receive input numbers, characters, or user characteristic information (such as fingerprints, iris, facial information, etc.), and generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.

[0180] Power supply 405 is used to supply power to various components of computer device 2000. Optionally, power supply 405 can be logically connected to processor 401 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Power supply 405 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0181] although Figure 3 As not shown in the diagram, the computer device 2000 may also include a wireless fidelity module, a Bluetooth module, etc., which will not be described in detail here.

[0182] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0183] As can be seen from the above, the computer device provided in this embodiment obtains a list of objects to be called, which includes multiple objects to be called and the potential business processing types of each object. It then selects target objects from the multiple objects to be called, where the number of potential business processing types exceeds a preset number. For each object in the list, an outbound call is made. When the object is not a target object, the call is made according to the potential business processing type of the non-target object, and a potential business processing type is recommended to the non-target object during each call. When the object is a target object, multiple potential business processing types are recommended to the target object. In this way, by making a comprehensive outbound call to objects with multiple potential business processing types in one go, the outbound call time is shortened and the outbound call efficiency is improved.

[0184] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0185] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of computer programs that can be loaded by a processor to execute steps in any of the control methods provided in the embodiments of this application. For example, the computer program can execute the following steps:

[0186] Obtain a list of objects to be called, which includes multiple objects to be called and the potential service types for each object. Select target objects from the multiple objects to be called whose number of potential service types exceeds a preset number. Make outbound calls to each object in the list. When the object to be called is not a target object, make outbound calls according to the potential service types of the non-target object, and recommend one potential service type to the non-target object during each outbound call. When the object to be called is a target object, recommend multiple corresponding potential service types to the target object.

[0187] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0188] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0189] Since the computer program stored in the storage medium can execute the steps in any of the outbound calling methods provided in the embodiments of this application, the beneficial effects that any of the outbound calling methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0190] The foregoing has provided a detailed description of an outbound calling method, apparatus, storage medium, and computer device provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. An outbound calling method, characterized in that, include: Obtain the user's historical usage information in different business applications, including whether there is any business processing form filling behavior and the user's historical browsing time in different business applications; The business application with the business processing form is identified as the user's potential business processing type, and the user with the potential business processing type is identified as the target of outbound calls. The historical browsing time of the target of outbound calls in the corresponding business application of the potential business processing type is determined. The potential business processing type is identified according to the historical browsing time of the business application of each potential business processing type, and a list of target of outbound calls with historical browsing time is obtained. The list of target of outbound calls includes multiple target of outbound calls and the potential business processing type of each target of outbound calls. The potential business processing type indicates the business processing type that the target of outbound calls has the potential to process. Select target outbound call objects from multiple outbound call objects whose number of potential business processing types is greater than a preset number. The target outbound call objects refer to outbound call objects that have multiple potential business processing types and require multiple recommendations in a single outbound call. The multiple recommendations are used to indicate that multiple potential business processing types are comprehensively recommended to the target outbound call objects during a single outbound call. Call each of the pending outbound call objects in the pending outbound call list. When the outbound call object is a non-target pending outbound call object, call outbound according to the potential business handling type of the non-target pending outbound call object, and recommend a potential business handling type to the non-target pending outbound call object for each outbound call. When the outbound call target is the target outbound call target, the identifier of the potential business processing type of the target outbound call target is obtained, the historical browsing time of the business application corresponding to each potential business processing type of the target outbound call target is obtained, the historical browsing time of the business application corresponding to each potential business processing type is sorted, and the corresponding multiple potential business processing types are recommended to the target outbound call target in sequence according to the sorted potential business processing types.

2. The outbound calling method according to claim 1, characterized in that, The step of recommending various potential business processing types to the target outbound call recipients according to the sorted potential business processing types includes: Obtain the recommended script for each potential business processing type after sorting; The recommended scripts corresponding to each of the sorted potential business processing types are used to sequentially recommend various potential business processing types to the target outbound call recipient.

3. The outbound calling method according to claim 1, characterized in that, The step of recommending a potential service type to the non-target callee during each outbound call includes: Obtain the recommended script corresponding to the current potential business processing type recommended to the non-target outbound call recipient; The recommended script corresponding to the current potential business processing type is used to recommend the business of the current potential business processing type to the non-target outbound call recipient.

4. An outbound calling device, characterized in that, include: The first acquisition module is used to acquire the user's historical usage information in different business applications. The historical usage information includes whether there is any business processing form filling behavior and the user's historical browsing time in different business applications. The business processing type corresponding to the business application where there is business processing form filling behavior is identified as the user's potential business processing type, and the user with the potential business processing type is identified as the outbound call target. The historical browsing time of the outbound call target in the corresponding potential business processing type business application is determined. The potential business processing type is identified according to the historical browsing time of the business application of each potential business processing type business type to obtain the outbound call list with historical browsing time. The outbound call list includes multiple outbound call targets and the potential business processing type of each outbound call target. The potential business processing type indicates the business processing type that the outbound call target has the potential to process. The filtering module is used to filter out target outbound call objects from multiple outbound call objects, where the number of potential business processing types is greater than a preset number. The target outbound call object refers to an outbound call object that has multiple potential business processing types and requires multiple recommendations in a single outbound call. The multiple recommendations are used to indicate that multiple potential business processing types are comprehensively recommended to the target outbound call object during a single outbound call. The first recommendation module is used to make outbound calls to each outbound object in the outbound call list. When the outbound object is a non-target outbound object, the outbound call is made according to the potential business handling type of the non-target outbound object, and a potential business handling type is recommended to the non-target outbound object for each outbound call. The second recommendation module is used to obtain the identifier of the potential business processing type of the target outbound call object when the outbound call object is the target outbound call object, obtain the historical browsing time of the business application corresponding to each potential business processing type of the target outbound call object, sort the historical browsing time of the business application corresponding to each potential business processing type, and recommend the corresponding multiple potential business processing types of services to the target outbound call object in sequence according to the sorted potential business processing types.

5. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted for loading by a processor to perform the steps of the outbound calling method according to any one of claims 1 to 3.

6. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the outbound calling method as described in any one of claims 1 to 3.

Images