The State of Telemarketing in 2026: STIR/SHAKEN, Lead Quality, and Sustainable Outbound Calling

Sustainable outbound calling in 2026 requires three separate checks: whether the caller is using an authenticated number, whether the business may place this particular call, and whether the contact information is accurate enough to make the conversation relevant. Passing one check does not satisfy the others.

STIR/SHAKEN helps authenticate caller ID. Lead enrichment can improve the information available before dialing. Neither creates consent or guarantees that a carrier will deliver a call without a spam label.

For sales and operations leaders, the practical priority is straightforward: build a calling program around verified identity, documented permission where required, current suppression data, and measurable contact quality.

What the latest numbers actually show

The FTC reported more than 258 million registered telephone numbers and more than 2.6 million Do Not Call complaints for fiscal year 2025 in its January 2026 report announcement. Complaints increased from the previous fiscal year. These are registry and complaint figures, not measurements of every unwanted call or of legitimate outbound conversion rates. FTC report announcement

That distinction matters when evaluating industry claims. A national complaint total cannot tell a business how many prospects will answer its calls. Likewise, a vendor’s customer success story cannot establish a universal improvement from enriched leads.

The useful takeaway is that recipients continue to report unwanted calling at substantial scale. A responsible outbound program should make relevance, recognition, and the ability to stop future calls central to its design.

What STIR/SHAKEN verifies

STIR/SHAKEN uses digital signatures to carry caller-identity information between participating providers. Full, or A-level, attestation indicates that the originating provider knows the caller and has verified the caller’s right to use the displayed number. B-level attestation indicates a known customer whose right to use that number has not been verified. Twilio technical documentation

An authenticated number can still originate an unwanted call. The authentication does not establish the recipient’s consent, the truth of a sales pitch, or the legality of the campaign. Those require separate evidence and controls.

Attestation also feeds a broader call-analytics process. Providers can use it alongside other signals when deciding whether to ring, label, divert, or block a call. A-level attestation therefore cannot promise delivery or a clean display on every handset. Twilio explanation of authentication and call analytics

The framework continues to evolve. In FCC 26-32, the FCC proposed stronger upstream-provider diligence, attestation standards, and measures addressing implementation gaps. The cited document is a proposed-rulemaking notice; its proposals should not be presented as already-effective requirements. FCC 2026 proposed-rulemaking notice

Ask your voice provider how it verifies number authorization, assigns attestation, preserves authentication across routes, and investigates incorrect blocking. Keep business identity and number ownership records current.

Unenriched versus enriched leads

An unenriched record might contain a name, number, and acquisition date. The calling team may have little information about whether the number is valid, whether it belongs to the intended person, or whether the inquiry still matches the offer.

An enriched record adds relevant, traceable information. Depending on the source and purpose, that could include a validated number format, line type, current company, role, service area, or recent first-party interaction. Phone-intelligence providers distinguish fields such as line type, line status, and reassignment information because they answer different questions. Twilio Lookup documentation

A useful workflow separates four categories:

• Contact accuracy: Is the number usable, and is the identity match sufficiently reliable?
• Commercial fit: Does the person or business match the campaign’s actual audience?
• Permission evidence: What supports this seller contacting this recipient through this calling method?
• Suppression status: Has the person opted out, or does another restriction prevent the call?

These categories should remain visible rather than collapsing into a single “good lead” score. An accurate match can still be ineligible for calling. A promising prospect can still have a stale number.

Reassignment deserves particular attention. The FCC’s Reassigned Numbers Database is designed to help callers identify whether a number has been reassigned since the date they knew the intended consumer held it. That check is different from proving who currently owns the number or establishing permission to call. FCC explanation of the database’s purpose and query dates

Measure enrichment without manufacturing a lift claim

The sources reviewed for this article do not establish a controlled, industry-wide percentage improvement from enriched versus unenriched telemarketing leads. Results depend on the original list, enrichment coverage, matching accuracy, offer, and calling process.

Test the benefit in your own operation. Apply the same required compliance and suppression controls to every test group. Then compare an optional enrichment treatment with the existing compliant process, using comparable lead sources, ages, agent assignments, and calling windows.

Track outcomes with explicit denominators:

• Wrong-party conversations divided by live conversations
• Intended-person conversations divided by eligible unique leads
• Qualified opportunities divided by eligible unique leads
• Opt-out requests divided by live conversations
• Total campaign cost divided by qualified opportunities

Include enrichment expense, agent time, and telephony costs. Record excluded leads and match confidence. A higher answer rate alone can hide more wrong-party calls; fewer dials can still produce better economics.

Build compliance into the calling decision

For covered consumer telemarketing, the FTC requires call-list synchronization with the National Do Not Call Registry at least every 31 days. Company-specific do-not-call requests need their own suppression process. Applicable exceptions require careful evaluation; a past relationship does not override a consumer’s request that the seller stop calling. The TSR’s general residential calling window is 8 a.m. to 9 p.m. at the called location, subject to its consent exception. State rules and FCC requirements may add restrictions. FTC compliance guide

Store the evidence behind eligibility: acquisition source, consent language where relevant, seller identity, capture date, applicable channel, and later changes. Avoid treating a purchased or appended telephone number as proof of permission.

Artificial-voice technology needs specific review. The FCC has confirmed that AI-generated voices fall within the TCPA’s artificial-or-prerecorded-voice provisions. Telemarketing calls using artificial or prerecorded voices generally require prior express written consent under the applicable FCC rules. A conversational interface does not remove those obligations. FCC declaratory ruling

For operations, prompt suppression is the safer design goal: capture requests where they arrive and propagate them to every relevant campaign and vendor. Keep auditable records. The FTC’s updated TSR recordkeeping guidance specifies five-year retention for required records, including relevant call, consent, and do-not-call information. FTC recordkeeping update

Keep litigator screening in its proper place

A vendor’s litigation-risk flag cannot determine whether a call is lawful. It is separate from DNC screening, consent verification, reassignment checks, and honoring opt-outs. Absence from a litigation-risk dataset provides no permission to call.

If such screening is used, assess its provenance, matching errors, and appropriate purpose with counsel. Every recipient deserves the same compliance controls, whether or not a database predicts that they might complain or sue.

A practical launch checklist

Before releasing a campaign:

1. Document the audience, seller, purpose, calling technology, and applicable jurisdictions.
2. Verify the evidence supporting call eligibility and apply required suppression checks.
3. Deduplicate records and quarantine uncertain identity matches.
4. Confirm authorized caller ID, working callbacks, and provider authentication settings.
5. Use appropriate local calling windows and a restrained contact cadence.
6. Test opt-outs end to end, including external calling partners.
7. Monitor wrong-party contacts, complaints, labels, and qualified outcomes; investigate deterioration before increasing volume.

Frequently asked questions

Does A-level attestation mean a call is compliant?

No. It addresses caller identity and number authorization. Consent, DNC restrictions, content, and calling practices remain separate questions.

Can enrichment make a purchased list safe to call?

Enrichment can add useful information, but it cannot supply missing permission merely by finding a phone number. Eligibility needs a separate, documented assessment.

What should an outbound team improve first?

Start with suppression reliability and contact accuracy, then verify caller identity and campaign relevance. Measure qualified outcomes and recipient experience before scaling dial volume.

Scope: U.S.-focused operational guidance, researched October 13, 2026. This article is educational and is not legal advice. Requirements vary by jurisdiction, recipient, call purpose, and technology; obtain qualified review for a specific campaign.