Process canvas management system and method

Abstract

The present application discloses a process canvas management system and method, which relates to the field of data processing technology. The system includes: 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 into the process canvas when the behavioral event of the existing user triggers the contact task type; the execution unit module is used to transfer the user flow details into the multi-channel contact module according to the 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. Through the process canvas management system, the present application can 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 ignore the situation where user interaction feedback is ignored, so that the data of existing users can be effectively contacted, and automatic contact and rapid response of existing users can be achieved.

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 sector, and the traditional financial industry is gradually shifting towards FinTech. The threshold for financial services is high, and online business consultations are extensive, covering areas such as credit card repayments, loan processing, and fund management. However, in the current highly competitive consumer finance market, there is a significant gap in user scale and asset size compared to leading industry institutions, and the gap is tending to widen. Furthermore, there is a gradual saturation of the market, slowing growth in new users, and a serious phenomenon of product homogeneity. Therefore, the data processing of existing users is currently a key focus, and the main problems it faces are as follows:

[0003] 1. The mismatch between customer needs and data processing strategies for existing users. First, there is a lack of clear customer segmentation and strategic coordination, and second, there is a mismatch between products and customer base.

[0004] 2. The contradiction between fragmented scenarios and insufficient data insights. First, data processing scenarios for existing users are fragmented and scattered, lacking a comprehensive data processing strategy for existing users throughout their entire customer lifecycle. Second, data is fragmented, lacking a holistic perspective. Customer data, risk data, behavioral data, and other data are scattered across various business systems, lacking a unified indicator caliber.

[0005] 3. The conflict between limited resources and policy segmentation. First, the level of automation is low. The data processing strategy for existing users is not highly automated, making it difficult to meet the complex and personalized data processing needs of existing users, resulting in inefficient data processing for existing users. Second, data connectivity is poor. The entire data processing process for existing users is fragmented, resulting in fragmented activity or policy data. Third, the level of intelligence needs to be improved. Currently, policy design and deployment rely primarily on manual experience, and there is a lack of intelligent tools for processing existing user data.

[0006] Therefore, in the current data processing methods for existing users, various activities are chaotic and isolated, ignoring user interactive feedback. This leads to 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 existing user data is currently an urgent problem that needs to be solved. Summary of the Invention

[0007] 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 interactive feedback is ignored, resulting in a mismatch between user needs and the data processing strategy of existing users, leading to low data processing efficiency.

[0008] To achieve the above objectives, the present application proposes a process canvas management system, which includes: a process entry module, an execution unit module, and a multi-channel access module;

[0009] The process entry module is used to transfer the user flow details of the existing user to 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;

[0010] 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;

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

[0012] The execution unit module is further configured to transfer existing users to which resource allocation has been completed out of the process canvas.

[0013] In one embodiment, the process entry module is further used to determine whether the behavior event of the existing user triggers a preset contact task type, and the contact task type includes a scheduled task and a triggered task;

[0014] The process entry module is further configured to determine whether the existing user belongs to the target user group when the behavior event triggers the scheduled task or the triggered task;

[0015] The process entry module is further 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.

[0016] In one embodiment, the process entry module is further configured to treat the existing user as a planned inflow user when the existing user belongs to the audience user group;

[0017] 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;

[0018] The process entry module is further 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.

[0019] In one embodiment, the execution unit module includes a diverter and a policer;

[0020] The splitter is used to split the user flow details flowing into the process canvas by scenarios, and transfer the split user flow details to the policy device;

[0021] The policy device is used to filter the user flow details after the diversion;

[0022] The policy controller is also used to determine whether the user flow details that have passed the screening meet the reward distribution conditions or reach conditions;

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

[0024] In one embodiment, the execution unit module further includes a delay device;

[0025] 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;

[0026] The policy device is further configured to transfer the user flow details with delay conditions set to the delay device;

[0027] 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;

[0028] The strategist is further configured to determine whether the delayed end user flow details meet the reward distribution conditions or reach conditions.

[0029] In one embodiment, the multi-channel contact module is further configured to determine again whether the incoming user flow details meet the hit rule;

[0030] The multi-channel reaching module is further configured to distribute rewards to user flow details corresponding to the user flow details that do not meet the hit rules if the hit rules are not met;

[0031] The multi-channel reaching module is further used to determine whether the user to be operated corresponding to the user flow details is a reached user when the reward distribution fails;

[0032] The multi-channel contact module is also used to provide communication reminders to the contacted user if the user is the contacted user.

[0033] In one embodiment, the multi-channel contact module is further configured to, when the incoming user flow details do not meet the hit rule, 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;

[0034] The multi-channel contact module is further used to distribute rewards to the corresponding user flow details if the reward distribution conditions are set;

[0035] The multi-channel access module is also used to determine whether the reward distribution is successful;

[0036] 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.

[0037] In addition, to achieve the above objectives, the present application also proposes a process canvas management method, which 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:

[0038] 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 to a process canvas, and the process canvas is used to perform periodic operations on the existing user;

[0039] The execution unit module transfers the user flow details entered into the process canvas into the multi-channel contact module according to the preset diversion delay strategy;

[0040] The multi-channel reaching module distributes resources to the existing users according to the user flow details;

[0041] The execution unit module transfers the existing users to which resource allocation has been completed out of the process canvas.

[0042] 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 to the process canvas, including:

[0043] The process enters the module to determine whether the behavior event of the existing user triggers a preset contact task type, and the contact task type includes a timed task and a triggered task;

[0044] 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;

[0045] 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.

[0046] 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:

