User touch method and device, program product and electronic equipment

Abstract

The invention discloses a user arriving method and device, a program product and electronic equipment, and relates to the field of financial science and technology or other related fields, and the user arriving method comprises the steps: blocking an outbound call to a target user when the outbound call to the target user in a target user list is detected through a channel end, and sending the outbound call to the target user; and calling a preset engine interface, sending a user arriving request to a preset engine based on the preset engine interface, controlling the channel end to call out a target user under the condition that an arriving result returned by the preset engine indicates a to-be-arrived state, and controlling the channel end to call out the target user under the condition that the arriving result returned by the preset engine indicates an arrived state. And deleting the target user from the target user list. According to the method and the device, the technical problem of relatively low efficiency of performing outbound call arrival on the user in the related technology is solved.

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and specifically, to a user contact method and its device, program product, and electronic device. Background Art

[0002] With the development of big data technology, financial institutions face numerous challenges in processing and analyzing user data. For smartphone outbound calls, effectively managing outbound call lists to minimize interruptions to users has become a pressing issue.

[0003] In the related art, the number of times each user is disturbed within a preset time period is usually calculated in a data lake, and then the outbound user list is manually updated. However, the above method has the following problems: (1) Inefficiency: Calculating the number of times each user is disturbed within a preset time period in a data lake usually requires a lot of time and resources. In addition, manually updating the outbound user list is also a very time-consuming process. (2) Data inconsistency: Since there may be delays in data synchronization between the data lake and the outbound user list, the number of times the user is disturbed is inaccurate, affecting the accuracy of decision-making. (3) Errors and omissions: Manually updating the outbound user list is prone to errors, which may cause users to be excessively disturbed or omitted. (4) High cost: Calculating and manually updating the outbound user list in the data lake requires a lot of human resources, which increases costs. (5) Lack of flexibility: It is impossible to make real-time adjustments based on business needs and user behavior.

[0004] To the above problems, no effective solution has been proposed yet. Summary of the Invention

[0005] The embodiments of the present invention provide a user contact method and its device, program product, and electronic device to at least solve the technical problem of low efficiency in outbound call contact for users in related technologies.

[0006] According to one aspect of an embodiment of the present invention, a user reaching method is provided, comprising: in a case where it is detected that an outbound call is made to a target user in a target user list through a channel end, blocking the outbound call to the target user and calling a preset engine interface, wherein the target user is any user in the target user list; based on the preset engine interface, sending a user reaching request to the preset engine, wherein the preset engine generates a reaching result based on the user reaching request; in a case where the reaching result returned by the preset engine indicates a waiting-to-be-reached state, controlling the channel end to make an outbound call to the target user, wherein the waiting-to-be-reached state indicates continuing to make outbound calls to the target user; in a case where the reaching result returned by the preset engine indicates a reached state, deleting the target user from the target user list, wherein the reached state indicates stopping making outbound calls to the target user.

[0007] Furthermore, before sending the user contact request to the preset engine, it also includes: determining the contact rules of each outbound call strategy, wherein the outbound call strategy refers to the strategy for making outbound calls to the user; and storing the contact rules of each outbound call strategy in the preset engine.

[0008] Furthermore, the user contact request carries an outbound call strategy identifier and a target user identifier. After sending the user contact request to the preset engine, it also includes: controlling the preset engine to determine the target contact rules based on the outbound call strategy identifier; controlling the preset engine to generate a contact result based on the target contact rules and the target user identifier.

[0009] Furthermore, the step of controlling the preset engine to generate a reach result based on the target reach rule and the target user identifier includes: controlling the preset engine to obtain historical reach information of the target user identifier from the preset queue; and controlling the preset engine to generate a reach result based on the historical reach information and the target reach rule.

[0010] Furthermore, the step of controlling the preset engine to obtain historical reach information of the target user identifier from the preset queue includes: controlling the preset engine to obtain all outbound call information associated with the target user identifier from the preset queue; and controlling the preset engine to determine the historical reach information based on all outbound call information.

[0011] Furthermore, the step of controlling the preset engine to generate a reach result based on historical reach information and target reach rules includes: controlling the preset engine to determine the number of times the target user is called within a preset time period based on historical reach information; when the number is less than the preset number of reaches included in the target reach rule, determining that the reach result is in a waiting-to-be-reached state; when the number is greater than or equal to the preset number of reaches included in the target reach rule, determining that the reach result is in a reached state.

