Your DIDs Are Probably Not “Burned”... Your Dialing Strategy Might Be

By: Ryan Shatzkamer

There are few phrases in outbound calling that create more panic than this one:

“Our numbers are burned.”

Or its cousin:

“The carrier blocked all of our DIDs.”

Or the really dramatic version:

“We need to replace everything immediately.”

And look, I get it...

When contact rates fall off a cliff, when agents are sitting around waiting for connects, when leadership is asking what happened to production, when someone sees a chart that says “block rate” and that number is suddenly 20%+...

The symptom FEELS like a catastrophic system failure.

It FEELS like something outside of your control.

It FEELS like the carriers woke up this morning, held a meeting, looked at your beautiful DID pool, and said:

“Yeah... kill those.” 🙂

BUT...

In many cases, that is not actually what happened.

And, more importantly, if you misdiagnose the problem, you will almost certainly prescribe the wrong fix.

That wrong fix is often number swapping.

Throw away the “bad” numbers.

Buy new numbers.

Start fresh.

Problem solved.

Except...

Usually, not really.

At outboundIQ, we have spent a lot of time looking at this problem across thousands and thousands and thousands of DIDs, across hundreds of customers, across many verticals, carriers, dialers, and campaign strategies.

And one of the biggest lessons we have learned is this:

A “burned DID” is usually not a permanent object.

It is usually a symptom.

And symptoms require diagnosis.

Not panic.

Not superstition.

Diagnosis. 🙂

Let’s start with the most important point.

Spam labeling is not generally a static, permanent property of a phone number.

One of the better explanations of this comes directly from Hiya’s own caller reputation guidance:

• “Spam labeling is dynamic for every phone call, not a static property of a phone number.”

That sentence matters a lot.

Because the industry often talks about spam tags as if the number itself has been branded forever.

As if the ten digits are now cursed.

As if the number was good on Monday, evil on Tuesday, and must be thrown into the ocean by Wednesday.

No.

That is not how these analytics engines generally work.

Every call is being evaluated against historical and real-time signals.

That means the same DID can behave very differently depending on how it is being used.

High velocity.

Bad pacing.

Repeated attempts.

Calling the same person over and over.

Aggressive recycle rules.

Poor answer behavior.

Low customer engagement.

Bad call outcomes.

All of these things matter.

So when someone says, “This DID is burned,” the first question should not be:

“How fast can we replace it?”

The first question should be:

“What behavior caused the system to view this traffic negatively in the first place?”

Because if the behavior does not change, the new numbers will eventually look just like the old numbers.

That is the trap.

And it is a very expensive trap.

NOW...

Let’s talk about “blocked” calls.

This is another area where the terminology can get people into trouble.

In many contact center environments, the dialer does not hand you a clean, magical disposition that says:

“Carrier blocked this call.”

Wouldn’t that be nice?

Just a big flashing sign that says:

“VERIZON BLOCKED THIS ONE.”

“AT&T DID NOT LIKE THIS ONE.”

“T-MOBILE IS MAD AT YOU.”

But that is not, generally, how the data comes through.

Instead, what you often have are system outcomes.

Busy.

Dial Error.

Operator Intercept.

Other SIP-code-driven results.

So when a platform or report shows an “estimated block rate,” it may not be a literal count of confirmed carrier blocks.

It may be an amalgamation of dispositions that are being used as a proxy for likely blocking, failure, or negative network outcomes.

“22% estimated block rate” and “22% of all calls were definitively blocked by the carrier” are not the same statement.

One is a diagnostic signal, the other is a conclusion.

And if you treat the signal as the conclusion, again, you risk applying the wrong fix.

Let’s say your estimated block rate is being driven by Busy, Dial Error, and Operator Intercept.

The next question should be:

“What happens after those outcomes?”

Because sometimes the most damaging part of the entire setup is not the original system outcome...

It is what the dialer is configured to do next.

If a Busy result forces a redial in 15 minutes...

And an Operator Intercept forces a redial in 4 hours...

And a Dial Error forces a redial in 2 hours...

What have we really built?

We have built a machine that repeatedly hammers the same records after negative system outcomes.

And then we act surprised when the ecosystem responds negatively.

🙂

This is where the “burned DID” conversation starts to become much less mysterious... because now we are not talking about cursed numbers.

We are talking about behavior.

The system hits a bad outcome, the configuration forces the record back into the dialing stream.

The same prospect gets called again, another negative outcome happens.

The number reputation weakens.

The carrier analytics engine sees poor traffic.

The contact rate drops and the team panics.

Someone says the DIDs are burned.

Someone suggests buying new ones.

And the loop continues.

That is not a phone number problem.

That is an operational design problem.

And operational design problems should be solved operationally.