[0047] The process entry module treats the existing user as a planned inflow user when the existing user belongs to the audience user group;

[0048] The process enters the module and 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;

[0049] The process entry module regards the planned inflow users that are not intercepted as actual inflow users, and transfers the user flow data of the actual inflow users into the process canvas.

[0050] One or more technical solutions proposed in this application have at least the following technical effects: This application proposes a process canvas management system, which includes: 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 behavioral 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 allocate 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 allocation out of the process canvas.

[0051] 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 user's interactive feedback is ignored, so that the stock user data of different user groups can be effectively reached, ensuring the systematic and efficient data processing of existing users, and realizing automatic reach and rapid response of operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] 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.

[0053] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0054] Figure 1 Functional module diagram provided for the first embodiment of the application process canvas management system;

[0055] Figure 2 A schematic diagram of the configuration steps of the process canvas provided in Example 1 of the present application;

[0056] Figure 3 A logical diagram of the process entry module provided in Example 1 of the present application;

[0057] Figure 4 A logical diagram of the multi-channel access module provided in Example 1 of the present application;

[0058] Figure 5 Functional module diagram provided for the second embodiment of the application process canvas management system;

[0059] Figure 6 A logical diagram of the execution unit module provided in Example 2 of the present application;

[0060] Figure 7 A schematic diagram of a data flow dashboard for an execution unit module provided in Example 2 of the present application;

[0061] Figure 8 A flowchart of a scenario for implementing data processing of existing users through a process canvas management system provided in Example 2 of this application;

[0062] Figure 9 This is a flowchart of the first embodiment of the application process canvas management method.

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

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

[0065] 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.

[0066] 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 diverse business scenarios, and realize a complete and coherent business process management closed loop from initial conception of the strategy, detailed design, internal approval, actual implementation to final effect feedback, ensuring the systematic and efficient activities of existing user data processing. Thereby improving the automation and intelligence level of existing user data processing, so as to achieve in-depth operation and refined management of existing customers.

[0067] 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.

[0068] 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.

[0069] 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". The logic of the process canvas management system is as follows: Figure 2 As shown, Figure 2 Schematic diagram of the configuration steps of the process canvas provided in Example 1 of this application. Operations personnel can first formulate a strategy for processing existing user data 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 based on the designed process and allocated resources through the process entry module, execution unit module, and multi-channel contact module, and collects user feedback and existing user data for effect data analysis.

[0070] Before the Process Canvas management system can automatically execute tasks, you must first create a process canvas and set up execution units. When configuring the task start time, you need to determine when to begin executing the existing user data processing policy. When configuring the target users, you need to clearly define the user groups for the policy. Finally, when configuring the existing user data processing channels, you need to select the channels through which to promote and execute the policy. Through these steps, the Process Canvas management system can configure different existing user data processing policies based on different existing user data processing scenarios to achieve existing user data processing goals.

[0071] The process entry module 10 is used to transfer the user flow details of the existing user into the process canvas when the behavioral event of the existing user triggers a preset contact task type. The process canvas is used to perform periodic operations on the existing user.

[0072] 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, various strategies need to be used to operate in order to maintain and further tap the value of existing customers.

[0073] Among them, behavioral 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 contact task type can be a task category pre-set in the process entry module to screen existing users for whether to perform data processing in the process canvas. For example, specific tasks can be set, or timed tasks can be set, which is not limited in this embodiment.

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

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

[0076] 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 directed 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.

[0077] 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 contact task type, and the contact task type includes a timed 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 timed 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.

[0078] It should be noted that if Figure 2 As shown, when setting up and selecting the reach task type, you can include scheduled tasks (i.e., reaching a trigger event) and triggered tasks (i.e., triggering based on a configured event). You can also set entry time and entry restrictions. Scheduled tasks can include Scheduled-Single and Scheduled-Recurring, and triggered tasks can include Trigger-Complete A and Trigger-Complete A but Not Complete B. Scheduled-Single can be used to create a process that is executed once, with existing users entering the process canvas at a fixed time. Scheduled-Recurring can be used to create a process that is executed repeatedly, with existing users entering the process canvas at one or more fixed times in each cycle, such as 10:00 every day in March and 16:00 every Friday in April. Trigger-Complete A can trigger a process (immediately or delayed) when an existing user completes a certain action. For example, a user's completion of a post collection, like, or forwarding triggers a points arrival reminder. Within the effective time of the task, multiple process triggers can be achieved if the trigger conditions are met. Trigger type - Complete A but not Complete B type, which can be used to create triggered tasks. When a 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 user does not access the page within 20 minutes after starting the application, the process execution is triggered. It is usually used for breakpoint data processing.

[0079] 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, and can be used to determine whether existing users entering the process canvas are in the audience user segmentation.

[0080] For ease of understanding, Figure 2As shown, when choosing to set audience users, the audience user attributes can support three configuration methods: label and behavior selection, existing grouping, and no restrictions. Different trigger conditions are coupled with the audience user selection method. Among them, label and behavior selection can be combined and selected through labels, attributes, grouping packages, detailed data, and behavioral 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 the configuration of ad slots will be allowed.

[0081] It should be understood that a hit rule can be used to block existing users from entering the process canvas temporarily. For example, if an existing user presents a risk control risk, then the hit rule is met and the existing user cannot enter the process canvas. Alternatively, if a certain existing user has a lower priority than other existing users, the existing user cannot enter the process canvas and must wait to enter. Other hit rules are also possible, and this embodiment does not limit them.