[0012] Furthermore, before controlling the preset engine to obtain the historical contact information of the target user identifier from the preset queue, it also includes: after making an outbound call to the user at any channel end, controlling the channel end to associate the user's user identifier with the outbound call information, and writing the outbound call information of the associated user identifier into the preset queue.

[0013] According to another aspect of an embodiment of the present invention, a user contact device is also provided, including: a blocking unit for blocking outbound calls to the target user and calling a preset engine interface when it is detected that an outbound call is made to a target user in a target user list through a channel end, wherein the target user is any user in the target user list; a sending unit for sending a user contact request to a preset engine based on the preset engine interface, wherein the preset engine generates a contact result based on the user contact request; an outbound call unit for controlling the channel end to make an outbound call to the target user when the contact result returned by the preset engine indicates a waiting-to-be-reached state, wherein the waiting-to-be-reached state indicates continuing to make outbound calls to the target user; a deleting unit for deleting the target user from the target user list when the contact result returned by the preset engine indicates a reached state, wherein the reached state indicates stopping making outbound calls to the target user.

[0014] Furthermore, the user contact device also includes: a first determination unit, used to determine the contact rules of each outbound call strategy before sending a user contact request to the preset engine, wherein the outbound call strategy refers to a strategy for making outbound calls to the user; a first storage unit, used to store the contact rules of each outbound call strategy to the preset engine.

[0015] Furthermore, the user contact device also includes: a second determination unit, which is used for the user contact request to carry an outbound call strategy identifier and a target user identifier, and after sending the user contact request to the preset engine, controls the preset engine to determine the target contact rules based on the outbound call strategy identifier; a first generation unit, which is used to control the preset engine to generate a contact result based on the target contact rules and the target user identifier.

[0016] Furthermore, the first generation unit includes: a first acquisition module, used to control the preset engine to obtain historical contact information of the target user identifier from the preset queue; a first generation module, used to control the preset engine to generate contact results based on the historical contact information and target contact rules.

[0017] Furthermore, the first acquisition module includes: a first acquisition submodule, used to control the preset engine to obtain all outbound call information associated with the target user identifier from the preset queue; and a first determination submodule, used to control the preset engine to determine historical reach information based on all outbound call information.

[0018] Furthermore, the first generation module includes: a second determination submodule, which is used to control the preset engine to determine the number of times the target user is called within a preset time period based on historical reach information; a third determination submodule, which is used to determine that the reach result is in a waiting-to-be-reached state when the number is less than the preset reach number included in the target reach rule; and a fourth determination submodule, which is used to determine that the reach result is in a reached state when the number is greater than or equal to the preset reach number included in the target reach rule.

[0019] Furthermore, the user contact device also includes: a first writing unit, which is used to control the channel end to associate the user's user identity with the outbound call information after making an outbound call to the user at any channel end before controlling the preset engine to obtain the historical contact information of the target user identifier from the preset queue, and write the outbound call information of the associated user identity into the preset queue.

[0020] According to another aspect of an embodiment of the present invention, a computer program product is also provided, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any one of the above-mentioned user access methods is implemented.

[0021] According to another aspect of an embodiment of the present invention, an electronic device is also provided, including one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by one or more processors, the one or more processors implement any one of the above-mentioned user access methods.

[0022] In the present invention, when it is detected that an outbound call is made to a target user in a target user list through a channel side, the outbound call to the target user is blocked, and a preset engine interface is called. Based on the preset engine interface, a user contact request is sent to the preset engine. When the contact result returned by the preset engine indicates a state to be contacted, the channel side is controlled to make an outbound call to the target user. When the contact result returned by the preset engine indicates a state to be contacted, the target user is deleted from the target user list, thereby solving the technical problem of low efficiency of outbound call contact to users in related technologies.

[0023] In the present invention, a real-time contact rule strategy is adopted to process the user contact request through a preset engine to obtain a contact result, so as to judge whether to make an outbound call to the user based on the contact result, thereby achieving the purpose of real-time monitoring and dynamic adjustment of the user's outbound call frequency, thereby realizing the technical effect of high-efficiency outbound call do not disturb requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0025] Figure 1 A hardware structure block diagram of a computer terminal (or mobile device) for implementing a user contact method is shown;

[0026] Figure 2 is a flowchart of a user contact method according to embodiment 1 of the present invention;

