Compliance

Convoso DID Health: High Volume Dialing Without Scam Likely

Convoso admins fighting Scam Likely at volume: how Ignite scoring and ClearCallerID work, and what still needs a carrier provisioned fix.

By James Hill, Founder, RizzDial · 2026-10-14

A Convoso admin watches agents burn through a list fast, then watches connect rates sink as Scam Likely starts showing up on screens the campaign depends on. Convoso builds tools directly into the platform for exactly this: Ignite scores every outbound number, ClearCallerID tracks which DIDs carriers have flagged or blocked, and local caller ID pools spread dials across numbers that match the area code being called. Those tools manage the DID pool you already have. They do not change what kind of number sits underneath it.

What is actually happening to a Convoso DID pool at volume?

Think of a DID pool less like a list of numbers and more like a budget. Every number in rotation can absorb a certain amount of dial volume and carrier scrutiny before something trips a flag. At low volume a thin pool barely gets tested. At high volume, the same pool gets hit from every angle at once, agents dialing fast, repeat attempts on the same list, and a narrower spread of area codes if local presence matching isn't configured carefully.

Convoso's own materials describe this lifecycle directly. Ignite automates the full number lifecycle, purchasing, scoring and assigning numbers, according to Convoso's Ignite product page. That phrasing matters because it treats a DID pool as something that needs ongoing management, not a one time setup. A pool sized for a smaller campaign does not automatically scale when dial volume climbs, and a pool that worked fine last quarter can thin out if numbers get retired faster than new ones come in.

The retirement side is the part admins tend to overlook. If scoring flags a number but nothing replaces it, the remaining numbers in the pool absorb more volume each, which accelerates the same wear pattern that got the first number flagged. A healthy pool needs replacement to roughly keep pace with retirement, in words rather than a fixed count, because the right pace depends on calling volume and how concentrated the dial list is by area code.

How does Convoso Ignite's 1 to 100 scoring actually work?

Ignite assigns every outbound number a score on a 1 to 100 scale, and Convoso says it uses that score to automatically favor the healthiest numbers available at any given moment, according to Convoso's Ignite product page. The inputs behind that score are also documented there: Convoso says the evaluation runs continuously on live data, including answer rates, contact rates, flagging trends, and carrier specific behavior.

That continuous evaluation is the useful part for an admin trying to diagnose a problem rather than just react to one. A number with a dropping score but no flag yet is an early warning. A number that drops fast right after a volume spike points at calling pattern, not the number itself. A number that scores low consistently across weeks, regardless of volume, is a candidate for retirement before it ever gets fully flagged.

None of that scoring changes what the number is underneath. Ignite is choosing the highest scoring option from the pool you have, the same way a dispatcher routes calls to the least busy line. If every number in that pool shares the same underlying weakness, the one Ignite currently favors will eventually show the same pattern as the one it replaced.

Where does ClearCallerID fit once a number is already flagged?

ClearCallerID is Convoso's detection and tracking layer, not a prevention tool. Convoso describes it as a product that "quickly identifies flagged and blocked phone numbers and tracks their impact via the tool's monitoring dashboard," according to Convoso's ClearCallerID launch announcement. It checks numbers "automatically across the major telco carriers on a regular basis," the same announcement states, and it can "detect 7+ flagged call categories from major carriers, including Telemarketer, Scam Likely, Fraud Risk, and more," according to that same page.

For teams running ClearCallerID Pro, Convoso adds automated alerts and carrier registration on top of the same dashboards that show which DIDs are flagged or blocked by each carrier, according to Convoso's ClearCallerID Pro announcement. The alerting matters more at volume than it does on a small list, because a flag on one number in a large pool can get lost in the noise of everything else running fine.

What ClearCallerID does not do is stop the label from happening. It tells an admin faster that it already did. That is a meaningful upgrade over checking caller ID screens manually, but it is still a response to a problem the carrier's analytics engine already decided on.

How do you work through a Convoso DID health check in order?