[0082] 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 prioritized, thereby maximizing the overall efficiency 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, it is determined 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 processed as not flowing into the canvas. If the existing user meets the entry conditions, the customer is processed 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 priorities 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 node of the user 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.

[0083] In a feasible implementation manner, the process entry module 10 described in this embodiment is also used to treat the existing users as planned inflow users when the existing users belong to the audience user group; the process entry module 10 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 10 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.

[0084] It should be noted that the planned inflow user can be the user who is scheduled to flow into the process canvas when the entry conditions (i.e., the task type) are met. The actual inflow user is the user who actually flows into the process canvas when the hit rule is not met.

[0085] Among them, considering the logic and efficiency of the process canvas management system in processing tasks, the importance of tasks can be differentiated based on the importance of business goals, the urgency of user needs, and the availability of system resources, and task priorities can be scientifically divided (priority occupation interception) to ensure that critical tasks are handled first, thereby maximizing the overall benefits of the process and user satisfaction. At the same time, taking into account 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) and prevented from continuing the process canvas. When the behavior of existing users violates regulations, poses 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).

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

[0087] In this embodiment, for ease of understanding, Figure 3 As shown, when existing users meet the entry criteria, the client processes them according to the inflow canvas. The planned inflow number is incremented by 1, and the user's flow details, including the flow location, flow type, and flow subclassification, are recorded. Then, the user flow is evaluated for match criteria. If the rules are met, the number of blocked users is incremented by 1 (for example, if the entry criteria are unavailable for operation, the number of blocked users is incremented by 1, or if the entry criteria are risk control rules, or if other high-priority canvases are occupied, resulting in the user being unable to enter, the number of blocked users is incremented by 1). At this point, existing users who don't meet the rules are considered actual inflow users, and the actual number of inflows is incremented by 1.

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

[0089] 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.

[0090] In the specific implementation, Figure 2 As shown, the diversion delay strategy can buffer 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).

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

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

[0093] 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 for multi-channel reach configuration.

[0094] For ease of understanding, let's assume a user logs into the app and browses a product. Three hours later, the process canvas management system automatically sends a message (with a limited-time coupon) to facilitate user conversion. Seven days later, the process canvas management system automatically executes an on-site review of the canvas, asking for product reviews and willingness to spend. For users who highly rate the product or show willingness, a text message is automatically triggered to guide them to withdraw cash. The subsequent actions of the above channel contact are used to set the next contact node.

[0095] In this embodiment, after the multi-channel reach module distributes resources to existing users according to the user flow details, the existing users to whom 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.

[0096] In a feasible implementation manner, the multi-channel reach module 30 described in this embodiment is also used to re-determine whether the incoming user flow details comply with the hit rules; the multi-channel reach 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 reach 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 reach module 30 is also used to provide a communication reminder to the reached user if it is the reached user.

[0097] For example, Figure 2As 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.

[0098] 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.

