<?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>Barkan 笔记</title>
    <link>https://trybarkan.com/zh/blog</link>
    <atom:link href="https://trybarkan.com/zh/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <description>用户激活、新用户引导，以及我们在打造和上线 AI 客户成功经理的过程中学到的东西。</description>
    <language>zh-Hans</language>
    <item>
      <title>你的 AI 客服，什么时候该停下来</title>
      <link>https://trybarkan.com/zh/blog/when-your-ai-support-agent-should-stop-talking</link>
      <guid isPermaLink="true">https://trybarkan.com/zh/blog/when-your-ai-support-agent-should-stop-talking</guid>
      <pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate>
      <dc:creator>Gabriel Lancelot</dc:creator>
      <description>拦截率这个指标，奖励的是 AI 客服绕开人工，哪怕客户的问题还没解决。转人工交接要设计得既保住上下文，又挽回信任。</description>
      <enclosure url="https://trybarkan.com/assets/images/og/when-your-ai-support-agent-should-stop-talking.jpg" type="image/jpeg" length="0"/>
    </item>
    <item>
      <title>AI Agent 的确认提示，本身就是一道权限边界</title>
      <link>https://trybarkan.com/zh/blog/ai-agent-approval-is-a-permission-boundary</link>
      <guid isPermaLink="true">https://trybarkan.com/zh/blog/ai-agent-approval-is-a-permission-boundary</guid>
      <pubDate>Sat, 29 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Maxence Rabrais</dc:creator>
      <description>设计 AI Agent 的操作确认，要围绕后果、时机、具体操作细节和一次性授权：日常操作照样快速推进，又不必交出宽泛的权限。</description>
      <enclosure url="https://trybarkan.com/assets/images/og/ai-agent-approval-is-a-permission-boundary.jpg" type="image/jpeg" length="0"/>
    </item>
    <item>
      <title>“第二个工作流”难题：为什么激活总在首战告捷之后夭折</title>
      <link>https://trybarkan.com/zh/blog/the-second-workflow-problem</link>
      <guid isPermaLink="true">https://trybarkan.com/zh/blog/the-second-workflow-problem</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Maxence Rabrais</dc:creator>
      <description>团队拼命优化前五分钟，用户却在第二周流失。了解第二个工作流为何决定激活、如何衡量它，以及如何解决。</description>
      <enclosure url="https://trybarkan.com/assets/images/og/the-second-workflow-problem.jpg" type="image/jpeg" length="0"/>
    </item>
    <item>
      <title>为什么 Barkan 读屏幕，而不是读文档</title>
      <link>https://trybarkan.com/zh/blog/why-we-read-the-screen-not-the-docs</link>
      <guid isPermaLink="true">https://trybarkan.com/zh/blog/why-we-read-the-screen-not-the-docs</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Gabriel Lancelot</dc:creator>
      <description>基于文档训练的助手，总是自信满满地泛泛而谈。Barkan 的每个回答都以实时渲染出的界面为依据。这里讲我们的思路、采集的内容，以及其中的取舍。</description>
      <enclosure url="https://trybarkan.com/assets/images/og/why-we-read-the-screen-not-the-docs.jpg" type="image/jpeg" length="0"/>
    </item>
    <item>
      <title>没人读你的文档——你的激活率就是证据</title>
      <link>https://trybarkan.com/zh/blog/nobody-reads-your-documentation</link>
      <guid isPermaLink="true">https://trybarkan.com/zh/blog/nobody-reads-your-documentation</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Maxence Rabrais</dc:creator>
      <description>文档由专家撰写，写给泛泛的读者，还开在另一个标签页里。看看激活究竟漏在哪里，聊天窗口为何没能堵上，以及什么才真正管用。</description>
      <enclosure url="https://trybarkan.com/assets/images/og/nobody-reads-your-documentation.jpg" type="image/jpeg" length="0"/>
    </item>
  </channel>
</rss>