[0027] Figure 3 is a schematic diagram of an optional user access device according to an embodiment of the present invention;

[0028] Figure 4 is a structural block diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) collected and involved in the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse. For example, an interface is set up between this system and the relevant users or institutions. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or institution through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or institution.

[0032] In this invention, by introducing an intelligent engine, it can determine whether a user meets the reach strategy before reaching the user. By subscribing to the message queue, the intelligent engine can obtain outbound call events from various channels, thereby calculating the number of outbound calls received by each user to be reached. Then, based on the number of outbound calls received, it can determine whether the user meets the reach strategy. It can determine whether the user can make outbound calls in real time, avoiding unnecessary outbound calls, improving the user experience, optimizing outbound call efficiency, and ensuring the accurate execution and timely adjustment of outbound call strategies.

[0033] The present invention will be described in detail below with reference to various embodiments.

[0034] Example 1

[0035] According to an embodiment of the present application, an embodiment of a user access method is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0036] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG1 shows a hardware structure block diagram of a computer terminal (or mobile device) for implementing a user contact method. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more ( Figure 1 102a, 102b, ..., 102n are used to illustrate) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera, wherein the network interface may be connected to a wired and / or wireless network. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0037] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuitry may be a single independent processing module, or may be incorporated in whole or in part into any of the other components of the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuitry serves as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0038] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the user access method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, realizing the above-mentioned user access method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0039] The transmission device 106 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the communications provider of the computer terminal 10. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0040] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0041] Under the above operating environment, this application provides Figure 2 User reach methods shown. Figure 2 is a flow chart of a user contact method according to embodiment 1 of the present invention. Figure 2 As shown, the method includes the following steps:

[0042] Step S201 , when it is detected that an outbound call is made to a target user in the target user list through the channel end, the outbound call to the target user is blocked and a preset engine interface is called, wherein the target user is any user in the target user list.

[0043] In an embodiment of the present invention, when a reach channel (i.e., a channel end, such as an intelligent outbound calling system) initiates an outbound call to a user on the target user list based on an outbound calling strategy, a blocking mechanism is first triggered, pausing the outbound call. Subsequently, the reach channel automatically calls a pre-configured intelligent engine interface (i.e., a preset engine interface), passing it specific information, including but not limited to the target user ID and outbound calling strategy ID, to assess whether the user should be reached.

[0044] Step S202: Based on the preset engine interface, a user contact request is sent to the preset engine, wherein the preset engine generates a contact result based on the user contact request.

[0045] In this embodiment of the present invention, after invoking the intelligent engine interface, the reach channel can send a reach request containing the target user identifier and outbound call strategy identifier to the intelligent engine. After receiving the request, the intelligent engine can determine whether the target user can be reached based on the stored reach rules, thereby obtaining a reach result.

[0046] Step S203: When the reaching result returned by the preset engine indicates a waiting-to-be-reached state, the control channel end makes an outbound call to the target user, wherein the waiting-to-be-reached state indicates continuing to make an outbound call to the target user.

[0047] In this embodiment of the present invention, if the intelligent engine determines that the target user is in the "waiting to be reached" state, it indicates that according to the real-time reach rule strategy, outbound calls can continue to be made to the target user. Upon receiving this feedback, the reach channel will unblock the outbound call and continue executing the outbound call plan.

[0048] Step S204: When the reach result returned by the preset engine indicates a reached state, the target user is deleted from the target user list, wherein the reached state indicates stopping outbound calls to the target user.

[0049] In this embodiment of the present invention, if the intelligent engine determines that the target user is in the "reached state," it means that the reach limit for the target user has been reached and further reach attempts in the short term will not meet the requirements. In this case, the reach channel will not only not execute an outbound call to the user, but will also remove the user from the target user list to avoid subsequent repeated attempts until the reach conditions are met again, at which point the user will be added back to the list through the corresponding mechanism.

[0050] In summary, by adopting the real-time contact rule strategy, the user contact request is processed through the preset engine to obtain the contact result, and the decision of whether to make an outbound call to the user is made based on the contact result, thereby achieving the purpose of real-time monitoring and dynamic adjustment of the user's outbound call frequency, thereby achieving the technical effect of high-efficiency outbound call do-not-disturb requirements, and further solving the technical problem of low efficiency of outbound call contact to users in related technologies.

