Get in touch with the dev team

I can definitely appreciate your take on it Dave, but I guess I don’t believe that I’m enabling Zwift support to not engage by helping - if anything I’d hope that trying to help solve some of the simple queries frees up zwift support to tackle the more intransigent issues. Maybe I’m fooling myself!

I guess what rankles most James is that out of everything that I’ve posted, the one post you “actioned” was one that you took objection to, whilst you and your support colleagues have so far failed to action (or even acknowledge) any of the following bugs that I have logged so far (list below). I don’t know if this is “your” job, or David’s, or Shooj’s - but as a customer I shouldn’t really have to care. I’ve logged the issues, and they’re getting ignored. Perhaps you could steer the appropriate one of your colleagues to the list below, all of which are evidenced with screenshots, many of which have reports from multiple users, and many of which myself and others have even done some investigative work on to try and figure out the cause or common factors, to save you time.

As Dave says, I’m annoyed at the lack of support, but I’m actively involved in this community and trying to help and often try and resolve other people’s problems for them. I don’t “hate” Zwift, I love it, and that’s why I want to see it improved. So it pains me that I take the time to log issues, only to have them met with - as far as I can tell - complete indifference from Zwift. It would be great to see acknowledgement and action on the below, with them being moved to known issues, assigned a ticket with development, and a timescale quoted for fix:

This my not be your job but it should be someones:

6 Likes