<?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>idea Incident Transparency in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/incident-transparency/idi-p/934932</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I have perhaps a controversial idea, but I think a pretty good one. Each time I call customer support (which is great by the way) I get an analyst on the other end who I believe has an enormous capability that I do not have.&lt;BR /&gt;&lt;BR /&gt;I will typically explain my problem and give them an error message if applicable and then they will conduct a search on their end in an attempt to solve the issue. What I am assuming is that the analysts are probably&amp;nbsp;querying through all the logged&amp;nbsp;tickets that the support staff have ever resolved.&lt;BR /&gt;&lt;BR /&gt;Wouldn't this be a huge benefit to ArcGIS users to be able to tap into the ESRI incident log prior to making a phone call to support. I realize that there would be a few privacy hurdles that would need to be worked out to keep client confidentiality intact, but I think&amp;nbsp;with some&amp;nbsp;tweaking&amp;nbsp;that could be accomplished.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Look, I know we have forums, and countless pages of help documents, but actually browsing resolved tickets would be a huge boon for users, and&amp;nbsp;I am willing to bet&amp;nbsp;considerable cost savings for ESRI. Allowing support staff to publish tickets to a searchable database that is accessable to ArcGIS users&amp;nbsp;in my mind would be the next step towards GIS nirvana.&lt;BR /&gt;&lt;BR /&gt;dave-o.

&lt;!-- content transformation source ID: 087E00000004oL8 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Jul 2013 17:33:26 GMT</pubDate>
    <dc:creator>daveostrander</dc:creator>
    <dc:date>2013-07-12T17:33:26Z</dc:date>
    <item>
      <title>Incident Transparency</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/incident-transparency/idi-p/934932</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I have perhaps a controversial idea, but I think a pretty good one. Each time I call customer support (which is great by the way) I get an analyst on the other end who I believe has an enormous capability that I do not have.&lt;BR /&gt;&lt;BR /&gt;I will typically explain my problem and give them an error message if applicable and then they will conduct a search on their end in an attempt to solve the issue. What I am assuming is that the analysts are probably&amp;nbsp;querying through all the logged&amp;nbsp;tickets that the support staff have ever resolved.&lt;BR /&gt;&lt;BR /&gt;Wouldn't this be a huge benefit to ArcGIS users to be able to tap into the ESRI incident log prior to making a phone call to support. I realize that there would be a few privacy hurdles that would need to be worked out to keep client confidentiality intact, but I think&amp;nbsp;with some&amp;nbsp;tweaking&amp;nbsp;that could be accomplished.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Look, I know we have forums, and countless pages of help documents, but actually browsing resolved tickets would be a huge boon for users, and&amp;nbsp;I am willing to bet&amp;nbsp;considerable cost savings for ESRI. Allowing support staff to publish tickets to a searchable database that is accessable to ArcGIS users&amp;nbsp;in my mind would be the next step towards GIS nirvana.&lt;BR /&gt;&lt;BR /&gt;dave-o.

&lt;!-- content transformation source ID: 087E00000004oL8 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Jul 2013 17:33:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/incident-transparency/idi-p/934932</guid>
      <dc:creator>daveostrander</dc:creator>
      <dc:date>2013-07-12T17:33:26Z</dc:date>
    </item>
    <item>
      <title>Re: Incident Transparency</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/incident-transparency/idc-p/934933#M3935</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I believe this is called ESRI Kube

&lt;!-- content transformation source ID: 00aE0000004L0VF --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Oct 2013 16:54:59 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/incident-transparency/idc-p/934933#M3935</guid>
      <dc:creator>daveostrander</dc:creator>
      <dc:date>2013-10-23T16:54:59Z</dc:date>
    </item>
  </channel>
</rss>