[0051] In order to facilitate the preset engine to generate the contact results, in the user contact method provided in Example 1 of the present application, before sending the user contact request to the preset engine, the contact rules of each outbound call strategy are determined, wherein the outbound call strategy refers to the strategy for making outbound calls to the user; the contact rules of each outbound call strategy are stored in the preset engine.

[0052] In an embodiment of the present invention, before starting an outbound calling campaign, various outbound calling strategies (i.e., strategies for making outbound calls to users) can be configured according to financial business needs. For example, an outbound calling strategy is set to require that all members of customer group A be reached every day through intelligent outbound calling within one month. Then, according to the purpose of each outbound calling strategy, contact rules are configured for each outbound calling strategy. For example, intelligent outbound calling channel A can reach users a maximum of 3 times within 7 days. In this way, it can be ensured that the outbound calling campaign meets business goals while taking into account user experience and avoiding excessive disturbances. Afterwards, after configuring the outbound calling strategy and its contact rules, the contact rules associated with each outbound calling strategy are stored in the preset engine.

[0053] Here, the preset engine is an intelligent processing system responsible for receiving user contact requests from contact channels, performing instant analysis and judgment based on stored contact rules, and generating contact results. For example, real-time anti-disturbance rules (i.e., contact rules) such as "If a user has received two outbound calls on channel A within 5 days, no more outbound calls will be allowed in the short term" or "If a user has been contacted by manual outbound calls within 2 days, they should not receive smart outbound calls again" can be stored in the preset engine.

[0054] This embodiment enables refined management and real-time execution of outbound call strategies. Business personnel can flexibly set reach rules, and the pre-set engine effectively transforms these rules into real-time control over outbound call activity. This allows reach channels to obtain the latest reach rule judgments before executing outbound calls, ensuring that outbound call activity adheres to business policies while dynamically adjusting to changing user behavior, maximizing customer satisfaction and outbound call efficiency.

[0055] Optionally, the user contact request carries an outbound call strategy identifier and a target user identifier. In order to improve the accuracy of generating the contact result, in the user contact method provided in Example 1 of the present application, after sending the user contact request to the preset engine, the preset engine is controlled to determine the target contact rule based on the outbound call strategy identifier; the preset engine is controlled to generate the contact result based on the target contact rule and the target user identifier.

[0056] In an embodiment of the present invention, when a reach channel (such as an intelligent outbound call system) prepares to make an outbound call, it sends a user reach request to the preset engine. The user reach request carries an outbound call strategy identifier and a target user identifier. After receiving the outbound call strategy identifier, the preset engine can match the outbound call strategy identifier with all stored strategy identifiers, obtain a matching outbound call strategy, and then determine the target reach rules under the strategy.

[0057] In this embodiment of the present invention, after determining the target reach rules, the preset engine will combine the target user ID and retrieve the user's historical reach records from the preset queue. The intelligent engine will analyze the historical reach records and the target reach rules to determine whether to continue reaching the user and obtain the reach result.

[0058] In this embodiment, personalized and intelligent management of outbound call activity is achieved by controlling the preset engine to determine target reach rules based on the outbound call strategy identifier and generating reach results based on the target user identifier. In this model, each outbound call request is judged in real time based on the most accurate strategy and user data, ensuring that the outbound call activity not only conforms to the preset business logic but also allows for timely adjustments based on the user's actual status and needs. This avoids excessive interruptions or missed calls to the target user, improving the customer experience and outbound call efficiency.

[0059] In order to further improve the accuracy of generating contact results, in the user contact method provided in Example 1 of the present application, the preset engine is controlled to obtain historical contact information of the target user identifier from the preset queue; the preset engine is controlled to generate contact results based on the historical contact information and the target contact rules.

[0060] In an embodiment of the present invention, before the intelligent outbound calling system prepares to reach a specific user (target user), the preset engine proactively retrieves the user's historical reach records from a preset message queue. This queue stores information on all user reach events, including reach time, reach channel, and other data. For example, when preparing to call a user, the preset engine examines the number of times the user has been reached via intelligent outbound calling or other channels in the past week, as well as the details of each reach. After collecting the target user's historical reach information, the preset engine immediately applies targeted reach rules to analyze this information. Target reach rules may include specific instructions such as "avoiding repeated reach of the same user in the short term" or "setting reach intervals for different channels." For example, if the rule is set to "reach the same user a maximum of once per week via intelligent outbound calling," and the preset engine detects that the user has already been reached once via intelligent outbound calling this week, it will generate a reach result of "reached," indicating that the user should not be called again. If the user has not been reached via intelligent outbound calling this week, it will generate a reach result of "pending reach," allowing the outbound call to continue.

