Verified purchaser
Technical clarification update & professional support follow-up.
During testing for my support flow, the backend constantly generated delivery errors (Error 463 / missing tctoken). This indicates that their system's Web wrapper connection completely lost its secure handshake with Meta's servers. My dashboard falsely displayed green checkmarks for sent messages, but the test devices received absolutely nothing.
When I contacted support, the technician (Sohaib) completely misread the backend logs. He falsely claimed that my "recipients reported and blocked me," and instructed me to "appeal via WhatsApp Business." However, all test numbers are my own physical devices (I never blocked myself), and my account is a standard personal account, NOT a business account.
My physical phone sends and receives messages perfectly fine. The connection failure occurs entirely on DM Champ's local sync database. Instead of fixing their wrapper disconnect bugs, they fabricated client reports to shift the blame. Extremely unprofessional service. Avoid this platform.
Update: The founder reached out, provided the detailed backend delivery logs, and clarified the technical misunderstanding regarding the wrapper sync parameters. I appreciate the active support and the follow-up to resolve the communication mix-up. Moving forward with a more balanced view.
sohaib.dmchamp
Edited Jul 19, 2026Hey, thanks for taking the time to write this up. Having read our whole exchange back, I honestly think most of what happened here is a misunderstanding between us, made worse by a language barrier, and I want to clear it up properly. If anything below is unclear, tell me and I will gladly rephrase it more simply.
Let me start with what I got wrong, because some of the confusion started with me. I told you to appeal through WhatsApp Business support without checking your account type. You are on a personal account, and you were right to call that out. I also said earlier that you were messaging people who had never contacted you first. When I re-checked your account records, that was wrong too: your conversations were started by people messaging you, and your bot was replying. Both of those are on me, and I am sorry for the confusion they caused. I understand why, after those two mistakes, it felt like we were not really looking at your problem.
Now let me clear up the misunderstandings on the other side, because I think each point in this review has a simpler explanation than it seems.
The error behind your failed messages is 463, and it comes from WhatsApp, not from us. Your account has exactly 20 failed messages in its entire history, all on July 19. Everything before that was delivered and marked read, and read receipts come from the receiving handset, so your devices were receiving and opening your messages right up until that day. In that same window we had hundreds of numbers connected and sending normally across multiple servers, and every single instance of that error on our infrastructure belonged to your number. That pattern cannot come from a fault in our system, because a system fault would hit other accounts too. It means WhatsApp placed a restriction on your number. And this is also the answer to the thing that I think convinced you we were wrong: your phone still works fine in the official app. That is exactly how WhatsApp restrictions behave. They limit automated sending first and hardest, while normal typing from the phone keeps working. What looked like proof that your number is healthy is actually the signature of a number under restriction.
Why did WhatsApp do it? Honestly, only they know for certain. Automated sending from a personal account is the most fragile setup WhatsApp tolerates, and their systems react to message content and to how recipients respond. If someone blocks or reports a number, delivery to them stops permanently and it counts against the number. None of that requires you to have done anything wrong on purpose. If WhatsApp matters for your revenue, the sturdy path is WhatsApp Business API with opted in recipients, which we support, and I will happily help you move over to it.
One fair point in your review that I will own and fix. Our dashboard marks a message as sent the moment WhatsApp accepts it, and a rejection can arrive a moment later, so for a short window the UI can show success for a message that is about to fail. That is what showed you green checkmarks for messages your devices never got, and I understand exactly why that read as us lying to you. It was not, but it is misleading, and we are changing it so the status stays pending until WhatsApp confirms delivery. Thank you for surfacing it.
So to sum up: two mistakes by me in support, one confusing status display by us, one restriction by WhatsApp that looks invisible from your phone, and a language barrier on top of all of it. I get why it added up to the review above. But none of it is instability in our platform, and none of it was us blaming you to dodge a bug.
We have email support at [email protected], a help center at help.dmchamp.com, and an active Skool community at skool.com/dm-champions where I answer most days. Write to me directly and I will personally help you get set up in a way that will not get your number restricted again. In whatever language is easiest, we will manage. The offer stands regardless of the rating.
Sohaib, DM Champ