[0099] In this embodiment, 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 again whether the customer can be processed (i.e., determine again 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 screened customers according to the strategy, and performing operations related to the distribution of rights and interests (i.e., distributing rewards to user flow details that do not meet the hit rules), including the distribution of 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 executing operations related to customer contact according to the policy configuration (i.e., if the user is contacted, the above-mentioned communication reminder is given to the contacted user). Strategy execution completion processing means that after the strategy is executed, based on the feedback during the execution process, customers are diverted to different processing nodes, including abnormal outflow canvas, normal outflow canvas, pending outflow canvas, or continuing to execute subsequent strategies. Among them, if the above reward distribution and reach fail and the failure outflow canvas is configured, the customer will be immediately out of the canvas; otherwise, the customer will continue to flow. If the current execution unit is the last, the customer will be immediately or delayed out of the canvas 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.

[0100] In a feasible implementation manner, the multi-channel reach module 30 described in this embodiment is also used to determine whether the user flow details corresponding to the hit rule that do not meet the hit rule are set with reward distribution conditions when the transferred-in user flow details do not meet the hit rule; the multi-channel reach module 30 is also used to distribute rewards to the corresponding user flow details if the reward distribution conditions are set; the multi-channel reach module 30 is also used to determine whether the reward distribution is successful; the multi-channel reach 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.

[0101] It should be noted that the reward distribution conditions may be to clearly define the specific elements that must be met for the reward distribution, such as completing a certain activity, meeting specific qualifications, etc., and the corresponding rewards will be distributed to users.

[0102] In this embodiment, for example, to facilitate understanding of the implementation process of the multi-channel access module, as shown in FIG. Figure 4 As shown, Figure 4 This is a logical diagram of the multi-channel reach module provided in Example 1 of the present application. When a customer who meets the conditions at the upper level enters the multi-channel reach module, it is first determined whether the customer has set up 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 again determined separately 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 be distributed 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 to determine 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 are flowed out of the canvas and the number of people who failed to reach and flowed out of the canvas is recorded plus 1. At this point, the process checks whether this node is the last execution unit in the multi-channel reach module. (If the above determination indicates that reach is not configured, or that reward distribution or reach is not configured, the process proceeds directly to this node.) If it is the last execution unit, the process checks whether the "no exit after completion" feature is enabled. If so, the number of people waiting to exit the canvas after completion is recorded, plus one. An hourly poll is performed to determine if the configured wait time has expired. If so, the canvas is exited after completion, and the number of people exiting is recorded, plus one. (If the above determination indicates that no exit after completion is not enabled, the process proceeds directly to this node and exits immediately.) While recording the number of people waiting to exit the canvas after completion, new policies can be approved. Once approved, exit is implemented, and a check is made to determine whether a lower-level execution unit has been configured. If so, the policy controller waiting to exit is executed, and the number of people exiting is recorded, plus one. (If the above determination indicates that this is not the last execution unit, the process proceeds directly to this node.) Finally, the process flows into the execution unit module for processing.

[0103] In the technical solution provided in this embodiment, a process canvas management system is constructed, which triggers the behavioral events of existing users into the process canvas through the process entry module, and then distributes resources to existing users based on the diversion of the execution unit module into the multi-channel contact module, thereby accurately responding 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 of existing users, and realizing automatic contact and rapid response of data processing.

[0104] 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 described in detail later. 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.

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

[0106] 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.

[0107] It should be noted that the diverter can be a module for guiding users to different process paths according to preset rules or user behavior. When a customer flows into the diverter, the customer is diverted to the corresponding policy device according to the diversion rules.

[0108] The splitter component represents traffic control and distribution, providing functions such as proportional splitting, random filtering, flow control, and reach-result splitting. This enriches the canvas's application scenarios and provides flexible traffic management and control for existing user data processing plans. For example, proportional splitting can be used to set up simple AB experiments through the process canvas.

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

[0110] It's important to note that the policy component represents the unit that performs data processing actions for existing users. It can execute data processing instructions such as user screening, user tagging, bonus distribution, campaign distribution, and user engagement. Policy attributes primarily consist of a basic information component, a user screening component, a user tagging component, a reward (bonus) distribution component, and a user touchpoint selection component. The policy can complete a set of data processing actions, with common scenarios including post-coupon notifications, proactive marketing campaign push, and quota and price adjustments.

[0111] The basic information component includes attributes such as the policy controller name, ID, priority, and whether it is the default policy controller. The default policy controller priority is the lowest priority in the same layer. A triggered default policy controller enters the default policy controller after the parent policy controller is executed and no other policy controllers in the same layer are triggered within a specified time.

[0112] After the user screening component is executed by the parent policy controller, if the user selection conditions of higher priority users at the same level are not met, the default policy controller will be entered.

[0113] The user tagging component can include tagging, default tagging, and custom tagging. Untagged refers to the default option, meaning no tagging is performed. Default tagging allows one-click tagging of customers entering the policy controller, including default tagging (for example, tagging using the canvas plus the policy controller ID), one-click addition to Event A list, and one-click addition to Event B list. Custom tagging allows custom tagging and custom tag values for customers entering the policy controller.

[0114] The Reward (Benefit) Distribution Component distributes and associates backend benefits to customers who access the Strategist. Functions include backend coupon distribution, point distribution, quota adjustment, price adjustment, external benefit distribution, and linking to proactive marketing campaign pages. It supports multiple selections, including multiple campaign landing pages and different types of rewards. Benefits and associated activities distributed through the Reward Distribution Component can be linked to the Reach Component configuration. Information such as the name and quantity of the associated benefit, as well as the link and name of the associated activity, can be automatically retrieved and used as variables by the Reach Component. The Reward Distribution Component can be automatically bound to the Operations (i.e., data processing for existing users) plan resource pool. Relevant reward or campaign landing pages are automatically associated and bound to the data processing plan, and can be presented and managed within the Operations plan resource pool. The Reward Distribution Component can also be monitored by the data processing plan and automatically added to the data processing plan's data system. It can be linked to and managed through dashboards and metrics.

[0115] The user touchpoint selection component is used to reach customers and interact with them through messaging or information via in-site messaging, SMS, voice, external marketing, and resource placement. This time, we've added resource placement for the campaign landing page to the touchpoint selection component, and added a new linkage with the reward distribution component. This means that when selecting a touchpoint, you can link it to the reward configured by the strategy controller (or this canvas), automatically retrieve the reward's name, link, quantity, and other attribute variables, and pass them into the message template or resource placement, making touchpoint configuration more convenient.

[0116] In this implementation, the policy controller can make intelligent decisions to filter 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.

[0117] In a feasible implementation manner, the execution unit module 20 described in this embodiment also includes a delayer 23; the strategist 22 is also used to mark the user flow details after the diversion, and to determine whether the marked user flow details are set with delay conditions; the strategist 22 is also used to transfer the user flow details with delay conditions into the delayer 23; the delayer 23 is used to delay the transferred user flow details and transfer the corresponding user flow details into the strategist 22 at the end of the delay; the strategist 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.

[0118] It's important to note that a delayer can control the pacing of users' progression to the next step of a process by setting specific time intervals. It represents a waiting instruction and can execute delay instructions such as delaying for a specific period of time, delaying to a specified time, delaying to a relative time, or delaying to a specific day of the week based on data processing needs. Unlike the delay component in a policy controller, a delayer can have multiple policy controllers attached to it. A delayer is a separate policy node displayed independently on the canvas. Customer traffic flowing through a delayer is not counted towards the policy controller's inflow. This helps balance system load, avoid congestion during peak hours, and provides users with appropriate buffer time, improving the user experience.

[0119] 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. According to the delay mode configured in the delayer, the incoming customer waits for the delay to end, and after the delay ends, the customer flows into the node where the delay is completed. When the customer flows into the policy device, the details of the customer flow out of and into the current policy device are recorded, and then the delay, reward distribution, and user contact are performed according to the configuration of the policy device. The use of delayers and policy devices helps to achieve personalized services, meet the specific needs of different user groups, optimize resource allocation, and improve overall data processing efficiency.

[0120] 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.

[0121] 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.

[0122] For ease of understanding, refer to Figure 6 , Figure 6This is a logical diagram of the execution unit module provided in Example 2 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 to the delayer or policy maker according to the rules of the diverter. When the customer flows into the policy maker, determine whether it flows 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, record the number of people flowing into the policy maker plus 1, and record the time of inflow. At this point, it can be determined whether a delay has been set. If so, the number of people who have completed the delay plus one is recorded (when the above-mentioned customer flows out of the upper node and directly into the delayer, the number of people who have entered the delayer plus one is recorded, and the delay ends. When the delay ends, the node "Record the number of people who have completed the delay plus one" is entered). The number of people who have completed the delay and are waiting to flow out is also recorded plus one. After the delay is determined, the policy controller determines whether the customer has set up reward distribution or reach. If so, it enters the multi-channel reach module to execute the reward distribution or reach. After execution, the number of people who are waiting to flow out of the canvas is recorded plus one.

[0123] 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.

[0124] The data flow dashboard (which stores statistical time and inflow times for each process) allows for daily storage of process data slices for key processes, including entry conditions (e.g., planned inflows, matching rules, and actual inflows), delayers (e.g., inflows, delays, pending outflows, and outflows), policymakers (e.g., inflows, outflows, delays, intercepted counts before triggering, and other policymaker-related data), and execution unit judgments (e.g., total outflows at the parent execution unit, intercepted counts, target outflows achieved, and actual total inflows to subordinate execution units). This allows for daily archiving of data slices within a specific timeframe. These data slices cover key processes, including entry conditions, delayers, policymakers, and execution unit judgments. This daily storage effectively manages data volume and improves query efficiency, while ensuring that all key process details are fully preserved, providing a solid foundation for subsequent data analysis and historical review.

[0125] 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 best service that meets their needs, thereby improving user satisfaction and conversion rate.

[0126] For example, to further understand the execution process of the process canvas, Figure 3 Take the example of the high priority occupancy judgment, customer occupancy logic, and overall data statistics logic to explain. Figure 3 In the , the logic for high-priority occupancy judgment refers to the canvas priority. Priority attributes can be configured based on customer willingness, behavior and demand insights, business lines, lifecycles, demand creation, and other categories. When the types are consistent, the canvas priority configured in the canvas can be viewed and judged numerically. The larger the value, the higher the priority. When the values are consistent, the priorities are consistent, and customers with the same priority cannot be snatched away. When a high-priority canvas snatches a customer, it flows out of this canvas in real time, and the policy engine stops delaying, rewarding, and reaching out to the customer. The results of the sent events continue to be captured, and the target completion status continues to be monitored. When the target event of the outflow canvas is completed, it flows out of this canvas in real time, and the policy engine stops delaying, rewarding, and reaching out to the customer. The results of the sent events continue to be captured, and the target completion status continues to be monitored.

[0127] Among them, the customer occupation logic means that the customer is occupied by the canvas from the time they actually enter the canvas and is released from the time they exit the canvas. The canvas exit rule means that only customers who enter the canvas will exit. When the canvas ends at 24:00, users in the canvas exit. The canvas exits when the canvas completes its goal and the target configuration allows users to exit the canvas after completing the goal. The canvas exits when the policy controller fails to distribute rewards. The canvas exits when the policy controller fails to configure reach. When a high-priority canvas occupies the customer, the customer exits the canvas in real time. When the canvas is executed, if no delayed exit is set, or when the exit time is reached, the customer exits the canvas.

[0128] The overall data statistics logic described above includes data timing and results. This includes real-time updates of the cumulative number of entries and the cumulative number of triggers in the data statistics results, as well as T+1 updates of the number of people who have completed the target and the target completion rate. For example, using the trigger-complete A task as an example, if the task starts between January 1st and January 7th, the user must have completed event A more than twice or event B more than three times. Multiple attempts are allowed. The target is set to complete event A within one day of entering the process. If 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 first entry at the second A, and all A's from the third A onward are counted towards the target completion; the second entry at the third B, and the third entry at the fifth A. Since valid data is returned T+1 after 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 from the previous few days will be corrected. The above number of times, after deduplication by person, is the number of people counted. For example, the number of people reached is the result of deduplication of the number of reaches by person. Filtering should be supported by sending time, policy controller, and reach method. If the reach method is SMS, the information will include the corresponding number of times and people.

[0129] For example, in order to help understand the function of the process canvas management system obtained by combining this embodiment with the above embodiment 1, please refer to Figure 8 , Figure 8 This is a scenario flow chart for implementing data processing of existing users through a process canvas management system provided in Example 2 of this application, specifically:

[0130] 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 (users who have never withdrawn cash after being granted a loan product) in customer lifecycle data processing scenarios. In full lifecycle scenarios, the goal of data processing is to identify marketing models, match corresponding solutions, and recall customers through proactive marketing in key scenarios. This can be mined based on current transaction conditions. Entry conditions can include: for customers at login and withdrawal breakpoints, if the application is not completed within 10 minutes, they will enter the canvas process. Key strategies can include: testing the responsiveness of customers who encounter this event to discounts, stratifying customers through marketing models such as competitive credit models, gradually increasing the strength of coupons based on the duration of the event, and simultaneously integrating robot and manual telemarketing to reach customers, and further optimizing strategies based on breakpoint conversion rate data.

[0131] like Figure 8As shown, the process canvas management system processes data for customers who have never withdrawn their funds. When the process canvas management system begins executing, customers who have never withdrawn their funds are added to the process canvas. At this point, the data processing strategy for these customers is determined based on the credit limit or interest rate matching model. These data processing strategies are categorized into two main categories: current credit limit less than the competitive credit limit, and current credit limit greater than or equal to the competitive credit limit. For cases where the current credit limit is less than the competitive credit limit, the data processing strategy can be categorized as follows: current interest rate greater than the competitive interest rate (the data processing strategy is credit limit adjustment, interest rate reduction, and loan discounts), and current interest rate less than or equal to the competitive interest rate (the data processing strategy is credit limit adjustment plus loan discounts). For cases where the current credit limit is greater than or equal to the competitive credit limit, the data processing strategy can be categorized as current interest rate greater than the competitive interest rate (the data processing strategy is business-side price adjustment plus loan discounts), and current interest rate less than or equal to the competitive interest rate (the data processing strategy is regular notification plus loan discounts). This strategy primarily utilizes data processing tools such as competitive credit limit models to stratify customer data, and leverages follow-up marketing response models and external value models to match user rights and outreach methods (e.g., if the customer is externally medium-to-high value and has a medium or high marketing response level, manual telemarketing is used; if the customer is externally low value and has a medium or high marketing response level, AI robot telemarketing is used; if the customer is externally low value and has a low marketing response level, manual telemarketing is used). Finally, the process canvas management system is used. Additionally, when a customer makes their first withdrawal, a limited-time cash red envelope reward can be activated, further increasing conversion rates through targeted outreach. The entire strategy aims to increase the borrowing willingness and conversion rate of silent customer groups through precise data processing.

[0132] 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". By abstracting the essential scenarios of data processing, building architectural solutions, establishing powerful strategy combinations and computing capabilities, and automatically adjusting configuration parameters, it can achieve automatic implementation and rapid response of strategies.

[0133] 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 life cycle data processing scenarios, credit and withdrawal full process exit and breakpoint operation scenarios, and online activity operation scenarios. Among them, the customer life cycle data processing scenario is a quantitative management system based on the customer life cycle, including first-time borrowing promotion scenarios, active promotion scenarios, repeat borrowing promotion scenarios and secondary credit promotion scenarios. 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 contact, marketing, member management and other means. At the same time, combined with risk strategies such as adjustment of credit limit, re-inspection, pre-credit, etc., 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 the customer life cycle data processing scenario, such as Figure 8As shown, by analyzing the profile of users who have not withdrawn their loan after being granted credit, combined with model predictions, targeted short-term and medium-term strategies have been developed to encourage withdrawals. Comprehensive anti-fraud measures have also been implemented to enhance risk prevention and control, including data processing and risk support strategies. These strategies, such as promoting promotional information and providing exclusive channels, encourage price adjustments and limit adjustments to improve withdrawal conversion rates. Strategies are adjusted promptly by observing lifecycle cycles, model predictions, and conversion attribution models. For example, if a customer's churn score indicates that their original credit limit is greater than or equal to Y and their credit limit utilization rate is 0%, an immediate 30% increase in the regular credit limit is applied, along with a ¥N discount. If the customer subsequently makes a withdrawal and their churn score is high the following month, an immediate 50% increase in the regular credit limit is applied, along with a ¥N plus ¥1 discount. If the customer subsequently withdraws their loan, their status becomes stable. The data processing scenarios for exit and breakpoints throughout the entire credit granting and withdrawal process focus on customer needs. By integrating key application submission and first-time withdrawal behaviors on the customer acquisition side, we identify the application submission and first-time withdrawal exit nodes. When users reach exit or breakpoints in the main process, we promptly expand post-exit or breakpoint services and establish an exit data processing system. For customers who exit or breakpoint, we explore and explore user scenarios and provide follow-up services to high-intent users with preferential interest rates to encourage them to return and complete business conversions. Through user surveys, we understand the reasons for user exit or breakpoints and their actual expectations, match them with better products and services, optimize the application submission and withdrawal processes, and ensure process efficiency. The data processing scenarios for online activities focus on building a financial loan product system around credit products. We launch quarterly inclusive themed festivals, weekly and monthly recurring inclusive activities, and special inclusive activities for birthdays, homecomings, and sharing events to support various marketing activities. For example, if you borrow 100 yuan, you can earn 1g of credit, with 100g worth 1 yuan. This credit is credited to your account in real time, and customers are prompted to use it as soon as possible before the loan expires. At the same time, a new task component is added to the marketing activity component to enrich the acquisition marketing scenarios. In the acquisition and consumption sections, new scenarios such as interaction, lottery, and deduction are added, and the previous task types and redemption benefits are reorganized. Other application scenarios are also possible and are not limited in this embodiment.

[0134] Regarding the above-mentioned improvement in the coverage of customer lifecycle data processing scenarios, the main focus is on the number of touch intentions in each scenario, the frequency of touch; the complaint rate; the number of strategy branches in each scenario; the conversion rate of a single touch; the duration of strategy maintenance; the frequency of strategy iteration; and the 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-line touch strategy * bottom-line touch rate * bottom-line strategy click rate * bottom-line participation / login rate * bottom-line strategy withdrawal conversion rate * bottom-line strategy withdrawal approval rate).

