From List to Meetings: A Tactical Email Campaign for Selling to High-Volume Support Teams on Zendesk & Salesforce (2026)

You've already used Origami to build a list of high‑volume support leaders on Zendesk and Salesforce. Now you need to turn that list into meetings—and you can do it without leaving the platform. Origami has a built‑in email sequencer on all paid plans, so you can launch a multi‑touch campaign directly from the same tool where you found the leads. No exporting, no syncing, no jumping between tabs. This guide walks through exactly how I refine, message, and send to this audience—and I’m including the full three‑touch sequence you can steal.

If you haven’t built the list yet, start with how to build a list of Selling to High-Volume Support Teams on Zendesk & Salesforce? Why Your Prospecting Playbook Is Broken. The rest of this assumes you’ve already got your list in Origami and are ready to launch.

---

Step 1: Build the List in Origami (A Quick Recap)

Just so we’re aligned, here’s the exact prompt you typed into Origami to pull this audience:

Find VP/Director/Head of Support at companies with 50-1000 employees, using Zendesk Support or Salesforce Service Cloud, handling >1,000 tickets per month, located in the US and Canada. Exclude companies with <25 employees.

In seconds, Origami’s AI agent searched the live web, chained data sources, enriched every contact, and qualified out the noise. What you got back: a targeted prospect list with verified names, work emails, direct dials where available, titles, company size, industry, tech stack signals (including Zendesk/Salesforce presence), and a confidence score based on how well each record matched your criteria.

If you haven’t run this yet, grab a free account—Origami gives you 1,000 credits with no credit card, enough to test a small batch.

---

Step 2: Refine and Qualify—Because a List Isn’t a Campaign

Raw output isn’t ready to email. You need to make a few manual passes so every send counts, especially when you’re targeting a specific persona: the support leader who’s drowning in tickets on Zendesk or Salesforce.

Remove obvious misfits first. Scan for titles that aren’t really decision-makers—individual contributors, QA analysts, tier‑2 team leads with no budget. Keep only VPs, Directors, Heads, and Senior Managers of Support, CX, or Operations. If a company uses Zendesk but only has one support person, that’s not high‑volume; cut them if employee count is under 30.

Segment into micro‑buckets. I split the list by:

• Zendesk vs. Salesforce Service Cloud (because the pain points differ—Zendesk users often hit scalability walls, Salesforce users wrestle with complexity and cost).
• Job title seniority (VP/Director vs. Manager). The Director gets a slightly different opener than the Manager.
• Company size band (50–200, 201–500, 501–1000). Mid‑market teams are my sweet spot; they feel the pain but still have budget flexibility.

What “qualified” looks like for this audience:

• Title: VP Customer Support, Director of Support Operations, Head of Customer Experience, Senior Support Manager.
• Company: 50–500 employees with a clear Zendesk or Salesforce Service Cloud footprint.
• Signals: Recent job post for support specialists, recent funding, growth in ticket volume (inferred from tech stack expansions), or a competitor tool on their site.
• One under‑used signal: look for companies whose support email is support@company.com with no help desk aliases; that often means they’re still early in their tooling journey and open to change.

Segmenting now means your sequences can hit the right nerve later.

---

Step 3: Create the Email Sequence

Inside Origami, you have two ways to build your outbound.

Option 1: Paste your own templates

Write your own 3‑touch sequence (like the one below), paste each message template into Origami’s sequencer, set the delays—I use Day 1, Day 3, Day 7—and hit “Launch.” Origami will personalize placeholders like , , and any custom field you’ve enriched automatically.

Option 2: Let the AI agent write it

Alternatively, you can ask Origami’s agent to generate a personalized 3‑day email sequence for every lead automatically. The agent reads the lead’s profile—title, company, industry, tools they use—and writes messages that feel custom without you lifting a finger. It works well if you’re scaling fast, but I always start by pasting my own proven sequence first and then A/B against the AI version later.

Below is the sequence I’ve used successfully with high‑volume support leaders. Each message is 50–100 words, short, and directly addresses pain points specific to Zendesk and Salesforce Service Cloud environments. Steal it outright.

---

Touch 1 — The “I See Your World” Email (Day 1)

Subject: idea for reducing your Zendesk ticket volume Preview: Without adding headcount.

Hi ,

I noticed runs a high‑volume support operation on Zendesk. Most teams I talk to at your scale are losing hours every week to manual classification, macros that don’t adapt, and the same repeat questions eating agent capacity.

We help support teams cut ticket volume by 30-40% using AI‑powered deflection that lives alongside Zendesk, not replacing it. Agents get the low‑intent work off their plate, and CSAT usually climbs because responses become faster.

Worth 15 minutes to see if this fits? Happy to show you how it works with Zendesk specifically.

Best,

---

Touch 2 — The “Peer Proof” Follow‑up (Day 3)

Subject: how a similar team cut first‑reply time 50% Preview: (and reduced escalations)

Hi ,

Just a quick follow‑up. A support director at a company like yours (similar ticket volume, also on Zendesk) added our layer and saw their average first‑reply time drop from 14 hours to under 7 in the first month. Escalations fell too because AI caught the easy stuff before it hit an agent.

They didn’t change headcount, didn’t rip out Zendesk. They just made their existing workflow lighter.

I’d love to share a 2‑minute screen recording and see if it sparks any ideas for ’s queue.

---

Touch 3 — The Breakup (Day 7)

Subject: closing the loop Preview: No more emails from me.

Hi ,

I’ll leave you alone after this. If now isn’t the time, I get it—support leaders are swamped.

But if the ticket volume ever makes you wonder whether you can answer faster without hiring, I’d still be glad to show you how we help teams inside Zendesk (and Salesforce) run leaner. The door stays open.

---

You can tweak the tool name or value prop to match what you sell, but keep the structure: acknowledge their specific platform, share a relevant outcome, don’t over‑pitch. Support leaders get boilerplate cold emails daily; being direct and platform‑aware will set you apart.

---

Step 4: Send the Sequence Directly from Origami

Here’s where the built‑in sequencer changes your workflow. In Origami, you simply select the list (or the segmented bucket), attach the sequence, set the sending schedule, and click launch. No CSV export, no email tool login, no manual import. The whole campaign runs from the same dashboard where you built the list.

What you see while it runs:

• Opens, clicks, replies—all reported back to the contact record in real time.
• Full context doesn’t disappear after the send. While looking at a contact’s engagement, you can still see their enriched profile: title, company size, tech stack, even the data sources Origami used. That means when you reply, you remember exactly why you reached out.
• Automatic un‑enrollment is built in. If a lead replies, the sequencer stops for that person. No risk of sending a breakup email after someone says “let’s talk.”

Cost structure: The sequencer itself is free on all paid plans. You only pay for the credits used to enrich leads—not for sending emails. So once you’ve built your list, the outreach is zero additional cost.

What response rate to expect: With this audience, expect a 3–7% reply rate if your list is well‑targeted and your first email lands. Zendesk and Salesforce users are bombarded with generic automation pitches; but when you name their platform and reference ticket volume pain specifically, engagement is noticeably higher. I usually see 4–5% reply at scale, with 1–2 conversions (meetings booked) per 100 sends.

When to iterate on messaging vs. iterate on the list: If open rates are above 50% but reply rates are under 2%, your subject lines work but your body copy doesn’t resonate—rewrite the email, not the list. If opens are below 35%, your list may have too many non‑decision‑makers or outdated emails; re‑check the enrichment and refine your segmentation. Origami lets you re‑enrich any list with a click, so you can tighten the audience without starting over.

---