Incident report closed due to ME not responding?

[Aibyouka-Mew]

<p>What kinda crap is that? I've been waiting since the 2nd for my [Removed for Content] petition to be answered, it was escalated a few times, and now it's supposeldy solved since I didn't respond again after 72 hours? It's been WAY longer than that. What gives?</p><p>Every 72 hours am I supposed to update it with, "This is not [Removed for Content] solved yet."? Come on already! I've been patient. I understand that the support team is supposedly overwhelmed with whatever they claim is delaying assistance. But 10 days of waiting, and now it's closed/solved because I havn't responded to it in a short amount of time compared to my total wait time?</p><p>Pft.</p>

[TSR-JoshuaM]

<p>Feel free to PM me your incident number and I'll look in to it.</p><p>However, I do have to point out the obvious.</p><p>First, this is the General Tech Support forums.  A ticket being solved does not require technical support.  You would be much better served contacting our Support Staff directly to inquire about that.</p><p>Next, tickets being set to solved is an automated function in our ticket system but only occurs when a ticket is in a "Waiting for Customer" state.  That means, whomever was servicing your ticket sent you an email that required a ticket response.  These are typically a GM asking you for more information or something along those lines.  After 72 hours, if you do not respond to them, the ticket is set to solved automatically.</p>

[Aibyouka-Mew]

<p>I contacted pretty much everyone. The problem was it was sorted incorrectly, as to not be solved or something along those lines, so it never got looked at. Was never recontacted for more information, was just filed wrong.</p><p>Took 2 csr people to finally figure it out, and was corrected the following business day.</p><p>Bit annoyed at the messy handling of it, but was happily fixed.</p>

[TSR-JoshuaM]

<p><cite>Aibyouka-Mew wrote:</cite></p><blockquote><p>I contacted pretty much everyone. The problem was it was sorted incorrectly, as to not be solved or something along those lines, so it never got looked at. Was never recontacted for more information, was just filed wrong.</p><p>Took 2 csr people to finally figure it out, and was corrected the following business day.</p><p>Bit annoyed at the messy handling of it, but was happily fixed.</p></blockquote><p>NM.</p><p>I did see what happened.  My apologies!  In the future, feel free to use me as a spot checker.  PM me your incident number any time and I'll go see whats happening with it <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /></p>