How to Run a Cold Email Campaign Targeting Salesforce Service Cloud Large Companies Prospects in 2026

Quick Answer: You’ve built a list of Salesforce Service Cloud large company decision-makers using Origami, which now includes a built-in email sequencer — so you can turn that list into a live campaign without leaving the platform. Here’s how to refine your list, craft a 3-touch sequence that speaks directly to enterprise support leaders, and send it all from one dashboard.

If you haven’t built your list yet, stop and read our guide on how to build a list of Salesforce Service Cloud Large Companies Prospects first. You’ll need a clean, qualified list before anything else. The rest of this post assumes you have that list loaded inside Origami and you’re ready to run a real campaign.

At the end of this guide, you’ll have three full email templates you can copy, tweak, and paste directly into Origami’s sequencer — and you’ll know exactly how to launch, track, and iterate. Everything I share here comes from running these exact campaigns for consulting practices and SaaS vendors that sell into large Service Cloud accounts.

---

Step 1: Build the List in Origami

Even though your list is probably already sitting in Origami from the parent guide, I want to ground this in the exact prompt that produced it. That way, if you need to expand your list or refresh it next quarter, you know exactly what to type.

The prompt I use to surface large Service Cloud prospects inside Origami looks like this:

Salesforce Service Cloud users at companies with 1,000+ employees and 50+ support agents, specifically those using Service Cloud for case management and field service, with decision-maker titles like VP Customer Service, Director of Support, Head of Service Operations, or IT Service Management leaders.

Origami’s AI agent takes that plain-English request, searches the live web, chains data sources, enriches contacts, and qualifies leads automatically. In a few minutes you get back a table with verified names, email addresses, job titles, company size, industry, and sometimes additional context like technologies deployed alongside Service Cloud.

If you’re still on the free plan (1,000 credits, no credit card required), you can test this right now and see exactly how the output looks. Paid plans start at $29/month, and you only pay for credits to enrich leads — the sequencer (which we’ll get to in a moment) is included on all paid plans at no extra cost.

---

Step 2: Refine and Qualify the List for Email

A raw export from any list‑building tool still needs a human review. Enterprise Service Cloud prospects are not all equal. You want to separate the list into segments that will get different messaging and different follow‑up cadences.

Here’s how I refine a Salesforce Service Cloud large company list inside Origami:

2.1 Remove obvious bad fits

Scan for:

• Wrong geography: If you only serve North America, strip EMEA and APAC contacts.
• Non‑decision‑makers: Titles like “Support Agent Lead” or “Service Cloud Developer” might be influencers, but they rarely own the budget for a new project. I keep anyone at Director level or above, and occasionally a Sr. Manager if the company is very large (10,000+ employees).
• Companies that clearly use alternative CRMs: Origami’s enrichment sometimes surfaces that a company also uses Zendesk Enterprise heavily. If Service Cloud is just a small part of a hybrid stack, your pitch needs to change — maybe save them for a different campaign.

2.2 Segment by what matters for Service Cloud buyers

I create at least three sub‑lists:

1. Field Service heavy — contacts where the company likely runs Salesforce Field Service. Pain points: mobile workforce scheduling, remote asset management, real‑time inventory visibility.
2. Pure case‑management — large contact centers with high ticket volumes. Pain points: agent efficiency, knowledge management, AI‑powered deflection.
3. Migration candidates — companies still on Classic with 500+ agents, likely feeling pressure to move to the latest Service Cloud architecture. Pain points: technical debt, custom code rewriting, downtime risk.

If your offer is relevant to all three, one sequence might work, but I usually tweak the Day 1 email to reference the specific pain. The templates I’ll give you below are written for the case‑management / pure support segment, since that’s the largest slice.

2.3 What “qualified” looks like for this audience

For a large Service Cloud account, a qualified lead isn’t just someone who has the title. I look for:

• The company has at least 50 support agents (less than that and they might not have the complexity to justify an add‑on or consultancy).
• The contact’s role is directly responsible for service delivery — VP Customer Experience, Director of Support Operations, Head of Service Management.
• There’s an event or trigger that makes timing right: a recent job change (decision‑maker with fresh mandate), a known technology partnership, or public mentions of “transforming customer service.”

Origami surfaces many of these signals during enrichment, so you can filter quickly without opening a dozen browser tabs.

---

Step 3: Create the Email Sequence

This is where the campaign lives or dies. The list gets your foot in the door; the sequence determines if someone actually replies.

Origami gives you two ways to build your sequence:

1. Paste your own templates: Write your own multi‑touch messages, set the delay between each touch (Day 1, Day 3, Day 7 — or any cadence you want), and launch.
2. Let the AI agent write it: Just tell Origami’s agent, “Generate a personalized 3‑day email sequence for my Salesforce Service Cloud enterprise leads,” and it writes unique messages based on each contact’s title, company, and industry.

I’ve found that option 2 works surprisingly well for initial testing, but for a high‑stakes campaign targeting large companies I always start with my own copy. Below is the exact 3‑touch sequence I use for the case‑management segment. You can copy, tweak, and paste directly into Origami’s sequencer.

The 3‑Touch Sequence (copy‑paste ready)

