CLN Login1. Pick one trigger
Choose one behavioral signal as your enrollment criterion. Resource ceiling, ticket pattern, or growth spike. Do not run on a generic "all shared customers" list.
Resource · Section 8 of the Playbook
The 3-Email Starter Kit
A complete sequence to convert shared hosting customers into VPS upgrades. Three emails over ten business days, triggered by a behavioral signal. Includes full copy, subject lines, placeholders, and adaptation notes for ecommerce, agencies, and SMBs.
How to use this kit
2. Adapt the body by segment
Substitute every {{double_brace}} token with your CRM merge fields before sending. The full list is at the bottom of this page.
3. Adapt the body by segment
The three segment-specific adaptation blocks below show what to swap in for ecommerce, agency, and SMB recipients.
4. Send from a real human
From: a named sales rep, not a noreply alias. Reply-to: the same rep's actual inbox. Open rates climb 20% to 40% versus generic sender.
The Sequence
Three emails. Ten business days. One behavior trigger.
CloudLinux OS Shared Pro was developed with shared hosting in mind. It is a state-of-the-art operating system that includes advanced automation, deep-look performance analytics, and centralized monitoring tools.
Day 0
1
The Signal
Acknowledge the friction
Day 4
2
The Proof
Customer story, same segment
Day 10
3
The Soft Close
Open the door, no pressure
Step 1 · Pick a trigger
The six behavioral signals worth enrolling on
Generic "upgrade your hosting" blasts convert poorly because they ignore intent. Behavioral signals are the difference between a 1% reply rate and a 12% reply rate. Pick one to start.
High-confidence
Resource ceiling hit twice or more
CPU, RAM, or I/O capped two or more days in the past 30. Strongest signal. Customer is already feeling the pain.
High-confidence
Support ticket about speed or downtime
Customer has opened a ticket in the last 45 days about site speed, timeouts, or stability. Reach out before they shop around.
mid-confidence
Site count climbing past 5
Customer has added two or more new sites to their shared account in the past 90 days. They are growing into a different tier.
Mid-confidence
Traffic up 40% month over month
Sustained traffic growth on a shared plan. The next spike will probably break something. Get ahead of it.
mid-confidence
Plan tenure past 18 months
Customer has been on the same shared plan for 18+ months and the business looks bigger than when they signed up. Worth a check-in.
lower-confidence
Ecommerce launched on shared
Customer installed WooCommerce, Magento, or a similar store on a shared plan in the last 60 days. Help them plan ahead.
Day 0 · Email 1 of 3
The Signal: acknowledge what they are already feeling
The first email mirrors the trigger event back to the customer in concrete terms. No marketing copy. Read like a human who happened to notice something.
Why this email works
It opens with a specific fact the customer already knows (their resource limit). It names the consequence in their language (slow pages, checkout timeouts). It removes the migration friction with a concrete commitment (under 72 hours, 14-day rollback). It closes with a low-commitment ask (a 15-minute call), not a hard upgrade pitch.
Subject:
Your site at {{domain}} just hit its ceiling
Preview:
Here is what is happening, and what you can do about it.
From:
{{sales_rep_name}} , {{hosting_provider}}
Reply-to:
{{sales_rep_email}}
Hi {{first_name}},
I noticed your account hit its resource limit for {{X}} days this month. That usually means one of two things: your business is growing faster than your plan was sized for, or a specific event drove a spike you did not see coming.
Either way, your customers are starting to feel it. Pages load slower. Checkout occasionally times out. Search engines start to notice.
The good news: we can move your sites to a plan that handles this traffic comfortably. I will do the migration for you, in under 72 hours, with a 14-day rollback in case anything breaks.
{{sales_rep_name}}
{{role}}, {{hosting_provider}}
{{role}}, {{hosting_provider}}
P.S. If now is not the right time, just reply with "later" and I will check back in 60 days.
Adapt the open: if your trigger is a support ticket, replace "hit its resource limit" with "opened a ticket about {{issue}}." If your trigger is traffic growth, use "your traffic is up {{growth_pct}}% this quarter."
Day 4 · Email 2 of 3
The Proof: a customer in the same segment, with a number
Email 2 leads with a result, not a feature. Pick a customer story from the same segment as the recipient: ecommerce to ecommerce, agency to agency, SMB to SMB.
Why this email works
Customer stories work when the reader sees themselves in the protagonist. Same business size. Same stack. Same problem. The 70% page-load reduction is specific (not "significant improvement") and traceable to a real customer. End with a one-line ask that does not require an answer this week.
Subject:
How {{customer_name}} cut page load by 70%
Preview:
Same setup as yours. Here is what changed when they moved off shared.
From:
{{sales_rep_name}} , {{hosting_provider}}
Reply-to:
{{sales_rep_email}}
Hi {{first_name}},
Following up on my note last week.
I wanted to share a customer story that lines up with your situation. {{customer_name}} runs a {{segment_descriptor}} business roughly your size. They were on a shared plan, hitting the same resource ceilings, and losing checkout conversions to slow page loads.
After moving to our VPS with CloudLinux and Imunify360:
- Page load times dropped by 70%.
- Support tickets about speed went to zero.
- They handled their Q4 spike without a single timeout.
The full story is here: {{case_study_link}}
If you want to see what your account would look like on the same setup, I can put together a sizing recommendation in about a day. No pressure either way.
Pick your customer story carefully: the story must be from the same segment and roughly the same business size as the recipient. Sending a 200-site agency story to a one-store ecommerce owner reads as off-target and lowers reply rates.
Day 10 · Email 3 of 3
The Soft Close: open the door, no pressure
Email 3 is the "where do things stand" email. Short. Personal. No sell. Its job is to close the loop politely so the customer either replies now or self-identifies as "not ready," which routes them out of the sequence cleanly.
Why this email works
Short emails outperform long ones at the close. The three-option structure (now, later, never) makes replying feel low-cost. The "not ready" option is what unlocks the reply rate: customers who would otherwise ignore a fourth follow-up will reply just to be polite.
Subject:
{{first_name}}, where do things stand?
Preview:
Three options, pick the one that fits.
From:
{{sales_rep_name}} , {{hosting_provider}}
Reply-to:
{{sales_rep_email}}
Hi {{first_name}},
I will be quick. Three options:
Whichever it is, a one-word reply is fine.
{{sales_rep_name}}
I will be quick. Three options:
- Now. Reply with a time this week and I will walk you through what your account would look like on VPS.
- Later. Reply with "60 days" and I will check back at the end of {{quarter}}.
- Not for me. Reply with "no thanks" and I will stop emailing about this.
Whichever it is, a one-word reply is fine.
{{sales_rep_name}}
What to expect: in tests across hosting providers, this three-option close reliably pulls a 15% to 25% reply rate. Most of the replies are "not for me," and that is a win: it stops you from wasting sales cycles on customers who already decided.
Step 2 · Adapt by segment
What to swap by segment
Pick the messaging pattern that matches your partner segment and adjust tone, proof, and CTA for better outcomes.
Ecommerce
Online stores
Lead with revenue, not resources. "Your store had {{X}} abandoned carts last month tied to checkout slowdowns" lands harder than "you hit your CPU limit."
Proof point: use a customer story with a conversion lift or revenue recovery number, ideally tied to a peak event (Black Friday, BFCM, Q4 holiday).
CTA: "Get a pre-Q4 capacity check" works better than "book a call." Tie the offer to the next peak.
Agency
Multiple client sites
Lead with time saved, not server power. Agencies do not want more control. They want less admin work. Frame the upgrade as "less time on hosting issues, more time on client work."
Proof point: use a customer story with a support-ticket reduction number, or a story about a noisy-neighbor incident that cost a client.
CTA: offer a free migration of one client site as a proof-of-concept. Lower commitment than moving the whole portfolio.
SMB
Small business owners
Lead with customer experience, not infrastructure. "Visitors are leaving your site before it loads" makes the problem real. Most SMB owners do not know what a VPS is.
Proof point: use a customer story with a recognizable industry parallel (a local accountant, a regional retailer, a service business).
CTA: emphasize the hands-off migration and the rollback guarantee. The biggest SMB objection is "what if you break my site."
Subject Line Library
Eight subject line patterns that work
Subject lines decide whether the rest of the email gets read. The patterns below have been tested across hosting upgrade campaigns. Pick the one that matches your trigger.
1
Specific signal
"Your site at acmestore.com just hit its ceiling"
When you have a clear behavioral trigger
2
First-name + question
"Lily, did you notice this last week?"
When you want to feel personal, not bulk
3
Customer outcome
"How HostArmada cut page load by 70%"
When you have a strong same-segment story
4
Quiet check-in
"quick one about your hosting"
When the relationship is warm but quiet
5
Before the spike
"Before Q4 hits your store"
When the recipient runs ecommerce
6
Direct cost
"15 abandoned carts last month, possibly fixable"
When you can quantify the loss
7
Three-option close
"{{first_name}}, where do things stand?"
Email 3 in the sequence
8
Useful resource
"The shared-to-VPS upgrade checklist (5 min read)"
When you need a softer Email 1 opener
Pro tip
Subject line discipline: avoid the word "upgrade" in your subject lines. It primes the reader to expect a pitch and drops open rates by 15% to 25% in most tests. Save "upgrade" for the body, where the customer has already opted in by opening.
Avoid emoji, exclamation marks, and all-caps. Hosting buyers (especially technical ones) read those as low-trust signals.
Placeholder Reference
Merge fields used in the sequence
Every {{token}} in the templates above maps to a CRM field. Before sending, replace each one with your equivalent merge tag. The list below names every token used.
| Placeholder | What it represents | Used in |
|---|---|---|
| {{first_name}} | Recipient first name | Email 1, 2, 3 |
| {{domain}} | Recipient's primary domain | Email 1 subject |
| {{X}} | Number of days resource limits were hit | Email 1 body |
| {{sales_rep_name}} | Sender's name | From line, all emails |
| {{sales_rep_email}} | Sender's reply-to address | Reply-to, all emails |
| {{role}} | Sender's role title | Email 1 signature |
| {{hosting_provider}} | Your company name | From line, all emails |
| {{calendar_link}} | Booking link for the sales rep | Email 1 CTA |
| {{customer_name}} | Name of the case study customer | Email 2 subject and body |
| {{segment_descriptor}} | Short business descriptor (e.g. "WooCommerce home goods store") | Email 2 body |
| {{case_study_link}} | URL to the full case study | Email 2 body |
| {{issue}} | The specific support ticket topic | Email 1 footnote variant |
| {{growth_pct}} | Traffic growth percentage | Email 1 footnote variant |
| {{quarter}} | Calendar quarter for follow-up | Email 3 body |