Process canvas management system and method

Abstract

The invention discloses a process canvas management system and method, and relates to the technical field of data processing, the system comprises a process entry module, an execution unit module and a multi-channel touch module; the flow entering module is used for transferring user flow details into a flow canvas when a behavior event of a stock user triggers a touch task type; the execution unit module is used for transferring the user flow details into the multi-channel touch module according to a shunting delay strategy; the multi-channel touch module is used for carrying out resource distribution on stock users according to user flow details; and the execution unit module is also used for transferring the stock user completing resource distribution out of the process canvas. Through the process canvas management system, various behavior events of the stock user can be accurately responded, the situation that various activities in a data processing mode of the current stock user are disordered and isolated, and user interaction feedback is ignored is avoided, and therefore the stock user data can be effectively touched, and the user experience is improved. And automatic touch and quick response of stock users are realized.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a process canvas management system and method. Background Art

[0002] With the rapid development of network technology, more and more computer technologies are being applied in the financial field, and the traditional financial industry is gradually transforming to financial technology. The threshold for financial services is high, and online business consultation is also very extensive, involving aspects such as credit card repayment, loan processing, and fund management. However, in the current highly competitive consumer finance market, there is a significant gap in user scale and asset scale with the industry's leading institutions, and the gap has a tendency to widen. In addition, there is a situation where the market is gradually saturated, the growth of new users is slowing down, and product homogeneity is serious. Therefore, data processing of existing users is the current focus, and the main problems it faces are as follows: 1. The contradiction between customer needs and the data processing strategy for existing users. First, there is a lack of clear customer stratification and strategy coordination, and second, there is a mismatch between products and customer groups.

[0003] 2. The contradiction between the fragmentation of scenarios and insufficient data insight capabilities. First, the data processing scenarios of existing users are fragmented and scattered, and there is a lack of a complete data processing strategy for existing users throughout the customer life cycle. Second, data is scattered and a global perspective is missing. Customer data, risk data, behavioral data, etc. are scattered in various business systems and lack a unified indicator caliber.

[0004] 3. The contradiction between limited resources and strategy segmentation. First, the degree of automation is low. The automation degree of the data processing strategy for existing users is not high, which makes it difficult to meet the complex and personalized data processing needs of existing users, resulting in low efficiency in data processing for existing users. Second, the data link is not smooth. The data link of the entire process of data processing for existing users is not smooth, and the activity or strategy data is scattered. Third, the level of intelligence needs to be improved. The current strategy design and deployment mainly rely on manual experience, and the application of intelligent data processing tools for existing users is insufficient.

[0005] Therefore, in the current data processing method for existing users, various activities are messy and isolated, ignoring the interactive feedback of users, resulting in a mismatch between user needs and the data processing strategy for existing users, resulting in low data processing efficiency and affecting user satisfaction. How to effectively process the data of existing users is an urgent problem to be solved. Summary of the invention

[0006] The main purpose of this application is to provide a process canvas management system and method, which aims to solve the technical problem that in the current data processing method of existing users, various activities are messy and isolated, and user interaction feedback is ignored, resulting in a mismatch between user needs and the data processing strategy of existing users, leading to low data processing efficiency.

[0007] To achieve the above objectives, the present application proposes a process canvas management system, the system comprising: a process entry module, an execution unit module and a multi-channel access module; The process entry module is used to transfer the user flow details of the existing user into the process canvas when the behavior event of the existing user triggers the preset contact task type. The process canvas is used to perform periodic operations on the existing user; The execution unit module is used to transfer the user flow details transferred into the process canvas into the multi-channel contact module according to the preset diversion delay strategy; The multi-channel reaching module is used to distribute resources to the existing users according to the user flow details; The execution unit module is also used to transfer the existing users to which resource allocation has been completed out of the process canvas.

[0008] In one embodiment, the process entry module is also used to determine whether the behavior event of the existing user triggers a preset reach task type, and the reach task type includes a timed task and a triggered task; The process entry module is also used to determine whether the existing user belongs to the audience user group when the behavior event triggers the scheduled task or the triggered task; The process entry module is also used to transfer the user flow details of the existing users into the process canvas according to the preset hit rules when the existing users belong to the audience user group.

[0009] In one embodiment, the process entry module is further used to treat the existing user as a planned inflow user when the existing user belongs to the audience user group; The process entry module is also used to intercept the planned inflow users according to preset hit rules, and the hit rules include non-operational interception, risk control rule interception and priority occupation interception; The process entry module is also used to treat the planned inflow users that are not intercepted as actual inflow users, and transfer the user flow data of the actual inflow users into the process canvas.

[0010] In one embodiment, the execution unit module includes a diverter and a policy device; The diverter is used to perform scenario diversion on the user flow details flowing into the process canvas, and transfer the diverted user flow details to the policy device; The policy device is used to filter the user flow details after the diversion; The policy device is also used to determine whether the user flow details that have passed the screening meet the reward distribution conditions or reach conditions; The strategist is also used to transfer the user flow details that meet the reward distribution conditions or the reach conditions to the multi-channel reach module.

[0011] In one embodiment, the execution unit module further includes a delay device; The policy device is further used to mark the event of the user flow details after the diversion, and determine whether the marked user flow details are set with a delay condition; The policy device is further used to transfer the user flow details with delay conditions set to the delay device; The delayer is used to delay the incoming user flow details and transfer the corresponding user flow details to the policy device when the delay ends; The policy device is also used to determine whether the user flow details that end with the delay meet the reward distribution conditions or reach conditions.

[0012] In one embodiment, the multi-channel reaching module is further used to determine again whether the incoming user flow details meet the hit rule; The multi-channel reaching module is further used to distribute rewards to the user flow details corresponding to the user flow details that do not meet the hit rules if the hit rules are not met; The multi-channel reaching module is also used to determine whether the user to be operated corresponding to the user flow details is a reached user when the reward distribution fails; The multi-channel reaching module is also used to provide communication reminders to the reached user if the user is the reached user.

[0013] In one embodiment, the multi-channel contact module is further used to determine whether the user flow details corresponding to the user flow details that do not meet the hit rule are set with reward distribution conditions when the transferred user flow details do not meet the hit rule; The multi-channel reaching module is further used to distribute rewards to the corresponding user flow details if the reward distribution conditions are set; The multi-channel access module is also used to determine whether the reward distribution is successful; The multi-channel contact module is also used to transfer the existing users corresponding to the failed reward distribution out of the process canvas when the reward distribution fails.

[0014] In addition, to achieve the above purpose, the present application also proposes a process canvas management method, which is applied to a process canvas management system, the system including a process entry module, an execution unit module and a multi-channel access module; the method includes: When a behavior event of an existing user triggers a preset reaching task type, the process entry module transfers the user flow details of the existing user into a process canvas, and the process canvas is used to perform periodic operations on the existing user; The execution unit module transfers the user flow details entered into the process canvas into the multi-channel access module according to the preset diversion delay strategy; The multi-channel reaching module distributes resources to the existing users according to the user flow details; The execution unit module transfers the existing users to which resource allocation has been completed out of the process canvas.

[0015] In one embodiment, when a behavior event of an existing user triggers a preset reach task type, the process entry module transfers the user flow details of the existing user into the process canvas, including: The process enters a module to determine whether the behavior event of the existing user triggers a preset reach task type, and the reach task type includes a timed task and a triggered task; The process entry module determines whether the existing user belongs to the audience user group when the behavior event triggers the scheduled task or the triggered task; When the existing user belongs to the audience user group, the process entry module transfers the user flow details of the existing user into the process canvas according to the preset hit rule.

[0016] In one embodiment, when the existing user belongs to the audience user group, the process entry module transfers the user flow details of the existing user into the process canvas according to a preset hit rule, including: The process entry module regards the existing user as a planned inflow user when the existing user belongs to the audience user group; The process enters the module preset hit rules to intercept the planned inflow users, and the hit rules include non-operational interception, risk control rule interception and priority occupation interception; The process entry module regards the planned inbound users that are not intercepted as actual inbound users, and transfers the user flow data of the actual inbound users into the process canvas.

