Posted April 14, 2021
high rated
So... I have an active unresolved ticket from JULY OF LAST YEAR.
This got a reply which didn't resolve the issue in August, so I followed that up expecting the conversation to continue. I didn't get any replies to it for longer than the expected response window I was quoted at the time - which was already up to 4 weeks - so I sent another reply asking for a follow-up in September.
Instead of a reply, this message got assigned a new ticket number. I replied to this clarifying that I already (and still) have an unresolved ticket and quoted the ticket number to confirm where to look.
The last email I got from a real person is STILL the reply in August. In December, I got another automated message telling me that there are huge delays and they're working on it.
Even the 4 week turnaround you were at before inappropriately forcing 2.0 onto customers was only justified as a "figuring out the workflow while the pandemic is starting" measure. You don't have that excuse any more. And not being able to manage replying to an unsolved ticket in LITERALLY MORE THAN HALF A YEAR is beyond incompetent. Maybe next time, DON'T push a tested AND CONFIRMED NOT READY update into being a live auto updating version of your app while you're in the middle of a massive loss in support service? And if you somehow forget that, make sure at least SOMEONE in your support team is actually capable of doing their jobs.
This is the exact wrong-est kind of impressive.
This got a reply which didn't resolve the issue in August, so I followed that up expecting the conversation to continue. I didn't get any replies to it for longer than the expected response window I was quoted at the time - which was already up to 4 weeks - so I sent another reply asking for a follow-up in September.
Instead of a reply, this message got assigned a new ticket number. I replied to this clarifying that I already (and still) have an unresolved ticket and quoted the ticket number to confirm where to look.
The last email I got from a real person is STILL the reply in August. In December, I got another automated message telling me that there are huge delays and they're working on it.
Even the 4 week turnaround you were at before inappropriately forcing 2.0 onto customers was only justified as a "figuring out the workflow while the pandemic is starting" measure. You don't have that excuse any more. And not being able to manage replying to an unsolved ticket in LITERALLY MORE THAN HALF A YEAR is beyond incompetent. Maybe next time, DON'T push a tested AND CONFIRMED NOT READY update into being a live auto updating version of your app while you're in the middle of a massive loss in support service? And if you somehow forget that, make sure at least SOMEONE in your support team is actually capable of doing their jobs.
This is the exact wrong-est kind of impressive.