Reporting a bug to Wemaxa is a simple, structured process designed to save time and ensure fast resolution. We provide clear channels for submitting issues, whether through a dedicated support portal, email, or your assigned project dashboard. Each submission prompts a response from our team, confirming receipt and setting expectations for when the issue will be addressed.

To help us resolve bugs quickly and accurately, we guide clients through a straightforward reporting format. You’ll be asked to describe the problem, provide the page or feature affected, and include any screenshots or steps to reproduce the issue. This clarity helps our developers pinpoint the cause without delay and start working on a fix right away.

Once a bug is logged, it is prioritized based on severity and impact. Critical issues such as broken functionality or security concerns are handled immediately. Minor visual or usability issues are typically scheduled into the next update cycle. We keep you informed throughout the process, from acknowledgment to resolution, so you’re never left in the dark.

At Wemaxa, we see bug reporting as part of an ongoing partnership. Our goal is to keep your website or app running at its best, and that means making sure you can report issues easily, get fast answers, and see real results without unnecessary back-and-forth.


🐞 How to Report a Bug to Wemaxa

1. Preferred Channels

You can report bugs through any of the following:

  • Email (e.g., support@wemaxa.com or your assigned project email)
  • Support chat (Telegram, WhatsApp, or Slack if part of your plan)
  • Client dashboard (if a project portal is provided)
  • Maintenance request form (for clients on a support plan)

2. What to Include in Your Report

To help us resolve the issue fast, please include:

Required InfoDescription
🔗 URLExact page or feature where the issue occurs
📝 DescriptionWhat happened, what you expected to happen
🖼️ Screenshots/VideosVisuals of the error, console logs, etc. (if possible)
🧪 Steps to ReproduceStep-by-step actions that lead to the bug
🔧 Browser/Device InfoExample: Chrome 124 on Windows 10 or iPhone Safari

3. Response Time

  • Basic Support: Within 72 hours
  • Pro Support: Within 48 hours
  • Enterprise or Critical: Within 24 hours or less

4. What Happens Next

  1. You receive a confirmation.
  2. Our devs replicate and diagnose the bug.
  3. Fix is applied and tested.
  4. You get a final confirmation + optional preventive suggestion.

📌 Need to Track Multiple Bugs?

If you’re working on a long-term or enterprise project, we can provide a shared bug tracker (e.g., Trello, Notion, GitHub Issues) to manage everything transparently.