[0061] In this embodiment, it is possible to ensure that each outbound call is based on a comprehensive consideration of sufficient historical data and current strategies, avoiding customer disgust and resource waste that may result from blind outbound calls. At the same time, with the support of message queue technology, the outbound decision-making process becomes real-time and efficient, improving the accuracy of outbound calls and user experience, and reducing outbound call costs.

[0062] In order to improve the accuracy of determining historical reach information, in the user reach method provided in Example 1 of the present application, the preset engine is controlled to obtain all outbound call information associated with the target user identifier from the preset queue; the preset engine is controlled to determine the historical reach information based on all outbound call information.

[0063] In an embodiment of the present invention, when the intelligent outbound call system is preparing to call a specific user (i.e., the target user), the preset engine will retrieve all historical outbound call records related to the user ID from the preset message queue. These records contain detailed information about each past outbound call, such as the date and time of the outbound call, the channel through which the outbound call was made, the content of the outbound call, and the results of the outbound call. After obtaining all the outbound call information associated with the target user ID, the preset engine can integrate this information to extract relevant historical contact information. For example, calculate the total number of times the target user has been contacted within a specific period of time in the past, identify which contacts were made through intelligent outbound calls, and the time of the most recent contact, etc.

[0064] In this embodiment, by using a preset queue to store and access outbound call information, the consistency and integrity of the data can be ensured, thereby achieving efficient support for outbound call decision-making.

[0065] In order to further accurately determine the reach result, in the user reach method provided in Example 1 of the present application, the preset engine is controlled to determine the number of times the target user is called within a preset time period based on historical reach information; when the number is less than the preset reach number included in the target reach rule, the reach result is determined to be in a waiting-to-reach state; when the number is greater than or equal to the preset reach number included in the target reach rule, the reach result is determined to be in a reached state.

[0066] In an embodiment of the present invention, a preset engine can calculate the total number of outbound calls made to a target user within a set time window (e.g., the past week, the past month, etc.) based on historical reach information. This calculation process relies on outbound call records obtained from a preset queue, each of which details the time, channel, and result of the outbound call. For example, if the target reach rule stipulates that "any user should not be reached by smart outbound calls more than three times in the past week," the preset engine will count the user's outbound call records in the past week. If the number of outbound calls made by the target user within the preset time period calculated by the preset engine is lower than the preset number of reaches included in the target reach rule, the engine will generate a reach result in the "waiting to be reached state," indicating that the target user is currently available for more reaches. If the preset engine finds that the number of outbound calls made by the target user within the preset time period has reached or exceeded the preset number of reaches, the engine will generate a reach result in the "reached state," indicating that the target user should no longer be reached. In this way, users can be protected from unnecessary frequent reaches and a good customer experience can be maintained.

[0067] In this embodiment, the preset engine can monitor and calculate the frequency of target user reach within a preset timeframe in real time, ensuring that each reach action is within a reasonable range, neither too frequent nor missing potential reach opportunities. This not only improves customer satisfaction and reduces customer annoyance caused by excessive outbound calls, but also optimizes the financial institution's resource allocation and avoids increased outbound call costs. Furthermore, with the help of historical reach information in the preset queue, the entire reach decision-making process becomes more transparent and controllable, enabling better monitoring and adjustment of reach strategies to respond to market changes and customer needs.

[0068] In order to facilitate the preset engine to obtain outbound call information from each channel end, in the user contact method provided in Example 1 of the present application, before controlling the preset engine to obtain the historical contact information of the target user identifier from the preset queue, after making an outbound call to the user at any channel end, the channel end is controlled to associate the user identifier with the outbound call information, and write the outbound call information of the associated user identifier into the preset queue.

[0069] In an embodiment of the present invention, after a user is contacted by any channel end (such as an intelligent outbound call system or a manual outbound call system), the channel end will associate the relevant information of this outbound call, including but not limited to: the time of the outbound call, the channel type, the outbound call result, etc., with the unique identifier of the user (user identifier). For example, if an outbound call to user A is completed through the intelligent outbound call system, the intelligent outbound call system will create an outbound call record, which clearly indicates information such as "outbound call time: 14:30, March 28, 2023", "channel type: intelligent outbound call system", "outbound call result: call successful", and attach the user identifier of user A.

