The Saleshandy Deliverability Problem (and the Infrastructure Fix That Doesn't Require Switching)

TLDR. Saleshandy's deliverability ceiling is the same infrastructure ceiling every shared-infra sender has — past a few hundred mailboxes the shared IPs and shared domain pools cap inbox placement at 60-70%, regardless of campaign quality. The fix is dedicated infrastructure underneath: isolated Azure tenants, dedicated IPs, automated SPF/DKIM/DMARC, and a hard per-mailbox cap of 2 outbound + 2 warmup = 4/day. Per-mailbox pricing on dedicated infrastructure runs $1.00/$0.85/$0.70/$0.55 by volume tier. Two- to four-hour setup, 14-day money-back. Saleshandy's campaign builder, sequences, unified inbox, and analytics stay exactly as they are.

Saleshandy has carved out a real position in the cold email tool market. Aggressive pricing, decent feature velocity, working unified inbox, solid reporting. Saleshandy as an application is reasonable for what it costs.

What Saleshandy doesn't provide is dedicated cold-email-grade infrastructure underneath your mailboxes. The deliverability ceiling shows up the same way it does on every other sending tool — past a few hundred mailboxes, inbox placement starts dropping despite no campaign content change.

This article explains exactly what breaks at scale on Saleshandy, how to verify whether you're hitting it, and the architecture that keeps Saleshandy as your campaign manager while fixing the deliverability layer underneath.

The 30-second answer

Same pattern as every other sending tool: Saleshandy the application is fine. The infrastructure tier underneath is what bottlenecks cold email at scale.

What Saleshandy is, what it isn't

Saleshandy ships the campaign manager + email scheduler + unified inbox + reporting. The team built a usable product at a price point lower than Instantly or Smartlead.

What Saleshandy uses but doesn't fully own:

• The mailboxes themselves — connected via SMTP/IMAP or OAuth from your Workspace / Microsoft 365.
• The sending IPs — shared pool when using bundled SMTP, your Workspace IPs when using Gmail / Outlook native.
• The DNS / SPF / DKIM / DMARC setup — Saleshandy documents requirements but doesn't provision DNS.
• The warmup network — Saleshandy-managed shared network of customers.

Shared parts work at low volume. They break at scale the same way they break for every other shared-infrastructure cold email setup.

Why "cheap sending tool" doesn't mean "cheap to run cold email"

Saleshandy's pricing positions it as the cost-conscious choice. The Pro plan at the time of writing is in the $39/month range, much lower than Instantly or Smartlead. That's true on the sending-tool subscription.

The math gets different when you add infrastructure:

The Saleshandy subscription is a fraction of the total. The infrastructure (Google Workspace user licenses) is the actual cost. And that infrastructure is shared-domain, shared-reputation, suspension-risk infrastructure.

Replacing the Workspace layer with dedicated cold-email-grade infrastructure changes the cost math:

Lower total cost AND dedicated-IP-level reputation control. The infrastructure layer is where the real money goes; replacing it changes the entire economics.

Saleshandy-specific failure modes (beyond shared infrastructure)

Beyond the shared-IP wall, Saleshandy operators hit four configuration-specific failure modes. Each one is silently invisible in Saleshandy's reports — the symptom is "lower reply rate" without obvious cause.

1. Tracking-domain defaulted to saleshandy.com shared subdomain. Saleshandy lets operators configure a custom tracking domain, but the default routes click and open tracking through track.saleshandy.com. That shared subdomain shows up in spam-trigger checkers as a known cold-email tracking domain, contributing to spam-folder placement. The fix is configuring a custom tracking domain (CNAME-mapped to Saleshandy's tracking endpoint) and validating end-to-end before any campaign uses it. The Email Deliverability Test catches misconfigured tracking domains in the link-audit step.

2. Per-mailbox daily caps left at Saleshandy defaults. Saleshandy's UI defaults per-mailbox sending higher than the deliverability-safe ceiling. Operators rarely lower them because the UI doesn't surface the cold-email cap explicitly. Mailboxes sending 10-30 cold emails per day burn reputation in 2-4 weeks. The fix is manually setting Daily Sending Limit to 2 across every mailbox, and accepting that scale comes from more mailboxes, not higher per-mailbox volume.

3. Email Verifier credits sized below actual contact volume. Saleshandy's Email Verifier is credit-based — operators buy verification credits separately from the sending plan. When credit allocations run low mid-campaign, operators sometimes skip verification on the remaining contacts to launch on schedule. Unverified contacts bounce at 5-15%, which tanks IP reputation faster than any other single factor. The fix is sizing verifier credits to twice the contact volume (allowing for re-verification on lists older than 90 days) and pausing campaign launches when verification credits run low.

4. Sequence step-spacing too tight, triggering rate-limit deferrals. Saleshandy's sequence builder lets operators set delays between steps. Operators sometimes tighten delays to compress campaigns, ending up with the same mailbox sending to the same domain multiple times per day. Gmail's per-sender per-recipient rate limit triggers receivers to defer or reject above ~3 messages per day to a single recipient. The fix is leaving step delays at 2-4 days minimum and confirming no two steps for the same prospect land on the same day.

5. Bulk mailbox import creating IMAP credential drift. When operators bulk-import 20+ mailboxes via Saleshandy's CSV importer, typos in IMAP credentials (wrong port, wrong host casing, wrong password) cause individual mailboxes to silently fail authentication. The unified inbox shows the campaign sending but never receives replies because IMAP polling fails for the broken mailboxes. The fix is running Saleshandy's "Test Connection" on every imported mailbox before launching campaigns.

Diagnostic checklist: run before contacting Saleshandy support

Before opening a support ticket, run through this ordered checklist. Most Saleshandy deliverability problems trace back to one of these.

1. Confirm warmup is active per-mailbox. Subscription-level toggle is necessary but not sufficient. Audit individual mailbox warmup status.
2. Run the Email Deliverability Test on your sending domain. SPF, DKIM, and DMARC misconfigurations block deliverability work before any tweak helps.
3. Check sending IPs against the Blacklist Checker. Spamhaus, Barracuda, SORBS — any blocklist hit explains the inbox-rate drop. If listed, follow the blocklist removal playbook.
4. Open Google Postmaster Tools. Domain Reputation below High on a previously-High domain is the infrastructure-side signal.
5. Pull per-mailbox bounce rate over 30 days. Above 3% on stable list quality means receiver-side reputation rejections. Cross-reference 5xx codes against the SMTP error library — codes like 550 5.7.1 SPF fail at Gmail, 550 5.7.1 DKIM fail at Gmail, or 550 5.7.1 unusual rate of unsolicited mail point to different root causes.
6. Audit per-mailbox daily send caps. The deliverability-safe cap is 2 outbound + 2 warmup = 4/day. Anything above 5 is burning reputation.
7. Verify Email Verifier coverage on every active campaign's contact list. Lists older than 90 days bounce at 5-10% even after past verification.
8. Sample 10 sends through Mail-Tester.com. Score below 8/10 = content or authentication needs work.
9. Validate the custom tracking domain end-to-end. Default track.saleshandy.com is a shared subdomain that shows up in spam triggers.
10. Check IMAP connection status per mailbox. Drifted credentials silently break reply detection.

Related deliverability fixes

The infrastructure ceiling shows up across every cold-email sender. Same fix architecture, different connection details:

• Instantly deliverability fix — same shared-IP and Workspace ceiling.
• Smartlead deliverability fix — canonical long-form on campaign-vs-infrastructure decoupling.
• Lemlist deliverability fix — same fix architecture, different connection flow.
• EmailBison deliverability fix — AI-first sender; same infrastructure underneath.

Diagnostic: is Saleshandy's infrastructure ceiling your problem?

Five signals. Two or more present = you're hitting it:

1. Inbox rate at 50 mailboxes was 85%+; at 200 mailboxes it's 60% or below. Classic shared-pool scaling curve. Individual mailboxes still test fine; the pool doesn't.

2. Reply rate dropped while open rate stayed roughly the same. Open rate gets prefetch noise from Apple Mail and Gmail proxies. Replies require real primary-inbox placement. Same opens with fewer replies = more spam-folder placement.

3. Postmaster Tools Domain Reputation drifted to Medium. Without a campaign change, that's the leading indicator of infrastructure-side reputation slipping. (Reading Postmaster Tools →)

4. SMTP rate-limit errors showing in Saleshandy's logs. A few percent is normal. Double-digit percent means receivers are throttling your IPs.

5. Bounce rate above 2% despite stable list quality. Reputation-driven rejections look like bounces but are infrastructure problems. (Bounce-code diagnostic →)

The fix: dedicated infrastructure under Saleshandy

The architecture is a clean split — Saleshandy stays the campaign manager, ColdRelay becomes the infrastructure layer.

Saleshandy supports custom SMTP/IMAP via their /v1/sender-emails/connect endpoint with emailServiceProvider: "other" — which is exactly the path ColdRelay-provisioned mailboxes go through.

The migration: keep Saleshandy, swap the infrastructure

Concrete steps:

1. Provision domains + mailboxes through ColdRelay. 60 minutes fully automated.
2. Push mailboxes into Saleshandy. Either via Saleshandy's API directly (ColdRelay's dashboard supports one-click push) or by exporting a Saleshandy-formatted CSV and importing manually.
3. Run new campaigns on the new mailboxes in Saleshandy. Existing campaigns continue on old mailboxes during the transition.
4. Pause old infrastructure for 7 to 14 days while new domain reputation builds. The new mailboxes are isolated; they don't inherit reputation from old shared-pool history.

No data migration. Campaigns, contacts, sequences, reporting stay in Saleshandy.

What about Saleshandy's bundled warmup?

Saleshandy includes warmup as a feature. Useful for the first few weeks of a brand-new domain when any warmup signal helps. At scale, the shared-network signals dilute and ColdRelay's infrastructure-level warmup (running at the SMTP layer with your dedicated IP) accumulates reputation faster.

Both can run in parallel — Saleshandy's contributes to message-exchange volume, ColdRelay's keeps the SMTP + IP history clean. No conflict.

What changes for the customer

The only operational change: in Saleshandy's "Sender Emails" page, swap the old Workspace-connected mailboxes for the new ColdRelay-provisioned ones. Reassign campaigns. Done.

FAQ

Will I lose Saleshandy data?

No. Campaigns, sequences, contacts, reports, unified inbox history — all stay in Saleshandy. The change is which mailboxes Saleshandy routes through.

Does Saleshandy support custom SMTP/IMAP mailboxes?

Yes. Saleshandy's API endpoint /v1/sender-emails/connect accepts emailServiceProvider: "other" for custom SMTP/IMAP setups. The bulk-import CSV also has fields for SMTP/IMAP host, port, encryption, etc. ColdRelay's dashboard exports a Saleshandy-formatted CSV or pushes via API directly.

How long until I see the deliverability improvement?

7 to 14 days for the first signal (Postmaster Tools Domain Reputation reaching High). Reply rate improvement typically lands in week 3 to 4 as the new mailboxes' reputation matures.

Is Saleshandy's daily quota the bottleneck, or is it the underlying infrastructure?

Almost always the infrastructure. Saleshandy's per-mailbox daily limit is configurable; ColdRelay's enforced cap is 2 cold sends + 2 warmup per mailbox per day (the volume that consistently keeps Postmaster Tools Domain Reputation at High). The limit isn't the bottleneck — the IP and domain reputation underneath the limit is.

Can I A/B test old vs. new infrastructure?

Yes. Most customers run parallel for the first 30 days — old campaigns continue on old infrastructure, new mailboxes provision on ColdRelay, side-by-side reply rates show the lift before full migration.

What if I'm using Saleshandy with Gmail/Outlook OAuth instead of SMTP?

The migration path is the same. ColdRelay provisions custom SMTP/IMAP mailboxes; you add them to Saleshandy as "other / custom" provider type instead of Gmail/Outlook OAuth. Saleshandy treats them as standard mailboxes; the campaign builder works identically.

Other sending tools?

Same pattern. ColdRelay has one-click push integration with Instantly, Smartlead, Lemlist, and EmailBison. The infrastructure layer is identical regardless of which sender sits on top.

Why is the daily cap 2 outbound + 2 warmup = 4/day per mailbox?

The cap isn't about infrastructure capacity. It's about Gmail's and Outlook's complaint-rate tolerance. Above 5 sends per mailbox per day, even low-single-digit complaint rates push past the threshold where Gmail flags the mailbox as a spam source. Below 5, complaint volume stays under the threshold even when list quality dips. Scale comes from more mailboxes, not higher per-mailbox volume. Saleshandy's UI defaults are higher; lower them manually.

Microsoft 365 vs Google Workspace for Saleshandy?

Both have shared-domain reputation pools and hit similar walls at scale. Microsoft 365 silently rate-limits at lower volumes before any individual mailbox hits its hard cap; Google Workspace has higher limits but more aggressive TOS enforcement. The structural fix is the same — dedicated infrastructure outside the corporate tenant. On the Microsoft 365 side, dedicated infrastructure has the added advantage of cross-tenant alignment when sending to other Microsoft 365 recipients.

What metrics should I monitor weekly?

Five metrics, weekly cadence. (1) Postmaster Tools Domain Reputation — should hold High. (2) Per-mailbox bounce rate — alert at 3%. (3) IP reputation via the Blacklist Checker on every sending IP. (4) Reply rate by campaign — drops signal content or deliverability issues. (5) IMAP polling status in Saleshandy — drift breaks reply detection silently.

When should I consider migrating off Workspace mailboxes entirely?

When you see three or more of: domain reputation Low for 21+ days, multiple sending IPs on major blocklists, bounce rate consistently above 5%, account suspensions on Workspace mailboxes, or a sustained reply-rate decline below 1% on previously-working campaigns. Tactical fixes inside Saleshandy don't recover from these — fresh domains on dedicated infrastructure is the structural move. The 14-day money-back window covers the migration trial.

Saleshandy is fine as a sending tool. Pair it with infrastructure purpose-built for cold email at scale, and the deliverability ceiling moves out by an order of magnitude.

See ColdRelay + Saleshandy in action → Try ColdRelay free · Test your current deliverability → Free test