Latest Updates
WHM Reseller Setup Checklist: Create Your First Client Account Safely
WHM reseller hosting gives you a control panel for creating and managing customer hosting accounts, but a successful launch requires more than logging in and creating the first domain. Packages, permissions, nameservers, SSL, email,…
WHM reseller hosting gives you a control panel for creating and managing customer hosting accounts, but a successful launch requires more than logging in and creating the first domain. Packages, permissions, nameservers, SSL, email, backups, and support boundaries should be tested before you accept customers.
This checklist is designed for a reseller preparing a first client account. It focuses on account-level work available to a reseller and separates it from server administration that must be handled by the hosting provider.
1. Confirm what your reseller account can do
Reseller WHM is not the same as root WHM. Your provider may restrict server restarts, IP assignment, global service configuration, automated backups, firewall changes, and other infrastructure functions.
Before creating accounts, review:
- Maximum number of cPanel accounts
- Disk space, bandwidth, CPU, memory, and inode limits
- Available PHP versions and extensions
- Private nameserver availability
- Backup and restore options
- SSL installation and renewal tools
- Email, DNS, migration, and escalation support
Knowing these limits prevents you from promising features that require root access or a different hosting plan.
2. Prepare your reseller brand and nameservers
If you are selling hosting under your own brand, prepare the public-facing details before onboarding a customer. This may include your hosting domain, support email, nameserver names, package names, welcome message, and service terms.
Private nameservers normally require registration at the domain registrar and the correct IP addresses from the hosting provider. Test the nameserver records from outside your own network before using them for client domains.
3. Create packages before accounts
A WHM package is a reusable collection of limits and permissions. Create packages before creating client accounts so every account begins with a deliberate configuration.
| Package setting | Why it matters |
|---|---|
| Disk and bandwidth | Prevents one account from consuming the entire reseller allocation |
| Addon and parked domains | Controls how customers use the account |
| Email accounts and lists | Sets expectations for business email use |
| Databases and database size | Supports WordPress and application requirements |
| Feature list | Controls which cPanel tools the customer can access |
| Resource limits | Helps isolate accounts and plan upgrades |
Use package names that make sense to customers, but keep an internal record of the technical settings behind each name. Avoid giving every account unrestricted access by default.
4. Create the first client account carefully
Collect the correct primary domain, account email, package, password, nameservers, and contact details before opening the account. Use a unique, strong password and never reuse your WHM password for a cPanel account.
Confirm that the account is assigned to the intended package and that the primary domain is spelled correctly. Changing the primary domain later can involve additional DNS and application work.
5. Configure DNS and SSL
After the account is created, confirm that the domain points to the correct nameservers or DNS records. Then verify the following:
- Website resolves with and without the www hostname
- HTTP redirects to HTTPS where intended
- SSL certificate is installed for the domain and common hostnames
- Mail records point to the intended mail service
- SPF, DKIM, and DMARC records match the email setup
- Propagation is checked from more than one network
Do not change DNS records blindly. Confirm whether the customer uses the hosting account for email or uses an external provider such as Google Workspace or Microsoft 365.
6. Test the client experience
Log in using the customer-level credentials or a limited test user. Check that the customer can access the features you promised and cannot see other accounts or reseller-level settings.
Test a normal website upload, database creation, email login, password reset, SSL status, backup access, and support contact process. A short test before launch is cheaper than troubleshooting a broken welcome experience after the customer has published their site.
7. Set backup and restore expectations
Confirm whether backups are included in the reseller plan, how often they run, how long they are retained, and whether you or the provider performs the restore. Keep an independent copy of critical customer data when your service agreement requires it.
Write the limits into your service description. A customer should know whether the plan includes daily backups, on-demand restores, database recovery, or only infrastructure-level protection.
8. Create your onboarding message
Your welcome message should provide the information a customer needs without exposing sensitive reseller credentials.
- Hosting package and billing cycle
- Nameservers and DNS guidance
- cPanel access URL and account username
- Support channel and response target
- Backup and restore policy
- Migration or setup instructions
- Emergency contact and escalation process
Keep provider-level credentials private. Your customer should receive only the access required for their own account.
9. Define the support boundary
The reseller is normally the first-line support contact for downstream customers. You should decide whether your hosting plan includes only account guidance or also includes WordPress updates, application troubleshooting, malware cleanup, performance work, and content changes.
WebyStrata supports the reseller account and hosting infrastructure. Your downstream customer relationship, billing, and first response remain your responsibility.
10. Use a launch checklist for every account
- Confirm the customer and domain details.
- Select the correct package.
- Create the account with a unique password.
- Configure nameservers or DNS records.
- Verify SSL and email routing.
- Test website, database, email, and account access.
- Record backup and restore details.
- Send the customer welcome information.
- Document any migration or custom change.
Final takeaway
A safe WHM reseller setup is a repeatable process. Create packages first, limit access deliberately, test DNS and SSL, document backups, and make the support boundary clear. Once the first account works correctly, turn the process into a template for every new customer.
WebyStrata reseller hosting gives agencies, developers, and hosting businesses a platform for creating their own client packages. Explore WebyStrata hosting options when preparing your reseller setup.
Frequently asked questions
Do reseller accounts have root WHM access?
Usually not. Reseller WHM provides account-level tools, while root WHM includes server-wide administration. Your provider controls which functions are available.
Should every customer use the same WHM package?
Not necessarily. Use a small set of clear packages with limits that match different customer needs. This makes upgrades and resource planning easier.
Who supports my downstream hosting customers?
The reseller normally provides first-line support to its own customers. WebyStrata supports the direct reseller account and infrastructure rather than acting as the downstream customer’s help desk.
Related Articles