[0017] One or more technical solutions proposed in the present application have at least the following technical effects: The present application proposes a process canvas management system, the system comprising: a process entry module, an execution unit module and a multi-channel contact module; the process entry module is used to transfer the user flow details of the existing user into the process canvas when the behavior event of the existing user triggers a preset contact task type, and the process canvas is used to perform periodic operations on the existing users; the execution unit module is used to transfer the user flow details transferred into the process canvas into the multi-channel contact module according to a preset diversion delay strategy; the multi-channel contact module is used to distribute resources to the existing users according to the user flow details; the execution unit module is also used to transfer the existing users who have completed resource distribution out of the process canvas.

[0018] Since this application constructs a process canvas management system, the behavioral events of existing users are triggered and transferred to the process canvas through the process entry module, and then diverted to the multi-channel contact module based on the execution unit module to distribute resources to existing users, so as to accurately respond to various behavioral events of existing users, avoiding the current data processing method of existing users, in which various activities are messy and isolated, and the interactive feedback of users is ignored, so that the data of existing users of different user groups can be effectively reached, ensuring the systematic and efficient data processing of existing users, and realizing automatic contact and rapid response of operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0021] Figure 1 Functional module diagram provided for the first embodiment of the application process canvas management system; Figure 2 A schematic diagram of the configuration steps of the process canvas provided in Example 1 of the present application; Figure 3 A logical diagram of a process entry module provided in Example 1 of the present application; Figure 4 A logical schematic diagram of a multi-channel access module provided in Example 1 of the present application; Figure 5 Functional module diagram provided for the second embodiment of the application process canvas management system; Figure 6 A logical schematic diagram of an execution unit module provided in Embodiment 2 of the present application; Figure 7 A schematic diagram of a data flow dashboard of an execution unit module provided in Embodiment 2 of the present application; Figure 8 A scenario flow chart for implementing data processing of existing users through a process canvas management system provided in Example 2 of the present application; Fig. 9 A flowchart diagram is provided for the first embodiment of the application process canvas management method.

[0022] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0023] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0024] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0025] In order to solve the above problems, this application has built a systematic, automated and intelligent process canvas management system, which deeply integrates multiple key links such as strategy management, strategy design and effect evaluation, so as to accurately respond to diversified business needs and provide customized existing user data processing services for different customer groups. Similarly, the system can accurately design and implement existing user data processing strategies for different customer groups based on diversified business scenarios, and realize a complete and coherent business process management closed loop from initial strategy conception, detailed design, internal approval, actual implementation to final effect feedback, ensuring the systematicness and efficiency of existing user data processing activities. Thereby improving the automation and intelligence level of existing user data processing, so as to realize the in-depth operation and refined management of existing customers.

[0026] Based on this, the embodiment of the present application provides a process canvas management system, referring to Figure 1 , Figure 1 This is a functional module diagram provided for the first embodiment of the application process canvas management system.

[0027] In this embodiment, the process canvas management system includes: a process entry module 10, an execution unit module 20 and a multi-channel access module 30.

[0028] It should be noted that the process canvas management system in this embodiment follows the closed-loop process of "strategy formulation-process design-resource allocation-strategy execution-effect evaluation". Figure 2 As shown, Figure 2 Schematic diagram of the configuration steps of the process canvas provided in Example 1 of this application. The operator can first formulate the existing user data processing strategy in the process canvas management system, and then import it into the process canvas for visual design. The process canvas management system automatically executes tasks through the process entry module, execution unit module, and multi-channel access module according to the designed process and allocated resources, and collects user feedback and existing user data for effect data analysis.

[0029] Before the process canvas management system automatically executes tasks, you need to create a process canvas, set up execution units, etc. When configuring the task start time, you need to determine when to start executing the existing user data processing strategy; when configuring the target users, you need to clarify the user group of the strategy; finally, when configuring the existing user data processing channel, you need to select which channels to promote and execute the strategy. Through these steps, the process canvas management system can configure different existing user data processing strategies according to different existing user data processing scenarios to achieve the existing user data processing goals.

[0030] The process entry module 10 is used to transfer the user flow details of the existing users into the process canvas when the behavioral events of the existing users trigger the preset contact task type. The process canvas is used to perform periodic operations on the existing users.

[0031] It should be noted that existing users (i.e. customers) can be existing customer groups in the financial field. At this time, as existing users, they need to be operated through various strategies to maintain and further tap the value of existing customers.

[0032] Among them, the behavior events can be various behaviors of existing users in the financial field, such as user login behavior, browsing specific pages or content, and behavior showing attention or interest in certain products or services. The touch task type can be a task category pre-set in the process entry module to screen whether existing users perform data processing on the process canvas. For example, specific task items can be set, and timed task items can also be set, which is not limited in this embodiment.

[0033] It is understandable that the user flow details may be information that records in detail the various steps and behaviors that the existing users go through in the business process.

[0034] It should be understood that the process canvas can be the core of the process canvas management system of this embodiment, and a series of logically related data processing activities can be combined in a visual design manner to form a complete data processing process. Through operations such as dragging and connecting, the position and role of each activity in the process can be intuitively seen, thereby ensuring the coherence and effectiveness of the data processing activities.

[0035] In this implementation, the prerequisites for triggering existing users to enter the process canvas (i.e., the type of access task) can be clearly defined in the process entry module. These conditions may be based on the user's behavioral events, the real-time status of the system, or specific events in the external environment to ensure that the user is guided to the corresponding process in the process canvas at the most appropriate time. When the behavioral events of existing users trigger the access task type, it means that the existing users need to process data through policies. At this time, the process entry module obtains the user flow details of the existing users and transfers the nodes of the existing users to the process canvas for processing.

[0036] In a feasible implementation manner, the process entry module 10 described in this embodiment is also used to determine whether the behavioral event of the existing user triggers a preset reach task type, and the reach task type includes a scheduled task and a triggered task; the process entry module 10 is also used to determine whether the existing user belongs to the audience user group when the behavioral event triggers the scheduled task or the triggered task; the process entry module 10 is also used to transfer the user flow details of the existing user into the process canvas according to the preset hit rule when the existing user belongs to the audience user group.

[0037] It should be noted that if Figure 2As shown, when setting and selecting the type of reach task, it can include timed tasks (i.e. reaching the trigger event) and triggered tasks (i.e. triggering according to the configured event), and the entry time and entry restrictions can be set. Among them, timed tasks can include timed-single and timed-repeated, and triggered tasks can include trigger-complete A and trigger-complete A but not complete B. Timed-single type can be used to create a single-execution process, and existing users enter the process canvas at a fixed time. Timed-repeated type can be used to create a repetitive process, and existing users enter the process canvas at one or more fixed times in each cycle, such as 10 o'clock every day in March, 16 o'clock every Friday in April, etc. Triggered-completed A type can be when the existing user completes a certain behavior to trigger the process (which can be done immediately or delayed), such as the user completing the post collection, like, and forwarding behavior to trigger the points arrival reminder. Within the effective time of the task, multiple process triggers can be achieved by meeting the trigger conditions. Trigger type - Complete A but not complete B type, which can be used to create triggered tasks. When the user completes a certain behavior A but does not complete another behavior B within a period of time, the process is triggered. For example, if the page is not visited within 20 minutes after starting the application, the process execution is triggered. It is usually used for breakpoint data processing.

[0038] It is understandable that audience user segmentation can be to divide existing users into different groups based on their characteristics, behaviors, preferences and other factors, which can be used to determine whether existing users entering the process canvas are in the audience user segmentation.

