I raised a ticket recently (prior to prepatch). It was related to an issue that I had researched thoroughly, where I’d completed an achievement some time ago, it was easily proven that I’d completed it, it was supposed to result in an item received that, when used, started a short quest, that then provided a battle pet as a reward. All of this process was easily checkable - did I complete the achievement? Yes; Did I have the quest item in my bags? No; did I have the quest in my quest log? No; was the NPC there who should spawn after activating the quest? No; did I have the quest reward? No.
It was therefore very easy to tell at which stage the achievement/quest had fallen down.
The ticket was answered within a few days, but by a “bot” that gave me a long talking to about checking the likes of wowhead and reloading my wow.
It then said that if that didn’t answer the question, to re-open the ticket.
I don’t know how the ticket bots are activated, but obviously not well. There was plenty of information in my ticket to suggest I’d done my due diligence before opening a ticket, and that simply reloading my UI wouldn’t suddenly fix the issue.
Unfortunately there was no option to re-open the ticket, so I had to create a new one (by which time it was around pre-patch time). That did have the attached “Microsoft time” timeframe on it - where every day the number went up, not down. But it was answered within a week. The stupid thing is, effectively, they themselves made that ticket harder than it needed to be. Because a GM had to respond with even more information, explaining the actions of the ticket bot, that took up more of their time.
My take-away from that experience was that (a) the ticket bot is no doubt very useful in certain circumstances - but it needs to be used in the correct circumstances; (b) they need a better system in place for filtering “easy fix” tickets as opposed to those from perhaps repeat offenders or the more complicated issues; (c) even if the response time on the ticket is the longest possible wait time - a month is not a reasonable time to expect to have to wait for a response.
And despite that suggestion, that is not what it actually says on the ticket - it says “average ticket wait time”. Which means the middle of the range - not the fastest response possible, not the longest possible.
If a month is the “average” wait time, then the actual longest wait time is probably closer to 7-8 weeks.