Run these in sequence rather than jumping straight to swapping numbers. Most flagged pools have more than one contributing factor, and fixing calling pattern while ignoring pool size, or the other way around, tends to produce the same result a few weeks later.

1. Open the Convoso admin portal and pull up Ignite's per number scores for the campaign in question. Note which numbers are trending down rather than just which ones are already flagged.
2. Check the ClearCallerID dashboard for any numbers already flagged or blocked by a specific carrier, and note which carrier, since the pattern often points at concentration in one area code or network.
3. Review local caller ID pool settings for area code matching, confirmed as a feature on Convoso's dialing admin page, and check whether the pool assigned to this campaign actually covers the area codes being dialed or is leaning on a handful of default numbers.
4. If ClearCallerID Pro is active, review the carrier registration and alert settings so a new flag reaches someone instead of sitting in a dashboard nobody checked that day.
5. Compare dial volume per number against the pool size for the campaign. If a handful of numbers are carrying most of the volume, that concentration is a bigger risk factor than any single setting.
6. Set a retirement cadence tied to Ignite's score trend rather than waiting for a full flag, and make sure replacement numbers are added to the pool at roughly the same pace numbers get pulled out.
7. If calling pattern looks clean, the pool is sized reasonably, and labels still keep returning, the underlying number type is the next thing to look at, not another setting inside Convoso.

That last step is where most high volume teams eventually land, because Convoso's tools manage the pool, not what each number looks like to a carrier before it ever gets a score.

What does Convoso's STIR/SHAKEN attestation claim actually cover?

Convoso states that it "signs outbound calls with the highest level of attestation under the STIR/SHAKEN framework, ensuring accurate caller ID information, stronger trust, and higher answer rates," according to Convoso's compliance page. Attestation is a claim about authentication, that the call genuinely comes from the number shown, and a carrier's separate analytics engine still decides independently whether to label that traffic as spam. For the full breakdown of attestation levels and how CNAM factors into labeling across every provider in this cluster, see the pillar guide to stopping Spam Likely labels.

Why would a carrier provisioned number still help after all of this?

Everything above manages the pool Convoso gives you more numbers to assign, a score to rank them, and a dashboard to catch flags faster. None of it changes how a carrier's network classifies the traffic type underneath a given number before Ignite ever scores it. James Hill, RizzDial's founder, has run outbound sales teams and seen this pattern directly: numbers bought through a platform like GoHighLevel tend to connect at a lower rate because carriers gauge that traffic as VoIP, voice over internet traffic, rather than a line from a traditional carrier. That is his read from managing calling operations, not a rule published by any carrier.

RizzDial's approach works on the number itself before it ever enters a pool. "We essentially make the carriers look at the number as if it's an actual number that you go purchase from the SIM carrier like AT&T, Verizon, T-Mobile," James explains, "and we do that by provisioning the numbers with the carriers." Building those ties took years, James says, pointing to direct relationships with AT&T, Verizon and T-Mobile that go back well before RizzDial existed as a platform and run on infrastructure built for that purpose rather than something assembled recently. Calls placed this way are signed and go out over a STIR/SHAKEN compliant carrier network, which is a baseline, not a guarantee against a future label.

Monitoring works the way a high volume pool needs it to. "Every single number is scrubbed every single day," James says, meaning each number is checked daily for spam flags, separate from any Do Not Call list scrubbing. He adds that RizzDial also pings real devices every day to see how numbers are showing up on a client's screen, which feeds into raising pickup rates. When something trips, James says the response is to pull the number rather than wait out a flag, keeping each line looking like a direct carrier line from AT&T, Verizon or T-Mobile, staying clean, and notifying the client once a number gets flagged. Per number reputation monitoring with flag alerts is an add on for teams that want notifications tied to specific lines. On the pool size question that matters so much at Convoso's volume, James is blunt about why a single number does not hold up: calling from just one number burns it out fast once volume lands on it, which is the same rotation logic behind Ignite and local caller ID pools, just applied to numbers provisioned differently underneath. He is also clear that RizzDial does not require an exclusive setup. Teams can bring their own carrier, such as their own Twilio account, and lean on managed carrier services rather than a locked in arrangement. Numbers a team brings that way stay that provider's numbers; the carrier provisioned path described above is RizzDial's own managed carrier service, built on its direct carrier relationships. Teams running dials through the GoHighLevel integration or through the RizzDial dialer run on carrier provisioned numbers that get the same daily checks. For GoHighLevel users specifically weighing LC Phone against a carrier provisioned pool, the LC Phone and Spam Likely breakdown covers that comparison directly, and the VoIP number versus carrier number explainer covers why the underlying number type drives so much of this in the first place.

