<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Supportman Changelog</title>
    <link>https://supportman.io/changelog/</link>
    <description>Product updates and improvements to Supportman.</description>
    <language>en-us</language>
    <lastBuildDate>Sun, 07 Jun 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://supportman.io/changelog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Approvals Workflow</title>
      <link>https://supportman.io/changelog/approvals-beta/</link>
      <guid isPermaLink="true">https://supportman.io/changelog/approvals-beta/</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Support agents make judgment calls all day — refunds outside policy, credits for service failures, exceptions for key accounts. Approvals gives those decisions a proper workflow instead of a shoulder-tap in Slack.</p>

<h2>How it works</h2>
<ul>
<li>Agents request approval from the Intercom inbox without leaving the conversation.</li>
<li>Managers receive the request in Slack with full context.</li>
<li>Approve or reject with a reason — the decision is recorded on the conversation.</li>
</ul>

<figure class="ui-shot">
<img src="/field-notes/approvals-inbox-request.png" alt="Supportman Approvals panel in the Intercom inbox with request type and details fields" width="327" height="318" />
<figcaption>Request an approval from the Approvals tab in the Intercom inbox.</figcaption>
</figure>

<figure class="ui-shot-wide">
<img src="/field-notes/approvals-slack-pending.png" alt="Pending approval request in Slack with Approve and Deny buttons" width="327" height="342" />
<figcaption>Managers approve or deny in #intercom-approvals with a required comment.</figcaption>
</figure>

<figure class="ui-shot">
<img src="/field-notes/approvals-inbox-decision.png" alt="Approved refund request shown in the Supportman Approvals panel in Intercom" width="328" height="339" />
<figcaption>The decision flows back to the agent in Intercom.</figcaption>
</figure>

<h2>Beta access</h2>
<p>Approvals is free during the limited release. Email <a href="mailto:team@supportman.io">team@supportman.io</a> to enable it for your workspace.</p>]]></description>
    </item>
    <item>
      <title>DSAT channel for Slack</title>
      <link>https://supportman.io/changelog/dsat-channel/</link>
      <guid isPermaLink="true">https://supportman.io/changelog/dsat-channel/</guid>
      <pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Most support teams want the whole team seeing every CSAT in one channel — and a separate place where dissatisfied ratings get immediate attention. DSAT channel splits those two needs.</p>

<h2>What's included</h2>
<ul>
<li>Route dissatisfied and neutral Intercom ratings (😠 🙁 😐) to a dedicated Slack channel.</li>
<li>Keep your main ratings feed for the full team view.</li>
<li>Configure the DSAT channel in Slack App Home — pre-filled with your current channel.</li>
</ul>

<figure class="ui-shot-banner">
<img src="/field-notes/slack-app-home-dsat-channel.png" alt="Supportman App Home in Slack showing main channel and DSAT channel dropdowns" width="1024" height="361" />
<figcaption>Select your main ratings channel and DSAT channel in Slack App Home.</figcaption>
</figure>

<figure class="ui-shot-wide">
<img src="/field-notes/slack-dsat-rating-notification.png" alt="Supportman Slack message showing a dissatisfied conversation rating with assignee, customer, and View Conversation link" width="756" height="396" />
<figcaption>Dissatisfied ratings land in your dedicated DSAT channel.</figcaption>
</figure>

<h2>Availability</h2>
<p>Available on Pro plans and above. Basic plans keep a single ratings channel.</p>]]></description>
    </item>
    <item>
      <title>Scheduled shares route to Slack channels</title>
      <link>https://supportman.io/changelog/scheduled-share-routing/</link>
      <guid isPermaLink="true">https://supportman.io/changelog/scheduled-share-routing/</guid>
      <pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>When you schedule a conversation share from the Intercom Inbox App, it now lands in the Slack channel you picked — not as a direct message.</p>

<h2>What changed</h2>
<ul>
<li>Scheduled inbox shares respect the channel destination you chose when setting up the share.</li>
<li>DM shares still work when you explicitly send a conversation to yourself.</li>
</ul>

<figure class="ui-shot">
<img src="/field-notes/inbox-app-send-schedule.png" alt="Send at dropdown with Now, In 15 minutes, In 2 hours, and Tomorrow at 9am options" width="764" height="840" />
<figcaption>Schedule a share to a channel — it now routes to the channel you selected.</figcaption>
</figure>]]></description>
    </item>
    <item>
      <title>Clearer First Reply and Response Time metrics</title>
      <link>https://supportman.io/changelog/first-reply-response-time-metrics/</link>
      <guid isPermaLink="true">https://supportman.io/changelog/first-reply-response-time-metrics/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Weekly reports now show First Reply and Response Time as distinct metrics — so you can see how quickly agents pick up conversations versus how long resolution takes.</p>

