You know the message: "Please cancel my hosting." It often arrives not because the customer is unhappy, but because they are between projects, cutting costs, or unsure about the next few months. A pause plan gives them a middle option: keep the account, stop most of the billing, and come back without rebuilding. It turns a churn event into a temporary hold.

What is a hosting pause plan and why offer one?

A hosting pause plan is a billing status where the service is suspended but the account, data and configuration are retained. The customer pays a reduced fee or nothing, and reactivation is quick. For you as a reseller, it keeps the customer relationship alive and protects recurring revenue. For the customer, it avoids the hassle of migrating away and back.

The alternative is cancellation, which usually means data deletion after a grace period. Once deleted, the customer must start over: re-upload files, recreate email accounts, reconfigure DNS. Most customers do not realise this until they need to come back. A pause plan removes that friction.

What pause duration tiers should you offer?

Offer two or three tiers with clear limits. For example:

  • Short pause (1–3 months): low monthly fee, full data retention, email kept live. Ideal for seasonal businesses or short breaks.
  • Extended pause (4–6 months): higher one-time or monthly fee, data retained but email and DNS frozen. Suitable for longer projects or sabbaticals.
  • Archive (7–12 months): one-time archive fee, data moved to cold storage, no email or DNS. For customers who want to keep the account but not use it.

Set a maximum pause duration, after which the account reverts to normal billing or is cancelled. This prevents indefinite holds that clog your systems.

What should you freeze versus keep live during a pause?

Decide per service component. Freezing everything is simplest, but some customers need email or DNS to stay live even when the website is down.

  • Website files and databases: freeze (suspend the web server). No traffic, no resource usage.
  • Email: keep live if the customer relies on it for contact. Alternatively, freeze and set an auto-responder explaining the pause.
  • DNS: keep live if the domain is registered with you and points to other services (e.g., a landing page). Freezing DNS can break email and other services.
  • Backups: keep running. This is critical for reactivation. Ensure backups are stored separately and retained for the pause duration.
  • SSL certificates: keep renewing if the site will be reactivated, or let them expire if the site is frozen.

Document these rules in your terms so customers know what to expect.

How should you price and bill a pause plan?

Pricing should cover your costs: storage, backups, and administrative overhead. A common approach is a monthly pause fee that is a fraction of the normal plan price. For example, if a shared hosting plan is €10/month, a pause fee might be €2/month. For archive tiers, a one-time fee of €20–€50 is typical.

When a customer pauses mid-cycle, prorate the unused portion of their current billing period and apply it as a credit toward future invoices. The same applies on reactivation: charge the prorated amount for the remainder of the month. Use your billing system's proration features to avoid manual calculations.

If you use Teculiar, upgrades are prorated automatically, and you can set a service to never auto-suspend, which is useful for pause states. The platform also handles VAT and invoicing, so pause fees are taxed correctly.

What reactivation SLA should you promise?

Reactivation should be fast and predictable. Promise a clear SLA: for example, reactivation within 1 business day for short pauses, 2 business days for extended pauses, and 3–5 business days for archive restores. State that reactivation is triggered by payment of the reactivation fee and any outstanding balance.

Automate where possible: when the customer pays the reactivation invoice, your system should unsuspend the service and send a confirmation. If manual steps are needed (e.g., restoring from archive), communicate the timeline upfront.

What email scripts turn a cancellation request into a pause?

Use these templates as a starting point. Personalise with the customer's name and specific service details.

Script 1: Immediate response to cancellation

Subject: Before you go – can we pause instead?

Hi [Name],

We received your cancellation request for [service]. Before we process it, I want to make sure you know about our pause plan. It lets you keep your account, data and settings for up to [X] months at a reduced fee, so you can come back without starting over.

Would you like me to switch you to a pause instead? Just reply to this email and I'll set it up.

Best regards,
[Your name]

Script 2: Follow-up if no response

Subject: Your account is scheduled for cancellation – last chance to pause

Hi [Name],

Your cancellation is scheduled for [date]. If you'd prefer to keep your data and reactivate later, our pause plan is available for [X] months at [fee]. No need to migrate or rebuild.

Reply to this email if you'd like to pause instead. Otherwise, we'll proceed with cancellation as requested.

Best regards,
[Your name]

Script 3: Reactivation reminder

Subject: Your pause ends soon – ready to reactivate?

Hi [Name],

Your pause plan for [service] ends on [date]. To reactivate, simply pay the reactivation invoice we'll send on that date. Your data will be ready within [SLA] after payment.

If you need more time, let us know and we can extend the pause for another [X] months.

Best regards,
[Your name]

What to do next

  • Define your pause tiers, including duration, fee, and what is frozen.
  • Update your terms of service to include pause conditions.
  • Configure your billing system to handle pause fees and proration.
  • Train your support team on the email scripts and reactivation process.

Start by listing every service component you can freeze and every one you must keep live.