The EU AI Act now reaches your cold email copy

Almost every outbound team now runs some version of the same machine: a model reads a prospect's site, writes a first line, and a sequencer sends it. Nobody in that chain has ever thought of themselves as deploying an AI system. As of August 2, 2026, European regulators disagree, and the reading that matters landed the following day.

Cooley published a client alert on August 3 walking through what came into force. The short version: Article 50 of the EU AI Act requires disclosure when a person is interacting with an AI system unless that is obvious, machine-readable marking of AI-generated synthetic content including text, and disclosure of AI-generated content published on matters of public interest unless a human has reviewed it. The alert states plainly that these rules apply to AI-generated emails and to any provider or deployer whose outputs reach EU users, across B2B, marketing and sales.

What changed on August 2

The AI Act has been law for a while. What happened on August 2 is that a specific chapter of it became enforceable, and it is the chapter about telling people when a machine made something. The obligations split into three that matter to a commercial team, and only two of them are likely to bite.

The third row is where most commentary goes wrong. A cold email pitching a security product is not content on a matter of public interest, and treating it as such produces compliance theater. The second row is the live one, and it is the row nobody in outbound has a process for.

Where the EU AI Act touches cold email

Work it through a normal sequence. A model enriches a prospect record, drafts a personalized opening line, and a human approves the template but not each individual send. The body of that email is, on any plain reading, AI-generated text delivered to a person. If that person sits in the EU, the marking obligation is in the frame.

Now change one thing. A human writes the template, the model only picks which of four pre-written variants to send, and the variable fields are pulled from a database rather than generated. That is closer to mail merge than to generation, and the risk profile drops sharply. The distinction between generated and selected is the single most useful line an outbound team can draw right now, and almost nobody has drawn it.

We have argued for a while that generated first lines underperform anyway, and there is data behind it: our teardown of AI-written versus human-written cold email spam flags found the generated variants carrying measurable deliverability cost before any regulator got involved. The compliance argument and the performance argument now point the same way, which is a rare and convenient thing.

The machine-readable marking problem

Here is where the obligation gets genuinely awkward for email. Machine-readable marking is a solved problem for images and audio, where provenance metadata standards exist and are shipping. For plain text in an email body, there is no widely adopted equivalent. You cannot watermark a sentence in a way a mail client will surface and a recipient will understand.

The extended deadline of December 2, 2026 for systems already on the market is the acknowledgement that this is unresolved. That is the window in which sending platforms will either ship a marking mechanism or lobby for a narrower reading. Either way, the operator response in the meantime is not to wait for the vendors.

“The obligation an outbound team can meet this month is not technical. It is telling the truth in one sentence and keeping a list of which campaigns a model wrote.”

The EU AI Act, cold email, and senders outside Europe

The instinct of every US-based outbound team reading this is that it does not apply to them. That instinct has been wrong about European regulation four times running, and the alert language is explicit that the rules attach where outputs reach EU users regardless of where the deployer sits.

The realistic enforcement expectation is different from the legal scope, and it is worth being honest about both. Scope is broad. Early enforcement will concentrate on large deployers, consumer-facing systems, and cases with an obvious harm story. A twelve-person B2B company sending 4,000 emails a month is not the first target. That is a reason to be proportionate, not a reason to do nothing, because the cheap controls are cheap and the expensive ones are not required yet.

The other reason to move now is that this is not arriving alone. The same week the obligations took effect, contact-data governance tooling started shipping explicitly against them: Convertr launched a product on August 13 aimed at enforcing source, supplier and policy controls on contact records before they reach a CRM, citing a Propeller Insights finding that 74% of managers lack full confidence they would pass a compliance audit of their lead data practices. Vendors do not build against a regulation they expect to be ignored.

The compliance work worth doing regardless

Strip out the legal framing and most of this is data hygiene an outbound team should already have. You need to know where every record came from, which supplier or scrape produced it, what basis you have for contacting that person, and which of your sequences were written by a machine. Three of those four are already required by GDPR for European contacts, which we covered when we looked at the legal exposure on guessed email addresses.

The fourth, the record of which sequences a model wrote, is new and trivial to build. It is a column in your campaign tracker. The reason nobody has it is that generation is buried inside the sending platform, applied per-send, and never logged at the campaign level. Logging it takes an afternoon and gives you the one artifact you cannot reconstruct after the fact.

If your record-of-origin discipline is weak more broadly, that is the deeper problem and the AI Act is only the newest symptom of it. The B2B data stack audit framework we published earlier this year is the version of this work that pays for itself independent of any regulator, and the same discipline underpins the outbound programs we run for regulated buyers across the B2B practice.

Your next two weeks

Two weeks is the right budget for this, and the reason is that the work is almost entirely discovery rather than engineering. Nothing here requires a platform migration, a legal opinion, or a new vendor. It requires knowing what your own machine is doing, which most outbound teams have never had to write down because generation arrived as a feature toggle rather than a decision.

Week one is inventory. List every sequence currently sending, mark which ones contain model-generated recipient-facing text, and flag which lists contain EU-based contacts. Most teams discover two things doing this: more sequences use generation than they thought, and their EU exposure is concentrated in one or two campaigns nobody remembers building.

Week two is the fix. Move your highest-volume EU-facing sequences from generated body copy to generated research with human-written templates, which lowers exposure and usually raises reply rate. Add a one-line disclosure to sequences that keep generation. Turn off autonomous reply agents on EU threads until your platform tells you how it handles interaction disclosure. Then write down what you did and when, because the record is the thing that matters if this is ever tested. Our work with regulated-sector clients like TechTrust starts from that same paper trail.

The uncomfortable part of this rule is not the fine. It is that it forces outbound teams to say out loud how much of their personalization is a machine writing plausible sentences about a company it has never understood. Most teams will find the honest answer embarrassing, fix it, and send better email. The full alert is worth reading at Cooley's August 3 client update.

See where you are cited today

A free snapshot audit of your rankings and AI citations before we ever talk.