[0070] In this embodiment of the present invention, once an association between outbound call information and a user ID is established, the channel side immediately pushes this information to a pre-set queue. The pre-set queue acts as a data transfer station, responsible for storing and transmitting all outbound call information generated by the channel side. This allows outbound call information to be delivered to the pre-set engine in real time. The pre-set engine obtains this information by subscribing to the pre-set queue, thereby updating the user's reach status in real time and providing the latest and most comprehensive data for subsequent reach decisions.

[0071] In this embodiment, after each successful outbound call, the user's ID's outbound call information is immediately recorded and associated with a pre-set queue, ensuring that the intelligent engine can obtain the latest user reach information in real time. This improves the real-time and consistency of data, avoids the delays and errors of manually updating reach records, and thus enhances the accuracy and timeliness of reach decisions.

[0072] The user contact method provided in the embodiment of the present application processes the user contact request through a preset engine to obtain a contact result, and determines whether to make an outbound call to the user based on the contact result, thereby achieving the purpose of real-time monitoring and dynamic adjustment of the user's outbound call frequency, thereby achieving the technical effect of high-efficiency outbound call do-not-disturb requirements, and further solving the technical problem of low efficiency of outbound call contact to users in related technologies.

[0073] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0074] Example 2

[0075] The embodiment of the present application also provides a user contact device. It should be noted that the user contact device of the embodiment of the present application can be used to execute the user contact method provided by the embodiment of the present application. The user contact device provided by the embodiment of the present application is introduced below.

[0076] According to an embodiment of the present application, a device for implementing the above-mentioned user contact method is also provided. Figure 3 is a schematic diagram of an optional user access device according to an embodiment of the present invention, such as Figure 3 As shown, the user access device may include: a blocking unit 30, a sending unit 31, an outbound call unit 32, and a deletion unit 33.

[0077] The blocking unit 30 is configured to block the outbound call to the target user and call the preset engine interface when detecting an outbound call to a target user in the target user list through the channel end, wherein the target user is any user in the target user list;

[0078] The sending unit 31 is configured to send a user contact request to the preset engine based on the preset engine interface, wherein the preset engine generates a contact result based on the user contact request;

[0079] The outbound calling unit 32 is configured to control the channel end to make an outbound call to the target user when the reach result returned by the preset engine indicates a pending reach state, wherein the pending reach state indicates that the outbound call to the target user continues;

[0080] The deleting unit 33 is used to delete the target user from the target user list when the reach result returned by the preset engine indicates a reached state, wherein the reached state indicates stopping outbound calls to the target user.

[0081] The user contact device provided in the embodiment of the present application processes the user contact request through a preset engine to obtain a contact result, and determines whether to make an outbound call to the user based on the contact result, thereby achieving the purpose of real-time monitoring and dynamic adjustment of the user's outbound call frequency, thereby achieving the technical effect of high-efficiency outbound call do-not-disturb requirements, and further solving the technical problem of low efficiency of outbound call contact to users in related technologies.

[0082] Optionally, the user contact device also includes: a first determination unit, used to determine the contact rules of each outbound call strategy before sending a user contact request to the preset engine, wherein the outbound call strategy refers to a strategy for making outbound calls to the user; a first storage unit, used to store the contact rules of each outbound call strategy to the preset engine.

[0083] Optionally, the user contact device also includes: a second determination unit, which is used for the user contact request to carry an outbound call strategy identifier and a target user identifier, and after sending the user contact request to the preset engine, controls the preset engine to determine the target contact rules based on the outbound call strategy identifier; a first generation unit, which is used to control the preset engine to generate a contact result based on the target contact rules and the target user identifier.

[0084] Optionally, the first generation unit includes: a first acquisition module, used to control the preset engine to obtain historical contact information of the target user identifier from the preset queue; a first generation module, used to control the preset engine to generate contact results based on the historical contact information and target contact rules.

[0085] Optionally, the first acquisition module includes: a first acquisition submodule, used to control the preset engine to obtain all outbound call information associated with the target user identifier from the preset queue; and a first determination submodule, used to control the preset engine to determine historical reach information based on all outbound call information.

