1. Open the intended website manager and select Automation. Confirm the domain and installation before editing a schedule.
2. Choose an available task, such as Automatic backups, Database clean-up, File check, Malware scan or Speed test.
3. Select the supported daily, weekly or monthly frequency and the relevant day and hour. Spread expensive tasks across your estate rather than scheduling every website together.
4. For automatic website backups, choose the retention count within the supported range. Review storage capacity and your separate disaster-recovery policy.
5. Save the schedule, then use Run now on a suitable test website where available.
6. Open History and confirm the result, completion time and any provider error.

Scheduled work uses the normal WHMCS cron. The service must be eligible and active, and account writes must not be paused for tasks that change account data. Check the server component behind each task before offering it.

Malware actions depend on the relevant Imunify360 integration and permissions. Speed testing needs the configured Google PageSpeed API key. A missing dependency should be resolved in the integration settings; repeatedly saving the schedule will not provide that capability.

Automatic backup retention applies to the automatic website backups managed by this workflow. It does not mean every manual backup or full account backup follows the same retention policy. Keep these backup types clearly named in staff and customer instructions.

Automatic update rules are a separate website policy. A maintenance schedule does not by itself define which WordPress core, theme or plugin updates should be installed.

Plan with AI can suggest a maintenance plan. Read the proposed tasks, timing and retention, then use Apply this plan only when it matches the website's needs. Review the saved schedule afterward. The suggestion cannot know every business event or third-party integration that makes a time unsuitable.

Check cron health, service status, paused writes, the saved schedule and the provider's response. Run a controlled manual test after correcting the cause. Preserve the error history so recurring capacity or permission issues can be fixed at their source.

• Configure and verify the WHMCS cron for Hosting Suite
• Define and test the backup scope of managed WordPress plans
• Set a WordPress update policy and validate changes in staging
• Enable optional website insights, malware and performance tools

• WHMCS: setting up the system cron
• cPanel: manage WordPress with WP Toolkit