By setting the task priority when you create a task, you can control the order in which users can reach users between tasks and through different channels within a task. You can also summarize and display data in the task management list.
Task management
Feature overview
1) Task priority
Task Type: Single Task and MA Task
Single-task: one-time, single-channel, batch-reaching users
MA Task: Multi-channel User Touch with Process Logic
2) Priority values and meanings:
1 to 10 (from high to low, 1 is the highest, 10 is the lowest), do not participate (default)
Tasks with a higher priority are executed first. Tasks with a higher priority are executed first. Tasks with the same priority are executed in parallel. During the execution, the low-priority task is stopped. After all the tasks are completed, the execution of the stopped low-priority task is resumed (regular touch users), and so on.
The result (success or failure) of a high-priority task on a user touch is consumed by fatigue. When a subsequent low-priority task is executed, it determines whether to continue to touch the user based on the current fatigue.
After the task is submitted and takes effect (some tasks need to be approved and take effect), including: immediate execution, waiting to be executed, and scheduled cycle execution. Once the task takes effect, the priority takes effect synchronously.
For example, if there is a new store opening activity the next day and a "high" priority short message group sending task is submitted at 17:00 p.m. today (a short message is sent at 9:00 am the next day), the "medium and low" priority tasks will be stopped after 17:00 today and will be resumed until the short message task is completed the next day.
The execution of a task that is configured as "do not participate" priority does not stop any other task, nor is it stopped by any task. (Service notification class, or emergency class touch user)
For example, in the scenario of reminding of the expiration of customer points, this task is suitable for configuring a long-term regular running MA task, in order not to be affected by other tasks, not to cause losses to the customer, can remind the customer in time, it is not necessary to participate in priority control between other tasks.
The same logic: If a task is executed for a long period of time, we recommend that you do not configure the "high" priority, which will cause other low-priority tasks to stop running.
Configuration steps
Create a task:
1) User marketing
SMS: Creating a Sending Task
Yu Yang Chaoxin: Joint Marketing Task, Own Signature Task
WeChat Public Number: Create and Send Tasks (Type 3 Ordinary Tasks)
WeChat applet: Create a new sending task
Email: Create Send Task
PUSH: creates a push task.
Webhook: Create a sending task
The following figure takes the creation task of Hillock YangChaoxin as an example.
2) Automated marketing:
New Marketing Campaign
Channel priorities in automated marketing tasks
1) Channels are executed in sequence.
2) Determine whether to use the next channel to reach users based on the channel reach results in sequence:
Priority Management
1) Display Portal: User Marketing-Marketing Management-Task List
2) List display task scope:
Only tasks that have taken effect appear (take effect after submission or approval)
