GMass FAQs: Cold Email Automation, Real-Time Verification, Teams Features & Intent Data — Answered

I've lost count of the calls that start some version of: "We need to get a campaign out by Friday, the list is a mess, and we can't afford another domain getting flagged." Sales ops with urgent launch deadlines is my lane — I've handled 200-plus time-critical campaign launches over the last five years, including a few same-day turnarounds I'd rather not repeat.

GMass comes up in most of those conversations, especially when the team is already on Gmail and doesn't want to rebuild its workflow around a separate sending platform. It's genuinely useful — and genuinely easy to misunderstand. So here are the questions I actually get asked, plus a couple I wish more teams asked before the first campaign went sideways.

Questions this guide answers

• What is cold email automation — and when should a B2B sales team use it?
• What is GMass, and why does the "Google extension" thing matter?
• How does GMass real-time email verification work?
• What are the GMass Teams features, actually?
• What does the intent data feature really do?
• Why does email warmup keep coming up?
• When should you NOT use GMass?

What is cold email automation — and when should a B2B sales team use it?

Cold email automation is software that handles the mechanics of sending outreach at scale: the personalization fields, the scheduling, the follow-up sequences, the bounce handling. You set the campaign up once, and it runs without a human clicking "send" a thousand times.

A B2B sales team should use it when three things are true: you have a defined audience, you have something relevant to say to them, and you've got basic deliverability hygiene in place — SPF/DKIM/DMARC set up, and a list that isn't mostly dead addresses. Size matters less than people think. I've seen a 300-contact campaign outperform a 50,000-contact dump because the targeting was sharp and the message was specific.

When should you not use it? If the list came from somewhere and nobody can explain exactly where, or the message is "I saw you're a decision maker, let's connect" — no automation tool fixes that. It just gets you blocked faster.

What is GMass, and why does the "Google extension" thing matter?

GMass is a cold email and mail merge platform that runs as a Chrome extension on top of Gmail or Google Workspace — the "GMass Google extension" that comes up in a lot of searches. You don't log into a separate dashboard. You compose in Gmail, and the extension adds the automation layer — personalization, follow-ups, scheduling, verification, warmup, reporting.

The "Google extension" thing matters more than it sounds like. It means:

• Your team keeps working in the inbox they already live in.
• Campaigns go out from accounts that already have a sending history — which is better for deliverability than a fresh domain.
• Setup is fast. Not "fast for sales software." Actually fast.

One realistic constraint: Google publishes a sending limit of 2,000 recipients per day per user for standard Workspace accounts (500/day for free Gmail). GMass works within those limits — you don't get to ignore them. If someone tells you otherwise, they're selling something.

Most people evaluating cold email tools focus on features and pricing and completely miss the deliverability side — domain reputation, authentication, complaint rates. Those determine whether any of it works. The tool doesn't create deliverability; it respects it (or doesn't).

How does GMass real-time email verification work?

Most email verification tools clean the list before you send. GMass does verification in real time — during the send. Each address gets checked as it's processed, and invalid ones are blocked before they hit the mail server. That's a meaningful difference, because bounces are one of the signals Gmail and other mailbox providers use to judge whether you're spam.

In March 2024, I got a call about 36 hours before a product launch. The team had a 3,800-contact list, roughly half of it assembled from scraped web data, and the verification tool their previous agency used had expired. We ran the campaign through GMass with real-time verification on. I remember the exact number — 312 bad addresses got blocked before they ever reached the server. If those had gone out as bounces in the first hour, that domain would've been in a bad spot for months.

The thing people assume is that "verification" means a one-time cleaning. But lists rot. People switch jobs, companies go under, inboxes get abandoned. Real-time verification is the difference between sending to a list that was fine in January and sending to a list that's fine right now.

Our policy after that campaign: nothing goes out without a verification pass. It's the first question I ask when someone says "this is urgent."

What are the GMass Teams features, actually?

Once more than one person on your team is sending campaigns, you need visibility. That's what GMass Teams features cover: shared campaign visibility, team-level statistics, and coordination so two SDRs don't accidentally send the same message to the same prospect. I've had mornings untangling that exact mess, so this is not theoretical.

From my perspective, the value is less about admin control and more about knowing what's happening before someone asks. When a rep says "I've sent a ton of emails," you can just look. Team reporting shows volume, deliverability, and replies across the group — which is what revenue ops people actually need.

To be fair, if you need heavy governance — complex approval routing, granular role-based permissions, territory-level access rules — that's a bigger sales engagement platform. GMass Teams is built for teams that want shared context without a project dedicated to managing the tool.

What does the intent data feature really do?

Intent data in GMass is about prioritization. It pulls external buying signals into the campaign flow, so you can rank who gets your best outreach effort instead of blasting everyone at the same priority.

Practically: you sort your list by intent score and focus volume where the signal is strongest. Combined with the LinkedIn Sales Navigator integration, it's a workflow for telling apart someone who's just a name on a list and someone worth the time right now.

Full disclosure: it's a newer feature, and my experience with it comes from testing across maybe a dozen accounts — if you're running a completely different model, like enterprise ABM versus high-volume SMB, your mileage may differ. It's a prioritization aid, not a crystal ball. Test it against your own campaigns.

Why does email warmup keep coming up?

Warmup is the process of gradually increasing sending volume from a domain or mailbox so internet service providers see a human pattern instead of a spam burst. A fresh domain that fires off 5,000 emails on day one might as well send a selfie captioned "please block me."

People skip it because it's slow and boring and "we'll deal with it later." I watched a team make that exact call — or rather, I watched them not make any call, because they assumed the tool would handle it. Their domain got flagged within a week of cold sending. Recovery took about two months: new domain, fresh authentication records, a warmup sequence they should've run at the start. They saved nothing. The total cost was way higher than the "delay" they were trying to avoid.

This is also where the causation gets inverted. People think the sending tool gets emails into the inbox. Actually, you get into the inbox because your sender reputation says you're legitimate. The tool's job is to not damage that reputation while carrying the message.

"Since February 2024, Google and Yahoo require bulk senders to authenticate with SPF, DKIM, and DMARC, keep spam complaint rates below 0.3%, and support one-click unsubscribe. These aren't optional suggestions." — Google/Yahoo bulk sender guidelines

GMass has a built-in warmup feature. And honestly, if you use any tool and skip warmup, you're setting yourself up for a repeat of the story above.

When should you NOT use GMass?

Let's be straight about fit, because nobody benefits from pretending one tool is right for everyone.

• If you need a CRM, GMass isn't one. It's an outreach layer on Gmail. The CRM lives elsewhere, or already does.
• If you're planning to send to a rented list of people who never opted in — no tool will save you, and GMass will just help you get blocked faster.
• If your team lives in Outlook or a non-Gmail stack, GMass doesn't apply. It's built around Gmail/Workspace.
• If you need enterprise-grade governance — approval flows, complex routing, granular access control — a full sales engagement platform is the right shape, at the cost of a lot more complexity.
• If your team won't watch deliverability — bounce rates, spam complaints, reply management — a more powerful tool makes a bad outcome happen faster.

GMass is a strong fit for Gmail-native teams that want serious cold email without migrating to a big new platform. That's a real sweet spot. But "strong fit" isn't "always fit." Anyone who tells you otherwise is pitching, not advising.