Aimogen support is built around direct access, clear channels, and fast resolution, not ticket mazes or anonymous systems. If you need help, you’re not funneled through layers. You reach the people who actually know the plugin.
Support is split intentionally between official support, community discussion, and self-service resources, so you can choose the fastest path depending on the issue.
Official Support Channels #
If you need direct, guaranteed support, the primary channel is the marketplace where your license is active.
If you purchased Aimogen on CodeCanyon, official support is handled through the item page on CodeCanyon. This is the correct place for bug reports, technical issues, and license-related questions tied to Envato purchases.
If you migrated or purchased Aimogen through WPBay, support is handled directly via WPBay. This channel is optimized for faster release cycles, update handling, and direct communication.
In both cases, support requests are handled by the plugin author and the CodeRevolution team, not outsourced staff.
What to Include in a Support Request #
To get fast, accurate help, include:
- a clear description of the issue
- what feature you’re using
- what you expected to happen
- what actually happened
- whether it’s reproducible
- relevant screenshots if visual
- Execution Logs and Usage Logs when AI execution is involved
Most delays happen when logs are missing. Logs turn guesswork into answers.
Community & Direct Interaction #
Aimogen has an active user community where discussions are informal, practical, and often faster than formal support for non-critical questions.
The main community space is the CodeRevolution Discord server, where users discuss setups, workflows, prompts, and real-world use cases. You can also get in touch with the author directly there.
Community channels are ideal for:
- workflow advice
- configuration ideas
- prompt strategy
- feature discussions
- feedback and suggestions
They are not a replacement for official support, but they are often the fastest way to unblock yourself.
Video Tutorials & Walkthroughs #
Aimogen includes a growing library of video tutorials covering features, workflows, and advanced use cases. These are available on the official CodeRevolution YouTube channel and the Aimogen updates playlist on YouTube.
Videos are especially useful for:
- seeing complex features in action
- understanding OmniBlocks
- learning chatbot workflows
- following setup steps visually
- reviewing new features after updates
If a feature feels complex, there’s usually a video that makes it click.
Documentation & Self-Service #
The documentation you’re reading now is the primary self-service resource. It’s designed to answer not just how something works, but why it works that way. Most configuration and behavior questions are covered here in detail.
Before opening a support ticket, it’s often faster to:
- search the documentation
- check the changelog
- review recent updates
- inspect Execution Logs
Many “issues” are configuration misunderstandings that become obvious once the execution flow is clear.
Feature Requests & Roadmap #
If you have ideas or want to influence future development, Aimogen maintains a public ideas and roadmap system where users can vote and comment on upcoming features. This is the correct place for feature requests rather than support tickets.
Feature requests are evaluated based on feasibility, demand, and long-term maintainability.
When Something Is Urgent #
If something is blocking production or affecting a live site:
- use official support, not community chat
- include logs immediately
- describe impact clearly
This helps prioritize the issue correctly.
Best Practices for Getting Help #
Be specific. Attach logs. Avoid assumptions. Mention whether the issue is new or long-standing. State whether automation or scheduled jobs are involved. These details drastically reduce back-and-forth.
Summary #
Getting help with Aimogen is intentionally straightforward. Official support through CodeCanyon or WPBay handles technical and licensing issues. The community offers fast, practical discussion. Video tutorials and documentation cover most workflows. Logs bridge the gap between “something’s wrong” and a real fix.
You’re not dealing with a black box. You’re dealing with a plugin that was built to be explained, supported, and improved in public.
