"Dialer" isn't what it used to be

This is the TitanX newsletter, where GTM is built on conversations, targeting, and, of course, Phone Intent™ - Read more.

I had two calls last week with heads of sales. In both, they mentioned not wanting to use a "dialer" because of the "pause" that hurt connect rates.

But that "pause" is only a feature of one very specific kind of dialer - parallel dialers.

In their mind, as in the minds of many sales leaders today, you're cold calling using one of a few options: a sequencer with a calling functionality (HubSpot, Outreach, Salesloft, Salesforce), your own mobiles (everyone agrees it's antiquated, but it happens, and not always the worst thing), or a parallel dialer (Nooks, Orum, etc.).

But this is hardly the full realm of sales dialer technology.

There are many kinds of dialer. They differ wildly. And yes, your success with the phone does depend on making a good choice here.

It happens. Usually these days, it means IT has done a great job with email deliverability, or a GTM Engineering person/vendor has deployed AI powered email campaigns (they sometimes work), or you run a solid ABM play with low volume calling.

But for most sales leaders with teams of more than a couple SDRs, not having a dialer is like competing in the Tour De France entirely on foot: you're moving… slowly.

If you've ever dialed out of Outreach or Salesloft or HubSpot you know this to be true. They work alright, but are incredibly "click-intensive" to navigate call steps. Worse than workflow, however: they do not invest much in call deliverability.

So the ambitious sales leader of the last few years goes shopping. And what does he find?

Parallel dialers.

(Sure, if Google is the point of shopping origin, he finds CloudTalk, Aircall, Justcall, Kixie - but most sales leaders sense these tend to be underpowered for cold calling use cases).

Not to mention, Orum for a while, and lately Nooks, have invested massively in awareness.

So much so that they have incited a rare case of semantic creep - which is what happens when the definition of a thing bleeds out into oversimplification.

In this case, "dialer" became synonymous with "parallel dialer" - the same way "smartphone" became synonymous with "phone."

If you're using the phone to sell things in 2026, you should know how parallel dialers work. This will explain why "dialer" should not mean "parallel dialer." I'd say I'm decently qualified to explain this, given I helped build and QA test a parallel dialer a couple companies back.

It's hard to do.

The "problem statement" for a parallel dialer works like this:

We're a sales org doing outbound calling, and we're not having enough conversations.

The parallel dialer response to this problem is:

What if you automatically called more numbers, and if someone picks up, our tool will hang up on all other lines and patch you in to the live connect?

Sounds ok. Until you think about it:

Interestingly, all five of those questions have one answer: the parallel dialer algorithm.

Every parallel dialer relies on an AI algorithm to determine if the line that picks up is being picked up by a human or a voicemail or a phone tree. It's not easy to do. Some phone trees and voicemails sound very much like a person answering the phone.

In which case, the algorithm will patch you through to a voicemail.

If multiple people pick up, the algorithm must hang up on all but one.

As far as TCPA compliance, that's a sticky subject. Parallel dialers have a sort of special carve-out in TCPA: that if a human picks up, a human representative of your organization must be available to talk to them within two seconds. This is why parallel dialer vendors will fight tooth and nail to claim they stay well under this limit, often citing under 1 second or something very specific like 0.7 seconds.

Parallel dialers are hungry animals. They require two things to be fed:

If you should rotate numbers every 80 dials, that's only a few minutes in a parallel dialer scenario.

Even the platform that created the parallel dialer category says it’s not worth it anymore:

This is where things get interesting and where most sales leaders' education stops.

Power dialers call one number at a time, automatically, from a list. No pause. No algorithm deciding whether a human or voicemail picked up. You just hear the ring, and if someone answers, you're there. If it goes to voicemail, you drop a pre-recorded message and move on. FrontSpin is an extremely robust power dialer. So are PhoneBurner and a handful of others.

The difference matters more than you think. Power dialers give you speed without sacrificing the one thing that actually produces pipeline: a clean first impression. No pause. No confused prospect saying "hello? hello?" while your algorithm figures out if they're a person.

