<?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>Altores, articles</title>
    <link>https://altores.mc/en/resources/blog/</link>
    <description>Field notes on building AI agents for a single industry.</description>
    <language>en-GB</language>
    <atom:link href="https://altores.mc/en/resources/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What an AI agent handles at a telecom operator, and what it leaves to the adviser</title>
      <link>https://altores.mc/en/resources/blog/ai-agent-telecom-operator/</link>
      <guid isPermaLink="true">https://altores.mc/en/resources/blog/ai-agent-telecom-operator/</guid>
      <description>With subscribers, an AI agent answers information requests on its own, at any hour and in their language. Connected to the operator’s systems, it can also look up a bill or trigger an action, within a scope set in advance. Whatever falls outside that scope, it hands to an adviser, together with what it has already checked.</description>
      <pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Altores team</dc:creator>
    </item>
  </channel>
</rss>
