PanelAlpha Documentation
Back Home
Live Demo Get Started

Documentation
    Introduction
Getting Started
    Installation Guide Update Guide SSL Configuration Translations
System Configuration
    General Configuration Plans Hosting Servers DNS Servers Email Servers Remote Backups Notifications Automatic SSL Plugins & Themes Background Billing Diagnostic Mode Automatic Tester
Admin Area
    Dashboard Instances Services Users Logs Migrations
Onboarding Methods
    Quick Onboarding Super Quick Onboarding Standard Onboarding
Hosting Servers
    Hosting Scenarios PanelAlpha Engine cPanel Plesk DirectAdmin WP Cloud
DNS Servers
    Cloudflare cPanel DNS Only PowerDNS
Email Servers
    Mailcow cPanel
Billing Systems Integrations
    PanelAlpha WordPress Hosting For WHMCS
Integrations
    Atarim AWStats Matomo Google Analytics Let's Encrypt Google PageSpeed Insights DB-IP Extendify WithoutDNS
Client Area - Instances
    List of Instances Creating New Instance Importing Existing Instance Instance Details Changing Domain Sharing Instances Monitoring Backups Plugins Advanced Settings
Client Area - Hosting
    Summary Domains FTP Accounts MySQL Databases Cron Jobs File Manager DNS Zone Editor Email Addresses Email Forwarders

# PanelAlpha WordPress Hosting For WHMCS

Direct Download

  • Features list

PanelAlpha WordPress Hosting For WHMCS is a module that integrates PanelAlpha platform provisioning and management options with your WHMCS system. As a widely recognized web hosting and billing platform, WHMCS empowers you to efficiently provision and bill your clients for a variety of services. These may include ordered accounts with WordPress websites, product addons like plugins and themes, and services offered by PanelAlpha.

# Features list

  • Admin Area
    • Create/Terminate/Suspend/Unsuspend PanelAlpha Service
    • Change Package
    • Configure Service Per PanelAlpha Plan
    • View Selected Plan Configuration From PanelAlpha:
      • Instances Limit
      • Onboarding Type
      • Server Type And Group
      • Disk Space And Memory Limit
      • Selected DNS And Email Server
    • Enable Automatic WordPress Instance Provisioning When Service Is Created
    • Define Default WordPress Instance Theme
    • Define Default WordPress Instance Name
    • Toggle WordPress Instance Name Field On Order Form
    • Enable Only Manual Service Termination
    • Enable PanelAlpha Single Sign-On (SSO) For Client Area
    • Configure Metric Billing For:
      • Active WordPress Instances
      • Remote Backups Size
      • Disk Usage
    • Create/Terminate Service Addons With Preconfigured Packages From PanelAlpha:
      • View Selected Package Configuration With Included Plugins And Themes
    • Synchronize Accounts Between WHMCS And PanelAlpha Platform
  • Client Area
    • Use Single Sign-On (SSO) To Manage WordPress Instances In PanelAlpha
    • View Current Usage Billing For:
      • Active WordPress Instances
      • Remote Backups Size
      • Disk Usage
  • General Info
    • Multi-Language Support
    • Supports PHP 8.2 Back To PHP 8.1
    • Supports WHMCS Themes "Six" And "Twenty-One"
    • Supports WHMCS V8.12 Back To WHMCS V8.9

# Installation

This comprehensive tutorial will provide you with step-by-step instructions on the installation and configuration process of the PanelAlpha WordPress Hosting For WHMCS module. Our guide will ensure you successfully set up the module and customize the offered options to meet your business needs.

  1. Download the module from our GitHub Repository (opens new window).
    • Direct download link: https://github.com/panelalpha/panelalpha-for-whmcs/archive/refs/heads/main.zip (opens new window)
  2. Upload and extract the module files into the main WHMCS directory.

That's it! You have just successfully installed the PanelAlpha WordPress Hosting For WHMCS module!

# Configuration

# Server

  1. Go to System Settings → Servers and press the Add New Server button.
  2. Next, choose PanelAlpha from the Module dropdown menu. Remember not to use SSL Mode for connections, keep this option disabled or otherwise you will encounter errors when testing the server connection.
    Fill in the following fields:
    • Name - Enter any name of your choice.
    • Hostname - Remember to always add the port number, as on the screen below.
    • API Token - The API token can be generated in PanelAlpha admin area in Configuration → Admins under the Enable API Token action.
  3. Check the connection when the server configuration of your server is ready.
    In order to check the connection with the PanelAlpha server, press the 'Test Connection' button.
  1. The next step is creating a server group. To do so, click on Create Server Group.
  2. Enter the name, click on your previously created server, press Add and Save Changes afterwards.