In many cases, the better move is patience and pacing.

For example, instead of forcing a redial 15 minutes after Busy, maybe that record should be marked Do Not Dial reactivated after a couple days.

Instead of forcing a redial 4 hours after Operator Intercept, maybe that should also rest for a couple days.

Instead of forcing a redial 2 hours after Dial Error, maybe that record should rest for 8 hours.

These are not universal rules for every business in every industry, of course.

But the principle is what matters:

• Do not blindly recycle negative outcomes back into the dialer at aggressive intervals and then blame the DID when the ecosystem reacts.

That is like repeatedly touching a hot stove and deciding the stove is “biased” against your hand.

No.

Stop touching the stove.

🙂

Now, let’s talk about number swapping.

We have written about this before, and I will say it again:

We are generally not fans of mass DID swapping.

Not because numbers never need to be replaced.

Of course they do sometimes.

Individual numbers can underperform.

Certain DIDs may need to be rested, remediated, paused, registered, reviewed, or eventually replaced.

That is normal.

But mass swapping as a primary contact-rate strategy is usually a sign that the actual problem has not been understood.

And worse, it can create new problems.

When you own and manage the same DID inventory over time, you are building history.

You are building consistency.

You are giving the ecosystem a chance to understand how those numbers behave.

You are maintaining callback continuity.

But when you throw away a large block of numbers and buy a large block of new ones, you are introducing unknown history.

Those “new” numbers may be new to you.

They are not necessarily new to the world.

Someone may have used them before.

Someone may have abused them before.

Someone may have run horrible traffic through them before.

So now, in the name of escaping “bad” history, you may have just purchased someone else’s bad history.

Congratulations.

You are now the proud owner of a mystery box. 🙂

And sometimes, from a compliance and customer-experience perspective as well.

Because numbers used for outbound calling should not simply disappear the moment they become inconvenient.

People may call them back.

People may want to speak to someone.

People may want to request not to be called.

Unreturnable calls are bad for everyone.

So when the instinct is “replace everything,” the better instinct is usually:

Slow down.

Look at the data.

Find the behavior.

Fix the configuration.

Remediate the inventory.

Monitor the response.

Then make targeted changes if needed.

Not all DID issues are DID issues.

Some are redial issues.

Some are disposition issues.

Some are lead-age issues.

Some are campaign-mix issues.

Some are agent-behavior issues.

Some are just bad reporting definitions creating scarier language than the data actually supports.

And THIS is why the diagnostic matters.

If someone says, “Carrier X blocked 700 numbers,” but those same numbers are still producing ANY contacts on Carrier X, that should give you pause.

If a DID has meaningful volume and a non-zero contact rate, it may be struggling, but it is probably not “blocked outright.”

If a carrier is supposedly the problem, but its contact rate is outperforming another major carrier, that should give you pause too.

If the estimated block rate is high, but the dispositions feeding that number are being aggressively recycled, you may have found a major contributor right there.

This is why we believe DID reputation management is not just about having more numbers.

It is about using the numbers correctly.

More inventory can help.

Absolutely.

But more inventory will not save a bad strategy.

More numbers will not fix toxic redial logic.

More DIDs will not cure poor pacing.

More area codes will not magically undo aggressive retry behavior.

More replacement inventory will not solve a process that keeps recreating the same reputation problem.

The real goal is not to own the largest pile of phone numbers.

The real goal is to build a healthy, stable, well-paced, well-managed outbound ecosystem.

One where numbers are treated like assets, not disposable napkins.

One where negative outcomes are handled intelligently.

One where disposition logic supports reputation instead of destroying it.

One where remediation and registration are part of a process, not a panic button.

One where the team understands the difference between a confirmed carrier block, a spam label, an estimated block-rate proxy, and a low contact rate.

Because those are not all the same thing.

And treating them as the same thing is how teams end up chasing ghosts.

So, the next time someone says:

“Our DIDs are burned.”

Ask:

“Based on what?”

The next time someone says:

“We need to replace all these numbers.”

Ask:

“What behavior are we changing when we do that?”

Because the answer is usually not one magic switch.

It is a system.

Inventory.

Pacing.

Disposition logic.

Registration.

Remediation.

Campaign configuration.

Lead strategy.

Agent behavior.

Reporting definitions.

All working together.

Or not.

When they work together, DID reputation can recover surprisingly quickly.

We have seen numbers that were supposedly “dead” begin performing again once the usage pattern changed.

Not because the digits changed.

Because the behavior changed.

And that, really, is the point.

There is no such thing as an “evil” phone number.

There is only poor use, good use, and everything in between.

So before you burn the DIDs...

Make sure the DIDs are actually the thing on fire. 🙂

Just something to think about, I guess...