Allocate packages from real reseller capacity and reserve space for customer growth, migrations and temporary operations.
Applies to: Reseller capacity and resource management
Resource allocation is both a technical and commercial decision. Monitor pooled usage, avoid assigning every account the maximum allowance and document what each customer package includes.
Before you start
- Sign in with the reseller account rather than a customer SiteWorx login.
- Identify the affected SiteWorx account, package and domain.
- Record the current package, DNS and account settings before making a production change.
Step-by-step
- List total plan allowances and current allocated capacity by resource.
- Separate allocated limits from actual use; both matter when overselling is disabled.
- Group customer packages by realistic website and mailbox profile rather than giving every customer the largest package.
- Reserve a capacity buffer for archives, backups, staging and migration overlap.
- Review the largest and fastest-growing accounts monthly and before sales campaigns.
- Upgrade the reseller service or rebalance packages before an account creation fails.
- Document any customer plan change and confirm it does not silently remove required limits.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| A package or SiteWorx account cannot be created. | Overselling is disabled and the requested allocation exceeds the reseller plan or a package field is invalid. | Compare allocated and available capacity, reduce the package or upgrade the reseller service before retrying. |
| A customer issue cannot be resolved from SiteWorx. | The fault is platform-level, network-level or requires provider permissions. | Collect the account, domain, timestamp, exact error and checks completed, then escalate from the reseller account without sharing customer passwords. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The reseller service and affected SiteWorx account
- The package name and current resource use
- The exact action attempted and error returned
- Whether the issue affects one or multiple customer accounts
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Understand Agency Reseller Hosting plan limits
- Monitor reseller resource usage
- Create and manage reseller packages
- Complete each field when creating a SiteWorx customer account
Last reviewed: 2026-07-18.