<h2>What changed</h2>
<ul>
<li>First Reply and Response Time no longer show the same value.</li>
<li>Each metric uses the correct calculation for its definition in the report.</li>
</ul>]]></description>
    </item>
    <item>
      <title>Weekly reports for active agents only</title>
      <link>https://supportman.io/changelog/weekly-reports-active-agents/</link>
      <guid isPermaLink="true">https://supportman.io/changelog/weekly-reports-active-agents/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Personal weekly report DMs now go only to agents who were active during the reporting week — less noise for inactive team members.</p>

<h2>What changed</h2>
<ul>
<li>Agents with no activity in the week no longer receive a personal weekly report DM.</li>
<li>Team channel reports are unchanged — managers still get the full team view.</li>
</ul>]]></description>
    </item>
    <item>
      <title>Weekly reports redesign</title>
      <link>https://supportman.io/changelog/weekly-reports-redesign/</link>
      <guid isPermaLink="true">https://supportman.io/changelog/weekly-reports-redesign/</guid>
      <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Weekly Slack reports have a refreshed layout — clearer week boundaries, warmer colours, and charts that make it obvious which team and period you're looking at.</p>

<h2>What's new</h2>
<ul>
<li>Redesigned Block Kit layout with a clear week header and team context.</li>
<li>New charts with a warmer colour scheme.</li>
<li>7-day ratings summary graph added to every report.</li>
</ul>

<figure class="ui-shot-banner">
  <img src="/changelog/weekly-report-may29.png" alt="Redesigned weekly report with charts and ratings summary" width="1200" height="720" />
  <figcaption>Weekly report with updated charts and colour scheme.</figcaption>
</figure>

<h2>Why we redesigned</h2>
<p>The new layout aligns with Supportman's refreshed identity — human-focused, warm, and clear at a glance. Each report signals the team and week without feeling like a data dump.</p>]]></description>
    </item>
    <item>
      <title>Intercom Inbox App rebuilt</title>
      <link>https://supportman.io/changelog/intercom-inbox-app/</link>
      <guid isPermaLink="true">https://supportman.io/changelog/intercom-inbox-app/</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>The Intercom Inbox App has been rebuilt from scratch. Share any conversation to a Slack channel for the team, or DM it to yourself for follow-up — without copying links or switching tools.</p>

<h2>What you can do</h2>
<ul>
<li>Send a conversation to any Slack channel your team uses.</li>
<li>DM a conversation to yourself for later.</li>
<li>Schedule a share for a specific time.</li>
<li>Pick channels from a rebuilt channel picker inside the inbox sidebar.</li>
</ul>

<figure class="ui-shot">
<img src="/field-notes/inbox-app-share-panel.png" alt="Supportman Share to Slack panel in the Intercom inbox sidebar" width="764" height="712" />
<figcaption>The Supportman panel in the Intercom inbox apps sidebar.</figcaption>
</figure>

<figure class="ui-shot">
<img src="/field-notes/inbox-app-channel-picker.png" alt="Share to dropdown showing Slack channels and direct message to yourself" width="764" height="712" />
<figcaption>Choose a channel or DM yourself from the Share to dropdown.</figcaption>
</figure>

<figure class="ui-shot-wide">
<img src="/field-notes/inbox-app-slack-message.png" alt="Slack message from Supportman showing a shared conversation with note and Open Intercom Conversation button" width="842" height="536" />
<figcaption>Shared conversations land in Slack with a link back to Intercom.</figcaption>
</figure>

<h2>Why we rebuilt it</h2>
<p>Every support team has the same version of this problem: a conversation the lead needs to see, something you pick up at 4 PM that waits until morning, or a pattern emerging across threads. The new inbox app makes sharing those conversations one step from Intercom.</p>]]></description>
    </item>
    <item>
      <title>Changelog and RSS feed</title>
      <link>https://supportman.io/changelog/changelog-launch/</link>
      <guid isPermaLink="true">https://supportman.io/changelog/changelog-launch/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>The Supportman changelog is live — a public record of what we ship, with an RSS feed so you can follow along without checking back.</p>

<h2>What's live</h2>
<ul>
<li>Changelog at <a href="/changelog/">supportman.io/changelog</a> — product updates and improvements, newest first.</li>
<li>RSS feed at <a href="/changelog/rss.xml">supportman.io/changelog/rss.xml</a> for readers and automations.</li>
<li>Draft entries from app merges land in our internal draft log before we publish.</li>
</ul>

<h2>How to follow</h2>
<p>Add the RSS feed to your reader, or bookmark the changelog page. New entries land here first before they go out in email.</p>]]></description>
    </item>
  </channel>
</rss>