srsakib
Active Member
Hi,
Currently, Clientexec only supports a single global suspension and termination rule within the service automation settings. However, hosting providers manage multiple service types, and each product requires a different overdue policy based on its cost, renewal structure, and data-retention requirements.
For example:
If the termination period is set too long, high-cost services such as VPS and dedicated servers may continue generating upstream charges even when the customer has not paid. This can cause direct financial losses for the hosting provider.
On the other hand, if the global termination period is shortened to protect the provider from those losses, shared hosting accounts may be permanently deleted too early. This can create unnecessary customer pain, data-loss complaints, support disputes, and damage to the provider’s reputation.
For example, setting global termination to 7 days may be suitable for VPS services, but it is often too aggressive for shared hosting customers. Setting it to 30 days may protect shared hosting data, but it forces the provider to carry the unpaid cost of VPS services for too long.
Manual termination is not a reliable solution, especially for providers managing hundreds or thousands of active services. It increases staff workload, creates room for human error, and makes overdue management difficult to scale.
Please consider introducing package-specific or product-group-specific automation settings that allow administrators to define:
Thank you for considering this request.
Currently, Clientexec only supports a single global suspension and termination rule within the service automation settings. However, hosting providers manage multiple service types, and each product requires a different overdue policy based on its cost, renewal structure, and data-retention requirements.
For example:
- Shared Hosting: Suspend after 5 days and terminate after 30 days
- VPS: Suspend after 3 days and terminate after 5–7 days
- Dedicated Servers: May require even faster action due to high recurring infrastructure costs
- Domain Names: Follow separate expiration, renewal, redemption, and deletion policies
If the termination period is set too long, high-cost services such as VPS and dedicated servers may continue generating upstream charges even when the customer has not paid. This can cause direct financial losses for the hosting provider.
On the other hand, if the global termination period is shortened to protect the provider from those losses, shared hosting accounts may be permanently deleted too early. This can create unnecessary customer pain, data-loss complaints, support disputes, and damage to the provider’s reputation.
For example, setting global termination to 7 days may be suitable for VPS services, but it is often too aggressive for shared hosting customers. Setting it to 30 days may protect shared hosting data, but it forces the provider to carry the unpaid cost of VPS services for too long.
Manual termination is not a reliable solution, especially for providers managing hundreds or thousands of active services. It increases staff workload, creates room for human error, and makes overdue management difficult to scale.
Please consider introducing package-specific or product-group-specific automation settings that allow administrators to define:
- Suspension period for each package or product group
- Termination period for each package or product group
- Optional final warning period before termination
- The ability to inherit global settings or override them per package
Thank you for considering this request.