[0135] To improve the effectiveness of data processing for exits and breakpoints throughout the entire credit granting and credit usage process, we focus on the credit grant exit intention, withdrawal exit intention, number of credit grant and exit strategy branches, single touch conversion rate, strategy maintenance duration, strategy iteration frequency, and strategy complaint rate. The credit exit strategy response rate is calculated as follows: average daily number of credit grant exit customers * (∑ intent hit rate * reach rate * participation / login rate * application acceptance rate * credit approval rate + cover intention hit rate * cover strategy reach rate * cover strategy participation / login rate * cover strategy application acceptance rate * cover strategy credit approval rate); the withdrawal exit strategy response rate is calculated as follows: average daily number of withdrawal exit customers * (∑ intent hit rate * reach rate * participation / login rate * withdrawal rate * withdrawal approval rate + cover intention hit rate * cover strategy reach rate * cover strategy participation / login rate * cover strategy withdrawal rate * cover strategy withdrawal approval rate).

[0136] To improve the effectiveness of online campaign data processing, consider the number of customers covered by campaigns by cycle (week / month / quarter / year); campaign launch frequency; campaign execution time; average marketing cost per customer; campaign complaint rate; and campaign response rate (∑ campaign exposures * campaign login rate * campaign participation rate * campaign attribution credit or application acceptance rate / total customer base capacity).