# Product

  1. In order to create and then configure a product, go to Setup → Products/Services → Products/Services.
    Click on the Create a New Group button.

  2. Enter the product group name and press Save Changes.

  3. Once you have a product group, you can assign your product to it. To create a product, click on Create a New Product.

  4. Next, choose your product type, assign the product to a group of products created in the previous step. Enter your product name, select module: 'PanelAlpha' and then press 'Continue'.
    Remember to disable the default 'Create as Hidden' option beforehand.

  5. Now, go to the 'Module Settings' section, choose both PanelAlpha and your previously created server group from the dropdown menus. Available options for the product configuration will appear:

    • PanelAlpha Plan - A plan will be assigned to the service on the basis of which the service will be created.
    • Plan Settings - depending on the selected paln and hosting server assigned, adequate settings option configuration will appear here.
    • Automatic instance provisioning - If enabled, a new instance will automatically be created with the selected theme when the service is created.
      • Default Instance Theme - Select a theme that will be installed once the service is created.
      • Default Instance Name - Provide the name of the instance that will be installed once the service is created.
      • Show Instance Name Field on Ordere Form - If enabled, a custom field with the instance name to provide will be visible on the order form.
    • Manual termination - If enabled, termination of the service will only occur after a manual action by the admin.
    • PanelAlpha SSO in main menu - If enabled, the user will receive a link to their PanelAlpha account on the main client area menu.
    • Automatically set number of sites - Automatically sets the number of sites when upgrading from trial to a product with 'sites' Configurable Option. When enabled, the system will automatically configure the sites value based on the client's current usage during upgrade from trial. If only one 'sites' Configurable Option exists, the system will redirect directly to checkout. Otherwise, the field will be locked with the automatically determined value.
  1. Do not forget to click on the 'Save Changes' button when your configuration is ready.

# Product settings for WP Cloud hosting server

If a plan with WP Cloud server has been selected, there will appear a setting called User Can Choose Location.

When the Allow User To Choose Location option is enabled in a plan, this setting is automatically selected. As a result, a button labeled Show Location On Order Form becomes visible. This button creates a custom field that allows customers to select their desired site location during the ordering process.

Note that you may manage the "Site Location" custom field name under your product details → Custom Fields. Remember that you may alter only the part following the "|" sign.
If you do not want to offer your client the location selection, simply remove the created custom field or disable it by unselecting the "Show on Order Form" and "Required Field" options.

# Using Configurable Options for location settings

You can also set up location selection as a Configurable Option in WHMCS. This gives you more flexibility in how you present location choices to your clients and allows you to assign different prices to different locations.

Important: If both a Configurable Option and a Custom Field for location are set up, the system will always prioritize the Configurable Option value. The Custom Field will only be used if no Configurable Option for location exists. However, it's recommended to use only one of these methods to avoid confusion.

# Using Configurable Options for sites limit

You can also use sites as a Configurable Option to set the maximum number of instances allowed per service. This option overrides the plan's instance limit and allows you to offer different tiers of service based on the number of sites/instances a client can create.

When you set up a Configurable Option with the name sites (or containing "Number of Sites"), it will define the maximum instance limit for that specific service, regardless of the plan's default settings. This gives you flexibility to offer various packages with different instance limits while using the same base plan.

# Addon

  1. Go to System Settings → Product Addons and press the 'Add New Addon' button.

  2. Next, choose the addon type as 'Independent Product', enter the package name and select the addon module: 'PanelAlpha'.

  3. Now, go to the addon's 'Module Settings' section and select the package:

    • Package - You can select a ready package configured in PanelAlpha.
    • Preview the package configuration:
      • Plugin automation on assign - Describes what happens to the plugins when the package is added to the service.
      • Theme automation on assign - Describes what happens to the themes when the package is added to the service.
      • Plugins included - List of plugins assigned to the selected package.
      • Themes included - List of themes assigned to the selected package.
  1. Assign the addon to the selected products at the 'Applicable Products' tab.
  1. Remember to 'Save Changes' when your addon configuration is ready.

# Management

# Admin area

As soon as you set up a server for a client, you can request various actions and view server details from the WHMCS admin area.

Available module commands:

  • Create/Suspend/Unsuspend/Terminate the service
  • Change Package
  • SSO (Single Sign-On) button to log in as the user in Client Area PanelAlpha

