<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Peter Jackman</title>
    <description>The latest articles on DEV Community by Peter Jackman (@peter_jackman).</description>
    <link>https://dev.to/peter_jackman</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4017041%2Fe8a08759-e2f1-4caa-8d78-d113a1937d71.png</url>
      <title>DEV Community: Peter Jackman</title>
      <link>https://dev.to/peter_jackman</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/peter_jackman"/>
    <language>en</language>
    <item>
      <title>Half of B2B Software Buyers Now Start Vendor Research in an AI Chatbot: What That Actually Says, and What It Changes</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:59:57 +0000</pubDate>
      <link>https://dev.to/peter_jackman/half-of-b2b-software-buyers-now-start-vendor-research-in-an-ai-chatbot-what-that-actually-says-1iip</link>
      <guid>https://dev.to/peter_jackman/half-of-b2b-software-buyers-now-start-vendor-research-in-an-ai-chatbot-what-that-actually-says-1iip</guid>
      <description>&lt;p&gt;There is a statistic doing the rounds in B2B decks right now: "51% of B2B software buyers begin vendor research in an AI chatbot, up from 29% in April 2025." It is being quoted as if half of all software buying journeys now open in ChatGPT instead of Google. We traced the figure to its owner, and that is not quite what the owner's page says. This post covers what G2 actually measured, where the wo&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;What the owner's page actually says&lt;/li&gt;
&lt;li&gt;The part that should actually worry you&lt;/li&gt;
&lt;li&gt;Classic funnel vs chatbot-first discovery&lt;/li&gt;
&lt;li&gt;What a B2B sales and marketing team should change&lt;/li&gt;
&lt;li&gt;1. Treat AI visibility as a channel, not a curiosity&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/b2b-buyers-ai-chatbot-vendor-research/" rel="noopener noreferrer"&gt;Half of B2B Software Buyers Now Start Vendor Research in an AI Chatbot: What That Actually Says, and What It Changes&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>Multi-Format AEO: Getting AI Engines to Cite Your Video, Audio and Transcripts</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:59:09 +0000</pubDate>
      <link>https://dev.to/peter_jackman/multi-format-aeo-getting-ai-engines-to-cite-your-video-audio-and-transcripts-4pm1</link>
      <guid>https://dev.to/peter_jackman/multi-format-aeo-getting-ai-engines-to-cite-your-video-audio-and-transcripts-4pm1</guid>
      <description>&lt;p&gt;Every 2026 AEO trend roundup says roughly the same thing: content is going multi-format, and your videos, podcasts and webinars are the next citation surface. The audience half of that claim is measurable and true — the numbers are below. The engine half is where the roundups get vague, because what OpenAI, Google and Perplexity actually publish about their own crawlers tells a less exciting, more&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;What OpenAI, Google and Perplexity actually document&lt;/li&gt;
&lt;li&gt;OpenAI: crawler docs describe pages, not media&lt;/li&gt;
&lt;li&gt;Google: metadata first, and a capable model is not a crawling promise&lt;/li&gt;
&lt;li&gt;Perplexity: search surfacing, nothing on formats&lt;/li&gt;
&lt;li&gt;Why the transcript is the citable layer&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/multi-format-aeo-video-audio-transcripts/" rel="noopener noreferrer"&gt;Multi-Format AEO: Getting AI Engines to Cite Your Video, Audio and Transcripts&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>The AI Crawler Allowlist: robots.txt Decisions for B2B SaaS in 2026</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:58:20 +0000</pubDate>
      <link>https://dev.to/peter_jackman/the-ai-crawler-allowlist-robotstxt-decisions-for-b2b-saas-in-2026-hoe</link>
      <guid>https://dev.to/peter_jackman/the-ai-crawler-allowlist-robotstxt-decisions-for-b2b-saas-in-2026-hoe</guid>
      <description>&lt;p&gt;Somewhere in the last two years, a security checklist probably told you to block AI crawlers in robots.txt. For a B2B SaaS company in 2026, that advice can quietly cost you the channel where buyers now do their research — because the same AI company typically operates one crawler that feeds model training and a different one that decides whether you appear in the answers a buyer reads. This post i&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;One company, several bots — and only some of them matter to revenue&lt;/li&gt;
