<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic FIFO Queue in Get Support</title>
    <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370350#M279539</link>
    <description>&lt;P&gt;With all the recent network problems wouldn't it be best if Public Mobile reconsidered their FIFO queue policy that is currently used by the &lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/22437"&gt;@CS_Agent&lt;/a&gt;&amp;nbsp;&amp;nbsp; and maybe implement some type of severity rating system that will allow them to allocate the most resources to fix the most serious customer problems first?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A customer without any service having to wait for 5 days to get a response because another customer ahead of him can't get VoiceMail to co-operate does not make sense.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jan 2022 12:31:59 GMT</pubDate>
    <dc:creator>geopublic</dc:creator>
    <dc:date>2022-01-05T12:31:59Z</dc:date>
    <item>
      <title>FIFO Queue</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370350#M279539</link>
      <description>&lt;P&gt;With all the recent network problems wouldn't it be best if Public Mobile reconsidered their FIFO queue policy that is currently used by the &lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/22437"&gt;@CS_Agent&lt;/a&gt;&amp;nbsp;&amp;nbsp; and maybe implement some type of severity rating system that will allow them to allocate the most resources to fix the most serious customer problems first?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A customer without any service having to wait for 5 days to get a response because another customer ahead of him can't get VoiceMail to co-operate does not make sense.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jan 2022 12:31:59 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370350#M279539</guid>
      <dc:creator>geopublic</dc:creator>
      <dc:date>2022-01-05T12:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: FIFO Queue</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370359#M279540</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/73984"&gt;@geopublic&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;With all the recent network problems wouldn't it be best if Public Mobile reconsidered their FIFO queue policy that is currently used by the &lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/22437"&gt;@CS_Agent&lt;/a&gt;&amp;nbsp;&amp;nbsp; and maybe implement some type of severity rating system that will allow them to allocate the most resources to fix the most serious customer problems first?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A customer without any service having to wait for 5 days to get a response because another customer can't get VoiceMail to co-operate does not make sense.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Agree...someone without service should be prioritized over more minor issues!&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2019 18:02:12 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370359#M279540</guid>
      <dc:creator>dabr</dc:creator>
      <dc:date>2019-05-17T18:02:12Z</dc:date>
    </item>
    <item>
      <title>Re: FIFO Queue</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370366#M279541</link>
      <description>&lt;P&gt;The only problem I could see with doing a prioritized system is people with low priority problems could end up getting bumped forever.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I would like to see is some way to track your moderator emails. My work uses an email system for tech support but when you send an email you get an incident number as a reply. And there is a page you can go to that can track the status of your incident. So you know it didn't get trashed and you can add more info if things change.&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2019 18:11:59 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370366#M279541</guid>
      <dc:creator>kelvarnsen</dc:creator>
      <dc:date>2019-05-17T18:11:59Z</dc:date>
    </item>
    <item>
      <title>Re: FIFO Queue</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370375#M279542</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/52139"&gt;@kelvarnsen&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;The only problem I could see with doing a prioritized system is people with low priority problems could end up getting bumped forever.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I would like to see is some way to track your moderator emails. My work uses an email system for tech support but when you send an email you get an incident number as a reply. And there is a page you can go to that can track the status of your incident. So you know it didn't get trashed and you can add more info if things change.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;a href="https://productioncommunity.publicmobile.ca/t5/user/viewprofilepage/user-id/52139"&gt;@kelvarnsen&lt;/a&gt;&amp;nbsp; Great idea, that would be ideal but is it costly to implement?&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2019 18:19:44 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370375#M279542</guid>
      <dc:creator>geopublic</dc:creator>
      <dc:date>2019-05-17T18:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: FIFO Queue</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370409#M279543</link>
      <description>&lt;P&gt;I understand some prioritization does occur. That said, there is a serious communication gap whenever incoming private messages cannot be cleared within 24 hours. Even worse when there's a systemic issue and moderators may not post updates in Announcements.&lt;/P&gt;&lt;P&gt;PM is a work in progress, and we're living through it! &lt;img id="robotwink" class="emoticon emoticon-robotwink" src="https://productioncommunity.publicmobile.ca/i/smilies/16x16_robot-wink.png" alt="Robot wink" title="Robot wink" /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2019 19:36:27 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370409#M279543</guid>
      <dc:creator>Luddite</dc:creator>
      <dc:date>2019-05-17T19:36:27Z</dc:date>
    </item>
    <item>
      <title>Re: FIFO Queue</title>
      <link>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370422#M279544</link>
      <description>&lt;P&gt;The only practical solution is FIFO.&amp;nbsp; To do priority ranking would require someone to read each private message and bin them.&amp;nbsp; This process adds extra work and thus further delay.&amp;nbsp; IMHO, the resolution to the long queues causes by widespread problems is to up the product quality and reduce the number of occurrences.&amp;nbsp; It has been one issue after another after another in recent times.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2019 19:52:31 GMT</pubDate>
      <guid>https://productioncommunity.publicmobile.ca/t5/Get-Support/FIFO-Queue/m-p/370422#M279544</guid>
      <dc:creator>will13am</dc:creator>
      <dc:date>2019-05-17T19:52:31Z</dc:date>
    </item>
  </channel>
</rss>