Metric Statistics:

  • Data on active instances assigned to the service
  • Data on the remote backup size
  • Disk usage analysis
  • Bandwidth usage tracking
  • Websites visitors statistics

# Addon page

If your product has an addon, you can also review its details from the admin area. Simply locate it in the list under the main product name.

Available actions on addons:

  • Create the addon
  • Terminate the addon

# Client area

Accessing their account on PanelAlpha is easy for clients, who simply need to click the Manage WordPress button in the navigation bar.

Access the PanelAlpha service, where you will find a button that allows direct login to the platform via SSO.

In the Metrics section, you can also view the current billing usage for active WordPress instances, the size of remote backups, disk usage, bandwidth consumption, and websites visitors statistics.

The Additional Information section provides details on the WordPress instance name that has been created on this service.

# Account synchronisation

Follow the below guide to synchronize and import services from PanelAlpha into your WHMCS.

  1. In your WHMCS installation, navigate to: System Settings → Servers.
  2. Step 1 - Locate your PanelAlpha server in the list and click the Sync Accounts button.
  1. Step 2: Analyse - A table will display available services and their details.
    • Select the services that are not yet synchronized and that you wish to import by checking the Import/Sync box. Then, click Continue.
  1. Step 3: Review - You will be moved to the Review step. Here, you can see the PanelAlpha services that will soon be created in WHMCS.
    • Configure account import settings:
      • Send Client Welcome Email - Enable to send a welcome email to clients for newly created accounts. Select the template from the dropdown menu, and set the status to Yes to activate.
      • Reset Service Account Passwords - Set to Yes to auto-generate new passwords for imported accounts.
      • Send Service Welcome Email - Set to Yes to send a welcome email for existing products only.
      • Set Recurring Billing Information - Enable to automatically set billing based on the selected cycle. This applies to existing products only.
    • Once configured, press Continue to complete the account synchronisation process.
  1. Step 4: Summary - Wait a moment for synchronization to complete. A success message will confirm the server synchronization completion.

Important!
The synchronization process verifies account existence in both WHMCS and PanelAlpha. This means that if a service exists in WHMCS but is no longer available in PanelAlpha, it may be removed from WHMCS during synchronization.

Services that no longer exist in PanelAlpha but still have active corresponding accounts in WHMCS are marked as shown on the screen below and can be selected in Step 2 of the account synchronization process. These services will be deleted from WHMCS upon successful completion of the process.

# Background Billing

To activate Background Billing in PanelAlpha, you need to have the WHMCS module version v1.2 or higher. This feature allows automated usage-based billing between PanelAlpha and WHMCS.

Follow these steps to configure Background Billing:

  1. Enable the WHMCS Addon Module by navigating to Setup → Addon Modules and activating the PanelAlpha WordPress Hosting For WHMCS module.

  1. After activation, generate an API token that will be used by PanelAlpha to communicate with your WHMCS installation.

  2. In the module configuration, you need to specify the IP addresses from which PanelAlpha servers will be allowed to connect to your WHMCS installation. Enter the IP addresses in a comma-separated format. You can use * to allow connections from all IP addresses, but for security reasons, it's recommended to specify only the PanelAlpha server IP addresses.

# Additional information

  1. Domain Require - The WHMCS option that determines whether a client needs to provide a domain when placing an order has been hidden from WHMCS product "Details" section. For PanelAlpha services, this field is automatically populated based on the onboarding type defined in the plan associated with the product.

# Billing Scenarios

The documentation provided below outlines the various use cases that can be set up with PanelAlpha in conjunction with WHMCS. Each use case is divided into two sections:

  • Workflow - this section provides an explanation of how the scenario works from both the end-customer and billing perspectives
  • Configuration - Here, you will find a step-by-step process explaining how to set up PanelAlpha in combination with WHMCS

Before you begin the setup process, please ensure that you have completed all of the following steps:

  • Installation
  • Server Configuration
  • Plan Configuration
  • Installation and configuration of the WHMCS module (covered in this document)

# Single WordPress Instance

# Offering a single WordPress instance as a service

This is the most commonly used workflow for most of our customers and is a perfect setup for end-users who want to "purchase a WordPress hosting service". The idea is to set up simple products that correspond to a single WordPress instance.

It covers the recommended Quick Onboarding Process which makes it easier for the end-customer to set up their first site without bothering about much configuration or even setting up their live domain. The first site is configured on a subdomain that can be changed to their own domain at a later stage.

