I submitted two zoom-related bugs which are NOT the 'inability to zoom due to vehicle binding 1 issue, but are instead entirely different bugs, using the insider bug reporting form, and in both cases I received canned responses telling me that I’d reported the known issue to do with vehicle binding. It’s as if my tickets weren’t even read, I was just copy-pasted a totally unrelated response based on the assumption I was submitting the keybinding conflict bug instead.
I won’t name any names, but are there bots combing the tickets by any chance? It’s a bit worrying when I pour hours into submitting a (pretty hefty) list of tickets and the representative who contacts me can’t even be bothered to read the titles of my tickets, which are quite clear.
So I guess my question is – will all tickets be ultimately read by humans, or are they going to have to pass through some kind of bot algorithm first? Because if the latter is true, I might need to pick different titles for tickets like the two examples above, lest they get swept aside mistakenly.
> 2533274931368952;1:
> I submitted two zoom-related bugs which are NOT the 'inability to zoom due to vehicle binding 1 issue, but are instead entirely different bugs, using the insider bug reporting form, and in both cases I received canned responses telling me that I’d reported the known issue to do with vehicle binding. It’s as if my tickets weren’t even read, I was just copy-pasted a totally unrelated response based on the assumption I was submitting the keybinding conflict bug instead.
>
> I get that they’re extremely busy, but it does concern me that the most basic, elementary part of my ticket (the title itself, in this case both
> “You can remain scoped / zoomed while reloading a weapon" and
> "Non-scope weapons are capable of zooming”
> received completely unrelated copy-pasted responses.
>
> I won’t name any names, but are there bots combing the tickets by any chance? It’s a bit worrying when I pour hours into submitting a (pretty hefty) list of tickets and the representative who contacts me can’t even be bothered to read the titles of my tickets, which are quite clear.
>
> So I guess my question is – will all tickets be ultimately read by humans, or are they going to have to pass through some kind of bot algorithm first? Because if the latter is true, I might need to pick different titles for tickets like the two examples above, lest they get swept aside mistakenly.
If you’re working 8+ hour shifts and working a keyboard all day, wouldn’t you have a list of prepared responses for your convenience? It saves time, makes you more productive, and lessens the chance of carpal tunnel.
I have had the same experience with the Zoom bug on Controller for Halo CE that I just submitted a couple days ago. The ticket looked like it was the common bug for keybinding, but it has nothing to do with Keyboard and Mouse (which the response I got was about rebinding the vehicle function 1 or your zoom button to something else)! The difference here is only using a Controller with playing Halo CE where the toggle for zooming doesn’t work properly on higher framerates, only at 60 fps locked does it work just fine like on Xbox One!
343 needs to keep in mind they are dealing with 100k invites (which was sent of there OWN choice!) and they should have actual people be responding to these bug reports because the bug I sent I thought might have been unique and not one many on PC playing on a gamepad was being talked about by the community (not just generic responses). Multiply that by 10 tickets being sent there way per person or maybe just 1 or 2 and now your dealing with that many close to 1 million. They should have a big enough staff on hand to deal with this amount of ticket traffic if they so choose to send out these many invites in the first place!!
If they honestly cannot deal with that much traffic, perhaps they need to keep it limited to a smaller pool of people like they did in the past. I know everyone wants to play the games early but I guess they have to make the choice in which they can deal with that many people sending in tickets. Maybe they use some kind of data table of types of responses submitted and see which ones are the outliers in the table grid.
> 2535454703778907;2:
> > 2533274931368952;1:
> > I submitted two zoom-related bugs which are NOT the 'inability to zoom due to vehicle binding 1 issue, but are instead entirely different bugs, using the insider bug reporting form, and in both cases I received canned responses telling me that I’d reported the known issue to do with vehicle binding. It’s as if my tickets weren’t even read, I was just copy-pasted a totally unrelated response based on the assumption I was submitting the keybinding conflict bug instead.
> >
> > I get that they’re extremely busy, but it does concern me that the most basic, elementary part of my ticket (the title itself, in this case both
> > “You can remain scoped / zoomed while reloading a weapon" and
> > "Non-scope weapons are capable of zooming”
> > received completely unrelated copy-pasted responses.
> >
> > I won’t name any names, but are there bots combing the tickets by any chance? It’s a bit worrying when I pour hours into submitting a (pretty hefty) list of tickets and the representative who contacts me can’t even be bothered to read the titles of my tickets, which are quite clear.
> >
> > So I guess my question is – will all tickets be ultimately read by humans, or are they going to have to pass through some kind of bot algorithm first? Because if the latter is true, I might need to pick different titles for tickets like the two examples above, lest they get swept aside mistakenly.
>
> If you’re working 8+ hour shifts and working a keyboard all day, wouldn’t you have a list of prepared responses for your convenience? It saves time, makes you more productive, and lessens the chance of carpal tunnel.
Curated responses that are actually relevant to the issue are one thing. However, in the world of tech support, there’s far too many times where a copy pasted response does not provide help in any shape to the one submitting the request or ticket.
I think they’re taking it seriously cuz they keep stoping these kinda posts and saying pls report w an email. I mean I guess they’ve gotten a lotta these.
> 2535454703778907;2:
> > 2533274931368952;1:
> > Blah
>
> If you’re working 8+ hour shifts and working a keyboard all day, wouldn’t you have a list of prepared responses for your convenience? It saves time, makes you more productive, and lessens the chance of carpal tunnel.
Yes, I probably would. But I wouldn’t select one that has nothing to do with the concern raised by the ticket. It’s one thing using a canned response. It’s another thing entirely using a totally unrelated canned response because you didn’t bother to read what you were responding to**.**As I said quite clearly in my post that I get that they’re busy, but they’ll invariably create even more work for themselves if they rush to the point where a very clearly written subject title and description are ignored in favour of a completely unrelated response.
**Your logic alone is baffling, because they would have saved time and energy by not having to submit an irrelevant response if they’d actually spent an extra second reading my tickets title.**It makes you wonder how many unrelated yet important tickets get overlooked because the developers assumed the content based on the briefest glance.
> 2533274931368952;1:
> So I guess my question is – <mark>will all tickets be ultimately read by humans</mark>, or are they going to have to pass through some kind of bot algorithm first? Because if the latter is true, I might need to pick different titles for tickets like the two examples above, lest they get swept aside mistakenly.
Hey Hirotoro4692,
First and foremost, thank you for taking the time to submit a ticket! The team loves receiving reported issues so we can help build better games.
I can confirm that I just pulled up the support team’s nightly reported issues report and I indeed see on it the reported bucket of grouped issues for “Remain Zoomed while reloading a weapon.” The Support team reviews each ticket submitted and groups them accordingly based on issues to discern high volume unique issues reported in flighting.
As it relates to responses for mass reported issues we draft responses for similar tickets to be sent. Sometimes overlap such as this happens where it is not a 1:1, but when bucketing and reporting on them internally we are reading and accounting for them. We value player feedback and reported issues and are working diligently to listen, identify problems, and act on issues reported by the community.
> 2727626560040591;9:
> > 2535406960473328;8:
> > I’m noticing that no one is playing reach for the flight, whats going on?
>
> CE is probably more popular considering it’s the first PC flight with it.
> 2533274931368952;1:
> I submitted two zoom-related bugs which are NOT the 'inability to zoom due to vehicle binding 1 issue, but are instead entirely different bugs, using the insider bug reporting form, and in both cases I received canned responses telling me that I’d reported the known issue to do with vehicle binding. It’s as if my tickets weren’t even read, I was just copy-pasted a totally unrelated response based on the assumption I was submitting the keybinding conflict bug instead.
>
> I get that they’re extremely busy, but it does concern me that the most basic, elementary part of my ticket (the title itself, in this case both
> “You can remain scoped / zoomed while reloading a weapon”
> and
> “Non-scope weapons are capable of zooming”
> received completely unrelated copy-pasted responses.
>
> I won’t name any names, but are there bots combing the tickets by any chance? It’s a bit worrying when I pour hours into submitting a (pretty hefty) list of tickets and the representative who contacts me can’t even be bothered to read the titles of my tickets, which are quite clear.
>
> So I guess my question is – will all tickets be ultimately read by humans, or are they going to have to pass through some kind of bot algorithm first? Because if the latter is true, I might need to pick different titles for tickets like the two examples above, lest they get swept aside mistakenly.
Well it is kind of like the OK we received your ticket response and depending on the topic depends on one o the Auto replies you may get
MIne was to do with controller input loss during volume adjustment.
But at least I got a Reply and in less than 24 hours and that is a vast improvement on some other AAA companies.
Sun 23/02/2020 7:35 PM
<ul class="++++++++++++++++++++++>Alan J T
##- Please type your reply above this line -##
Halo Support has recieved your request (2XXXX) and it will be reviewed by an agent.
To add additional comments, reply to this email.
This email is a service from Halo Insider Support. Delivered by Zendesk | Privacy Policy[XXXXXXXX]
<mark>This post has been edited by a moderator. Please refrain from making non-constructive posts.</mark> *Original post. Click at your own discretion.
There’s no need to be concerned, your feedback, or anyone else’s for that matter, will never be taken seriously.
> 2533274861485842;12:
> This post has been edited by a moderator. Please refrain from making non-constructive posts.*Original post. Click at your own discretion.There’s no need to be concerned, your feedback, or anyone else’s for that matter, will never be taken seriously.
Why such negativity? It seems like you’re on every thread I visit just being a downer. You aren’t even being constructive, just being angry for the sake of it. Seriously dude…
I am reassured by Postums’ response in this thread. The sheer volume of tickets has got to be staggering. But yeah, the fact he replied to the thread alone does tell me someone’s listening. Also, the changes in the recent flight build demonstrated that they’re working hard to implement feedback.