Maintenance for the week of September 22:
• NA megaservers for maintenance – September 22, 4:00AM EDT (8:00 UTC) - 10:00AM EDT (14:00 UTC)
• EU megaservers for maintenance – September 22, 8:00 UTC (4:00AM EDT) - 14:00 UTC (10:00AM EDT)

No response from support for TWO weeks. Now the answer has been received - and it is terrible.

R_Roar
R_Roar
5o30f1xssdq7.png
I opened a ticket for my problem (the question is purely technical). At first, communication was quite active: support asked for more information, screenshots, etc. The problem has been recognized. But TWO WEEKS have passed since my last reply (again, with clarifying information). There are no more contacts, no more requests to me - just an open ticket and that's it.
How do I find out what's going on and if there's any movement on the issue at all?
Edited by R_Roar on July 26, 2025 7:26AM
  • ZOS_Kraken
    ZOS_Kraken
    admin
    @R_Roar Can you please tell me your ticket number?
    Staff Post
  • LPapirius
    LPapirius
    ✭✭✭✭✭
    Also, there is some mixed messaging going on in these situations.

    They tell us on the forum not to update our tickets because that moves the ticket to the end of the line. While at the same time the formatted canned responses we get automatically clearly state that if they don't hear back from us within 4 days the issue will be considered resolved.

    So which is it?

    @ZOS_Kevin
  • freespirit
    freespirit
    ✭✭✭✭✭
    ✭✭✭
    @LPapirius , you should reply to all emails you get to keep your ticket active, you only get put to the back of the queue if you open a totally new ticket for the same problem.

    So reply to emails on the active ticket do not open a new ticket. :)
    When people say to me........
    "You're going to regret that in the morning"
    I sleep until midday cos I'm a problem solver!
  • R_Roar
    R_Roar
    @ZOS_Kraken Ofc, ticket 250704-001250
  • ZOS_Kraken
    ZOS_Kraken
    admin
    @R_Roar I have left you a forums message about the status of your ticket.
    Staff Post
  • R_Roar
    R_Roar
    I see. Not very good information, but at least it's something, thank you.
  • R_Roar
    R_Roar
    In short, my problem is that my main character DIDN'T do the Q1 quest, but the game thinks he did it. So in early July, employee A, after clarifying questions/screenshots, says (briefly): "Yes, according to your logs, quest Q1 has NOT BEEN COMPLETED. We're taking the time to sort out the situation." After TWO(!!) WEEKS(!!!) of waiting, ANOTHER employee B reports: "You have COMPLETED the Q1 quest, have a good day, take care of yourself." I do not even know how to comment on this... WHY is it necessary to "switch" employees in the middle of solving the issue?? Why can't employee A keep a ticket from the moment it is opened until it is closed? And if employee B has taken over from Employee A, why doesn't he read the entire ticket history from the very beginning and doesn't take into account previous statements and previously established facts? Now I have to lose at least a week again to prove that the quest Q1 was not completed. But employee B, as I understand it, can be replaced by employee C at any time, right?
Sign In or Register to comment.