# Workflow illustration

  1. End-customer orders a new service in the WHMCS system, in our example that will be: "WordPress Single Site - Bronze"
  2. They go through the standard ordering process (Note: "Lagom One Step Order Form For WHMCS" is a recommended setup).
  1. After the payment for the ordered product is complete:
    • The end-customer will receive an email message with details about their service
    • From the client area in WHMCS they can directly proceed to the new PanelAlpha user page. Simply use the "WordPress Management" section in the menu - it uses SSO to automatically authenticate them into PanelAlpha
    • Alternatively, they can go to their service page and click "Log In To PanelAlpha" - it uses SSO to automatically authenticate them into PanelAlpha as well
  1. Once they are redirected to PanelAlpha, again SSO is used to for automatic authentication
  2. The first page that they see is the option to create the first instance.
    • clients may either create a brand new site or migrate their instance from an already existing hosting
    • for a migration workflow, read more about Migration here
  1. When they choose to create a new site, the system will present them with the available themes to choose from
  1. Once chosen, they will be asked to enter their site name. Press the "Create Site" button and the site will be provisioned right away.
    The site name (domain) can surely be changed later on, so you may type in any name at this point.
  1. The new site is ready for the client to manage!

# Configuration in PanelAlpha

  1. Plan Configuration - Provide basic details to create a new plan:
  • Plan Name
  • Instances Limit - in our case that will be "1"
  • Upgrade Link - a hyperlink that directs to a page where users can upgrade their current plan
  • Label Color - indicates a visual identifier associated with a specific plan, usually used to point the difference between several plan types
  • Preview
  1. Onboarding - You may select between two onboarding methods: "Quick Onboarding" and "Standard Onboarding" to establish a service based on a predefined plan. Check for the details and differences between them now:
  • "Quick Onboarding" - it is specifically designed to deliver an exceptional user experience, similar to web-builder products, ensuring optimal satisfaction for end-users. The end-customer can place an order for a basic service in your WHMCS, even without requiring a domain. Upon completion of the order, they can log in to PanelAlpha, where they will be presented with a selection of templates to proceed with.
    • To enhance the overall experience, you can integrate it with a pre-installed website builder plugin for WordPress, enabling users to enjoy a seamless and high-quality experience.
    • Utilize the free trial feature within WHMCS, which can effectively increase conversion rates.

This selection is highly recommended for all the advanced users.
Available options:

  • Force installation for new users after log in - enabling this option is highly recommended

  • Domain used for subdomains - enter the main domain to allow creating subdomains

  • Automatic subdomain format:

    • Friendly name based on website name; e.g. john-blog.mydomain.com
    • Friendly name random combination; e.g. purplegoose.mydomain.com
    • Specified number: enter description and the next number to generate a subdomain, eg. "temp{number}", "100000": temp100000.mydomain.com
    • Random Length: enter the number of signs to generate a subdomain, eg. "10": 4d7wg9r98x.mydomain.com
  1. Hosting - Server selection and configuration.

  • Server Type - choose your server type between:

    • cPanel
    • PanelAlpha Engine

  • Server Group - choose one from the previously created groups (read more here)

  • Server Assignment Rule:

    • Random - the service will be set up on a randomly selected server
    • Least Accounts - the service will be set up on the server within the specified group of servers that has the smallest number of accounts
    • Specific Server - the service will be set up on the pointed server

  • Hosting Account Configuration:

    • WHM Package Name
  1. DNS - Select and configure the DNS server responsible for translating domain names into IP addresses.
    Available DNS server types to choose from:

  • cPanel's DNS Server

  • PowerDNS

    • select DNS Server for your services
    • enter the zone template name
  1. Email - Select and configure the email server. Please choose email server type:

  • Use cPanel's Email Server

  • None

  • Mailcow

    • choose email server
    • enter the Mailcow package name
  1. Domains - Add domains that users of this plan will be allowed to use as subdomains.
    Press "Add New Domain" to star, a modal will appear where you have to type in the new domain name to add it.
    Manage the blacklist: create a list of forbidden words, enable "Block Profanity" to blacklist all uncensored expressions at once.

  1. Plugins&Themes - Manage the plugins that will be installed or deactivated on instances.

  • Automation:

    • Default Plugin & Theme Packages - Assign packages of plugins and themes to a WordPress instance within the plan.
    • Automatic Plugin Installation - Assign plugins that will be automatically installed during the WordPress instance installation process.
    • Automatic Theme Installation - Assign themes that will be automatically installed during the WordPress instance installation process.
    • Default Theme - select a default theme that will be installed on the instance.

  • Blacklist:

    • Plugin Blacklist - Assign prohibited plugins that will be deactivated from any WordPress instance in the plan
    • Delete Blacklisted Plugins - Assign prohibited plugins that will be removed from any WordPress instance in the plan
    • Delete Blacklisted Themes - Assign prohibited themes that will be removed from any WordPress instance in the plan

  • Scan:

  • Scan Interval (in hours) - Assign the frequency (in hourly time interval) at which the cron will deactivate and remove prohibited plugins and themes from the WordPress instances in the plan