[0039] For ease of understanding, Figure 2 As shown, when choosing to set audience users, audience user attributes can support three configuration methods: label and behavior selection, existing grouping, and no restrictions. Different trigger conditions are coupled with audience user selection methods. Among them, label and behavior selection can be combined and selected through labels, attributes, grouping packages, detailed data, and behavior data. For existing groups, this function can be used to directly select the group that has been selected and use it directly. No restrictions are divided into two categories. When the trigger-type canvas is configured with no restrictions, it means that after the existing users trigger the event, the audience user filtering will no longer be performed, and all users who meet the event conditions will flow downward; when the timed canvas is configured with no restrictions, the canvas's contact method and distribution rights will be restricted, and only the selection of activity landing pages and configuration operations related to ad positions are allowed.

[0040] It should be understood that the hit rule can be a rule set to intercept existing users and temporarily prevent them from entering the process canvas. For example, when an existing user has a risk control risk, the hit rule is met, and the existing user cannot enter the process canvas; or when a certain existing user has a lower priority than other existing users, the existing user cannot enter the process canvas and needs to wait to enter; it can also be other hit rules, which are not limited in this embodiment.

[0041] In this implementation, the process entry module has pre-defined and clearly defined the types of tasks that trigger users to enter the process, and has divided the tasks into priority levels based on the importance of business goals, the urgency of user needs, and the availability of system resources, ensuring that key tasks are given priority, thereby maximizing the overall benefits of the process and user satisfaction. Figure 3 As shown, Figure 3 A logical diagram of the process entry module provided for Example 1 of the present application. When the behavioral event of an existing user triggers the above-mentioned contact task type, determine whether the existing user meets the entry conditions (for example, whether it belongs to the above-mentioned audience user group); if the existing user does not meet the entry conditions, the customer is treated as not flowing into the canvas. If the existing user meets the entry conditions, the customer is treated as flowing into the canvas. At this time, the existing users can be intercepted according to the above-mentioned hit rules to ensure that existing users with risk control risks or low priority are temporarily suspended from entering the process canvas. The remaining existing users who have not been intercepted can enter the process canvas. At this time, the user flow details of the user are obtained, and the user's node is transferred to the process canvas for processing. Through the above design, the process canvas can optimize customer flow and data flow, achieve business goals, and improve user experience.

[0042] In a feasible implementation manner, the process entry module 10 described in this embodiment is also used to treat the existing users as planned incoming users when the existing users belong to the audience user group; the process entry module 10 is also used to intercept the planned incoming users according to preset hit rules, and the hit rules include non-operational interception, risk control rule interception and priority occupation interception; the process entry module 10 is also used to treat the planned incoming users who are not intercepted as actual incoming users, and transfer the user flow data of the actual incoming users into the process canvas.

[0043] It should be noted that the planned inflow users can be the users who are planned to flow into the process canvas when the entry conditions (i.e., the task type) are met. The actual inflow users are the users who do not meet the hit rules and actually flow into the process canvas.

[0044] Among them, considering the logic and efficiency of the process canvas management system in processing tasks, the importance of tasks can be distinguished based on the importance of business goals, the urgency of user needs, and the availability of system resources, and the task priorities can be scientifically divided (priority occupation interception) to ensure that key tasks are given priority, thereby maximizing the overall benefits of the process and user satisfaction. At the same time, considering the risk control rules and standards, existing users who have potential risks or do not meet the requirements of the rules can be blocked or restricted (i.e., risk control rule interception) to prevent them from continuing the process canvas. When the behavior of existing users violates regulations, has safety hazards, does not meet quality standards, does not meet specific conditions, etc., in order to avoid possible adverse consequences or ensure normal data processing, they can be restricted (i.e., non-operational interception).

[0045] Therefore, through the above-mentioned hit rules, existing users can be hit and intercepted to improve the smoothness and efficiency of the overall system process.

[0046] In this implementation mode, for ease of understanding, Figure 3 As shown, when the existing users meet the entry conditions, the customer processes the inflow canvas. At this time, the planned inflow number is increased by 1 as the planned inflow users, and the flow location, flow type, flow sub-classification and other data of the user flow details are recorded. Then, the hit rule judgment is performed. If the above hit rule is hit, the number of intercepted users is increased by 1 (for example, the number of intercepted users due to the entry condition of non-operation is increased by 1, or the number of intercepted users due to the entry condition-risk control rule is increased by 1, or the number of users who cannot flow in due to the occupation of other high-priority canvases is increased by 1). At this time, the existing users who do not hit the above hit rule are regarded as the actual inflow users, and the actual inflow number is recorded plus 1.

[0047] The execution unit module 20 is used to transfer the user flow details entered into the process canvas into the multi-channel access module according to a preset diversion delay strategy.

[0048] It should be noted that the diversion delay strategy can be used to balance the load of the process canvas management system and avoid congestion during peak hours. It is a strategy set to give existing users appropriate buffer time.

[0049] In the specific implementation, Figure 2 As shown, the diversion delay strategy can buffer the existing users by selecting an execution unit (such as a diverter or a delayer) in the execution unit module, and then transfer the user flow details to the multi-channel reach module for processing through other execution units (such as a policy device).

[0050] The multi-channel reaching module 30 is used to distribute resources to the existing users according to the user flow details.

[0051] The execution unit module 20 is also used to transfer the existing users to which resource allocation has been completed out of the process canvas.

[0052] It should be noted that the multi-channel reach module can set up multi-channel reach through the process canvas, such as user group comparison, copywriting comparison, push function effect comparison, etc., to complete a certain event as the trigger action and perform multi-channel reach configuration.

[0053] For example, for ease of understanding, if a user logs in to the APP and browses a product, the process canvas management system will automatically send a message (with a limited-time coupon) 3 hours later to promote user conversion. After 7 days, the process canvas management system automatically executes the canvas's on-site evaluation, asking for product evaluation and willingness to spend money. For users with high evaluations or willingness, a text message is automatically triggered to guide them to withdraw cash. The next touch node is set based on the aftereffect behavior of the above channel touch.

[0054] In this implementation, after the multi-channel reach module distributes resources to existing users according to the user flow details, the existing users to which the resource distribution has been completed are transferred out of the process canvas, and the data processing of the existing users is completed at this time.

[0055] In a feasible implementation manner, the multi-channel reaching module 30 described in this embodiment is also used to determine again whether the transferred-in user flow details comply with the hit rules; the multi-channel reaching module 30 is also used to distribute rewards to the user flow details corresponding to the hit rules if they do not comply with the hit rules; the multi-channel reaching module 30 is also used to determine whether the user to be operated corresponding to the user flow details is a reached user when the reward distribution fails; the multi-channel reaching module 30 is also used to provide a communication reminder to the reached user if the user is the reached user.

[0056] For example, Figure 2 As shown, communication reminders may include reaching customers through SMS messages, application push, in-site information, AI robot telemarketing, manual telemarketing, etc., to remind customers to use their benefits or promote customer conversion.

[0057] Among them, the above-mentioned hit rules and judgment of reached users are mainly used to determine whether the customer can be processed by data. Customers who cannot be processed by data will flow out of the process canvas directly, while customers who can be processed by data will continue to flow.