Setting the cadence: I send touch 1 on a Tuesday morning, touch 2 on Thursday (2 days later), and the breakup on the following Tuesday (7 days after the first email). That rhythm respects enterprise inboxes and avoids the Monday/ Friday dead zones.

---

Day 1: Initial Cold Email

Subject: Scaling Service Cloud at [Company]? Preview text: Quick idea on reducing agent handle time

Hi [First Name],

I saw [Company] leverages Service Cloud for support at scale. Many enterprise teams I speak with struggle to keep agent handle time down as case volume grows — especially when knowledge articles and routing rules haven’t been revisited in years.

I help service leaders tune their Service Cloud setup to cut resolution time without big custom code projects.

Would a 15‑minute call next week make sense?

Best, [Your Name]

Why this works: It’s specific to Service Cloud, names a real operational pain (handle time), and frames the ask around small, practical optimization — not a full platform overhaul.

---

Day 3: Follow‑Up (Different Angle)

Subject: Service Cloud + AI — a quick thought Preview text: How peers are cutting resolution time by 40%

Hi [First Name],

Following up on my note. A recurring theme among large Service Cloud shops is layering AI‑driven case classification and recommended next steps on top of their existing workflows. When done right, it trims minutes off every interaction without retraining agents.

I have a few examples from teams of similar size — some saw measurable CSAT lifts within a month.

Happy to share them over a brief call.

Cheers, [Your Name]

Why this works: It introduces a strategic layer (AI) that many Service Cloud leads are actively evaluating, backed by a soft proof point. It also shows you understand the platform’s evolving capabilities.

---

Day 7: Breakup Email

Subject: Closing the loop Preview text: Last try — a resource worth seeing

Hi [First Name],

I won’t keep following up. If optimizing your Service Cloud environment is a priority this quarter, I pulled together a short guide on the top 5 process bottlenecks we fix in enterprise deployments — things like case routing decay, outdated macros, and field service dispatch gaps.

Reply “guide” and I’ll send it over. If the timing isn’t right, no problem at all.

Appreciate your time.

[Your Name]

Why this works: The breakup leaves the door open without pressure. The offer of a specific, low‑commitment resource often triggers a reply from busy executives who meant to respond earlier.

---

I keep each message between 50‑100 words. No marketing fluff, no “we’re the leading provider,” just direct, industry‑aware language that shows you know what it’s like to run a large service operation on Salesforce.

If you’re targeting the field service or migration segments, tweak the pain points accordingly. For field service, replace handle time with “first‑time fix rate” and “mobile worker scheduling.” For migration prospects, emphasize “de‑risking the move from Classic to Lightning” and “code audit.”

---

Step 4: Send the Sequence Directly from Origami

This is where Origami saves you from the usual headache of exporting CSVs, syncing with a separate outreach tool, and trying to track everything across two dashboards.

You launch the campaign entirely inside Origami.

Here’s the flow:

1. After building and qualifying your list, go to Origami’s Sequencer tab.
2. Create a new sequence, paste your three email templates, and set the delay between each touch (I use Day 1, Day 3, Day 7).
3. Assign the sequence to your Salesforce Service Cloud list.
4. Hit Launch.

Origami’s built‑in email sequencer sends the multi‑step sequence automatically with configurable delays. While the campaign runs, everything you need is in the same dashboard where you built the list:

• Sending & tracking: Opens, clicks, and replies appear in real time. No switching tools.
• Prospect context: When you look at a contact’s activity, you can still see their enriched profile — title, company, tools used — so you immediately recall why you reached out.
• Automatic un‑enrollment: If someone replies, they exit the sequence instantly. You’ll never accidentally send a breakup email after a meeting is already booked.

This matters more than you think for enterprise outreach. A VP of Customer Service who replies “tell me more” doesn’t want to get an automatic “closing the loop” email three hours later. Origami handles that gracefully.

Cost: only pay for enrichment, not sending

The sequencer is included on all paid plans. You’re not paying per email sent; you’re only paying for the credits used to enrich your leads. For a typical campaign targeting 200 Service Cloud contacts, the credit cost is minimal, and you can test with the 1,000 free credits on the Free plan before committing.

Response rates to expect

For this specific audience — large‑company Service Cloud decision‑makers — a healthy positive reply rate falls between 7% and 12% if your list is tight and your messaging is relevant. When I first ran a version of the sequence above, I saw an 11% positive reply rate on a list of 180 contacts, with three meetings booked from the Day 3 follow‑up alone.

If you’re getting below 5% after two weeks:

• Iterate the messaging before you toss the list. Try a different opening pain point or a shorter Day 1 email. Sometimes the smallest tweak — like mentioning a specific Service Cloud feature (Omni‑Channel routing vs. just “case management”) — lifts replies.
• Refine the list if replies are cursory or auto‑responses. You might have too many legacy Classic users who aren’t thinking about optimization, or too many lower‑level decision influencers.

One platform from list to outreach

That’s the core advantage of using Origami for this: you find, enrich, sequence, send, and track without leaving the product. No exporting CSVs, no syncing with a separate sequencer, no broken link between your prospect data and your outreach actions.

When a contact replies, you’re looking at the same enriched profile you built, so you can pivot the conversation naturally based on what you already know — their service tech stack, company size, and the reason they ended up on your list in the first place.

---