# Configuration of product in WHMCS

Before you proceed to your WHMCS and start server and product configuration, you must previously generate your API token, you will need it in further steps.

Proceed to your PanelAlpha admin area → Configuration → Admins → API Token.

Once you enable the API Token, you will get a one time access to it. Keep in mind that this is the only moment when you see it, so please copy it and keep in a safe place!

Once ready, you may now move to your WHMCS platform and begin the configuration.

  1. Under System Settings → Products/Services → Servers create a new server. Fields that must be filled out are:

    • Name - any name for your server.
    • IP Address - provide the IP address with a port number where your PanelAlpha is located. The Hostname field may be lefty empty, after saving the changes, it will be filled in automatically.
    • API Token - PanelAlpha token generated as described in the steps above.

  2. Under System Settings → Products/Services → Servers create a new group of servers and assign the just created server to this group.

  1. Next, proceed to System Settings → Products/Services and create a new group of products.

  2. Once you have the group, you may finally create your PanelAlpha product.

    • Product Type - set it to "Shared Hosting"
    • Product Group - select the just created group
    • Product Name - in our example that is: "WordPress Single Site - Bronze"
    • Module - please select "PanelAlpha" from the dropdown menu
      Press "Continue" to move to the next step.
  1. Now, go to 'Module Settings' section. As the module name has been already selected, find the server group where the server you need to connect with is assigned in the dropdown menu. Once selected, all the module configuration settings will appear.
    • PanelAlpha Plan - select the plan you wish to assign to this product In the described now example, that will be "Single Instance"
    • Based on the selected plan, all the further settings will be automatically filled in. Save the changes once the settings configuration is ready.
  1. Finally, set the pricing details for your product, you may do that in the "Pricing" tab.

# Predefined WordPress Template

# Offering a predefined WordPress Template

This is a similar workflow as offering a single instance, in this case, however, the customer will have their WordPress automatically installed when the service is activated. This is a recommended configuration for companies offering their own instance templates.

For example: Site with predefined plugins, theme and configuration that works perfectly for a dental clinic business.

# Workflow illustration

  1. End-customer orders a new service in a billing system, for example WHMCS, in our example that will be: "Dental Clinic"
  2. They go through the standard ordering process.
  1. After the payment for the ordered product is complete:
    • The end-customer will receive an email message with details about their service
    • From the client area in WHMCS they can directly proceed to the new PanelAlpha user page. Simply use the "WordPress Management" section in the menu - it uses SSO to automatically authenticate them into PanelAlpha
    • Alternatively, they can go to their service page and click "Log In To PanelAlpha" - it uses SSO to automatically authenticate them into PanelAlpha as well
  1. Once they are redirected to PanelAlpha, again SSO is used to for automatic authentication.
  2. The first page that they see is the information on the process of the instance installation. Wait a moment until the process is complete.
  1. The new site is ready for the client to manage! The end-customer, after opening the dashboard, can access their new site.

# Configuration in PanelAlpha

  1. To start using instance templates, you must first create them. Navigate to Admin Area → Instances → Instance Details and locate the action button labeled Save as Template. Provide a name for the template and confirm by pressing Save. Currently, saving an existing instance as a template is the only method available for creating them.
  1. The created template will appear on the list of Instance Templates, make sure its status is active, as only then you will be allowed to assign it to a plan.

  1. Let's proceed to the configuration of a plan that allows creating instances from templates. For demonstration purposes, we will show how it works using the recommended Quick Onboarding method.

  2. Create a new plan, fill in the details section by providing the plan name - we have set it to 'Dental Clinic - Predefined Template', define the instances limit (1), and fill out the remaining options according to your preferences.

  1. In Onboarding tab, make sure to select the instance template that will be used by default for creating the new website. In our case, we are leaving the "Allow to choose themes" and "Ask for domain" unselected and "Force installation for new users after login" selected. This way, after being logged in to PanelAlpha client area, the end user will simply have the website installed automatically without being asked any questions and steps to complete.

  1. Define the Hosting, DNS and Email servers details to establish the connection.

  2. Define the Domains creation rules. Skip the "Plugins&Themes" section as in our case you are going to offer a predefined instance template with already installed plugins and themes.

  3. Enable automatic backups and set up the frequency. You may skip the "Other" section. Save the changes to confirm creating the plan.

