Token autodetection is broken

That only works for the initial bot! Then it tells you to close the convo and click “contact support”.

I am already waiting in line for a human (for an hour), but there is another chat bot that checks in every 5 minutes if you’re still there. You have to reply or you lose your spot in the queue. Replying connect me to a support agent there does absolutely nothing.

“The #1 in queue” has been there the whole time btw.

See:

I understand how frustrating that could be. Please just have a bit more patience or try again another time that is more convenient for you

1 Like

Yeah I don’t want to waste more time waiting and trying to report this.

I’ve already sent all the details in here and in the support chat. Going to close it now because I’ve been “number 1 in queue” for an hour. And I have to ping the bot every 5 minutes to not lose the spot in the queue. Done that 12 times in a row…

\

All the details (including full video that showcases how it looks like on my end) are in that chat. I don’t need to hear what the support has to say so I don’t necessarily need to stick around. They just need to be made aware of the issue, and all the details and video showcasing what happens are in that chat.

I hope that closing the chat doesn’t fully remove the ticket, otherwise it would have been pointless. But at this point in time I’ve reported like 20+ issues to MM in the past and wasted probably like 12h of my time reporting and troubleshooting things. Probably another 5h waiting in line and having to reply to the bot not to lose my spot in the queue.

Hope it gets resolved for other users, but I’m about to fully port to other wallets.

1 Like

So sorry for experiencing that. Yeah, all the feedback will surely get to the team

1 Like

Thank you for the detailed feedback, and I’m sorry you had to wait so long to create a ticket :blue_heart: Normally, opening a ticket is much quicker, so this may have changed recently. If you have any specific questions or additional feedback, you can try again tomorrow. I’ve already reported this issue to the team as well.

1 Like