&lt;li&gt;Who actually commits to honouring robots.txt&lt;/li&gt;
&lt;li&gt;The trade-off the checklist missed&lt;/li&gt;
&lt;li&gt;A decision matrix by site type and goal&lt;/li&gt;
&lt;li&gt;A copy-paste allowlist for the common SaaS case&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/ai-crawler-allowlist-robots-txt-b2b-saas/" rel="noopener noreferrer"&gt;The AI Crawler Allowlist: robots.txt Decisions for B2B SaaS in 2026&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>Which AI Crawlers Actually Matter: Training Bots vs On-Demand Fetchers</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:57:32 +0000</pubDate>
      <link>https://dev.to/peter_jackman/which-ai-crawlers-actually-matter-training-bots-vs-on-demand-fetchers-31f</link>
      <guid>https://dev.to/peter_jackman/which-ai-crawlers-actually-matter-training-bots-vs-on-demand-fetchers-31f</guid>
      <description>&lt;p&gt;Open a server log on any B2B site in 2026 and you will find a crowd of user agents with AI-sounding names: GPTBot, ClaudeBot, PerplexityBot, meta-externalagent, Amazonbot, Bytespider. Most teams treat them as one blob called "AI bots" and either block the lot or ignore the lot. Both reactions miss the point, because these crawlers do two completely different jobs — and only one involves a potentia&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Why the split matters to a revenue team&lt;/li&gt;
&lt;li&gt;The training crawlers: feeding a future model&lt;/li&gt;
&lt;li&gt;The on-demand crawlers: a buyer may be on the other end&lt;/li&gt;
&lt;li&gt;Search indexers — they decide whether you're findable&lt;/li&gt;
&lt;li&gt;User-triggered fetchers — someone is reading you right now&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/ai-crawlers-training-bots-vs-on-demand-fetchers/" rel="noopener noreferrer"&gt;Which AI Crawlers Actually Matter: Training Bots vs On-Demand Fetchers&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>When You're Not on G2: Earning AI Citations Without a Review-Site Profile</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:56:43 +0000</pubDate>
      <link>https://dev.to/peter_jackman/when-youre-not-on-g2-earning-ai-citations-without-a-review-site-profile-5bbj</link>
      <guid>https://dev.to/peter_jackman/when-youre-not-on-g2-earning-ai-citations-without-a-review-site-profile-5bbj</guid>
      <description>&lt;p&gt;Nearly every answer engine optimisation playbook for SaaS opens the same way: claim your G2 profile, complete it, run a steady review-generation motion. Our own piece on citation-source concentration called review platforms "the highest-leverage surface you directly control" — advice that holds if you have a shipped product and customers to review it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;First, the claim doing the rounds — and where it falls apart&lt;/li&gt;
&lt;li&gt;The review-site gate is real: G2 excludes beta products by policy&lt;/li&gt;
&lt;li&gt;Review-site alternatives that are open pre-launch&lt;/li&gt;
&lt;li&gt;The six citation surfaces that remain — and how they compare&lt;/li&gt;
&lt;li&gt;Comparison: citation surfaces open without a review profile&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/ai-citations-without-review-site-profile/" rel="noopener noreferrer"&gt;When You're Not on G2: Earning AI Citations Without a Review-Site Profile&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>Local Pages for AI Visibility: Do Geographic Pages Win AI Citations in 2026?</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:55:55 +0000</pubDate>
      <link>https://dev.to/peter_jackman/local-pages-for-ai-visibility-do-geographic-pages-win-ai-citations-in-2026-1iop</link>
      <guid>https://dev.to/peter_jackman/local-pages-for-ai-visibility-do-geographic-pages-win-ai-citations-in-2026-1iop</guid>
      <description>&lt;p&gt;Every few months a tactic from classic SEO gets rebadged for the AI-search era, and in 2026 it is the local page. HubSpot's answer-engine-optimisation trends piece puts "use local pages to your advantage" at the top of its list, and agencies have started pitching country-page programmes as an AEO deliverable. Before anyone commissions forty city pages, two things being blurred need separating: the&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;What HubSpot's trends piece actually says&lt;/li&gt;