[0058] In this implementation, the multi-channel contact module mainly performs the functions of reward distribution and customer contact, which mainly includes strategy pre-execution processing, reward distribution execution, customer contact execution, and strategy execution completion processing. The purpose of strategy pre-execution processing is to determine whether the customer can be processed (i.e., determine whether the transferred user flow details meet the hit rules) before execution, so as to avoid disturbing customers who cannot be processed due to customer feedback or other reasons. Executing reward distribution means distributing corresponding rewards to the screened customers according to the strategy, and performing operations related to distribution rights (i.e., distributing rewards to user flow details that do not meet the hit rules), including distributing coupons, points, activities and game privileges, etc.; and recording customer flow details at the beginning and end of distribution, and then contacting the customer and recording customer flow details at the beginning and end of contact. Executing customer contact means performing operations related to customer contact according to the policy configuration (i.e., if it is a contact user, the above-mentioned communication reminder is given to the contact user). Strategy execution completion processing means that after the strategy is executed, according to the feedback during the execution process, customers are diverted to different processing nodes, including abnormal outflow canvas, normal outflow canvas, pending outflow canvas, or continue to execute subsequent strategies; among them, if the above reward distribution and reach fail and the failed outflow canvas is configured, the customer will flow out of the canvas immediately, otherwise the customer will continue to flow, if the current is the last execution unit, the customer will flow out of the canvas immediately or after a delay according to the configuration, otherwise the customer will flow into the execution completion pending outflow node and wait for the customer to flow into the lower-level execution unit.

[0059] In a feasible implementation manner, the multi-channel reaching module 30 described in this embodiment is also used to determine whether the user flow details corresponding to the hit rules that do not meet the hit rules are set with reward distribution conditions when the transferred-in user flow details do not meet the hit rules; the multi-channel reaching module 30 is also used to distribute rewards to the corresponding user flow details if the reward distribution conditions are set; the multi-channel reaching module 30 is also used to determine whether the reward distribution is successful; the multi-channel reaching module 30 is also used to transfer the existing users corresponding to the failed reward distribution out of the process canvas when the reward distribution fails.

[0060] It should be noted that the reward distribution conditions may be to clarify the specific elements that must be met for the reward distribution, such as completing an activity, meeting specific qualifications, etc., and the corresponding rewards will be distributed to the user.

[0061] In this embodiment, for example, to facilitate understanding of the implementation process of the multi-channel access module, Figure 4 As shown, Figure 4A logical diagram of a multi-channel reach module provided in Example 1 of the present application. When a customer who meets the conditions of the superior enters the multi-channel reach module, first determine whether the customer has set reward distribution or reach. If reward distribution or reach is set, a hit rule judgment is performed, and the hit users flow out of the canvas and the number of outflows is recorded plus 1. For users who are not hit, it is determined again whether reward distribution is set. If reward distribution is set, reward distribution is performed, and the nodes where reward distribution starts and reward distribution is completed are recorded; if distribution fails, the users who failed to distribute flow out of the canvas and the number of outflows is recorded plus 1. At this time, it is determined separately whether reach is set (if the above judgment is that reward distribution is not set, you can also directly enter the operation of determining whether reach is set). If reach is set, the reach operation is started, and the nodes where reach starts and reach is completed are recorded; if reach fails, the users who failed to reach flow out of the canvas and the number of people who failed to reach out of the canvas is recorded plus 1. At this time, determine whether the node is the last execution unit in the multi-channel reach module (if the above judgment is that the reach is not set or the above judgment is that the reward distribution or reach is not set, you can also directly enter the process node). If it is the last execution unit, determine whether the execution is set to not flow out. If the execution is set to not flow out, the number of people who have completed the execution and are waiting to flow out of the canvas plus 1 is recorded, and polling is performed once an hour to determine whether the configured waiting time has been reached. If the configured waiting time has been reached, the execution is completed and the canvas is flowed out, and the number of people who have flowed out is recorded plus 1 (if the above judgment is that the execution is not set to not flow out, enter the node directly and flow out immediately). In the above process of recording the number of people who have completed the execution and are waiting to flow out of the canvas, the new strategy can also be approved. When the new strategy is approved, the flow is implemented, and it is determined whether a lower-level execution unit is set. If a lower-level execution unit is set, the execution of the waiting flow out strategy device is completed, and the number of people is recorded plus 1 (if the above judgment is not the last execution unit, you can also directly enter the process node). Finally, it flows into the execution unit module for processing.

[0062] In the technical solution provided in this embodiment, a process canvas management system is constructed, and the behavioral events of existing users are triggered and transferred into the process canvas through the process entry module, and then diverted into the multi-channel contact module based on the execution unit module to distribute resources to the existing users, so as to accurately respond to various behavioral events of existing users, avoid the current data processing method of existing users, where various activities are messy and isolated, and the interactive feedback of users is ignored, so as to provide customized services for different user groups, ensure the systematic and efficient data processing of existing users, and realize automatic contact and rapid response of data processing.

[0063] Based on the above first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above first embodiment can be referred to the above introduction, and will not be repeated in the following. Figure 1 and Figure 5 , Figure 5 This is a functional module diagram provided for the second embodiment of the application process canvas management system.

[0064] The execution unit module 20 described in this example includes a diverter 21 and a policy device 22 .

[0065] The diverter 21 is used to perform scenario diversion on the user flow details flowing into the process canvas, and transfer the diverted user flow details to the policy device 22.

[0066] It should be noted that the diverter may be a module for guiding users to different flow paths according to preset rules or user behaviors. When a customer flows into the diverter, the customer is diverted to a corresponding strategist according to the diversion rules.

[0067] The diverter component represents the traffic control and traffic distribution component, providing functions such as proportional diversion, random screening, traffic control, and reach result diversion, enriching the application scenarios of the canvas and providing flexible traffic management and control for the data processing plan of existing users. For example, a simple AB experiment can be set up by proportional diversion through the process canvas.

[0068] The policy device 22 is used to screen the user flow details after the diversion.

[0069] It should be noted that the components of the policy device represent the units that perform data processing actions for existing users, and can execute data processing instructions such as user screening, user tagging, rights distribution, activity distribution, and user contact. The policy device attributes mainly consist of basic information components, user screening components, user tagging components, reward (rights) distribution components, and user contact selection components. Through the policy device, a set of data processing actions can be completed. Common scenarios include notification after coupon distribution, active marketing activity push, and quota and price adjustment.

[0070] The basic information component includes properties such as the policy name, ID, priority, and whether it is the default policy. The default policy priority is the lowest priority in the same layer. The triggered default policy is the default policy when the parent policy is executed and no other policy in the same layer occurs within the specified time.

[0071] After the user screening component is executed by the parent policy controller, if the user selection conditions with higher priority at the same layer are not met, the default policy controller is entered.

[0072] User labeling components can include labeling, default labeling, and custom labeling. Among them, no labeling refers to the default item, which does not perform labeling; default labeling means that customers entering the policymaker can be labeled with one click, including default labeling (for example, labeling by adding the policymaker ID to the canvas), one-click addition to the activity A list, one-click addition to the activity B list, and other operations. Custom labeling means that customers entering the policymaker can be customized and have customized label values.

[0073] The reward (rights) distribution component can be a component that distributes and associates backend rights to customers who enter the strategist. Its functions include backend coupon distribution, backend points distribution, quota adjustment, price adjustment, external rights distribution, and association with active marketing activity pages. It supports multiple selections, and can select multiple activity landing pages or multiple different types of rewards. The rights and interests distributed by the reward distribution component can be associated in the touch component configuration, and the name, quantity, link, name and other information of the related rights and interests, and the related activities can be automatically obtained, and used as variables by the touch component. It can be automatically bound to the operation (i.e., data processing of existing users) plan resource pool, and the relevant rewards or activity landing pages will be automatically associated and bound by the data processing plan, and can be presented and managed in the operation plan resource pool. It can be monitored by the data processing plan, and will automatically join the data processing plan data system, and can be associated through the dashboard and indicators, and related monitoring and management can be performed.

[0074] The user touchpoint selection component refers to a component that reaches customers and interacts with them through messages or information through in-site messages, SMS, voice, external marketing, resource position configuration, etc. This time, the resource position configuration of the activity landing page is also added to the touchpoint selection component, and a new linkage with the reward distribution component is added, that is, when selecting a touchpoint, it can be associated with the reward configured by the strategist (or this canvas), automatically obtain the attribute variables such as the name, link, and quantity of the reward, and pass it into the message template or resource position, increasing the convenience of the touchpoint configuration.