[0137] By implementing data processing for each of the aforementioned scenarios through the Process Canvas Management System, customer insights and analytical feedback can be achieved. Customer insights refer to establishing a rich, comprehensive, and complete customer tag center based on big data mining and analysis capabilities, conducting in-depth user behavior analysis, integrating user data with business transaction data, and covering information such as customer identity, asset status, purchasing preferences, value potential, and behavioral tendencies. This creates data-driven customer profiles, enabling the characterization and insight into individual customers and customer groups. Various marketing models can be fully utilized to achieve deep insights into customer value and intelligently upgrade marketing models, thereby enhancing marketing precision. Analytical feedback refers to empowering marketing personnel at all levels through data processing and analysis tools. By streamlining online and standardized business processes, a holistic presentation of performance and operations is provided, providing managers with a basis for digital decision-making. Optimizing data access mechanisms provides data analysts with fast and convenient data resources, improving the timeliness of data processing and analysis responses. 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.

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

[0139] Based on the above process canvas management system, the present application embodiment provides a process canvas management method, referring to Figure 9 , Figure 9 This is a flow chart of the first embodiment of the process canvas management method of this application. The process canvas management method is applied to the above-mentioned process canvas management system, which includes a process entry module, an execution unit module, and a multi-channel access module.

[0140] In this embodiment, the process canvas management method includes steps S10 to S40:

[0141] Step S10: When a behavioral event of an existing user triggers a preset contact 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.

[0142] 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 directed 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 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.

[0143] 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; the process entry module transfers the user flow details of the existing user into the process canvas according to the preset hit rules when the existing user belongs to the audience user group.

[0144] 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 prioritized, thereby maximizing the overall efficiency 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, it is determined 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 processed as not flowing into the canvas. If the existing user meets the entry conditions, the customer is processed 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 priorities 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 node of the user 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.

[0145] 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 rules 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 entry module intercepts the planned inflow user according to the preset hit rules, and the hit rules include non-operational interception, risk control rule interception and priority occupation interception; the process entry module regards the planned inflow user that is not intercepted as the actual inflow user, and transfers the user flow data of the actual inflow user into the process canvas.

[0146] It should be noted that the planned inflow user can be the user who is scheduled to flow into the process canvas when the entry conditions (i.e., the task type) are met. The actual inflow user is the user who actually flows into the process canvas when the hit rule is not met.

[0147] Among them, considering the logic and efficiency of the process canvas management system in processing tasks, the importance of tasks can be differentiated based on the importance of business goals, the urgency of user needs, and the availability of system resources, and task priorities can be scientifically divided (priority occupation interception) to ensure that critical tasks are handled first, thereby maximizing the overall benefits of the process and user satisfaction. At the same time, taking into account 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) and prevented from continuing the process canvas. When the behavior of existing users violates regulations, poses 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).

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

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

[0150] In the specific implementation, Figure 2 As shown, the diversion delay strategy can buffer 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).

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

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

[0153] 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 for multi-channel reach configuration.

[0154] For ease of understanding, let's assume a user logs into the app and browses a product. Three hours later, the process canvas management system automatically sends a message (with a limited-time coupon) to facilitate user conversion. Seven days later, the process canvas management system automatically executes an on-site review of the canvas, asking for product reviews and willingness to spend. For users who highly rate the product or show willingness, a text message is automatically triggered to guide them to withdraw cash. The subsequent actions of the above channel contact are used to set the next contact node.

[0155] In this embodiment, after the multi-channel reach module distributes resources to existing users according to the user flow details, the existing users to whom 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.

[0156] 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 existing users, thereby accurately responding to various behavioral events of existing users, avoiding the current data processing method of existing users, where various activities are messy and isolated, and the user's interactive feedback 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.

[0157] 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 the above-mentioned embodiment 1 can be referred to the above introduction and will not be repeated later.

[0158] As an embodiment, the execution unit module includes a diverter and a policy device; the step S20 includes the steps of: the diverter performs scenario 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 user flow details that pass the screening meet the reward distribution conditions or the reach conditions; the policy device transfers the user flow details that meet the reward distribution conditions or the reach conditions to the multi-channel reach module.

[0159] As an embodiment, the execution unit module also includes a delayer; the step of the policy device screening 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 into the delayer; the delay device delays and waits for the transferred user flow details, and transfers the corresponding user flow details into the policy device at the end of the delay; the policy device determines whether the user flow details at the end of the delay meet the reward distribution conditions or the reach conditions.

[0160] As an embodiment, 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.

[0161] As an embodiment, after the step of the multi-channel reach module again judging whether the transferred user flow details comply with the hit rules, it also includes: when the transferred user flow details do not comply with the hit rules, the multi-channel reach module judges 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 judges 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.