&lt;li&gt;How AI engines localise answers — what the owners document&lt;/li&gt;
&lt;li&gt;ChatGPT: IP-based location and query rewriting&lt;/li&gt;
&lt;li&gt;Gemini: documented for the consumer apps, not for API grounding&lt;/li&gt;
&lt;li&gt;The doorway trap: Google wrote the policy for exactly this&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/local-pages-ai-visibility-2026/" rel="noopener noreferrer"&gt;Local Pages for AI Visibility: Do Geographic Pages Win AI Citations in 2026?&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>Front-Loading for AI Citation: Where on the Page AI Engines Actually Quote From</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:55:07 +0000</pubDate>
      <link>https://dev.to/peter_jackman/front-loading-for-ai-citation-where-on-the-page-ai-engines-actually-quote-from-4d4k</link>
      <guid>https://dev.to/peter_jackman/front-loading-for-ai-citation-where-on-the-page-ai-engines-actually-quote-from-4d4k</guid>
      <description>&lt;p&gt;At a glance: AI engines quote from positions on a page, not from pages as wholes — and the measurable bias is toward the top. The most-circulated figure, that 55% of sampled Google AI Overview citations came from the first 30% of the cited page, traces to a 100-citation analysis published by CXL in March 2026: a small, single-engine sample, but directionally consistent with the rest of the public &lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The circulating claim — and who actually ran the sample&lt;/li&gt;
&lt;li&gt;Why position matters: what the engine owners actually document&lt;/li&gt;
&lt;li&gt;Why front-loading works (and what it actually means)&lt;/li&gt;
&lt;li&gt;The restructure guide: before and after&lt;/li&gt;
&lt;li&gt;FAQ: page position and AI citations&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/front-loading-ai-citation-page-position/" rel="noopener noreferrer"&gt;Front-Loading for AI Citation: Where on the Page AI Engines Actually Quote From&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>AI Agents and the Australian Privacy Act Review: What Outbound Teams Should Prepare For</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:54:18 +0000</pubDate>
      <link>https://dev.to/peter_jackman/ai-agents-and-the-australian-privacy-act-review-what-outbound-teams-should-prepare-for-3g2k</link>
      <guid>https://dev.to/peter_jackman/ai-agents-and-the-australian-privacy-act-review-what-outbound-teams-should-prepare-for-3g2k</guid>
      <description>&lt;p&gt;Australia's privacy overhaul is not one event — it is a staged program, and teams treating it as a single future deadline are already behind on the parts that are law today. The Privacy Act Review produced 116 reform proposals; the first tranche was legislated in December 2024 and commences in pieces, while the second tranche — the one aimed squarely at direct marketing — is still being drafted. I&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Where the reform actually stands in August 2026&lt;/li&gt;
&lt;li&gt;Already in force: the statutory tort is the sleeper risk for outbound&lt;/li&gt;
&lt;li&gt;The hard deadline: ADM transparency by 10 December 2026&lt;/li&gt;
&lt;li&gt;Tranche 2: the direct-marketing reforms outbound teams should watch&lt;/li&gt;
&lt;li&gt;A preparation plan that survives the uncertainty&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/privacy-act-review-ai-outbound-teams/" rel="noopener noreferrer"&gt;AI Agents and the Australian Privacy Act Review: What Outbound Teams Should Prepare For&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>llms.txt in 2026: Does Any AI Engine Actually Read It?</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:53:30 +0000</pubDate>
      <link>https://dev.to/peter_jackman/llmstxt-in-2026-does-any-ai-engine-actually-read-it-h5o</link>
      <guid>https://dev.to/peter_jackman/llmstxt-in-2026-does-any-ai-engine-actually-read-it-h5o</guid>
      <description>&lt;p&gt;At a glance: No major AI engine — OpenAI, Anthropic, Google or Perplexity — has ever documented consuming llms.txt from third-party websites; their crawler docs name exactly one control file, robots.txt. Confusingly, several of those companies publish llms.txt for their own docs, and Chrome's Lighthouse now audits your site for one. Serving the file is cheap, but treat claims that it drives AI cit&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;What llms.txt actually is — a proposal, not a standard&lt;/li&gt;
&lt;li&gt;Producing is not consuming&lt;/li&gt;
&lt;li&gt;What John Mueller actually said (and where)&lt;/li&gt;
&lt;li&gt;The Lighthouse wrinkle: Google's products don't agree with each other&lt;/li&gt;
&lt;li&gt;What each owner actually documents&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/llms-txt-ai-engines-2026/" rel="noopener noreferrer"&gt;llms.txt in 2026: Does Any AI Engine Actually Read It?&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>The Do Not Call Register and AI Voice Agents: What ACMA Enforcement Actually Looks Like</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Thu, 20 Aug 2026 04:52:41 +0000</pubDate>
      <link>https://dev.to/peter_jackman/the-do-not-call-register-and-ai-voice-agents-what-acma-enforcement-actually-looks-like-4kk</link>
      <guid>https://dev.to/peter_jackman/the-do-not-call-register-and-ai-voice-agents-what-acma-enforcement-actually-looks-like-4kk</guid>
      <description>&lt;p&gt;Vendor blogs love to imply that AI voice agents occupy some regulatory grey zone in Australia. They don't. The Do Not Call Register Act 2006 (Cth) defines a "voice call" to include "a call that involves a recorded or synthetic voice" — words that predate anyone strapping a large language model to a SIP trunk. An AI agent making outbound sales calls to Australian numbers is a telemarketer, full sto&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The synthetic-voice clause: why an AI agent is a telemarketer&lt;/li&gt;