[0075] In this implementation, the policy maker can make intelligent decisions to screen the details of the diverted user flows (for example, whether delayed service is required, whether it meets the preferred service, etc., which is not restricted in this implementation), ensuring that each user obtains the service that best meets their needs, thereby improving user satisfaction and conversion rate.

[0076] In a feasible implementation manner, the execution unit module 20 described in this embodiment also includes a delayer 23; the strategy device 22 is also used to mark the user flow details after the diversion, and determine whether the marked user flow details are set with delay conditions; the strategy device 22 is also used to transfer the user flow details with delay conditions into the delay device 23; the delay device 23 is used to delay the transferred user flow details, and transfer the corresponding user flow details into the strategy device 22 when the delay ends; the strategy device 22 is also used to determine whether the user flow details at the end of the delay meet the reward distribution conditions or reach conditions.

[0077] It should be noted that the delayer can control the rhythm of users entering the next process link by setting a specific time interval. It is a unit that represents the line waiting instruction. It can execute delay instructions such as delay for a period of time, delay to a specified time, delay to a relative time, or delay to a day of the week according to the needs of data processing; the difference from the delay component in the strategy is that multiple strategy devices can be hung under the delayer; the delayer is an independent strategy node and is displayed independently in the canvas; the customer flow in the delayer is not counted as the inflow of the strategy device. This helps to balance the system load and avoid congestion during peak hours, while giving users appropriate buffer time to improve the experience.

[0078] In this implementation, when a customer flows into the delayer, the records of the flow out of and into the delayer from the upper node are recorded, and according to the delay mode configured by the delayer, the incoming customer waits for the delay to end, and after the delay ends, the customer flows into the node to be flowed out after the delay is completed. When the customer flows into the policy device, the details of the customer flow flowing out of and into the policy device from the upper node are recorded, and then the delay, reward distribution and user contact are performed according to the configuration of the policy device. Through the delayer and policy device, it is helpful to realize personalized services, meet the specific needs of different user groups, optimize resource allocation, and improve overall data processing efficiency.

[0079] The policy device 22 is also used to determine whether the user flow details that have passed the screening meet the reward distribution conditions or reach conditions.

[0080] The strategist 22 is also used to transfer the user flow details that meet the reward distribution conditions or the reach conditions to the multi-channel reach module 30.

[0081] For ease of understanding, refer to Figure 6 , Figure 6A logical diagram of the execution unit module provided for the second embodiment of the present application. When the canvas actually flows into the user, first determine whether the node below is a policy maker, a delayer, or a diverter. If it is a diverter, divert it into the delayer or policy maker according to the rules of the diverter. When the customer flows into the policy maker, determine whether to flow into the policy maker based on the type of the policy maker; when the type is unrestricted, it flows directly into the policy maker; when the type is event-type, it flows into the policy maker after the corresponding event or fallback policy occurs, otherwise it stays in the upper-level policy maker; when the type is label-type, it determines that the customer's label meets the label condition and flows into the policy maker, otherwise the customer does not flow into this policy maker. When the customer flows out from the upper-level node and flows into this node, the number of people flowing into the policy maker is recorded plus 1, and the time of inflow is recorded. At this point, it can be determined whether a delay is set. If a delay is set, the number of people who have completed the delay plus 1 is recorded (when the above-mentioned customers flow out from the upper node and flow directly into the delayer, the number of people who have flowed into the delayer plus 1 is recorded, and the delay is waited for. When the delay ends, enter the "record the number of people who have completed the delay plus 1" node), and the number of people who have completed the delay and are waiting to flow out plus 1 is recorded. After the delay judgment is completed, the policy device determines whether the customer has set reward distribution or reach. If reward distribution or reach is set, it enters the multi-channel reach module to execute reward distribution or reach. After execution, the number of people waiting to flow out of the canvas is recorded plus 1.

[0082] Furthermore, in order to improve the query efficiency of the process canvas management system, this embodiment can also refer to Figure 7 , Figure 7 A schematic diagram of the data flow dashboard of the execution unit module provided in Example 2 of the present application.

[0083] Through the data flow dashboard (which saves the statistical time and the inflow time of each process), the process data slices of key processes such as entry conditions (for example, the planned inflow number, the above hit rules, and the actual inflow number, etc.), delayers (for example, the inflow number, the delay number, the delay number, the delay number, the outflow number, etc.), strategists (for example, the inflow number, the outflow number, the delay number, the interception number before the trigger, and other data related to the strategist, etc.), and execution unit judgment (the total outflow number of the upper execution unit, the interception number, the target outflow number, the actual inflow number of the lower unit execution number, etc.) can be stored daily, that is, the data slices within a certain period of time are archived and stored at regular intervals every day. These data slices cover the process data of key processes such as entry conditions, delayers, strategists, and execution unit judgments. Through daily storage, the data volume can be effectively managed, the query efficiency can be improved, and the details of all key processes can be fully retained, providing a solid foundation for subsequent data analysis and historical backtracking.

[0084] In the technical solution provided in this embodiment, users can be pre-screened through the above-mentioned policy device, delay device, and diverter to ensure that each user obtains the most suitable service for his or her needs, thereby improving user satisfaction and conversion rate.

[0085] For example, to further understand the execution process of the process canvas, Figure 3 Take the example to explain the high priority occupancy judgment, customer occupancy logic, and overall data statistics logic. Figure 3 In the , the logic of high-priority occupation judgment refers to the canvas priority. The priority attributes can be configured according to customer willingness, behavior and demand insights, business lines, life cycle, demand creation and other categories. When the types are consistent, you can view the canvas priority configured in the canvas, and the numerical judgment, the larger the value, the higher the priority; when the numerical values ​​are consistent, the priorities are consistent, and customers with consistent priorities cannot be snatched; when a high-priority canvas snatches a customer, it flows out of this canvas in real time, and the strategy engine stops delaying, rewarding, and reaching the customer. The sent ones continue to capture the sending results, and the target completion continues to monitor. When the target event of the outflow canvas is completed, it flows out of this canvas in real time, and the strategy engine stops delaying, rewarding, and reaching the customer. The sent ones continue to capture the sending results.

[0086] Among them, the customer occupation logic means that the customer is occupied by the canvas from the time the customer actually flows into the canvas, and is released from the time the customer flows out of the canvas; the canvas outflow rule means that only customers who flow into the canvas will flow out. When the canvas ends at 24:00, the users in the canvas flow out; when the canvas completes the goal and exits the canvas after completing the goal as configured in the target configuration; when the strategy controller fails to distribute the configured rewards; when the strategy controller fails to reach the configured reach; when a high-priority canvas occupies the customer, the customer flows out of this canvas in real time; when the canvas is executed, the customer flows out of the canvas if no delayed outflow is set or the outflow time is reached.

[0087] The above-mentioned overall data statistics logic includes data statistics timing statistics logic and data statistics result statistics. Data statistics timing statistics logic includes real-time updates of the cumulative number of entries and cumulative number of triggers in the data statistics results, and T+1 updates and displays of the number of people who have completed the target and the target completion rate. For example, the data statistics result statistics logic takes trigger-complete A as an example. The task start time from January 1 to January 7 is when event A is performed more than 2 times or event B is performed more than 3 times, and multiple participations are allowed. The goal is set to perform event A within 1 day after entering the process. When the same user triggers events in the order of AABABCBAACB, the timing of the user's repeated entry into the process and the number of target completions are as follows: the user enters the process for the first time at the second A, and all A's starting from the third A will be counted into the number of target completions; the user enters the process for the second time at the third B, and the third time at the fifth A. Since the valid data is returned T+1 after the push, the cumulative number of triggers on the day is the data sent by the push call. Before 12:00 noon on T+1, the data of the previous few days will be corrected. The above number of times, after deduplication by person, is the number of people statistics; for example, the number of people reached is the result of deduplication of the number of reaches by person. It should support filtering according to the sending time, strategy device, and reach method. The reach method is SMS information, and the information contains the corresponding times and people mentioned above.