[0162] The process canvas management method provided in this application is implemented based on the process canvas management system described in the aforementioned embodiments. Compared to the prior art, the process canvas management method provided in this application achieves the same beneficial effects as the process canvas management system described in the aforementioned embodiments. Other technical features of the process canvas management method are the same as those disclosed in the aforementioned embodiments and are not further elaborated here.

[0163] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application 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 to 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 further configured to transfer existing users to which resource allocation has been completed out of the process canvas; Among them, the process entry module is also used to determine whether the behavioral event of the existing user triggers a preset contact task type. The contact task type includes a scheduled task and a triggered task. The scheduled task includes a scheduled-single type and a scheduled-repeated type. The triggered task includes a triggered-completed A type and a triggered-completed A but not completed B type. When the behavioral event triggers the scheduled task or the triggered task, it is determined whether the existing user belongs to the audience user group. The audience user group is provided with three audience user attributes: label and behavior circle selection, existing grouping, and unrestricted. When the existing user belongs to the audience user group, the user flow details of the existing user are transferred to the process canvas according to the preset hit rule. Among them, the process entry module is also used to treat the existing users as planned inflow users when the existing users belong to the audience user group; record the user flow details of the planned inflow users, the user flow details include flow location, flow type and flow subclassification, and intercept the planned inflow users according to preset hit rules, the hit rules include non-operational interception, risk control rule interception and priority occupation interception; if the hit rule is hit, the number of non-operational interception people will increase by 1, or the number of risk control rule interception people will increase by 1, or the number of people who cannot flow in due to high priority canvas occupation will increase by 1; the planned inflow users that are not intercepted will be regarded as actual inflow users, and the user flow data of the actual inflow users will be transferred to the process canvas; Among them, the functions of the multi-channel contact module include pre-strategy execution processing, reward distribution execution, customer contact execution and strategy execution completion processing; the multi-channel contact module is also used to re-determine whether the transferred user flow details meet the hit rules; if they do not meet the hit rules, rewards are distributed to the user flow details corresponding to the user flow details that do not meet the hit rules; when the reward distribution fails, it is determined whether the user to be operated corresponding to the user flow details is the contact user; if it is the contact user, a communication reminder is sent to the contact user; The multi-channel reach module is also used to determine whether the customer has set reward distribution or reach when the customer who meets the conditions at the upper level enters; if reward distribution or reach is set, the hit rule judgment is performed, the hit user flows out of the process canvas and the number of outflows is recorded plus 1; for the user who is not hit, it is again determined separately whether reward distribution is set, if reward distribution is set, reward distribution is performed, and the nodes when reward distribution starts and reward distribution is completed are recorded; if distribution fails, the user who failed distribution flows out of the process canvas and the number of outflows is recorded plus 1; it is then determined separately whether reach is set, and if it is set, If the node is reached, the reaching operation will be started and the nodes where the reaching starts and ends will be recorded. If the reaching fails, the users who failed to be reached will flow out of the process canvas and the number of users who failed to flow out of the canvas will be recorded plus 1. When the node is the last execution unit, it will be determined whether the setting of "no flow after completion of execution" is set. If the setting of "no flow after completion of execution" is set, the number of users who have completed the execution and are waiting to flow out of the canvas will be recorded plus 1, and polling will be performed once an hour to determine whether the configured waiting time has been reached. If the configured waiting time has been reached, the execution will be completed and the flow out of the canvas will be recorded, and the number of users who have flowed out will be recorded plus 1. Until the node flows into the execution unit module for processing.

2. The system according to claim 1, wherein The execution unit module includes a diverter and a strategy device; The splitter is used to split the user flow details flowing into the process canvas by scenarios, and transfer the split user flow details to the policy device; The policy device is used to filter the user flow details after the diversion; The policy controller 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 into the multi-channel reach module.

3. The system according to claim 2, wherein: 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 configured 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 strategist is further configured to determine whether the delayed end user flow details meet the reward distribution conditions or reach conditions.

4. A process canvas management method, characterized in that: The process canvas management system according to claim 1 implements the process canvas management method, the system comprising a process entry module, an execution unit module, and a multi-channel access module; the method comprising: 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 to 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 contact 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 who have completed resource allocation out of the process canvas; Among them, when the behavior event of the existing user triggers the preset reach task type, the process entry module transfers the user flow details of the existing user into the process canvas, including: the process entry module determines whether the behavior event of the existing user triggers the preset reach task type, the reach task type includes a scheduled task and a triggered task, the scheduled task includes a scheduled-single type and a scheduled-repeated type, and the triggered task includes a triggered-completed A type and a triggered-completed A but not completed B type; when the behavior event triggers the scheduled task or the triggered task, determines whether the existing user belongs to the audience user group, the audience user group is provided with three audience user attributes: label and behavior circle selection, existing grouping, and no restriction; when the existing user belongs to the audience user group, the user flow details of the existing user are transferred to the process canvas according to the preset hit rule; Among them, the step of transferring 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 includes: the process entry module regards the existing users as planned inflow users when the existing users belong to the audience user group; records the user flow details of the planned inflow users, the user flow details include the flow position, flow type and flow subclassification, and intercepts the planned inflow users according to the preset hit rules, the hit rules include non-operational interception, risk control rule interception and priority occupation interception; if the hit rules are hit, the number of non-operational interception people increases by 1, or the number of risk control rule interception people increases by 1, or the number of people who cannot flow in due to high priority canvas occupation increases by 1; the planned inflow users who are not intercepted are regarded as actual inflow users, and the user flow data of the actual inflow users are transferred to the process canvas.

Images