Before you start
- The client has been connected to multiple enterprise-owned WhatsApp test accounts.
- The accounts and test content participating in the task have been authorized to use accordingly.
- Administrators or team members have setting rights for the current maintenance task.
Where to find it
Employee client → account maintenance; administrator admin console → account maintenance management → account maintenance strategy, account maintenance material management, account maintenance behavior record, account maintenance statistics.
Make it clear what this feature does #
The "account maintenance" module in the interface allows you to configure the content and schedule of automated interactions between accounts. Configuration items and execution checks are described here to make it easier for enterprises to verify tasks across their own test accounts. The name does not represent the platform-approved account maintenance method, nor does it promise to improve account credibility or avoid restrictions.
Before starting, list the participating accounts and their uses, and first confirm that these accounts can log in and send and receive normally. Don’t mix disconnection repair, authorization recovery and maintenance tasks together: account connection failures should be handled first according to the login and message troubleshooting process.
Prepare task content #
- Open the corresponding material management page of "account maintenance material" or admin console.
- Enter text for testing. The screenshot prompt text can be organized by line, and an entry for batch uploading of images is provided.
- Check whether the content is suitable for sending to the selected test account and avoid including customer information or irrelevant business information.
- If you choose to use company materials, first confirm the content of the currently shared materials with the administrator; the interface switch will affect the actual data source used.
Check the policy before starting #
The "account maintenance strategy" screenshot shows settings such as start time, chat start and end time, message sending interval, whether to use company materials, interaction methods, daily number of messages sent, and account selection. Fill in according to the current interface and enterprise task specifications, first use a small-scale test for easy verification, and do not copy the example values.
- Check the task start time and the time period allowed for daily execution.
- Check the content source, interaction method and participating accounts; the information shows the selection method of participating or blocking customer service accounts, and pay attention to the direction of selection.
- After saving the settings, use the startup operations provided on the current page. The client entry in the screenshot is "Start account maintenance".
- When administrators configure the admin console policy, they must first confirm which front-end accounts are being executed and coordinate with team members to avoid repeating tasks.
Judge results based on records and actual messages #
After the configuration is saved, check the "account maintenance statistics" or admin console behavior records, and then check the actual messages between the test accounts to confirm that the sending time, content source, and account selection match the settings. The manual does not fully provide the rules for interruption recovery, failure retry or offline execution; when missing, the current task status should be retained, and the online and configuration conditions should be checked first, without inferring that the task has been completed.
Check your result
- The time and materials in the strategy are consistent with the participating accounts and test plan.
- The corresponding execution status can be viewed in the task record.
- The specified test account actually received the expected content; it was not sent to non-test accounts.
Frequently asked questions
Can account security be ensured by setting up account maintenance tasks?
No. The manual shows automated task configurations and does not provide verifiable guarantees of account security or reduced restrictions. It should be used according to actual business needs and platform rules.
Both the client and admin console can be set up, who should be responsible?
The enterprise should clearly identify the person responsible for the main configuration. The administrator first confirms whether there are tasks in the admin console, and then the team members check the front-end account and execution status to avoid repeated configuration.
What should I do if I save the strategy but there is no message?
First check whether the task has been started, whether the time period is met, whether the selected account is online, and whether the material source is correct, and then check the behavior record. The information does not provide general failure codes and retry rules.
According to pages 38, 39, 40, and 41 of the "2026-SalesEpoch Operation Manual".
Menus and features may vary by client version or account access. Follow the current interface and verify critical workflows with a test account first.