Threema Support No Replies

Stelle deine Frage öffentlich an die Threema-Forum-Community - über 4.800 Mitglieder helfen dir weiter. > Frage stellen <
  • Öffentlicher Beitrag
    Mir ist bewusst, dass dieser Beitrag öffentlich ist.

    Hi, is anyone else having issues with getting replies from Support? My account is locked from their side and need it unfrozen asap. The Support page says takes up to 3 days but we are well past that date

    Have emailed 8 days ago. They finally replied yesterday 1 time with a generic email, I replied with the issue and nothing since

    Used a separate Threema account to message their support and same thing, a generic message, and when I replied with the issue, they haven't responded again in 5 days now

    Issue for my account is coming from their server side. This is becoming incredibly frustrating how slow it is and the lack of support. Anyone else having the same issue?

  • Hi there

    What do you mean with "my account is locked from their side"? When you open up Threema, do you see a yellow/red horizontal line also known as a connection indicator? What have you done before?

    What does threema.ch/netcheck say?

    Threema has a very good spam and scam detection. So if your threema id is marked for spam, you very likely do not have any chances and your blocked from the Threema servers. Just that I said it.

  • Hi Julian,

    I do not see the yellow/red horizontal line

    threema.ch/netcheck are all green and working

    Yes, I believe their spam bot incorrectly got me. What happened was I downloaded Threema Desktop, went to sync, after few minutes I thought was frozen so disconnected and was going to sync again, but before I did that, I replied to messages for about 5 minutes. Then this happened. Which is why I believe their spam bot mistakenly got my account

    And now, I have told the above to Support and just can't get a reply back from them

  • What is the detailed message in Threema?
    It really say something like "your account is blocked"?

    There is no detailed message. I just know it is, because few months back I used another one of Threema provided features, the Distribution List (DL), and even though this is a feature provided by Threema bundled into the app, my account got blocked when I sent out my first message in the DL. Had to email Support then, waited 4 days till they replied and advised me my account got marked as spam and they unblocked it. Exact same behavior is happening again. This is incredibly frustrating, because I am a using the features Threema provides, and been incorrectly blocked twice now, though this time I am not getting the courtesy of even a reply after 9 days

    When you send a message to ECHO ECHO (ID ECHOECHO) does the message come back or not?

    Nothing comes back. No it is not an internet issue, etc. I been through all of this the first time it happened a few months back, so I know the steps need to take

    If you send me the ticket number as a PM, I can take a quick look what's going on. No guarantees though. :)

    Guess better then nothing... Thank you

  • I used another one of Threema provided features, the Distribution List (DL), and even though this is a feature provided by Threema bundled into the app, my account got blocked when I sent out my first message in the DL.

    Be very careful who you add to the distribution list. Only add people who have opted in to receive messages from you.

    If you get reported as spam or for content by too many recipients, you're looking for trouble. According to the ToS you're not allowed to send unsolicited messages.

    Using the distribution list feature responsibly will certainly not trigger the spam bot.

  • BTW: In my opinion it's a bad idea to create an account named "Threema_No_Support" after a subjectively perceived short-time-experience.

    I appreciate your feedback and certainly didn’t intend for my username to cause any offense. It was created in haste while focusing on solving a technical issue, hardly a statement of any kind. I’m surprised something so trivial could be taken personally, especially in a context where the name itself is simply a reflection of the problem at hand.

    That said, I apologize if it upset you. It was never my intention, and I’ll keep your perspective in mind moving forward. Thanks for taking the time out of your day to write the comment

    Using the distribution list feature responsibly will certainly not trigger the spam bot.

    Was a few months back now, but wasn't what was communicated to me by Support, they said their spam bot grabbed it, not that it was reported. And everyone did opt to be added in.

    Also, just as an FYI - as soon as I hit the send button, it froze up within 10 seconds, only half the messages even left the phone, other half didn't. No human is that fast to report.

  • Claus just for some clarity for both of us my friend, below was DM to me on the previous issue, but I still don't know why it happened on the current issue with Threema Desktop sync issue

    Just so you know, you're not being reported by anyone, you're being auto-blocked by the system because you're sending a lot of messages at once to a lot of recipients.

    Einmal editiert, zuletzt von Threema_No_Support (28. Januar 2026 um 20:09) aus folgendem Grund: More to the point without extra words

  • Hi Skipper

    Appreciate you jumping in but think this is being deralied/off topic. The current issue has nothing to do with the Distribution List. That was 3 months back. And the feature has not been used again after discussing it with Support at the time and matter of fact, that distribution list has been deleted, so I couldn't tell you how many people are in it as it was 3 months ago or whenever that issue happened (again, which is now resolved 3 months ago with Threema Support and is not the current issue, its finished, never been used again and doesn't exist)

    Mentioned previously current issue - the spam bot blocked me while syncing with the Desktop app and it failed, so I went to reconnect it. This should not be against the ToS. This is the current issue trying to resolve.