[0088] For example, to help understand the function of the process canvas management system obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 8 , Figure 8 The scenario flow chart for implementing data processing of existing users through the process canvas management system provided in the second embodiment of the present application is as follows: The above-mentioned process canvas management system can be used in a variety of business scenarios, and can customize data processing strategies for silent customers (referring to users who have never withdrawn cash after a loan product is granted credit) in customer lifecycle data processing scenarios. In the full lifecycle scenario, the goal of data processing is to identify marketing models, match corresponding solutions, and recall customers through active marketing in key scenarios. Mining can be carried out in combination with the current circulation situation. Among them, the entry condition can be that for customers at the login and withdrawal breakpoints, if the application is not completed within 10 minutes, the canvas process will be entered; the main strategy can be: test the responsiveness of customers who hit the event to the discount, stratify customers through marketing models such as competitive quota models, gradually increase the strength of coupons according to the length of time the customer event occurs, and at the same time, combine robot telemarketing, manual telemarketing, etc. to reach out, and continue to optimize the strategy through breakpoint conversion rate data.

[0089] like Figure 8As shown, the scenario of data processing of customers who have never withdrawn cash by the process canvas management system is used as an example to illustrate that when the process canvas management system starts to execute, the customer group who has never withdrawn cash can be admitted to the process canvas. At this time, the customer's data processing strategy is determined according to the credit limit or interest rate matching model. It is divided into two categories: the current credit limit is less than the competitive credit limit and the current credit limit is greater than or equal to the competitive credit limit. Among them, in the case where the current credit limit is less than the competitive credit limit, it can be divided into: the current interest rate is greater than the competitive interest rate category (the data processing strategy is credit limit adjustment plus interest rate reduction plus borrowing discount) and the current interest rate is less than or equal to the competitive interest rate category (the data processing strategy is credit limit adjustment plus borrowing discount); in the case where the current credit limit is greater than or equal to the competitive credit limit, it can be divided into the current interest rate is greater than the competitive interest rate category (the data processing strategy is business side price adjustment plus borrowing discount) and the current interest rate is less than or equal to the competitive interest rate category (the data processing strategy is regular notification plus borrowing discount). This strategy mainly uses data processing tools such as competitive quota models to process customer data in layers, and uses follow-up marketing response models and external value models to match user rights and contact methods (for example, if the customer is externally medium-high value and the marketing response level is medium or high, then use manual telemarketing; if the customer is externally low value and the marketing response level is medium or high, then use AI robot telemarketing; if the customer is externally low value and the marketing response level is low, then use manual telemarketing), and finally end the process canvas management system. In addition, when a customer withdraws cash for the first time, a limited-time cash red envelope task reward can be activated, and the conversion rate can be further improved through targeted contact. The entire strategy aims to increase the borrowing willingness and conversion rate of silent customers through precise data processing.

[0090] It should be noted that the process canvas management system of this application mainly has a dual-engine driving mode of "business scenario driven and data value driven". It abstracts the essential scenarios of data processing, builds architectural solutions, establishes powerful strategy combinations and computing capabilities, and automatically adjusts configuration parameters to achieve automatic implementation and rapid response of strategies.

[0091] Among them, the process canvas management system can not only be used for the data processing scenarios of the above-mentioned customers who have not withdrawn cash, but also include customer lifecycle data processing scenarios, credit and withdrawal full process exit and breakpoint operation scenarios, and online activity operation scenarios. Among them, the customer lifecycle data processing scenario is a quantitative management system based on the customer lifecycle, including scenarios to promote first borrowing, promote activeness, promote repeat borrowing, and promote secondary credit. It applies data stratification and model judgment to formulate short-term to long-term data processing strategies, and optimizes the user's full-process conversion rate through means such as contact, marketing, and member management. At the same time, combined with risk strategies such as adjustment of credit limit, re-inspection, and pre-credit, the proportion of high-quality customer assets is increased to achieve more efficient customer value management and risk control, and improve customer retention. Among them, customers who have not withdrawn cash also belong to customer lifecycle data processing scenarios, such as Figure 8As shown in the figure, through the user portrait of loan products that have not withdrawn cash after credit is granted, combined with model prediction, targeted short-term and medium-term strategies are formulated to promote user withdrawals. At the same time, comprehensive anti-fraud measures are built to enhance risk prevention and control, including data processing strategies and risk support strategies, such as pushing preferential information, providing exclusive channels, etc., to promote the adjustment of credit limit and price to improve the withdrawal conversion rate. Strategies are adjusted in a timely manner by observing the life cycle flow, model prediction, conversion attribution model, etc. For example, in the customer churn score, if the original credit limit is greater than or equal to Y and the credit limit utilization rate is 0%, then the credit limit will be increased immediately by 30% of the regular increase, and a discount of N yuan will be issued. If the customer does not withdraw cash subsequently and the churn score is high next month, the credit limit will be increased immediately by 50% of the regular increase next month, and a discount of N plus x1 yuan will be issued. If the customer withdraws cash subsequently, the status becomes stable. Among them, the data processing scenarios of the exit and breakpoint of the whole process of credit granting and cash withdrawal mainly focus on customer demands, combine the key entry and first cash withdrawal behaviors of the customer acquisition end, clarify the entry and first cash withdrawal exit nodes, and timely expand the exit or breakpoint services when the user enters the main process exit or breakpoint, establish an exit data processing system, and explore and tap the needs of user scenarios for high-willing users. Provide follow-up services for users in combination with interest rate discounts to promote users to return to complete business conversion. Through user surveys, understand the reasons for user exit or breakpoint and the actual expectations of users, match users with better products and services, optimize the entry and withdrawal processes, and ensure the efficiency of the process. Among them, the online activity data processing scenario builds a financial loan product system around credit products, carries out inclusive theme festival activities every quarter, carries out long-term inclusive activities every week and month, and carries out exclusive inclusive activities such as birthdays, going home, and sharing to support the development of various marketing activities. For example, if you borrow 100 yuan, you will accumulate 1g, and 100g is equivalent to 1 yuan. It can be credited in real time when borrowing, and remind customers to use it as soon as possible before the expiration date. At the same time, a new task component is added to the marketing activity component to enrich the acquisition marketing scene, and new interaction, lottery, deduction and other scenes are added to the acquisition and consumption sections, and the past task types and exchange preferential rights are re-planned. Other application scenarios can also be used, and this embodiment does not limit this.

[0092] Regarding the above-mentioned improvement of the coverage of customer lifecycle data processing scenarios, it mainly focuses on the number of touch intentions and frequency of touch in each scenario; complaint rate; number of strategy branches in each scenario; single touch conversion rate; strategy maintenance time; strategy iteration frequency; strategy complaint rate; among them, the customer response rate of each scenario = customer capacity * (∑ scenario intention hit rate * touch rate * click rate * participation / login rate * withdrawal conversion rate * withdrawal approval rate + bottom-up touch strategy * bottom-up touch rate * bottom-up strategy click rate * bottom-up participation / login rate * bottom-up strategy withdrawal conversion rate * bottom-up strategy withdrawal approval rate).

[0093] To improve the data processing effect of the whole process of credit granting and credit use, and the data of breakpoints. Mainly focus on the credit granting exit intention; cash withdrawal exit intention; the number of credit granting and exit strategy branches; single touch conversion rate; strategy maintenance time; strategy iteration frequency; strategy complaint rate; among which the credit granting exit strategy response rate = the average number of credit granting exit customers per day * (∑ intention hit rate * touch rate * participation / login rate * application rate * credit approval rate + bottom intention hit rate * bottom strategy touch rate * bottom strategy participation / login rate * bottom strategy application rate * bottom strategy credit approval rate); Mainly focus on the cash withdrawal exit strategy response rate = the average number of cash withdrawal exit customers per day * (∑ intention hit rate * touch rate * participation / login rate * withdrawal rate * withdrawal approval rate + bottom intention hit rate * bottom strategy touch rate * bottom strategy participation / login rate * bottom strategy withdrawal rate * bottom strategy withdrawal approval rate).

