It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Firek: I now see that Genoan beat me to it, and we both replied.
avatar
rtcvb32: Two replies for the price of one!

What a deal!
It's a special promo.
avatar
Ciris: [...]

- if you send multiple tickets before getting a reply, they get "stuck together" as one and put at the end of the queue (with the most recently submitted ticket).

[...]
What if we reply to the first automated response to add something or bump a ticket after some time of waiting? Does this sort of action also put it at the end of the queue again?
avatar
Ciris: [...]

- if you send multiple tickets before getting a reply, they get "stuck together" as one and put at the end of the queue (with the most recently submitted ticket).

[...]
avatar
HypersomniacLive: What if we reply to the first automated response to add something or bump a ticket after some time of waiting? Does this sort of action also put it at the end of the queue again?
Multiple tickets send a thing to the back of the queue.

Our inbox isn't a forum, "bumping" doesn't put a thing at the top - if it did, we'd get 20 tickets from each user and our support team would probably die ;)
avatar
Ciris: Our inbox isn't a forum, "bumping" doesn't put a thing at the top - if it did, we'd get 20 tickets from each user and our support team would probably die ;)
I thought they already had died and that was why everything was so slow *BADOOMSH*
high rated
avatar
Ciris: Multiple tickets send a thing to the back of the queue.

Our inbox isn't a forum, "bumping" doesn't put a thing at the top - if it did, we'd get 20 tickets from each user and our support team would probably die ;)
So, even if it's a reminder of the same ticket (same ticket ID), it's treated the same way as a new/ separate one?

I guess then that people that open threads here are doing the correct thing to draw attention to tickets they're waiting a long time on to get a reply.

*makes note to do the same in the future*
Thanks everyone!
It seems the delay was due to the topic I chose for the ticket, thanks Firek for handling it! :-)
avatar
Ciris: Multiple tickets send a thing to the back of the queue.

Our inbox isn't a forum, "bumping" doesn't put a thing at the top - if it did, we'd get 20 tickets from each user and our support team would probably die ;)
avatar
HypersomniacLive: So, even if it's a reminder of the same ticket (same ticket ID), it's treated the same way as a new/ separate one?

I guess then that people that open threads here are doing the correct thing to draw attention to tickets they're waiting a long time on to get a reply.

*makes note to do the same in the future*
No, do note that she said "multiple tickets". Replying in order to add information isn't a new ticket, making a new support request is.
Post edited February 12, 2015 by Maighstir
high rated
avatar
Maighstir: No, do note that she said "multiple tickets".

* If more information regarding an issue is required or requested, don't make a new ticket for it, reply to the last response you got on that ticket/issue.
* If you keep having the same issue (before you've gotten confirmation that it's been solved), keep quiet, it's being worked on.
* If you find a new - different - issue, make a new ticket, it most likely isn't related to the other issue and they'll get handled separately..
I think you misunderstood the point of the timeline I'm referring to. When I submit a support ticket I get an automated reply which includes the line "If you want to tell us more about this issue, please answer this email". Let's say that it's #125 in the queue at the time of submission (though I have no way of knowing how long the queue is). Ten days pass and my ticket is now #63 in the queue, If at that time (note: no reply from an actual staffer yet) something related pops up and I want to let GOG Support know about it or simply remind them that I'm waiting for ten days, I reply to that first automated email I got.
According to what she replied, my ticket will be pushed at the end of the queue which may very well be further down than the initial #125.
At least that's how I understood it.

So, instead of "bumping" the initial ticket that remains unanswered, making a forum thread about it seems the better option to get an issue addressed.
avatar
Maighstir: No, do note that she said "multiple tickets".

* If more information regarding an issue is required or requested, don't make a new ticket for it, reply to the last response you got on that ticket/issue.
* If you keep having the same issue (before you've gotten confirmation that it's been solved), keep quiet, it's being worked on.
* If you find a new - different - issue, make a new ticket, it most likely isn't related to the other issue and they'll get handled separately..
avatar
HypersomniacLive: I think you misunderstood the point of the timeline I'm referring to. When I submit a support ticket I get an automated reply which includes the line "If you want to tell us more about this issue, please answer this email". Let's say that it's #125 in the queue at the time of submission (though I have no way of knowing how long the queue is). Ten days pass and my ticket is now #63 in the queue, If at that time (note: no reply from an actual staffer yet) something related pops up and I want to let GOG Support know about it or simply remind them that I'm waiting for ten days, I reply to that first automated email I got.
According to what she replied, my ticket will be pushed at the end of the queue which may very well be further down than the initial #125.
At least that's how I understood it.

So, instead of "bumping" the initial ticket that remains unanswered, making a forum thread about it seems the better option to get an issue addressed.
I edited my post before you posted your reply though. A reply is not a new ticket (or of it is, it's not only very different from any support line I've worked at, but also quite retarded and unfair to issues that may need more information).

To quote:
avatar
Ciris: - if you send multiple tickets before getting a reply, they get "stuck together" as one and put at the end of the queue (with the most recently submitted ticket).
Replying to the autoreply in order to add more information is not a new ticket (or if it is, it's not only very different from any support line I've worked at, but also quite retarded and unfair). Using the support page to file a new issue (and probably sending a mail that is not a reply) is a new ticket (that will be joined with the earlier ticket, but given the new ticket's number and filed last in the queue).
Post edited February 13, 2015 by Maighstir
avatar
rtcvb32: Two replies for the price of one!

What a deal!
avatar
Ciris: It's a special promo.
a one off promo or will it be extended ?
high rated
avatar
Maighstir: I edited my post before you posted your reply though. A reply is not a new ticket (or of it is, it's not only very different from any support line I've worked at, but also quite retarded and unfair to issues that may need more information).

To quote: Replying to the autoreply in order to add more information is not a new ticket (or if it is, it's not only very different from any support line I've worked at, but also quite retarded and unfair). Using the support page to file a new issue (and probably sending a mail that is not a reply) is a new ticket (that will be joined with the earlier ticket, but given the new ticket's number and filed last in the queue).
Sorry, didn't get a notification for your reply.

I understand this, but reread what she replied to my inquiry; I made it quite clear that I'm referring to the same ticket, and not to a new one submitted via the support page. According to her reply, GOG's system treats both cases the same.

As for GOG's support line being different from what you know - well, it's GOG we're talking about, they often do things in ways that make no sense to us.
avatar
HypersomniacLive: Sorry, didn't get a notification for your reply.
I know, I realised just as I submitted the post that it had become a reply to Ciris, not to you as it was intended (because I quoted you, typed up the reply, then wanted to quote Ciris and ended up submitting that instead of copying the final post and hitting "reply" to you again in order to notify you).

Maybe you're right, maybe I am. I'm very likely just assuming in the way that I figure seems most logical.
avatar
Firek: [...]
Could you please clarify the situation discussed in posts #22-#24, and #26-#27?