Cold Emailing: Tactical Steps to Increase Opens and Replies (+ GMass vs Mailshake vs lemlist)

Cold email still works in B2B when you treat it like an operating system: clear targeting, conservative sending, real follow-ups, and compliance-by-default.

This guide updates the “5 tips” approach into a repeatable workflow you can hand to SDRs, founders, or growth teams and actually run weekly.

Quick take (30 seconds)

• If you want to run cold outreach from Gmail with a simple setup and strong follow-up mechanics, GMass is built around automated sequences and threaded replies.
• If you want a sales engagement workflow with trigger-based follow-ups and multi-touch tasks, Mailshake is designed around automated follow-ups that stop when a recipient takes an action (like replying).
• If your differentiation is personalization (especially visuals), lemlist supports variable-based custom images pulled from a CSV (public image URLs ending in.png/.jpeg).

Dominant search intent (what readers want)

Most searchers here want a practical playbook to improve open rates and reply rates without getting their domain flagged, their inbox rate-limited, or their team stuck doing manual follow-ups.

That means your “win condition” isn’t clever copy—it’s a system that controls volume, follow-up logic, and compliance while staying personal enough to earn replies.

Tool comparison (structured)

The 2026 cold email workflow (step-by-step)

Step 1) Define a narrow ICP and “reason to email”

Write your targeting in one sentence: “We help [role] at [company type] do [outcome] without [pain].” Then build a list that fits that sentence—don’t try to fix weak targeting with more follow-ups.

Step 2) Pick your sending motion (and tool) based on operations, not hype

• If your team lives in Gmail: pick a Gmail-native motion (for example, GMass) so sending + replies stay in the same place.
• If you want automation + triggers: pick a sales engagement platform designed for automated follow-ups (for example, Mailshake).
• If you win on personalization assets: build a “visual personalization” motion (for example, lemlist custom images via CSV variables).

Step 3) Engineer deliverability constraints into your plan (limits & pacing)

Before you write copy, decide your daily volume and ramp schedule so you don’t trigger provider limits mid-campaign.

In Google Workspace Gmail, Google documents daily sending and recipient limits and notes that users who exceed limits can be blocked from sending for up to 24 hours.

• Google Workspace Gmail lists a “maximum messages per day” (for example, 2,000 per user) and separate recipient-based quotas (including recipients per message and total recipients per day).
• Limits can change without notice and are applied over a rolling 24-hour period, so avoid “end of day” mental math.

Step 4) Write a simple email that earns the right to a follow-up

Strong cold emails are usually short, specific, and easy to answer. Avoid cramming in every feature—opt for one problem, one credible reason you picked them, and one low-friction CTA.

If you want templates your team can reuse, see Cold email templates for B2B.

Step 5) Build follow-ups that stop automatically (and don’t annoy people)

The goal of follow-ups is not “persistence” as a personality trait—it’s respectful re-surfacing with new information or a simpler ask.

• GMass positions its auto follow-ups as sequences that can continue until a reply/click/open depending on your stop conditions, and it supports threaded replies so follow-ups can appear like a normal conversation thread.
• Mailshake documents that you can add automatic follow-ups and have them stop sending when a recipient takes an action you specify (such as replying).

Step 6) Use “personalization that scales” (without faking it)

Personalization is not just FirstName. It’s a relevant detail that proves you chose the prospect for a reason (a hiring signal, a product motion, a technical footprint, a recent initiative).

If visual personalization fits your market, lemlist documents a workflow for inserting personalized images via CSV variables that map to public image URLs ending in.png/.jpeg.

Compliance floor (CAN-SPAM essentials)

If you send commercial email in the U.S., CAN-SPAM is the baseline you build on—not an optional checkbox.

• The FTC states CAN-SPAM covers all commercial messages (not just bulk email) and makes no exception for B2B email.
• The FTC’s guidance lists requirements including truthful header information, non-deceptive subject lines, identifying the message as an ad, including a valid physical postal address, providing a clear opt-out mechanism, and honoring opt-out requests within 10 business days.
• The FTC notes penalties can be up to $53,088 per violating email, so it’s worth operationalizing compliance in every template.

For your internal policy page, add a CAN-SPAM compliance checklist for cold outreach.

Implementation checklist (copy/paste for your team)

• ICP written in one sentence; list built only from that ICP.
• Daily volume and ramp schedule defined (and aligned to provider limits).
• One offer, one CTA, one follow-up reason per step.
• Stop conditions set (stop on reply at minimum).
• Unsubscribe/opt-out handling and physical address included when required.
• Tracking + review cadence: weekly subject line test, monthly offer test.

Decision tree: which tool should you start with?

1. If you’re sending from Gmail and want follow-ups that behave like normal replies, start with GMass and its threaded follow-up approach.
2. If you want trigger-based follow-ups (e.g., send based on a click) and broader engagement workflows, start with Mailshake.
3. If your market responds to “proof you looked,” start with lemlist-style image personalization and QA your asset pipeline first.

Troubleshooting (real failure scenarios)

Problem: Gmail blocks sending mid-campaign

• Likely cause: you hit a sending or recipient limit; Google notes sending can be blocked for up to 24 hours after exceeding a limit.
• Fix: reduce daily volume, stagger sends, and monitor rolling 24-hour totals (not calendar days).

Problem: Follow-ups keep going after someone replies

• Fix: set explicit stop conditions (stop on reply) and verify the behavior in your platform (GMass and Mailshake both document stop logic in their follow-up features).

Problem: Personalized images don’t render

• Likely cause: image URL isn’t public or doesn’t end in.png/.jpeg; lemlist documents these prerequisites.
• Fix: open every URL in a browser before launch; keep image dimensions reasonable (lemlist recommends under 1200px).

FAQ

Recommended external documentation

• Follow the FTC’s CAN-SPAM compliance guide when you build templates and opt-out handling.
• Use Google’s Workspace Gmail sending limits documentation to set daily quotas and avoid sending lockouts.