[0086] Optionally, the first generation module includes: a second determination submodule, used to control the preset engine to determine the number of times the target user is called within a preset time period based on historical reach information; a third determination submodule, used to determine that the reach result is in a waiting-to-be-reached state when the number is less than the preset reach number included in the target reach rule; and a fourth determination submodule, used to determine that the reach result is in a reached state when the number is greater than or equal to the preset reach number included in the target reach rule.

[0087] Optionally, the user contact device also includes: a first writing unit, which is used to control the channel end to associate the user's user identity with the outbound call information after making an outbound call to the user at any channel end before controlling the preset engine to obtain the historical contact information of the target user identifier from the preset queue, and write the outbound call information of the associated user identity into the preset queue.

[0088] The above-mentioned user access device may also include a processor and a memory. The above-mentioned blocking unit 30, sending unit 31, outbound call unit 32, deletion unit 33, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize the corresponding functions.

[0089] The processor includes a kernel that retrieves the corresponding program unit from the memory. The kernel can be configured with one or more kernel parameters, and can be configured to remove a target user from the target user list when the reach result returned by the preset engine indicates that the target user has been reached.

[0090] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0091] It should be noted that the blocking unit 30, sending unit 31, outbound call unit 32, and deletion unit 33 correspond to steps S201 to S204 in Example 1. The examples and application scenarios implemented by the above units and the corresponding steps are the same, but are not limited to the contents disclosed in Example 1. It should be noted that the above units can be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n). The above units can also be part of the device and can be run in the computer terminal 10 provided in Example 1.

[0092] Example 3

[0093] An embodiment of the present application may provide an electronic device, Figure 4 1 is a structural block diagram of an electronic device according to an embodiment of the present invention. Figure 4 As shown, the electronic device may include: one or more ( Figure 4 Only one is shown) processor 402, memory 404, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0094] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the user access method and device in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned user access method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely located relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include but are not limited to the Internet, corporate intranet, local area network, mobile communication network and combinations thereof.

[0095] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: when it is detected that an outbound call is made to the target user in the target user list through the channel end, the outbound call to the target user is blocked, and the preset engine interface is called, wherein the target user is any user in the target user list; based on the preset engine interface, a user contact request is sent to the preset engine, wherein the preset engine generates a contact result based on the user contact request; when the contact result returned by the preset engine indicates a waiting-to-be-reached state, the channel end is controlled to make an outbound call to the target user, wherein the waiting-to-be-reached state indicates continuing to make outbound calls to the target user; when the contact result returned by the preset engine indicates a reached state, the target user is deleted from the target user list, wherein the reached state indicates stopping making outbound calls to the target user.

[0096] The processor can call the information and applications stored in the memory through the transmission device to perform the following steps: determine the contact rules for each outbound call strategy, where the outbound call strategy refers to the strategy for making outbound calls to users; store the contact rules for each outbound call strategy in the preset engine.

[0097] The processor can call the information and applications stored in the memory through the transmission device to perform the following steps: control the preset engine to determine the target contact rules based on the outbound call strategy identifier; control the preset engine to generate the contact results based on the target contact rules and the target user identifier.

[0098] The processor can call the information and applications stored in the memory through the transmission device to perform the following steps: control the preset engine to obtain the historical contact information of the target user identifier from the preset queue; control the preset engine to generate the contact result based on the historical contact information and the target contact rules.

[0099] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: control the preset engine to obtain all outbound call information associated with the target user identifier from the preset queue; control the preset engine to determine the historical reach information based on all outbound call information.

[0100] The processor can call the information and applications stored in the memory through the transmission device to perform the following steps: control the preset engine to determine the number of times the target user is called within a preset time period based on historical contact information; when the number is less than the preset number of contacts included in the target contact rule, determine that the contact result is in the waiting to be reached state; when the number is greater than or equal to the preset number of contacts included in the target contact rule, determine that the contact result is in the reached state.

[0101] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: after making an outbound call to the user at any channel end, control the channel end to associate the user's user ID with the outbound call information, and write the outbound call information of the associated user ID into the preset queue.

[0102] The embodiments of the present application provide a user contact solution. A preset engine processes user contact requests to obtain contact results, which are then used to determine whether to place an outbound call to the user. This achieves the goal of real-time monitoring and dynamic adjustment of the user's outbound call frequency, thereby achieving the technical effect of high-efficiency outbound call do-not-disturb requirements and resolving the technical problem of low efficiency in outbound call contact for users in related technologies.