&lt;li&gt;What the Do Not Call Register Act mechanically requires&lt;/li&gt;
&lt;li&gt;The Industry Standard: hours, identification, termination, caller ID&lt;/li&gt;
&lt;li&gt;What enforcement actually looks like: two ACMA actions&lt;/li&gt;
&lt;li&gt;V Marketing (Federal Court, March 2025) — the case vendor blogs half-remember&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/do-not-call-register-ai-voice-agents-acma-enforcement/" rel="noopener noreferrer"&gt;The Do Not Call Register and AI Voice Agents: What ACMA Enforcement Actually Looks Like&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>The US State AI Call-Disclosure Patchwork: What Texas SB 140 Actually Says, and Which States Really Require Disclosure</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Tue, 18 Aug 2026 04:33:59 +0000</pubDate>
      <link>https://dev.to/peter_jackman/the-us-state-ai-call-disclosure-patchwork-what-texas-sb-140-actually-says-and-which-states-really-3a69</link>
      <guid>https://dev.to/peter_jackman/the-us-state-ai-call-disclosure-patchwork-what-texas-sb-140-actually-says-and-which-states-really-3a69</guid>
      <description>&lt;p&gt;If you run AI voice or chat outreach into the United States, the compliance question you keep getting asked — "do we legally have to say it's an AI?" — has no single federal answer. The FCC proposed one in August 2024 and has not adopted it. So the operative disclosure rules are state rules, and they are a genuine patchwork: different triggers, different wording, different timing, different enforc&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The federal layer: consent rules, not disclosure rules&lt;/li&gt;
&lt;li&gt;The verified state map&lt;/li&gt;
&lt;li&gt;What Texas SB 140 actually does&lt;/li&gt;
&lt;li&gt;Where the map has holes&lt;/li&gt;
&lt;li&gt;What to actually implement&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/us-state-ai-call-disclosure-laws/" rel="noopener noreferrer"&gt;The US State AI Call-Disclosure Patchwork: What Texas SB 140 Actually Says, and Which States Really Require Disclosure&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
    <item>
      <title>Inbound AI Callers: Preparing Your Phone Lines for Consumer Agents That Ring Your Business</title>
      <dc:creator>Peter Jackman</dc:creator>
      <pubDate>Tue, 18 Aug 2026 04:33:10 +0000</pubDate>
      <link>https://dev.to/peter_jackman/inbound-ai-callers-preparing-your-phone-lines-for-consumer-agents-that-ring-your-business-2bpg</link>
      <guid>https://dev.to/peter_jackman/inbound-ai-callers-preparing-your-phone-lines-for-consumer-agents-that-ring-your-business-2bpg</guid>
      <description>&lt;p&gt;Almost everything written about AI on the phone assumes the machine is on the outbound side: your agent, your dialler, your list. The flip side is already live and barely discussed. Consumer-side assistants now ring businesses on a person's behalf to check a price, confirm stock or book a slot. The call arrives on your main line, in business hours, sounding like a polite customer. It is not one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this covers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;What is confirmed, and what is not&lt;/li&gt;
&lt;li&gt;Human caller versus consumer AI caller&lt;/li&gt;
&lt;li&gt;When their agent calls your agent&lt;/li&gt;
&lt;li&gt;Does an AI caller have to say it is an AI?&lt;/li&gt;
&lt;li&gt;The inbound readiness checklist&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This is a technical summary. The full guide — with the tables and worked examples — is on our site: *&lt;/em&gt;&lt;a href="https://zian.ai/inbound-ai-callers-phone-line-readiness/" rel="noopener noreferrer"&gt;Inbound AI Callers: Preparing Your Phone Lines for Consumer Agents That Ring Your Business&lt;/a&gt;*&lt;em&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zian.ai/" rel="noopener noreferrer"&gt;Zian AI&lt;/a&gt; is an autonomous AI sales-agent platform (phone, SMS, email, WhatsApp) currently in waitlist beta.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>machinelearning</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
