A bot pitching a B2B prospect on a discovery call can withhold that it is not human in most U.S. states. The proposition anchors an inkl report titled "AI Sales Agents Won't Tell You They're Bots: In Most States, They Don't Have To."

That headline is the entire verifiable finding. Inkl does not enumerate the states, name the statutes, or quantify the share of the country covered by the disclosure gap. The piece states a single proposition: most U.S. states do not require AI sales agents to identify themselves as bots.

How wide is the gap?

The piece characterizes the regulatory map as a patchwork. State-level statutes on automated communication — the kind that govern prerecorded voice, SMS, and robocalls — predate generative AI on the sales floor. The inkl framing is that those older statutes do not capture a language-model agent holding a first conversation with a buyer.

No specific state is named as having a mandate. No specific state is named as lacking one. The verifiable claim is the headline: most states do not require disclosure, and disclosure, where it occurs, is voluntary.

What does the gap mean for sales and procurement?

For revenue leaders running outbound at scale, the practical question is straightforward: do you self-impose a disclosure rule, or wait for one to be forced on you? Outbound-first teams — those whose initial buyer contact is a bot, an email sequence, or a chat agent — sit in the most exposed segment.

Three operating scenarios follow from the inkl finding. First, a vendor ships a "human or AI" opener before procurement asks. Second, a competitor ships one first, and disclosure becomes a checkbox on the RFP. Third, no vendor moves, and the disclosure gap persists until a state legislature or the FTC closes it.

The inkl report names no vendors in any of those categories. The data point the market will demand next: which enterprise software companies have shipped disclosure scripts, and which have not.

Procurement teams already ask vendors, in writing, whether the first outreach is automated. The inkl framing suggests that under current law the disclosure burden sits with the buyer, not the seller. The buyer asks. The seller may answer, or may not. No statute, in most states, compels the answer.

That inversion — buyer-asks, seller-decides — is the operational consequence. Sales engineers walking into a discovery call under that regime will know, before the call starts, whether their counterparty cares about the answer.

What comes next?

The inkl piece is the prompt. The follow-on data the sales operations community will need is a state-by-state map of bot-disclosure mandates, the list of vendors that have shipped a disclosure script, and the first enforcement action taken under any existing statute. None of those data points are in the source.

The forward read, grounded in the source: a state attorney general, or a buyer with standing, will test the patchwork inkl describes the moment someone asks a court to enforce disclosure on an AI agent. That case is the data point the rest of the market will copy.

— Daniel Okafor