Selling your first reseller hosting account is exciting. Onboarding it badly is how new resellers lose customers in the first 30 days. This article walks through a clean onboarding workflow — pre-sales, account creation, welcome materials, and the first-week support cadence that keeps clients happy.
Pre-sales: the conversation before payment
Before charging anything, ask three questions:
- What are you hosting? Static brochure site, WordPress blog, e-commerce store, web app? This determines tier sizing and which features matter.
- Are you migrating from another host? If yes, get the existing host's name, the cPanel URL (if any), and credentials. Free migration is a closer.
- Do you manage your own domain? If they're on a registrar that requires unfamiliar DNS changes (Squarespace, Wix-bundled domains), warn them now. This is the biggest onboarding pain point.
Pricing should already be clear from your sales page. Don't haggle — if your tiers are sane, customers either fit one or they don't.
Account creation
Once payment clears, the actual setup is fast:
- Log in to WHM.
- Account Functions → Create a New Account.
- Fill in:
- Domain: their primary domain
- Username: automatically generated; you can override
- Password: use the auto-generate button — produces a strong unique password
- Email: their contact email
- Package: the tier they bought
- Tick Send the account information email. WHM emails them their cPanel URL, username, and password automatically.
- Click Create.
The whole process takes 30 seconds. If you've set up packages well, the account is correctly resourced from the moment it's created.
Customize the welcome email
WHM's default welcome email is functional but bland. Customize it once and every account creation uses your version:
- WHM → Server Configuration → Customize Email Templates.
- Select Account Information from the list.
- Edit the template. Add:
- A friendly greeting with your brand name
- The cPanel login URL with both the IP-based and domain-based options
- FTP/SFTP server details (host, port, username = cPanel user)
- Your support contact methods (ticket portal, email, hours of availability)
- A link to your knowledgebase or "getting started" page
- A reminder that DNS propagation takes 24-48 hours after they update nameservers
- Save.
This single step prevents about 40% of first-week support tickets.
The first-week cadence
Don't just wait for tickets — reach out proactively at three points:
Day 1: Welcome + check-in
A short personal email or ticket within 24 hours of account creation: "Account is live, here are your details, here's how to reach me, want me to do anything to help you get started?" Even one in three responses turns into a meaningful relationship.
Day 3-5: Migration check-in (if applicable)
If they're migrating, check whether the migration completed and DNS has been updated. The "I forgot to change my nameservers" failure mode is shockingly common.
Day 14-21: Health check
"Everything running smoothly?" Three sentences max. Most won't respond, but the ones who do are the customers most likely to stay (or upgrade).
Set them up for self-service
Customers who can solve their own problems don't become tickets. In your welcome materials, include:
- A link to your knowledgebase (if you have one) or to ours.
- How to reset their cPanel password (cPanel Password & Security)
- How to add a new email account
- How to install WordPress if applicable
- What to do if their IP is firewalled
Common first-week pain points
- "My website isn't showing yet." They updated nameservers but DNS is still propagating, or they updated the wrong DNS panel. Talk them through testing with a temporary URL or hosts file.
- "My email isn't working." Almost always wrong server settings. Walk through SSL ports (993/465) and "use the full email address as username".
- "I get blocked when I try to log in." CSF firewall after multiple failed logins. Walk them through the firewall manager unblock process.
- "My SSL certificate is showing as not secure." AutoSSL hasn't completed yet. Wait for DNS to propagate then run AutoSSL manually.
Getting paid: WHMCS automation
If you're running WHMCS as your billing system (recommended), set up:
- Auto-suspend on overdue: System Settings → Automation Settings → suspend after 7 days overdue.
- Auto-terminate after extended overdue: 30 days. This protects your resources and signals seriousness.
- Late fees: 5% or $5, whichever is greater, after 5 days. Small enough to not antagonize, real enough to motivate payment.
Automation lets you treat suspension as a non-emotional process — the customer agreed to terms when they signed up.