[0094] To improve the effect of online activity data processing, you can pay attention to the number of customers covered by activities by cycle (week / month / quarter / year); the frequency of activity releases; the duration of activity execution; the average marketing cost per customer; the activity complaint rate; the activity response rate = ∑ number of activity exposures * activity login rate * activity participation rate * activity attribution credit or submission rate / total customer base capacity.

[0095] By implementing data processing for the above scenarios through the process canvas management system, customer insights and analytical feedback can be achieved. Among them, customer insights refer to the establishment of a rich, comprehensive and complete customer tag center based on big data mining and analysis capabilities, in-depth user behavior analysis, connecting user data and business transaction data, covering customer identity, asset status, purchase preferences, value potential, behavioral tendencies and other information, forming a data-driven customer portrait, and achieving the characterization and insight of single customers and customer groups. Various marketing models can be used in depth to achieve deep insight into customer value and intelligent upgrades of marketing models, and improve the level of marketing precision. Among them, analytical feedback refers to empowering marketing personnel at all levels through data processing and analysis tools, and by combing online and standardized business processes, holographically presenting performance and operating conditions, providing managers with a basis for digital decision-making. Optimize the data access mechanism, provide data analysts with fast and convenient data resources, and improve the response time of data processing and analysis. Establish a link between underlying data and marketers, support self-service query and analysis statistics, provide efficient and reliable data support for data processing decision analysis, form execution feedback through user data, transaction data, marketing data and existing user data, enable timely adjustment of marketing strategies based on data-driven, iterative optimization, and form a marketing closed loop.

[0096] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the process canvas management system of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0097] Based on the above process canvas management system, the present application embodiment provides a process canvas management method, referring to Fig. 9 , Fig. 9 A flowchart diagram of the first embodiment of the process canvas management method of the present application is provided. The process canvas management method is applied to the above process canvas management system, which includes a process entry module, an execution unit module and a multi-channel access module.

[0098] In this embodiment, the process canvas management method includes steps S10 to S40: Step S10: When a behavioral event of an existing user triggers a preset reach task type, the process entry module transfers the user flow details of the existing user into a process canvas, and the process canvas is used to perform periodic operations on the existing user.

[0099] In this implementation, the prerequisites for triggering existing users to enter the process canvas (i.e., the type of task to be reached) can be clearly defined in the process entry module. These conditions may be based on the user's behavioral events, the real-time status of the system, or specific events in the external environment to ensure that the user is directed to the corresponding process in the process canvas at the most appropriate time. When the behavioral events of existing users trigger the task type to be reached, it means that the existing users need to be operated through strategies. At this time, the process entry module obtains the user flow details of the existing users and transfers the nodes of the existing users to the process canvas for processing.

[0100] In a feasible implementation, step S10 of this embodiment may include the following steps: the process entry module determines whether the behavior event of the existing user triggers a preset reach task type, and the reach task type includes a timed task and a triggered task; the process entry module determines whether the existing user belongs to the audience user group when the behavior event triggers the timed task or the triggered task; when the existing user belongs to the audience user group, the process entry module transfers the user flow details of the existing user into the process canvas according to the preset hit rule.

[0101] In this implementation, the process entry module has pre-defined and clearly defined the types of tasks that trigger users to enter the process, and has divided the tasks into priority levels based on the importance of business goals, the urgency of user needs, and the availability of system resources, ensuring that key tasks are given priority, thereby maximizing the overall benefits of the process and user satisfaction. Figure 3 As shown, Figure 3A logical diagram of the process entry module provided for Example 1 of the present application. When the behavioral event of an existing user triggers the above-mentioned contact task type, determine whether the existing user meets the entry conditions (for example, whether it belongs to the above-mentioned audience user group); if the existing user does not meet the entry conditions, the customer is treated as not flowing into the canvas. If the existing user meets the entry conditions, the customer is treated as flowing into the canvas. At this time, the existing users can be intercepted according to the above-mentioned hit rules to ensure that existing users with risk control risks or low priority are temporarily suspended from entering the process canvas. The remaining existing users who have not been intercepted can enter the process canvas. At this time, the user flow details of the user are obtained, and the user's node is transferred to the process canvas for processing. Through the above design, the process canvas can optimize customer flow and data flow, achieve business goals, and improve user experience.

[0102] In a feasible implementation manner, the process entry module described in this embodiment transfers the user flow details of the existing user into the process canvas according to the preset hit rule when the existing user belongs to the audience user group, including: when the existing user belongs to the audience user group, the process entry module regards the existing user as a planned incoming user; the planned incoming user is intercepted according to the hit rule preset by the process entry module, and the hit rule includes non-operational interception, risk control rule interception and priority occupation interception; the process entry module regards the planned incoming users that are not intercepted as actual incoming users, and transfers the user flow data of the actual inflow users into the process canvas.

[0103] It should be noted that the planned inflow users can be the users who are planned to flow into the process canvas when the entry conditions (i.e., the task type) are met. The actual inflow users are the users who do not meet the hit rules and actually flow into the process canvas.

[0104] Among them, considering the logic and efficiency of the process canvas management system in processing tasks, the importance of tasks can be distinguished based on the importance of business goals, the urgency of user needs, and the availability of system resources, and the task priorities can be scientifically divided (priority occupation interception) to ensure that key tasks are given priority, thereby maximizing the overall benefits of the process and user satisfaction. At the same time, considering the risk control rules and standards, existing users who have potential risks or do not meet the requirements of the rules can be blocked or restricted (i.e., risk control rule interception) to prevent them from continuing the process canvas. When the behavior of existing users violates regulations, has safety hazards, does not meet quality standards, does not meet specific conditions, etc., in order to avoid possible adverse consequences or ensure normal data processing, they can be restricted (i.e., non-operational interception).

[0105] Therefore, through the above-mentioned hit rules, existing users can be hit and intercepted to improve the smoothness and efficiency of the overall system process.

[0106] Step S20: The execution unit module transfers the user flow details entered into the process canvas into the multi-channel access module according to a preset diversion delay strategy.

[0107] In the specific implementation, Figure 2 As shown, the diversion delay strategy can buffer the existing users by selecting an execution unit (such as a diverter or a delayer) in the execution unit module, and then transfer the user flow details to the multi-channel reach module for processing through other execution units (such as a policy device).

[0108] Step S30: The multi-channel reaching module distributes resources to the existing users according to the user flow details.

[0109] Step S40: the execution unit module transfers the existing users to which resource allocation has been completed out of the process canvas.

[0110] It should be noted that the multi-channel reach module can set up multi-channel reach through the process canvas, such as user group comparison, copywriting comparison, push function effect comparison, etc., to complete a certain event as the trigger action and perform multi-channel reach configuration.

[0111] For example, for ease of understanding, if a user logs in to the APP and browses a product, the process canvas management system will automatically send a message (with a limited-time coupon) 3 hours later to promote user conversion. After 7 days, the process canvas management system automatically executes the canvas's on-site evaluation, asking for product evaluation and willingness to spend money. For users with high evaluations or willingness, a text message is automatically triggered to guide them to withdraw cash. The next touch node is set based on the aftereffect behavior of the above channel touch.

[0112] In this implementation, after the multi-channel reach module distributes resources to existing users according to the user flow details, the existing users to which the resource distribution has been completed are transferred out of the process canvas, and the data processing of the existing users is completed at this time.

