SocialEpochHelp Center
Browse Help Topics
AI and automationFor: Administrator

Create One-Time, Triggered, and Recurring Campaigns

Select customers by shared tag or stage, configure content and sending accounts, and define customer-update conditions.

Page contentsBefore you startChoose the right task type firstSetting objects and executing team membersSet up messages and subsequent updatesValidate triggering results with a small rangeCheck your resultFrequently asked questions

Before you start

  • Have marketing automation management rights, and the executive team member has obtained the corresponding product qualifications.
  • The customer has agreed to receive this relevant information, and the public tags or customer stages have been sorted accurately.
  • The WhatsApp account used for execution has been logged in to the corresponding client; prepare internal test objects first.

Where to find it
SalesEpoch admin console → Marketing Interaction → Marketing Automation → New

Choose the right task type first #

typeUsage scenarios
single marketingExecute once for the specified customer group and end after the task is completed.
real-time marketingTriggered when the customer meets the specified public label and other conditions, such as entering the agreed service stage.
cycle marketingExecuted at a set period and time, such as sending service reminders to subscribed customers every week.

Real-time and periodic tasks will continue to affect subsequent customers, and the trigger range must be checked before creation. Don't just change the task name but keep the inappropriate execution type.

Setting objects and executing team members #

  1. Click "New", select the task type and fill in a name that is easy to identify.
  2. Select the public label or customer stage in "Select Customer Group" and then check the number of matching people. Personal team member tags are not a direct substitute for the public tags required here.
  3. Set the executor in the interface. This field corresponds to a team member, not a single customer; the execution scope also involves the WhatsApp account logged in by the team member, which should be checked in advance.
  4. Check settings such as "Execute all/Responsible person only", daily quantity, sending interval and "Specified execution". Parameters are determined according to corporate policies and the current interface, and fixed numbers or intervals are not regarded as account security guarantees.
  5. Check "Trigger"; screenshot example includes WhatsApp, equals and trigger content. The values ​​of different conditions should be filled in based on actual goals and do not apply other people's examples.
One-shot, real-time and cycle marketing; example names and performers blocked · Handbook page 61 · Click to enlarge

Set up messages and subsequent updates #

  1. Fill in the content to send. When you need a customer's title, use "Click to insert variable properties" to select a variable, and do not treat unknown placeholders as available variables.
  2. Add images as needed, first using a test client to check the variable values with the actual display. The information states that multiple pictures can be sent randomly, and you should avoid breaking up content that must be read at the same time into random material.
  3. Set "Complete automatic reach updates" to decide whether to update the account stage or label after sending.
  4. When you need to receive a reply before updating, check the conditions of "when receiving a reply from the customer" and the valid range indicated on the current interface.
  5. For periodic marketing, set the cycle and time separately; finally review the customer group, executor, content and update rules, and click "Confirm".

Validate triggering results with a small range #

First, let the designated test team member log in to verify whether the test customer meets the conditions, whether the correct message is received, and whether the stage or label is updated at the set time. There are two different results: the message has been sent and the customer has replied. The manual does not give complete rules for repeated triggering, offline reissue or failed retry, so do not promise that a customer will only receive it once, or that the task will still be completed on time when offline.

Check your result

  • The task type, matching customer groups and executing team members are in line with this goal.
  • The test client receives a message with correct content and normal variables.
  • The customer stage or label only changes as expected after the selected update conditions are met.

Frequently asked questions

Why can’t I find the team member’s own label in the customer group option?

This page's flow supports public tags or customer stages. Administrators and team members first unify public labels and then check for matching customers.

What should I do if the task is created but not sent?

First check the executing team member, the WhatsApp account the team member is logged in to, the designated execution end, customer group conditions and task status, and then check the specific prompts; do not directly increase the number and try again.

Can the customer stage be updated both when a reply is received and when the sending is completed?

The interface provides two types of update settings. The activation conditions should be checked separately to avoid premature or repeated modifications of the same business stage.