Edited By
Leonardo Moretti

Three tickets opened; frustration mounts over lack of replies
A wave of frustration is washing over users of Kraken as reports of unresponsive customer service become increasingly common. With three open tickets and zero responses from support, one individual shared their struggle on various forums.
The situation escalated over the weekend, when an individual reached out for help via live chat on May 17, but received no acknowledgment. The person's disappointment is echoed by others in the community, raising concerns on user boards about Krakenโs responsiveness.
Comments on the issue highlight a shared dissatisfaction:
Ticket numbers noted: "16595904, 16614193, 16604844"โthese have gone unanswered despite repeated requests.
Support requests are increasingly prioritized, leaving many puzzled.
A community member requested ticket specifics, signaling eagerness to assist and demand accountability from Kraken.
"Could you please share one of the ticket numbers? We will check this for you and help."
The sentiment among people seems notably negative, with many noting Kraken's lack of communication as a major concern. Noticing that some individuals feel abandoned, could this shake customer loyalty?
โ ๏ธ Support tickets seem to be ignored; many users report similar issues.
๐ Frustration is building as users seek answers from customer support; no clear timeline for resolution.
๐ฌ "Itโs disheartening to see no response from a platform we trust." - A comment reflecting the general mood.
As users await answers, the clock is ticking for Kraken to address these concerns effectively. How will the platform rectify these communication failures moving forward?
Given the current situation, there's a strong chance Kraken will face mounting pressure to enhance their customer service protocols. As users express dissatisfaction, the platform might prioritize addressing these communication gaps. Experts estimate around a 60% likelihood that Kraken will implement a more responsive support system within the next few months. If unresolved, continuous frustration may drive users to explore alternative exchanges, risking long-term loyalty.
In a less obvious but relevant parallel, consider the challenges faced by tech giants during significant outages. In 2015, a major social media platform experienced a day-long service failure, leading to widespread user backlash and a decline in trust. Much like Kraken today, the company was forced to reassess its customer service strategy to prevent further dissention, ultimately leading to policies aimed at quicker communication. The echoes of that situation remind us how swift action can mitigate long-term fallout, a lesson Kraken may need to embrace soon.