Guide Reseller Hosting

How to create a hosting account for a client

Sizing the package, creating the account, and handing it to a client cleanly, from your reseller control panel.

Updated 8 min read Beginner

Creating a client account is the easy part of running a hosting business — it takes minutes once you know your process. The mistakes that cause problems later almost all happen before that: sizing the wrong package, skipping the nameserver decision, or handing over access without checking it actually works. This walks through doing it properly, not just doing it fast.

Decide the package before you open the control panel

Work out which of your existing plans fits this client — site size, expected traffic, number of mailboxes — before you touch anything. If none of your current tiers fit, that is a packaging problem worth solving properly rather than a reason to build a one-off configuration for a single client. See how to design the plans you sell if you find yourself doing this often; a business running dozens of bespoke configurations is much harder to support than one running three or four standard tiers.

Check the limits before you promise them

Never quote a client a storage, bandwidth or account allowance from memory. Confirm your reseller plan's actual current limits at /reseller-hosting or in your control panel before you put a number in an email — plans and their allowances change, and a promise you cannot keep is worse than no promise at all.

  1. Open your reseller control panel

    This is the reseller-level panel, distinct from the panel any individual hosting account gets. It is where packages and client accounts are both managed from a single place.

  2. Create the package, if you do not already have one

    Set the storage, bandwidth, email account allowance and domain limit for this tier. Name it something you will still recognise in a year — "Starter" and "Business" age better than a client's name or a one-off description.

  3. Create the account and assign it to the package

    Enter the client's primary domain and contact details. This is also where you set the account's username, so pick something consistent with how you name accounts generally — it will show up in file paths and database names, and an inconsistent scheme becomes a genuine headache once you have thirty client accounts to keep straight.

  4. Decide the nameservers

    If you have set up private, branded nameservers, this is where you point the client's domain at them instead of the platform's own. See how to set up private nameservers if you have not done this yet — it is worth doing once, early, rather than retrofitting it across existing clients later.

  5. Hand over access properly

    Send login details using your own template and branding, not a raw copy of anything generated by the underlying platform. This is the moment a client forms their first impression of how professional the hosting relationship is going to be.

  6. Test before you tell the client it is ready

    Load the domain, send a test email to and from the new mailbox if one was set up, and check the account shows the right resource limits. A client discovering a broken account themselves costs you far more credibility than the five minutes it takes to check first.

Set expectations at the same time you set up the account

Use the handover email to confirm what the client is getting: the plan tier, what support you provide and how to reach you, and where your terms of service and acceptable use policy live. This is also the point at which any migration work — moving an existing site onto the new account — needs to be scheduled and communicated, rather than left implicit. How to bring a client site onto your platform covers that process if this account is replacing an existing host rather than starting fresh.

Keep a record outside the control panel too

A simple spreadsheet or your billing software should track, per client: which package they are on, what they are paying, when it renews, and any non-standard terms you agreed. The control panel tells you what exists technically; it will not tell you what you promised somebody eighteen months ago. If you are running more than a handful of clients, this is exactly the gap that billing software like WHMCS is built to close.

When the client outgrows the account

Accounts do not stay the right size forever. When a client's site grows past its current package, how to upgrade or downgrade a client covers moving them cleanly rather than leaving a struggling site on a plan that no longer fits it.

None of this is complicated, but it rewards being consistent. A hosting business with a repeatable, checked process for creating accounts looks — and runs — like a considerably more established one than the size of the company might suggest.

Frequently asked questions

Should I create one package per client or reuse the same few packages?

Reuse a small number of standard packages. A handful of consistent tiers is far easier to price, support and upgrade clients between than a different one-off configuration for every account. Create a new package only when you have a genuine new tier to offer, not for a single client's specific request.

Can I create the account before the client has paid?

You can, but decide this as a policy rather than case by case. Most resellers provision after the first payment clears, particularly once billing is automated through software like WHMCS, which can create the account itself the moment payment is confirmed.

Related reading