[0103] It can be understood by those skilled in the art that Figure 4 The structure shown is for illustration only, and the electronic device may also be a terminal device such as a smart phone, a tablet computer, a PDA, or a mobile Internet device (MID). Figure 4 It does not limit the structure of the above electronic device. For example, the electronic device may also include Figure 4 More or fewer components (such as network interfaces, display devices, etc.) shown in, or with Figure 4 Different configurations shown.

[0104] A person skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0105] Example 4

[0106] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the user contact method provided in the first embodiment.

[0107] Optionally, in this embodiment, the storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0108] The present application also provides a computer program product which, when executed on a data processing device, is suitable for executing the steps of the user access method.

[0109] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0110] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0111] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0112] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0113] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0114] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0115] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A user contact method, characterized in that: include: When an outbound call is detected to a target user in the target user list through the channel end, the outbound call to the target user is blocked and a preset engine interface is called, wherein the target user is any user in the target user list; Based on the preset engine interface, sending a user contact request to the preset engine, wherein the preset engine generates a contact result based on the user contact request; When the reach result returned by the preset engine indicates a pending reach state, controlling the channel end to make an outbound call to the target user, wherein the pending reach state indicates continuing to make an outbound call to the target user; In a case where the reach result returned by the preset engine indicates a reached state, the target user is deleted from the target user list, wherein the reached state indicates stopping outbound calls to the target user.

2. The user contact method according to claim 1, characterized in that: Before sending the user contact request to the preset engine, it also includes: Determine the reach rules for each outbound calling strategy, wherein the outbound calling strategy refers to the strategy for making outbound calls to the user; The reaching rules of each outbound calling strategy are stored in the preset engine.

3. The user contact method according to claim 2, characterized in that: The user contact request carries an outbound call strategy identifier and a target user identifier. After sending the user contact request to the preset engine, the method further includes: Controlling the preset engine to determine a target contact rule based on the outbound call strategy identifier; Control the preset engine to generate the reaching result based on the target reaching rule and the target user identifier.

4. The user contact method according to claim 3, characterized in that: The step of controlling the preset engine to generate the reaching result based on the target reaching rule and the target user identifier includes: Control the preset engine to obtain historical contact information of the target user identifier from a preset queue; Control the preset engine to generate the reach result based on the historical reach information and the target reach rule.

5. The user contact method according to claim 4, characterized in that: The step of controlling the preset engine to obtain historical contact information of the target user identifier from a preset queue includes: Controlling the preset engine to obtain all outbound call information associated with the target user identifier from the preset queue; Control the preset engine to determine the historical reach information based on all the outbound call information.

6. The user contact method according to claim 4, characterized in that: The step of controlling the preset engine to generate the reach result based on the historical reach information and the target reach rule includes: Controlling the preset engine to determine the number of outbound calls to the target user within a preset time period based on the historical reach information; When the number of times is less than the preset number of times of touch included in the target touch rule, determining that the touch result is the waiting-to-touch state; When the number is greater than or equal to the preset number of touches included in the target touch rule, it is determined that the touch result is the touched state.

7. The user contact method according to claim 4, characterized in that: Before controlling the preset engine to obtain the historical contact information of the target user identifier from the preset queue, the method further includes: After an outbound call is made to a user at any channel end, the channel end is controlled to associate the user ID of the user with the outbound call information, and write the outbound call information associated with the user ID into the preset queue.

8. A user contact device, characterized in that: include: a blocking unit configured to, upon detecting an outbound call to a target user in the target user list through a channel end, block the outbound call to the target user and call a preset engine interface, wherein the target user is any user in the target user list; A sending unit, configured to send a user contact request to a preset engine based on the preset engine interface, wherein the preset engine generates a contact result based on the user contact request; An outbound calling unit, configured to control the channel end to make an outbound call to the target user if the reach result returned by the preset engine indicates a pending reach state, wherein the pending reach state indicates continuing to make an outbound call to the target user; A deleting unit is used to delete the target user from the target user list when the reach result returned by the preset engine indicates a reached state, wherein the reached state indicates stopping outbound calls to the target user.

9. A computer program product, characterized in that It includes a non-volatile computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, it implements the user contact method described in any one of claims 1 to 7.

10. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the user contact method described in any one of claims 1 to 7.

Images