# Configuration in WHMCS

  1. Before you proceed to your WHMCS and start server and product configuration, you must previously generate your API Token, you will need it in further steps.

  2. Once you enable the API Token, you will get a one time access to it. Keep in mind that this is the only moment when you see it, so please copy it and keep in a safe place!

  3. Proceed to your PanelAlpha admin area → Configuration → Admins → API Token.

Once ready, move to your WHMCS platform and begin the configuration.

  1. Under System Settings → Products/Services → Servers create a new server. Fields that must be filled out are:
    • Name - any name for your server.
    • IP Address - provide the IP address with a port number where your PanelAlpha is located. The Hostname field may be lefty empty, after saving the changes, it will be filled in automatically.
    • API Token - PanelAlpha token generated as described in the steps above.
  1. Under System Settings → Products/Services → Servers create a new group of servers and assign the just created server to this group.
  1. Next, proceed to System Settings → Products/Services and create a new group of products.
  1. Once you have the group, you may finally create your PanelAlpha product.
    • Product Type - set it to "Shared Hosting"
    • Product Group - select the just created group
    • Product Name - in our example that is: "Dental Clinic"
    • Module - please select "PanelAlpha" from the dropdown menu
      Press "Continue" to move to the next step.
  1. Now, go to Module Settings section. As the module name has been already selected, find the server group where the server you need to connect with is assigned in the dropdown menu. Once selected, all the module configuration settings will appear.
    • PanelAlpha Plan - select the plan you wish to assign to this product In the described now example, that will be "Dental Clinic - Predefined Template"
    • Based on the selected plan, all the further settings will be automatically filled in. Save the changes once the settings configuration is ready.
  1. Finally, set the pricing details for your product, you may do that in the "Pricing" tab.

# Multiple WordPress Instances

# Offering a service with multiple WordPress instances limit

This is a recommended service that you can offer for large customers or agencies that manage multiple WordPress instances. In such case it does not make sense to ask them to order a new service from your billing system for every instance. You can offer a predefined limit packages (e.g. 10 sites, 50 sites, 100 sites) or use Usage Billing to charge for the total number of instances in use.

# Workflow illustration

  1. End-customer orders a new service in a billing system, for example WHMCS, in our example that will be: "Multiple WordPress Sites - Bronze"
  2. They go through the ordering process.
  3. After the payment process is complete, they receive an email with details about their service and can use "Manage WordPress" section in the menu with SSO authentication.
  4. Once they are redirected to PanelAlpha, SSO is used to automatically authenticate them.
  5. The end-customer can click on "Add New" to create a new site.
  6. They fill in a dedicated form and the site is created immediately.

The configuration follows similar steps as the Single WordPress Instance scenario, but with the instances limit set to the desired number (e.g., 10, 50, 100).

# Plan Upgrade

# Upgrading a plan

PanelAlpha offers a user-friendly method for customers to seamlessly manage plan upgrades directly within the application. When users approach the maximum number of available sites or their hosting space nears capacity, they can initiate an upgrade for their website.

# Workflow

  1. When the end client reaches the limit of their sites, they will get a dashboard notification with information that they cannot create any new instances before they upgrade their plan.
  1. In the "My Hosting" section of the PanelAlpha client area, in the top right corner of the 'Plan Usage' table, there is a button that allows upgrading the current plan.

  1. The upgrade process is handled through WHMCS, where customers can select a higher-tier product and complete the payment.

  2. Once the payment is complete, the user will see the new product active and can return to PanelAlpha to create new instances within the upgraded limit.

# Cross-Selling Scenarios

# Cross-Selling Paid Plugins and Themes

PanelAlpha supports cross-selling paid plugins and themes as additional services through WHMCS product addons. This allows you to offer premium plugins and themes that customers can purchase and have automatically installed on their WordPress instances.

# Cross-Selling Domains

You can configure PanelAlpha to integrate with domain registrars through WHMCS, allowing customers to purchase domains directly from their WordPress management interface and have them automatically configured with their instances.