Close CRM sequences need a seed panel per rep

Close is a sales CRM built around calls and email. Reps connect their own mailbox — Gmail, Outlook, or a custom SMTP — and Close orchestrates sequences on top of that mailbox. The whole model is that the sender is a real person, not a marketing domain. Prospects get a message from Anna at the company, not from noreply@marketing.company.com.

That architecture is excellent for reply rates. It is also fragile for deliverability, because every sales rep becomes their own sending entity with their own reputation, their own DMARC alignment, and their own placement pattern. If Anna’s Outlook mailbox quietly starts landing in Junk, Close will not tell you. Close reports opens, clicks, and replies — not folder placement. You need seed addresses on every rep’s sequence to catch this.

How Close sequences actually send

When a rep enrols a lead into a sequence, Close queues the email with the rep’s connected mailbox. The email goes through Gmail’s or Microsoft’s SMTP, signed by their DKIM, aligned to their domain in DMARC (or not, depending on how Close is configured). Each step of the sequence is an individual outbound message originating from that mailbox.

Three consequences follow:

• Per-rep reputation. Anna and Ben both work at the same company, but their mailboxes build reputation independently. Anna could land inbox while Ben lands spam.
• Per-mailbox volume limits. Gmail and Microsoft cap daily outbound. A rep pushing 300 sequenced emails a day is already at the edge of those caps.
• Mailbox health drifts silently. One rep replying to a spammy inbound chain, or having their mailbox flagged by corporate IT, changes placement with no signal in Close.

Why “open rate” lies in Close

Close tracks opens via a 1-pixel tracker. Modern mail clients — Apple Mail, Gmail with image proxying, Outlook with privacy features — either pre-fetch or block these pixels. The result is that open rate has become a noisy, provider-biased signal. You cannot use it to distinguish “my deliverability is fine” from “my deliverability tanked but recipients still pre-fetched the pixel.”

Reply rate is the only hard signal. But reply rate is volume-sensitive: at five prospects per rep per day, three replies versus one reply feels like a crisis but is statistical noise. You cannot detect a two-week deliverability slide from reply volume alone.

Seed addresses restore a ground-truth signal. The seed inbox is literally a mailbox that received (or did not receive) the email. No pixel games, no reply noise.

Setting up per-rep seed panels

The unit of deliverability in Close is the rep’s mailbox. Your seed setup should reflect that.

Step 1: seed leads per rep

For each rep, create a small set of seed leads in Close. Give each seed lead a realistic company, a realistic title, and an email at a different major provider (Gmail, Outlook, Yahoo, Yandex, Mail.ru). Tag them with seed-rep-anna, seed-rep-ben, and so on.

Step 2: enrol seeds in every sequence

Whenever a rep starts or updates a sequence, enrol their seed leads alongside real prospects. You can do this manually per sequence or via the Close API to automate enrolment. The seeds receive every step exactly like a real lead.

Step 3: check seeds daily

Reps should open their seed mailboxes at the end of the day and confirm that today’s sequence steps landed inbox. Two minutes per rep. When a seed flags junk or Promotions, raise it immediately before the sequence continues to 50 more prospects tomorrow.

Close-specific deliverability pitfalls

Close has a few sharp edges that seed testing will surface:

• SPF misalignment when using custom SMTP. Reps sometimes point Close at a shared SMTP relay. If SPF is not updated to include that relay, DMARC fails and seeds land junk at Microsoft.
• Tracking pixel triggering Promotions. The Close open-tracking pixel, combined with link rewriting, is a classic Gmail Promotions signal. Seeds will show this instantly.
• New reps on day 1. A brand-new rep with no sending history will often land Promotions at Gmail for the first week. Seed testing during warmup helps you see the ramp.
• Reply-chain contamination. A rep’s mailbox also receives normal business email. Spam there hurts the whole sending reputation.

Turning seed data into alerts

Once you have seed panels on every rep, turn it into a routine instead of an ad hoc check. A simple rhythm that works for a five-rep team:

1. Monday morning: spot-check every rep’s seed inbox at Gmail and Outlook. One minute per rep.
2. Mid-week: a deliverability tool run against each rep’s domain to confirm SPF, DKIM, DMARC still pass and placement is stable at 20+ providers.
3. Friday: review the week’s seed placement log. Any rep with more than one day of Promotions or Junk gets their sequence paused and reviewed.

FAQ