Ready to send better email?
Brew is the AI-native ESP. Define your brand once, ship on-brand email in minutes.
Brew is the AI-native ESP. Define your brand once, ship on-brand email in minutes.
Agents do not get a separate inbox. Same CAN-SPAM rules, same Gmail thresholds, same need to split marketing from transactional on the wire.
An agent can draft, segment, and send faster than a coordinator. It does not get a courtesy lane at Gmail.
Mailbox providers score domains, IPs, and complaint rates. They do not score whether a human clicked Send. If the agent ships a promotional body through the transactional IP, you inherit the same problem you would have created by hand, only sooner.
This is a companion to the email deliverability guide, not a replacement. That post covers reputation, authentication, and list hygiene. This one is about the mistakes that show up when software is the one hitting send.
txn_... sends on a separate IP and, if you can, a separate domain.
The agent is another client on the same sending identity. The inbox still sees your domain.
CAN-SPAM applies to commercial messages. The primary-purpose test is about the subject line and the body, not about who typed them.
If the agent writes a "your invoice is ready" subject and a launch offer in the body, the message is commercial. You still need an honest subject, a physical address, and a working unsubscribe. "The model wrote it" is not a defense.
The same is true in reverse. A password reset the agent triggered on a real security event is still transactional, as long as the body stays on that event.
Gmail's sender requirements apply once you are in the bulk-sender bucket. The page's current threshold is 5,000 or more recipients in a day to personal Gmail. Marketing mail then needs:
p=none or stricter policy.List-Unsubscribe and List-Unsubscribe-Post.Transactional mail is exempt from the one-click rule. It is not exempt from authentication, and it is not exempt from spam complaints if you load the template with a sale.
Yahoo asks high-volume senders to put marketing and transactional on different IPs, and preferably different domains. An agent that "just uses the default sender" will collapse that split the first week you let it run unattended.
Give the agent a promotional sending identity for campaigns and automations. The domain you warm, the IP you expect complaints on, the unsubscribe headers you have tested.
Keep transactional ids, txn_... in Brew, on a separate identity. The agent can compose the template. The send path should still be POST /v1/sends with a transactionId, not "send this draft to the list."
Do not let the agent pick the From address from a pile of verified domains "to see what lands." That is how you train two reputations at once and understand neither.
The failure mode is not a typo. It is a fluent paragraph that cites a number you never published, or a subject that looks like a receipt.
Before you let an agent send without a queue:
Cory Nelson at Harmonya told Noah Adelstein he did that first-campaign read before he trusted the loop. That is the correct order.
Speed is not a new channel. It is the same channel with less time to notice you mixed a sale into a receipt. Authenticate the domain, split the IPs, tell the agent which identity is which, and keep a human on the first send.
The brief that stops invented numbers is in how to brief an email agent. The Harmonya first-campaign read is in how Harmonya turned a newsletter into a lifecycle program. To contact us about this article, write Brew support.
Agent-sent email is still email. Mailbox providers do not give models a courtesy lane.
The primary-purpose test is how US law decides if the message is commercial.
One-click unsubscribe is a header requirement for bulk commercial mail, including RFC 8058.
For example, a receipt that spends most of the body selling a plan is still a campaign.
| Move | Why it matters |
|---|---|
| Split marketing from transactional | Folder names in the ESP do not decide the law |
| Authenticate the domain | The agent does not skip SPF, DKIM, or DMARC |
US commercial mail still follows the FTC CAN-SPAM guide and 16 CFR 316.3. Bulk sending still has to meet Gmail's sender requirements. To contact us about this article, use the support link above.
No. Gmail and Yahoo score the sending identity. An agent is another client on your domain.
Gmail's bulk-sender page exempts transactional mail from the one-click header. It does not exempt it from authentication or from spam complaints if you load the template with a sale. One-click itself is RFC 8058.
Promotional campaigns and automations on the warmed marketing identity. Transactional sends through POST /v1/sends with a transactionId. Do not let it pick From addresses "to see what lands."
Fluent copy will cite numbers you never published, or wear a receipt-shaped subject on a sale. Read it against the brief, seed-test Gmail, Yahoo, and Outlook, then confirm the headers.
