Why Agencies Should Answer "Is This AI?" Replies Honestly
Prospects do ask it. Sometimes it is a joke, sometimes a test, sometimes a genuine question: "Was this written by a bot?" "Am I talking to a real person?" "Is this AI?"
For an agency running outbound on a client's domain, the reply to that question is a small decision with a large blast radius. Our position is simple: answer it honestly, every time, in plain language. Do not dodge, do not get cute, and never claim a person did something a person did not do.
The legal floor is already moving in this direction
We are not lawyers, and the rules depend on where the prospect is and what the interaction is. But two state laws show the direction.
California's bot disclosure law. Business and Professions Code section 17941 makes it unlawful to use a bot to communicate with a person in California online "with the intent to mislead the other person about its artificial identity" in order to incentivize a purchase or sale. Disclosing that it is a bot removes the liability, and the disclosure has to be "clear, conspicuous, and reasonably designed" to inform the person. The statute defines a bot as an automated online account where all or substantially all of the actions or posts are not the result of a person.
Utah's generative AI disclosure rule. Utah Code section 13-77-103 says a supplier that uses generative AI to interact with an individual in connection with a consumer transaction must disclose that the person is interacting with generative AI and not a human, if the person asks. The 2025 amendments narrowed the trigger to "a clear and unambiguous request" to find out whether the interaction is with a human or with AI, as Davis Polk's summary of the changes explains.
Whether either law reaches a particular B2B cold email is a question for counsel. The practical point does not need a lawyer: when someone asks directly whether they are talking to a machine, the safe and decent answer is the true one.
Why honesty is also the better sales move
A lie that gets caught ends the conversation, and the client relationship. If the prospect asks "is this AI?" and gets "No, this is just me," and later learns otherwise, the client's name is now attached to a deception. The prospect may post the exchange. The agency has to explain it to the client.
The honest answer is usually boring, and that is good. If the setup is a team using software to research and draft, with people owning the relationship, saying exactly that tends to defuse the question.
The question can be a buying signal in disguise. A prospect who bothers to ask is reading closely. A straight answer, followed by a clear next step, keeps them in the conversation.
What a good answer looks like
Keep it short, true, and specific to how the client actually works. For example:
Fair question. We use AI software to research companies and draft first messages. A person on our team reads every reply, including this one. Happy to keep going here, or I can set up a quick call with [name].
Only say "a person reads every reply" if that is true for that client. If replies are routed automatically for some categories, say what is true instead.
Three rules for the answer:
- Never deny AI involvement that exists. "No, this is all handwritten" is the one answer that must never go out.
- Have a human send it. A question about whether a human is present should get a human answer.
- Offer a way to opt out. Some people ask because they do not want AI-written mail. Give them a clean exit and suppress them.
Build it into the client playbook
Add an "is this AI?" reply to every client's reply playbook before the first send, alongside the categories we covered in reply intent triage. Agree on the wording with the client. Make the question its own reply label, route it to a person, and keep the agreed answer in the client's voice brief so nobody improvises.
Where GTM fits
In GTM, a reply stops the sequence and lands in a shared inbox, so a person on the agency or client team owns the answer. GTM writes first messages from prospect evidence in the client's voice, and every send passes a compliance gate. Honest answers to direct questions belong in that same discipline.
If you run outbound for several clients and want replies to reach a person fast, join the waitlist.
Sources
- California Business and Professions Code, Chapter 6 (Bots), sections 17940–17943: https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?lawCode=BPC&division=7.&title=&part=3.&chapter=6.&article=
- Utah Code section 13-77-103, Required disclosures: https://le.utah.gov/xcode/Title13/Chapter77/13-77-S103.html
- Davis Polk, "Utah scales back reach of generative AI consumer protection law": https://www.davispolk.com/insights/client-update/utah-scales-back-reach-generative-ai-consumer-protection-law