You've just sold a hosting plan to a new customer. Now what? Behind the scenes, a dozen steps have to happen before their website goes live—and a dozen more before they get their first invoice. If you're doing those steps by hand, you're burning hours on work that software can do in seconds. But not everything should be automated. This walkthrough follows a hosting account from signup to renewal to suspension and shows exactly which tasks the automation handles and which decisions still require a human.

This journal is published by Teculiar, hosted billing and provisioning software for hosting companies.

What happens at the moment a customer signs up?

When a customer places an order, the clock starts. The first thing that must happen is payment capture. If you sell through an online storefront, the payment gateway charges the card or processes the PayPal transaction automatically. The order status flips from "pending" to "paid" only after the payment is confirmed. If payment fails, the system should send a polite retry email—no human needed.

Once payment clears, the provisioning begins. Provisioning is the process of creating the actual hosting account on a server. Automation software connects to your server (often through an API) and runs the necessary commands: it creates the cPanel or Plesk account, sets up the domain, generates the DNS records, and sends the welcome email with login details. This all happens in seconds, and the customer can start building immediately.

What still needs a human? If the customer orders a custom configuration—say, a specific PHP version or a dedicated IP—you might need to manually verify that the server can support it. Also, if fraud screening flags the order, a human should review it before provisioning. Most automation platforms let you set rules: for example, automatically provision if the payment is verified, but hold orders from high-risk countries for manual review.

How does automation handle day-to-day account management?

Once the account is live, the recurring tasks begin. The most obvious is invoicing. On the billing cycle date, the system generates an invoice and sends it to the customer. If they pay automatically, the system records the payment and updates the account. If they don't, it sends reminders at set intervals—say, three days before the due date, on the due date, and three days after. All of this is automated, and you can customize the email templates to match your brand.

Another behind-the-scenes task is resource monitoring. Automation software can watch disk space, bandwidth, and CPU usage, and send a warning email when a customer approaches a limit. Offering an upgrade at that point is fine, but the decision to upgrade should always be the customer's, not the software's. Automation can notify, but it shouldn't force a plan change without consent.

Domain renewals are another area where automation shines. If you're a domain reseller, your platform can sync with a registrar API to check expiration dates and automatically renew domains before they lapse. It can also handle the transfer of DNS management to your own nameservers. The human touch needed here is rare, but when a domain is about to expire and the customer hasn't paid, you might want to manually decide whether to renew it out of pocket and bill them later, or let it drop.

What happens when a customer doesn't pay?

When an invoice goes unpaid, the system follows a grace period you define. After the due date, the account is still fully functional—this is your chance to collect. The automation sends reminder emails. If the invoice remains unpaid after, say, seven days, the system can suspend the account. Suspension is a technical action: it disables the website, blocks email, and locks the control panel. The customer sees a suspension notice when they try to visit their site.

But suspension is not a decision to automate lightly. You should set clear policies: how many days of grace, what happens to data, and whether you allow payment plans. The software can execute the suspension, but you should be the one who sets the rules and reviews exceptional cases. For example, if a customer calls and says they've had a family emergency, you might want to extend their grace period. That decision is human.

After suspension, the system can continue to send payment reminders. If the customer pays, the account is automatically unsuspended—the website comes back, email works again, and the customer gets a confirmation. If they don't pay after a final notice (say, 30 days), you decide what happens next. Disabling the service and keeping it for a retention period is safer than deleting it at once, and deleting is irreversible, so a person should always approve it. Teculiar follows the same rule: cancelling disables a service at the provider, and nothing is deleted on its own.

What about renewals and upgrades?

Renewals are the lifeblood of a hosting business, and automation makes them smooth. When a subscription is about to expire, the system generates a renewal invoice and attempts to charge the stored payment method. If it succeeds, the account continues without interruption. If it fails, the system sends a notification and retries after a few days. This cycle repeats until the customer updates their payment details or the account lapses.

Upgrades are a slightly different story. When a customer outgrows their plan, they often want to upgrade to a bigger one. Automation can handle the technical side—increasing quotas or adding resources. But the customer's choice of plan is a human decision. Your job is to make it easy: the automation can show upgrade options, calculate prorated charges, and provision the new plan once the customer clicks "upgrade." The human element is in the sales conversation, if there is one.

What decisions should always stay human?

Even with powerful automation, some decisions require judgment, empathy, or risk assessment. Here's a short list:

  • Fraud and abuse: If a customer uploads illegal content or launches a DDoS attack, you need to act fast—but you also need to be sure. Automation can flag suspicious activity, but a human should review the evidence before terminating an account.
  • Refunds and disputes: When a customer demands a refund, the system can process it, but you should decide whether to grant it based on your policy and the customer's history.
  • Exceptional support cases: If a customer's website is hacked, automation can restore a backup, but a human should guide them on securing their site.
  • Plan changes outside the norm: If a customer wants a custom configuration, you might need to manually provision it.

The key is to let automation handle the repetitive, rules-based tasks, and reserve human attention for the edge cases that require nuance.

What to do next

Now that you understand the lifecycle, audit your own processes. List every step from signup to suspension and mark whether it's currently manual or automated. Then think about which steps could be automated with the right tool. If you're looking for a platform that handles provisioning, billing, and domain management, look at Teculiar. And if you're just starting out, our documentation can help you get set up.

Automation isn't about removing humans from the loop—it's about giving you time to focus on the decisions that matter.