Single-line dialers with click-to-call are what most of you already have inside your SEP. Outreach, Salesloft, HubSpot. These are fine if you're making 30 calls a day. They are not fine if you're trying to have 15-20 conversations.

The point is: you have choices. And the choice you make directly impacts three things that most sales leaders don't connect to their dialer decision: deliverability, compliance, and the size of your reachable market.

Every outbound call your team makes is being evaluated by the carrier on the other end. AT&T, Verizon, T-Mobile - they all run analytics engines (Hiya, TNS, First Orion respectively) that are watching your calling patterns in real time.

These analytics engines don't care about your intent. They care about your behavior. And your behavior, as a high-velocity outbound caller, looks a lot like a robocaller's.

Short call durations. Low answer rates. Volume spikes. Lots of calls from the same number. These are the signals that get your numbers flagged as "Spam Likely."

And once you're flagged? Over 95% of those calls go unanswered. That's not a typo. Ninety-five percent.

This is the dirty secret of the parallel dialer value proposition. They promise more conversations through more simultaneous dials. But more simultaneous dials means more numbers burned faster. It means more short-duration calls (algorithm hangs up when multiple people answer). It means lower average call duration across the board. It means you're triggering every single flag that carriers are looking for.

You're optimizing for volume on a channel that punishes volume.

There's a framework called STIR/SHAKEN. If you don't know what it is, you need to. It's a caller authentication protocol mandated by the FCC that verifies your identity as a caller. Calls get assigned an attestation level - A, B, or C - and that level directly impacts whether the carrier on the other end trusts your call enough to let it through without a spam label.

A-level attestation means your provider vouches for your identity AND your right to use that number. This is what you want.

B-level means your provider knows who you are but can't verify your relationship to the number. This is where most sales teams end up if they haven't done the work. And it's where problems start.

Here's what you should actually be doing - and I stole most of this checklist from our own onboarding because we obsess over this stuff with customers:

Cap your call velocity per number. We've seen internal data and industry benchmarks converge around 75-80 calls per day per number as the ceiling. After that, you're playing with fire. Parallel dialers blow past this in minutes.

Rotate intelligently. Rotation isn't just "use a different number." It's having enough clean, warmed numbers in rotation that no single one takes on a suspicious pattern. And it's pulling flagged numbers out immediately - not after your reps have been dialing into the void for two weeks wondering why no one picks up.

Register with the carrier analytics engines proactively. You can register your numbers with Hiya, TNS, and First Orion before they flag you. Most teams only discover these tools after the damage is done. That's backwards.

Monitor your number health weekly. If your reps' calls are lasting 3-4 seconds and going to voicemail, that's not "bad luck." That's your numbers showing as spam. Just because you're not being flagged as spam with one carrier doesn't mean you're not being flagged as spam at all. If your calls are lasting three, four, five seconds and going to voicemail, you're appearing as spam likely.

If you're a sales leader evaluating your phone tech stack, here's my actual advice:

Stop conflating your dialer decision with your deliverability strategy. They're different problems. Your dialer moves calls. Your deliverability strategy ensures those calls land. One without the other is a waste.

If you're parallel dialing, at least understand the cost. You're burning numbers faster, cutting your reachable market, introducing a pause that hurts first impressions, and creating TCPA exposure that your legal team probably hasn't fully evaluated. That doesn't mean parallel dialers are always wrong. It means the tradeoffs are real, and most teams don't quantify them.

Invest in the boring stuff. STIR/SHAKEN compliance. Number rotation protocols. Weekly number health audits. It's not sexy. It's not a LinkedIn post that gets 700 likes. But it's the difference between your calls reaching real humans and disappearing into the spam void.

And get intelligence on your list before you dial it. Knowing who answers the phone before you call them changes every downstream metric. Connect rate, conversion rate, rep efficiency, number health, morale. All of it.

The dialer category has been oversimplified into "parallel or nothing." It shouldn't be. 

Your phone strategy deserves more nuance than that.

Thanks for reading,

Evan Dunn (LinkedIn)

P.S. If you have questions, hit reply. I read every response.