What won't any of this fix?

No scoring system, dashboard, or carrier relationship repairs a list problem. If the numbers being dialed came from a purchased list with no consent on file, or the same contact gets called again after opting out, complaints keep landing regardless of how the DID pool is managed or who provisioned the underlying numbers. Swapping a flagged number for a fresh one just moves the same complaint pattern onto a different line if the calling behavior behind it does not change. Even a carrier provisioned, daily checked number can pick up a label if volume spikes hard in a short window, because rescoring by the analytics engines behind these labels is ongoing, not a one time pass. Treat Ignite's score, ClearCallerID's dashboard, and a carrier relationship as ways to reduce risk and catch problems fast, not as a guarantee a label never shows up again.

If your Verizon reach is a meaningful share of a Convoso campaign, the Verizon Call Filter and TNS breakdown covers what that carrier's analytics engine looks at specifically. Teams that have already worked through registration and scoring tools and still need to file a dispute directly with a carrier can walk through the dispute process for outbound sales teams. For warm follow up with contacts who already know your business and carry an iPhone, messages and calls over iMessage and FaceTime Audio through RizzDial's sister product Beam ride over data, so carrier spam labels do not apply there at all.

What FAQs come up about Convoso DID health and Scam Likely labels?

What does a low Convoso Ignite score actually mean?

Convoso says Ignite evaluates every phone number continuously using live data, including answer rates, contact rates, flagging trends, and carrier specific behavior, with scores ranging from 1 to 100, according to Convoso's Ignite product page at convoso.com. A low score means one or more of those inputs has moved in the wrong direction recently, not that the number is permanently unusable.

Does ClearCallerID stop a number from getting labeled in the first place?

No. Convoso describes ClearCallerID as a tool that identifies flagged and blocked phone numbers and tracks their impact through a monitoring dashboard, checking numbers across major carriers on a regular basis, according to Convoso's ClearCallerID launch announcement at convoso.com. That is detection and tracking of a label that already happened, which is still useful, but it is a different job than preventing the label.

What is different about ClearCallerID Pro?

Convoso positions ClearCallerID Pro as the premium tier of the same reputation tool, adding automated alerts and carrier registration alongside dashboards that show which DIDs are flagged or blocked by each major carrier, according to Convoso's ClearCallerID Pro announcement at convoso.com. The core monitoring is the same; Pro adds the alerting and registration layer on top.

Does Convoso's attestation claim mean calls never get a Spam Likely label?

No. Convoso says it signs outbound calls with the highest level of attestation under the STIR/SHAKEN framework, ensuring accurate caller ID information, stronger trust, and higher answer rates, according to Convoso's compliance page at convoso.com. Attestation confirms the call came from the number it claims to use; a carrier's analytics engine still makes its own, separate decision on how to label that traffic.

Do local caller ID pools in Convoso replace a carrier provisioned number strategy?

Not entirely. Convoso lists local caller ID pools for area code matching and local presence dialing as a feature available to dialing admins, according to Convoso's dialing admin page at convoso.com. That spreads volume across more numbers tied to the dialed area code, but the underlying numbers can still read as internet voice traffic to a carrier depending on how they were provisioned.

How do you get a Convoso pool checked against a carrier line?

If Ignite scores are trending down across a campaign and ClearCallerID keeps catching new flags no matter how the pool gets resized, that pattern is worth walking through against a carrier provisioned setup directly. Book a demo and bring your current DID health numbers so the comparison is based on your actual pool, not a generic pitch.