Support
Get help that keeps store work moving.
Support works best when we can see the exact store context, the workflow you were trying to complete, and the result you expected from OumsAI.
Context firstScreenshots and steps help faster.
Active customersLicense and account checks guide priority.
Store-safe helpWe focus on clear fixes and next actions.
Choose the right support route
Send the issue to the right lane so it can be understood quickly.
Installation help
Use this for plugin upload errors, missing menus, WordPress compatibility issues, or failed setup steps.
License and activation
Use this when a license key is missing, rejected, attached to the wrong domain, or not unlocking updates.
WooCommerce workflow issue
Use this when a product, order, coupon, campaign, or report behaves differently than expected.
AI agent behavior
Use this when the Brain Agent or an app agent gives incomplete, confusing, or unexpected assistance.
Billing and account
Use this for invoices, renewals, plan changes, account access, or payment records.
Security or privacy
Use this for suspected vulnerabilities, data concerns, or sensitive account questions.
What to include in a support request
The more precise the report, the faster support can separate configuration, conflict, and product behavior.
01
Account context
Include the purchase email, order number if available, license key status, and the site URL where the issue happens.
02
Workflow context
Explain the exact task: product cleanup, order review, content drafting, activation, reporting, or another OumsAI workflow.
03
Expected and actual result
Write what you expected to happen, what actually happened, and whether the behavior repeats every time.
04
Evidence
Attach screenshots, browser console errors, WordPress debug logs, or screen recordings when they make the issue easier to reproduce.
How support is prioritized
Critical store-impacting issues need a different response than general usage questions.
We prioritize issues that block activation, break core plugin behavior, affect checkout or order operations, or create a security or privacy concern.
General setup questions, workflow guidance, and feature requests are still important, but they are easier to resolve when they arrive with clear context and a focused example.
Highest priority
Activation failures, security concerns, site errors, and issues that block essential WooCommerce workflows.
Standard priority
Configuration questions, workflow guidance, module behavior, and account support.
Product feedback
Feature requests, interface suggestions, and ideas for improving OumsAI operating workflows.
Self checks before opening a ticket
These checks often solve the issue or make the support request much stronger.
Update safely
Check WordPress, WooCommerce, OumsAI, and relevant plugins on staging before pushing production changes.
Test plugin conflicts
If an issue appears after a new plugin or theme change, note the timing and test with only essential plugins where possible.
Confirm permissions
Make sure the WordPress user has the admin or manager permissions needed for the workflow.
Review the docs
The documentation page covers activation, modules, workflow design, and troubleshooting paths.
Capture the state
Screenshots of settings, errors, and the exact screen are more useful than a general description.
Avoid public sensitive data
Do not paste passwords, full payment details, API keys, or private customer data into a general request.
Open support
Send the smallest complete report.
A focused report with the site URL, license email, steps to reproduce, and screenshots gives support the clearest path to help.