Blue Tracker
World of Warcraft Blue Posts
Diablo II: Resurrected Blue Posts
Diablo III Blue Posts
Hearthstone Blue Posts
Overwatch Blue Posts
Heroes of the Storm Blue Posts
Diablo IV Blue Posts
BlizzCon Blue Posts
Warcraft Rumble Blue Posts

Twitter Not Updating Ticket Information?

Forum Avatar
Gariellen
#0 - Oct. 20, 2010, 9:41 a.m.
Blizzard Post
Hail,

I am quite sure that with all of the problems with this most recent patch that you all are swamped, however, the website before the patch actually encouraged people to go to Twitter to get an updated status on the turn around of tickets and escalated tickets.

I submitted a ticket, which turned into an escalated ticket, which turned into a response telling me to get updates on the forums on the issue, only not to have any updates on the issue I submitted. :(

Again I am very patient, no matter how frustrating it is, however, it would be nice to have information on the turn around time on the tickets and escalated tickets properly again displayed on your twitter page, or to have it posted here on a daily basis for your customers.

No I do not feel this is a suggestion, but a customer service issue, as it was my understanding that the Twitter page was indeed being handled by the C/S department.

It is a great feature, but I do not need updates on content not yet available, or more Blizzcon commericals...I know (GASP, how dare I say that blah blah) :), but this information I believe if available again would make yours and everyone's frustration levels decrease quite a bit.

Thanks for all that you all do, and please put that information back on the top page of your Twitter Page.

Gariellen
Forum Avatar
Orlyia
#2 - Oct. 20, 2010, 9:46 a.m.
Blizzard Post
Twitter is typically updated a couple times a day during the week with that sort of information, Gar.

I see a petition here on Northern Spices, which is a known issue but I have no further word on at the moment.

I also see you have a petition in about a quiver that didn't seem to convert to a bag - but that petition was abandoned. You could certainly reopen that issue, but I've no information on that at all at this time.