Not currently email is the one channel we can staff properly as a small team, and honestly, it's also the better fit for what we do. A written description of a bug with a screenshot beats a rushed phone call every time. If the site grows to the point where chat makes sense, it'll be announced on this page first.

Three things: which tool you were using, what you did (the value you entered or the file you uploaded), and what happened versus what you expected. Your browser and device help too "Chrome on Android" is enough. With that, most bugs are reproducible on our end in minutes; without it, we're guessing.

You can ask, but here's the honest limitation: because our tools process files locally on your device, we never see your images or values so we can't look up "that file you converted yesterday". We can absolutely help you redo it or troubleshoot the steps, though. This is the trade-off of the privacy model, and we think it's the right one.

No. Everything on Okemall is written by the team that builds the tools, and that won't change our guides carry our name and our standards. If you're a publisher or researcher who found a factual issue in a guide, though, that's a different email and always welcome.

First, check your spam or promotions folder replies from small independent sites end up there more than they should. If it's genuinely not there, send a follow-up with "Follow-up" in the subject and we'll get to it. It's almost never intentional; it's a small inbox doing its best.