Hextechnician live chat is completely broken

Logistical·11/22/2018, 9:17:53 PM·6 votes·2,023 views

I submitted a ticket because my honor rewards are not showing up in my inventory. I got a quick response from Riot Support, but every single time I open a live chat support response, it just redirects me to https://support.riotgames.com/hc/en-us/articles/360001882308-You-re-chatting-with-a-Hextechnician- even if I have every single browser extension turned off (I tried this in Chrome, Firefox, and even Internet Explorer). I even tried clearing cookies. Riot pls fix your live chat, it's broken.

7 Comments

Snabkol11/23/2018, 6:38:20 AM2 votes

I also have this problem.

FATE Walvrus11/23/2018, 8:53:19 PM1 votes

I swear to god,I started to flame Jeff P. ( the hextechnician ) for that. I prefer a 3 day GOOD ANSWER than a corrupted adress that made me uninstall adblock and other extensions

Better Jungler11/23/2018, 8:55:53 PM1 votes

Live chat is open from 1 pm to 10 pm pst for select support channels, monday through saturday (i think saturday), excluding holidays.

It's currently 12:55 pm.

and yesterday was thanksgiving

A Muddy ELF11/23/2018, 10:38:42 PM1 votes

As am I, I don't even have adblock on my phone.

paranormlreality11/24/2018, 12:26:26 AM1 votes

I had the same problem when I got linked. I literally deleted EVERYTHING (all ad block, all extensions, all background stuff) off my Firefox and it finally worked. It's a garbage system that has noone's best interest in mind. I don't even know if they even helped me or the problem sorted itself out because I barely even talked to him outside of "this isn't working for me"

Gejako11/25/2018, 12:18:43 PM1 votes

I had the same problem, after time my ticket just got ''closed as solved'' yesterday even tho i couldnt see the answers at all. So i did submit a ticket yesterday again (everything the same) and now i can see the chat from the hextechnician. I can even see the answers from my ticket before (and it would have fixed my issue already :D) So just submitting another ticket fixed it for me. (maybe it was just buggy all along and riot fixed it today?)