WHMCS automation is the reason most hosting companies buy WHMCS in the first place, yet many installs run on the default settings for years. Those defaults are a reasonable start, but they weren’t chosen for your business. A few minutes spent on the right settings can mean fewer late payments, fewer awkward suspension emails and a lot less manual work. Here are the settings we think every hosting business should review.
Where to Find the WHMCS Automation Settings
In current versions of WHMCS, go to System > Automation > Automation Settings. Older versions list it under System Settings. Everything below lives on that one page. For the full list of options, see the official WHMCS automation settings documentation.
None of it works without the cron job, so check that first. WHMCS recommends running the cron every five minutes, and the automation status page shows when it last ran. If you haven’t set it up yet, our WHMCS cPanel setup guide covers it in Step 5.
1. Invoice Generation
This WHMCS automation setting controls how many days before the due date WHMCS creates a renewal invoice. Too short, and customers don’t have time to pay before the due date. Too long, and the invoice gets forgotten. Somewhere between 7 and 14 days works well for monthly hosting. For yearly plans and domains, a longer lead time gives customers time to budget.
2. Payment Reminders
Turn on the unpaid invoice reminder so customers get a nudge before the due date, not just after it. A friendly heads-up a few days ahead prevents more late payments than any overdue notice. This is one of the simplest WHMCS automation wins.
3. Overdue Notices
WHMCS can send up to three overdue reminders at intervals you choose. A common pattern is 1, 3 and 7 days after the due date. Edit the email templates too, so they sound like your business and clearly explain what happens next and how to pay.
4. Late Fees
Late fees are optional. They can encourage on-time payment, but they can also annoy good customers who simply missed an email. If you use them, set a grace period of a few days first and mention the fee in your terms of service so it’s never a surprise.
5. Automatic Suspension
Suspension is where WHMCS automation saves you the most awkward conversations. Choose how many days after the due date an unpaid service gets suspended. Too quick feels harsh; too slow means hosting people for free. Many hosts settle on somewhere between 5 and 14 days. Turn on the suspension email so the customer knows exactly why their site is down and how to fix it.
6. Automatic Unsuspension
Always turn this on. When a suspended customer pays, WHMCS brings their account back right away, even at 2 a.m. on a Sunday. Without it, a paying customer stays offline until someone notices, and that’s how you lose them.
7. Automatic Termination
Termination deletes the account and its data from the server, so it can’t be undone. Leave plenty of time, often 30 days or more after the due date, and make sure your backup policy is clear before you turn it on. Some hosts prefer to leave termination off and handle it by hand; that’s a reasonable choice for a small business.
8. Card Payment Retries
If you take card payments through a gateway that stores cards, WHMCS can charge saved cards a set number of days before the due date and retry failed charges. Charging a few days early gives customers time to update an expired card before anything is overdue. Retrying failed charges for a week or so recovers many payments that fail for temporary reasons.
9. Closing Inactive Support Tickets
WHMCS can close tickets automatically when a customer hasn’t replied for a set number of hours. This keeps your ticket queue focused on open problems. Pick a window long enough that customers aren’t cut off mid-conversation; 48 to 72 hours is common.
WHMCS Automation Beyond the Settings Page
The settings page covers billing and support, but WHMCS automation can go much further:
- Provisioning modules create accounts the moment an order is paid. See how they work in our guide to WHMCS provisioning modules.
- Hooks let you run your own code when something happens, like logging a payment or alerting your team about a large order. Our WHMCS hooks guide has examples.
- Self-service tools cut support tickets before they’re opened. A community forum, like our WHMCS Client Forum, lets customers answer each other’s common questions.
A Quick WHMCS Automation Checklist
- The cron job runs every five minutes and shows a recent run time.
- Invoices go out early enough for customers to pay on time.
- Reminders go out before the due date, and overdue notices after it.
- Suspension has a fair grace period and sends a clear email.
- Unsuspension is turned on.
- Termination is either off or set well after suspension, with backups in place.
- Your email templates sound like your business, not the defaults.
Frequently Asked Questions
Why isn’t WHMCS automation running?
Almost always because the cron job isn’t running or is failing. Check the last run time on the automation status page, and make sure the cron command in cPanel matches the one WHMCS shows.
Can I stop one customer from being suspended?
Yes. Open the customer’s service and tick the option to exempt it from automatic suspension. It’s useful for trusted customers who pay by check or on custom terms.
How often should the WHMCS cron run?
WHMCS recommends every five minutes. Daily tasks like invoicing and suspensions still only run once a day, at the time you set, but other tasks need the more frequent runs.
Want WHMCS to Do More?
If there’s a task you still do by hand every week, there’s a good chance it can be automated. We build custom WHMCS modules and hooks for exactly that. Browse our WHMCS addons, or tell us what you’d like to automate.
