We Had 36 Hours to Verify 3,000 Mobile Numbers. Here's What Cognism Support Taught Me

I'm a revenue operations lead at a B2B SaaS company. I've handled more 'this is urgent' data requests than I can count — maybe 200, give or take. But the one I remember best happened in March 2024, 36 hours before a campaign deadline.

The Setup: A Lead Gen Tool Wasn't Enough

We had 3,000 contacts in our CRM. Actually, 2,847, but 3,000 sounds better in the urgent message the SDR lead sent me. It was 4:37 PM on a Tuesday, and the email said, 'We're sending texts before the conference on Thursday. We need verified mobile numbers for as many of these as possible.'

My first reaction wasn't panic. We already used Cognism. I'd always treated it as a lead generation tool: build a list, export, upload to Outreach. I didn't really think of it as an enrichment engine. When I first started managing data tools, I assumed the one with the most contacts wins. That assumption didn't last long.

The Process: The Cognism Mobile Phone Number Verification Process

I uploaded the CSV to Cognism's enrichment feature. The first output looked solid. If I remember correctly, we got a 72% match rate, and about a third of the records came back with mobile numbers. Then I saw a column I'd never noticed before: verification status.

Some records said 'Unverified.' Some said 'Landline.' Some said 'Risk.' That's when I realized what the Cognism mobile phone number verification process actually does. Here's something vendors won't tell you: 'verified mobile number' isn't one thing. Some tools mark a number as verified if it once existed. The Cognism process, as it was explained to me by support, flags whether a number is live, whether it's a mobile or a landline, and whether it's risky to contact. We needed mobile numbers for SMS, so a 'direct dial' wouldn't help. The statuses let us filter for what we actually needed.

So I contacted Cognism support. This is the part I almost skip over, because it's not about data. I've opened support tickets for other tools and waited a day for a generic answer. This time, a support engineer replied in about four minutes. They walked me through the verification process in plain English.

At one point I asked a blunt question: 'How is this different from buying a list?' Their answer stuck with me.

'We don't help you send more messages. We help you avoid sending messages that get you into trouble.'

The surprise wasn't the data quality. It was the support. Never expected a support conversation to be the deciding factor in a data purchase. In hindsight, it makes sense. Under a deadline, you need someone who can explain what a field actually means. That's more valuable than another 10 million rows.

The Real Test: CRM Enrichment Under Pressure

The surprise wasn't the match rate. It was what happened after the data came back. We had to push enriched records into Salesforce, and that's where most enrichment projects fall apart. We'd tried before with another tool, and the integration created duplicate accounts and overwrote good fields. I only believed in the append-only setting after ignoring it once and spending a weekend cleaning up the mess.

Cognism's CRM enrichment let us map mobile numbers and verification fields to custom fields. We set it to append only, so existing data stayed intact. Setup took maybe 30 minutes. That doesn't sound like a headline feature, but in a deadline situation, it's the feature that saved us.

A few years ago, a CRM integration like this would have required an IT ticket and a week of back-and-forth. That's changed. Modern tools assume a RevOps person can set it up. It's a good thing, but it also means you need to evaluate the mapping experience carefully.

What Should Revenue Operations Teams Evaluate in Data Enrichment Features?

If you're evaluating a lead generation tool or an enrichment platform, don't start with the size of the database. Start with these five things.

1. The verification process. Ask what 'verified' means. Look for statuses like mobile, landline, dead, unverified, and risk. Decide which ones you're willing to target.
2. CRM enrichment controls. Can you control append vs. overwrite? Can you map fields yourself? Does it dedupe? This matters more than match rate.
3. Compliance. With GDPR and CCPA, you need to know where data comes from and whether the vendor is accountable. According to Cognism's GDPR page (cognism.com/gdpr, accessed January 2025), they're registered with the ICO. Verify current registration for any vendor you consider.
4. Support speed. When a campaign is on the line, support chat is more useful than a knowledge base article.
5. Integration with your stack. A tool isn't useful if it doesn't sync with your CRM and your sales engagement platform.

Also, we weren't some giant enterprise account with a dedicated CSM. We were a mid-sized team on a regular plan. Cognism support still took us seriously. That might sound small, but if you've been ignored by a vendor because your annual contract is under six figures, you know it matters.

The Campaign and the Aftermath

The campaign went out on time. I don't have the exact response rate in front of me, and I don't think quoting a number from memory is honest. What I can say is we avoided the disaster we were heading toward. We had real mobile numbers, a field in Salesforce that told SDRs which contacts were verified, and no last-minute list purchase.

Oh, and we built a checklist for next time. It starts with 'check the verification statuses before you upload anything to Outreach.' It ends with 'book a call with support before you buy, not after you're in a crisis.'

I used to think the data itself was the product. I was wrong. The product is confidence. You need to know which numbers are safe, which are guesses, and which are traps. That's what Cognism support taught me, and it's why I now evaluate data enrichment features completely differently.