<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>customerSupport &amp;mdash; Micro Matt</title>
    <link>https://micro.baer.works/tag:customerSupport</link>
    <description>Micro thoughts and mini posts.</description>
    <pubDate>Fri, 17 Apr 2026 01:35:28 +0000</pubDate>
    <image>
      <url>https://i.snap.as/4R3vdrBj.png</url>
      <title>customerSupport &amp;mdash; Micro Matt</title>
      <link>https://micro.baer.works/tag:customerSupport</link>
    </image>
    <item>
      <title>Switching from a crowded email inbox to a more organized system for customer...</title>
      <link>https://micro.baer.works/switching-from-a-crowded-email-inbox-to-a-more-organized-system-for-customer?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[Switching from a crowded email inbox to a more organized system for customer support has helped a ton over the past month. Now, that “email hour” I added to my daily schedule actually works, because I have limited inboxes to visit, and can view each request as a to-do item.&#xA;&#xA;Everything is powered by our Discourse forum. Write.as users get a certain email address to send to, based on their support level. Those emails show up in different Discourse group inboxes. The high-priority group also pings my personal email, just so I don’t forget it’s there. But the low-priority group won’t ever disturb me — I have to visit that inbox to see messages there.&#xA;&#xA;When my email hour starts, first I visit my high-priority inbox, where paying users send their requests. As soon as I respond, I archive the thread, so I eventually get to “inbox zero” and know that I’m done. Then I move on to the low-priority inbox, and then public conversations on the forum.&#xA;&#xA;Between limiting how much I’m personally pinged, and having a UI that shows requests as a limited to-do list, all of it is much more manageable.&#xA;&#xA;customerSupport&#xA;&#xA;Thoughts? a href=&#34;https://remark.as/p/micro.baer.works/switching-from-a-crowded-email-inbox-to-a-more-organized-system-for-customer&#34;Discuss.../a]]&gt;</description>
      <content:encoded><![CDATA[<p>Switching from a crowded email inbox to a more organized system for customer support has helped a ton over the past month. Now, that “<a href="https://micro.baer.works/working-on-putting-a-better-system-in-place-for-customer-support">email hour</a>” I added to my daily schedule actually works, because I have limited inboxes to visit, and can view each request as a to-do item.</p>

<p>Everything is powered by our Discourse forum. Write.as users get a certain email address to send to, based on their support level. Those emails show up in different Discourse group inboxes. The high-priority group also pings my personal email, just so I don’t forget it’s there. But the low-priority group won’t ever disturb me — I have to visit that inbox to see messages there.</p>

<p>When my email hour starts, first I visit my high-priority inbox, where paying users send their requests. As soon as I respond, I archive the thread, so I eventually get to “inbox zero” and know that I’m done. Then I move on to the low-priority inbox, and then public conversations on the forum.</p>

<p>Between limiting how much I’m personally pinged, and having a UI that shows requests as a limited to-do list, all of it is much more manageable.</p>

<p><a href="https://micro.baer.works/tag:customerSupport" class="hashtag"><span>#</span><span class="p-category">customerSupport</span></a></p>

<p><em>Thoughts? <a href="https://remark.as/p/micro.baer.works/switching-from-a-crowded-email-inbox-to-a-more-organized-system-for-customer">Discuss...</a></em></p>
]]></content:encoded>
      <guid>https://micro.baer.works/switching-from-a-crowded-email-inbox-to-a-more-organized-system-for-customer</guid>
      <pubDate>Tue, 04 Jan 2022 17:22:01 +0000</pubDate>
    </item>
    <item>
      <title>Working on putting a better system in place for customer support.</title>
      <link>https://micro.baer.works/working-on-putting-a-better-system-in-place-for-customer-support?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[Working on putting a better system in place for customer support. I’ve tried setting aside an “email hour” every day — literally scheduling it on my calendar. But the email inbox is too messy; I have a system for marking important requests but things get pushed down and out of sight; in the end it’s too overwhelming for me to sit down and get through everything in a consistent way.&#xA;&#xA;I think we’ll get some kind of support ticket system in place, so there’s a dedicated area for people to go when they need help with something, and a single place I can log into every morning to go through and clear out. I’m not sure where we’ll send people that have questions before they use the product — I’ll need to figure out a sane channel for them that doesn’t get used for all kinds of other things. But my priority is keeping track of customer issues.&#xA;&#xA;Today, all day, I worked on nothing but my backlog of requests — they piled up a bit after a mental break trip last week. There are still important requests and conversations I need to follow up on. It’s really not too much overall, if I took care of everything and then stayed on top of it going forward. Just need to get to that point. (If I haven’t answered your email, you should hear from me soon!)&#xA;&#xA;customerSupport&#xA;&#xA;Thoughts? a href=&#34;https://remark.as/p/micro.baer.works/working-on-putting-a-better-system-in-place-for-customer-support&#34;Discuss.../a]]&gt;</description>
      <content:encoded><![CDATA[<p>Working on putting a better system in place for customer support. I’ve tried setting aside an “email hour” every day — literally scheduling it on my calendar. But the email inbox is too messy; I have a system for marking important requests but things get pushed down and out of sight; in the end it’s too overwhelming for me to sit down and get through everything in a consistent way.</p>

<p>I think we’ll get some kind of support ticket system in place, so there’s a dedicated area for people to go when they need help with something, and a single place I can log into every morning to go through and clear out. I’m not sure where we’ll send people that have questions before they use the product — I’ll need to figure out a sane channel for them that doesn’t get used for all kinds of other things. But my priority is keeping track of customer issues.</p>

<p>Today, all day, I worked on nothing but my backlog of requests — they piled up a bit after a mental break trip last week. There are still important requests and conversations I need to follow up on. It’s really not too much overall, if I took care of everything and then stayed on top of it going forward. Just need to get to that point. (If I haven’t answered your email, you should hear from me soon!)</p>

<p><a href="https://micro.baer.works/tag:customerSupport" class="hashtag"><span>#</span><span class="p-category">customerSupport</span></a></p>

<p><em>Thoughts? <a href="https://remark.as/p/micro.baer.works/working-on-putting-a-better-system-in-place-for-customer-support">Discuss...</a></em></p>
]]></content:encoded>
      <guid>https://micro.baer.works/working-on-putting-a-better-system-in-place-for-customer-support</guid>
      <pubDate>Thu, 18 Nov 2021 00:48:32 +0000</pubDate>
    </item>
  </channel>
</rss>