[0113] In the technical solution provided in this embodiment, through the constructed process canvas management system, the behavioral events of existing users can be triggered and transferred to the process canvas through the process entry module, and then diverted to the multi-channel contact module based on the execution unit module to distribute resources to the existing users, so as to accurately respond to various behavioral events of existing users, avoiding the current data processing method of existing users, in which various activities are messy and isolated, and the interactive feedback of users is ignored, thereby providing customized services for different user groups, ensuring the systematic and efficient data processing, and realizing automatic contact and rapid response of data processing.

[0114] Based on the first embodiment of the process canvas management method of the present application, in the second embodiment of the present application, the same or similar contents as those of the first embodiment can be referred to the above introduction and will not be repeated later.

[0115] As an implementation mode, the execution unit module includes a diverter and a policy device; the step S20 includes the steps of: the diverter performs scene diversion on the user flow details flowing into the process canvas, and transfers the diverted user flow details to the policy device; the policy device filters the diverted user flow details; the policy device determines whether the filtered user flow details meet the reward distribution conditions or the reach conditions; the policy device transfers the user flow details corresponding to the reward distribution conditions or the reach conditions to the multi-channel reach module.

[0116] As an implementation mode, the execution unit module also includes a delayer; the step in which the policy device screens the user flow details after the diversion includes: the policy device marks the event of the user flow details after the diversion, and determines whether the marked user flow details are set with a delay condition; the policy device transfers the user flow details with the delay condition to the delay device; the delay device delays and waits for the transferred user flow details, and transfers the corresponding user flow details to the policy device when the delay ends; the policy device determines whether the user flow details at the end of the delay meet the reward distribution conditions or the reach conditions.

[0117] As an implementation mode, the step S30 includes the steps of: the multi-channel reach module again determines whether the transferred user flow details comply with the hit rules; if the multi-channel reach module does not comply with the hit rules, rewards are distributed to the user flow details that do not comply with the hit rules; when the multi-channel reach module fails to distribute rewards, it determines whether the user to be operated corresponding to the user flow details is the reached user; if the multi-channel reach module is the reached user, a communication reminder is given to the reached user.

[0118] As an implementation mode, after the step of the multi-channel reach module again determining whether the transferred-in user flow details comply with the hit rules, the multi-channel reach module further includes: when the transferred-in user flow details do not comply with the hit rules, the multi-channel reach module determines whether the user flow details corresponding to the hit rules are set with reward distribution conditions; if the multi-channel reach module is set with the reward distribution conditions, the corresponding user flow details will be rewarded; the multi-channel reach module determines whether the reward distribution is successful; when the reward distribution fails, the multi-channel reach module transfers the existing users corresponding to the failed reward distribution out of the process canvas.

[0119] The process canvas management method provided in this application is implemented based on the process canvas management system in the above embodiment. Compared with the prior art, the beneficial effects of the process canvas management method provided in this application are the same as those of the process canvas management system provided in the above embodiment, and other technical features in the process canvas management method are the same as those disclosed in the above embodiment system, which will not be described in detail here.

[0120] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A process canvas management system, characterized in that: The system includes: a process entry module, an execution unit module and a multi-channel access module; The process entry module is used to transfer the user flow details of the existing user into the process canvas when the behavior event of the existing user triggers the preset contact task type. The process canvas is used to perform periodic operations on the existing user; The execution unit module is used to transfer the user flow details transferred into the process canvas into the multi-channel contact module according to the preset diversion delay strategy; The multi-channel reaching module is used to distribute resources to the existing users according to the user flow details; The execution unit module is also used to transfer the existing users to which resource allocation has been completed out of the process canvas.

2. The system according to claim 1, characterized in that The process entry module is also used to determine whether the behavior event of the existing user triggers a preset reach task type, and the reach task type includes a timed task and a triggered task; The process entry module is further used to determine whether the existing user belongs to the audience user group when the behavior event triggers the scheduled task or the triggered task; The process entry module is also used to transfer the user flow details of the existing users into the process canvas according to the preset hit rule when the existing users belong to the audience user group.

3. The system according to claim 2, characterized in that The process entry module is further used to treat the existing user as a planned inflow user when the existing user belongs to the audience user group; The process entry module is also used to intercept the planned inflow users according to preset hit rules, and the hit rules include non-operational interception, risk control rule interception and priority occupation interception; The process entry module is also used to treat the planned inflow users that are not intercepted as actual inflow users, and transfer the user flow data of the actual inflow users into the process canvas.

4. The system according to claim 1, characterized in that The execution unit module includes a diverter and a policy device; The diverter is used to perform scenario diversion on the user flow details flowing into the process canvas, and transfer the diverted user flow details to the policy device; The policy device is used to filter the user flow details after the diversion; The policy device is also used to determine whether the user flow details that have passed the screening meet the reward distribution conditions or reach conditions; The strategist is also used to transfer the user flow details that meet the reward distribution conditions or the reach conditions to the multi-channel reach module.

5. The system according to claim 4, characterized in that The execution unit module also includes a delay device; The policy device is further used to mark the event of the user flow details after the diversion, and determine whether the marked user flow details are set with a delay condition; The policy device is further used to transfer the user flow details with delay conditions set to the delay device; The delayer is used to delay the incoming user flow details and transfer the corresponding user flow details to the policy device when the delay ends; The policy device is also used to determine whether the user flow details that end with the delay meet the reward distribution conditions or reach conditions.

6. The system according to claim 2 or 3, characterized in that: The multi-channel reaching module is further used to determine again whether the incoming user flow details meet the hit rule; The multi-channel reaching module is further used to distribute rewards to the user flow details corresponding to the user flow details that do not meet the hit rules if the hit rules are not met; The multi-channel reaching module is also used to determine whether the user to be operated corresponding to the user flow details is a reached user when the reward distribution fails; The multi-channel reaching module is also used to provide communication reminders to the reached user if the user is the reached user.

7. The system according to claim 6, characterized in that The multi-channel contact module is further used to determine whether the user flow details corresponding to the non-compliant hit rule are set with reward distribution conditions when the transferred user flow details do not comply with the hit rule; The multi-channel reaching module is further used to distribute rewards to the corresponding user flow details if the reward distribution conditions are set; The multi-channel access module is also used to determine whether the reward distribution is successful; The multi-channel contact module is also used to transfer the existing users corresponding to the failed reward distribution out of the process canvas when the reward distribution fails.

8. A process canvas management method, characterized in that: The process canvas management method is applied to a process canvas management system, the system includes a process entry module, an execution unit module and a multi-channel access module; the method includes: When a behavior event of an existing user triggers a preset reaching task type, the process entry module transfers the user flow details of the existing user into a process canvas, and the process canvas is used to perform periodic operations on the existing user; The execution unit module transfers the user flow details entered into the process canvas into the multi-channel access module according to the preset diversion delay strategy; The multi-channel reaching module distributes resources to the existing users according to the user flow details; The execution unit module transfers the existing users to which resource allocation has been completed out of the process canvas.

9. The method according to claim 8, characterized in that When a behavior event of an existing user triggers a preset reach task type, the process entry module transfers the user flow details of the existing user into the process canvas, including: The process enters a module to determine whether the behavior event of the existing user triggers a preset reach task type, and the reach task type includes a timed task and a triggered task; The process entry module determines whether the existing user belongs to the audience user group when the behavior event triggers the scheduled task or the triggered task; When the existing user belongs to the audience user group, the process entry module transfers the user flow details of the existing user into the process canvas according to the preset hit rule.

10. The method according to claim 9, characterized in that The process entry module transfers the user flow details of the existing user into the process canvas according to the preset hit rule when the existing user belongs to the audience user group, including: The process entry module regards the existing user as a planned inflow user when the existing user belongs to the audience user group; The process enters the module preset hit rules to intercept the planned inflow users, and the hit rules include non-operational interception, risk control rule interception and priority occupation interception; The process entry module regards the planned inbound users that are not intercepted as actual inbound users, and transfers the user flow data of the actual inbound users into the process canvas.

Images