<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Flocly Blog</title>
    <link>https://www.flocly.com/blog</link>
    <description>Product updates, engineering notes, and thinking on AI-assisted technical support from the Flocly team.</description>
    <language>en</language>
    <atom:link href="https://www.flocly.com/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>AI support tools make replies faster. Technical support isn&apos;t slow at replying.</title>
      <link>https://www.flocly.com/blog/ai-support-tools-speed-up-the-wrong-half</link>
      <guid isPermaLink="true">https://www.flocly.com/blog/ai-support-tools-speed-up-the-wrong-half</guid>
      <pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate>
      <description>Roll out an AI reply tool on a technical queue and resolution time barely moves. Not because the AI is bad - because it&apos;s pointed at the wrong half of the ticket.</description>
    </item>
    <item>
      <title>Why technical support doesn&apos;t scale by hiring</title>
      <link>https://www.flocly.com/blog/technical-support-doesnt-scale-by-hiring</link>
      <guid isPermaLink="true">https://www.flocly.com/blog/technical-support-doesnt-scale-by-hiring</guid>
      <pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate>
      <description>New hires absorb the easy tickets fast. But the easy tickets were never where the time went - and the hard ones still route to the same three people they always did.</description>
    </item>
    <item>
      <title>No answer should be learned twice</title>
      <link>https://www.flocly.com/blog/no-answer-learned-twice</link>
      <guid isPermaLink="true">https://www.flocly.com/blog/no-answer-learned-twice</guid>
      <pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate>
      <description>Support knowledge lives in a few senior heads and a thousand Slack threads nobody can find. Flocly learns from every resolved ticket so the next one like it doesn&apos;t start from zero.</description>
    </item>
    <item>
      <title>Investigation and memory: two features that compound</title>
      <link>https://www.flocly.com/blog/investigation-and-memory-compound</link>
      <guid isPermaLink="true">https://www.flocly.com/blog/investigation-and-memory-compound</guid>
      <pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate>
      <description>Investigation solves the first hard ticket. Memory means you never solve it the hard way again. Here&apos;s why the two together are worth more than the sum of the parts.</description>
    </item>
    <item>
      <title>Ticket deflection is a knowledge problem, not a chatbot problem</title>
      <link>https://www.flocly.com/blog/ticket-deflection-is-a-knowledge-problem</link>
      <guid isPermaLink="true">https://www.flocly.com/blog/ticket-deflection-is-a-knowledge-problem</guid>
      <pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate>
      <description>A chatbot can only surface answers that exist. In technical support, the answers that drive ticket volume were never written down - they&apos;re locked in resolved tickets and a few people&apos;s heads.</description>
    </item>
    <item>
      <title>How AI investigation works under the hood</title>
      <link>https://www.flocly.com/blog/how-ai-investigation-works</link>
      <guid isPermaLink="true">https://www.flocly.com/blog/how-ai-investigation-works</guid>
      <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
      <description>An orchestrator, a fan-out of specialists, and a synthesis step - here&apos;s how Flocly turns a raw ticket into a root cause with evidence.</description>
    </item>
    <item>
      <title>Introducing Flocly: support that starts with the answer</title>
      <link>https://www.flocly.com/blog/introducing-flocly</link>
      <guid isPermaLink="true">https://www.flocly.com/blog/introducing-flocly</guid>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <description>Technical tickets don&apos;t fail at the answer - they fail at the start. Here&apos;s how Flocly investigates every ticket the moment it arrives.</description>
    </item>
  </channel>
</rss>
