Your client calls a lead back four minutes after the form comes in, and the lead's phone says the call might be spam. The FCC just proposed writing down exactly what a carrier has to know before it can say otherwise.

Every agency running lead gen has had this argument with a client, and it is always the same argument. The ads work. The forms come in. The calls do not connect, and the client is convinced somebody is throttling them.

Nobody is throttling them. There is a signal riding along with every call that says how well the originating carrier actually knows who is placing it — and on July 9 the FCC proposed writing down, in the rules, exactly what a carrier must do before it is allowed to send the strongest version of that signal. Comments close August 10.

The signal has three levels and the top one requires three things. Not two.

One and two are about the customer. Three is about the number. And three is where every modern marketing stack lives: a tracking number on the landing page, a number pool from one vendor, a dialer or CRM from another, a client whose main line was ported years ago from a carrier nobody at the agency has ever spoken to. The FCC has a name for that arrangement. It calls it the knowledge gap, and it describes it precisely.

That is not an exotic case. That is the default configuration of a small business with a phone system bought after 2015.

So the FCC proposes to specify, for the first time, the mechanisms a provider may use to satisfy element three — and the list is short. Two things in, and one very familiar thing out.

The two mechanisms the FCC proposes to permit for establishing a verified association between a customer and the telephone number used on a call.

A delegate certificate, under the separate ATIS-1000092 standard, lets an entity get a certificate from the carrier that assigned the number, proving its authority to use it, and present that to whoever originates the call.

Read that twice if you have ever signed a telephony vendor's terms of service. The paperwork promise — customer represents it is authorized to use the numbers it presents — is in nearly every VoIP, call-tracking and dialer contract in the country. The FCC's position is that it is not knowledge. It is a sentence.

And the case it cites as the example is the reason any of this is moving: the Commission found that Lingo Telecom applied A-level attestations to 3,978 spoofed robocalls carrying a deepfake AI voice message purporting to be a sitting president. The mechanism that let those calls look fully vouched-for is the same mechanism a legitimate contractor's callback runs on.

The FCC's problem is that full attestation stopped meaning anything. The fix runs through every business whose calls originate somewhere other than where its numbers came from.

Kept honest: this is a proposed rule and nothing in it is in force. The FCC is seeking comment throughout — including on whether it should permit other mechanisms, and specifically whether to “allow business agreements or certifications that specify the active telephone numbers the customer will use,” which is a narrower version of the paperwork route that could survive. It also asks whether to require providers to accept delegate certificates at all, having declined to mandate acceptance in a 2025 order. I have not claimed, and the document does not say, that any particular call-tracking or CRM platform's calls carry a particular attestation level today — that varies by provider and by arrangement, which is exactly why the question above is worth asking rather than assuming. The proposal's own view is that the primary driver of improper attestations is bad-actor providers, not ordinary businesses, and the KYUP portions of the proceeding are aimed at those providers. The statistics quoted are the FCC's citations to third-party data (the STIR/SHAKEN Governance Authority, the American Bankers Association, Transaction Network Services) as reproduced in the Federal Register text; I have not gone behind them to the underlying studies. None of this is legal or regulatory advice.

Sources (primary, verified today): Federal Communications Commission, “Enhancing Know-Your-Upstream-Provider Requirements and Strengthening STIR/SHAKEN (Call Authentication Trust Anchor; Advanced Methods To Target and Eliminate Unlawful Robocalls),” proposed rule, 91 FR 42602 (July 9, 2026), WC Docket No. 17-97, CG Docket No. 17-59, FCC 26-32 — the attestation-level criteria, the Scenario 1 knowledge-gap description, the two permitted and two prohibited mechanisms for establishing a verified number association, the Lingo Telecom figure, the analytics-engine language and the comment dates are all quoted from the govinfo text of that document (federalregister.gov serves its full-text file behind a block); the deadlines and docket numbers were confirmed against the Federal Register JSON API. The 93.4%, 48%, American Bankers Association and Transaction Network Services figures are the FCC's own citations inside that text. Delegate certificates are described there by reference to ATIS-1000092. No trade coverage supplied any fact in this edition.

If you run lead gen for local businesses, there's a proceeding closing on August 10 that decides something you've probably blamed on the algorithm.

The FCC published a proposed rule on July 9 (91 FR 42602) about caller ID authentication. Buried in it is the first attempt to write down, in the rules, what a carrier must actually KNOW before it can fully vouch for a call.

Full attestation — A-level, the strongest signal a call can carry — requires three things:

"(1) is responsible for the origination of the call onto the IP network, (2) has a direct authenticated relationship with its customer and can identify the customer, and (3) has established a verified association between its customer and the telephone number used for the call."

One and two are about the customer. Three is about the NUMBER. Miss only three, and the call drops to B-level — partial.

Three is where every marketing stack lives. A tracking number pool from one vendor. A dialer or CRM from another. A client's main line ported years ago from a carrier nobody at the agency has ever spoken to.

The FCC has a name for that. It calls it the knowledge gap, and it describes it exactly: "when the originating provider that is authenticating the call is a separate entity from the telephone number service provider (TNSP) that provisioned the telephone numbers to the customer initiating the call."

That is not an exotic setup. That is the default configuration of any small business with a phone system bought after 2015.

So the FCC proposes to specify what satisfies element three. Two mechanisms in: the originating provider assigned the number itself, or the customer presents a delegate certificate from the carrier that did (ATIS-1000092).

And one mechanism out, which you have signed:

"we do not believe this association can be established by a business agreement or certification that includes only a general statement that the customer will only use numbers with which it has a verified association. This is essentially the mechanism that Lingo Telecom used when it misassigned A-level attestations for spoofed calls."

The paperwork promise. "Customer represents it is authorized to use the numbers it presents." It's in nearly every VoIP, call-tracking and dialer contract in the country. The FCC's position: that's not knowledge, it's a sentence.

And the case it cites is why this is moving at all — Lingo Telecom put A-level attestations on 3,978 spoofed robocalls carrying a deepfake AI voice purporting to be a sitting president. The mechanism that let those calls look fully vouched-for is the same one a legitimate roofer's callback runs on.

Why it's your problem and not your client's telecom vendor's: attestation is an INPUT. From the proposal — "voice service providers also use attestations to inform call analytics engines," and improper ones can contribute to "inaccurate blocking and labeling determinations." Analytics engines decide whether your client shows up on a screen as a name, as nothing, or as a warning.

One thing to do this week. Email the platform that ORIGINATES your clients' outbound calls — not the cell carrier — and ask: what attestation level do our calls carry, and on what basis? If the answer is A-level, and that platform didn't assign the numbers, and doesn't use delegate certificates, you've found the exact gap this proposal aims at. Fifteen minutes, and it'll tell you more about answer rates than a month of dashboards.

Comments close August 10, replies September 8. WC Docket 17-97 and CG Docket 17-59. That record will be carriers, associations and enforcement advocates. Almost nobody in it places calls for a plumbing company.

To be fair to the Commission: it says the primary driver of improper attestations is bad-actor providers, not ordinary businesses. And it's still asking whether to allow narrower certifications that "specify the active telephone numbers the customer will use" — so the paperwork route may survive in some form. Nothing here is in force.

Source: 91 FR 42602 (July 9, 2026), read from the govinfo text. Not legal advice.

FIRST SOURCE · one verified original-source finding, composed for one reader · this edition: marketing — written for the agencies whose clients measure everything up to the moment someone picks up the phone