Support
How to get help with AI Product Tools, and what to include so the first reply can actually solve it.
Most problems are already answered on this site: check Troubleshooting for the exact message you are seeing, and the FAQ for plan, data, and compatibility questions, before reaching out. If neither covers it, here is how to contact the team directly, and what to include.
Contact
- Email: dogu@aiforwoo.com
- Website: aiforwoo.com
- From inside WordPress: AI Product Tools → Contact Us opens a secure ticket form for licensed accounts; email reaches the same team and works whether or not you have an active license.
Feature requests and bug reports
Both go to the same address. For a feature request, a short description of what you are trying to do (not just the feature itself) helps. For a bug, use the checklist below.
What to include
A report with this information can usually be answered in the first reply, without a back-and-forth to gather basics:
Your versions
- Plugin version: Plugins screen, or AI Product Tools → AI Toolkit.
- WordPress version: Dashboard → At a Glance, or WooCommerce → Status → System status.
- WooCommerce and PHP version: also on that same System status report.
The exact error message
Copy the full text, not a paraphrase. The plugin's messages are specific on purpose (see Provider errors for the full list), and the exact wording usually identifies the cause immediately.
Which AI provider and feature
Which provider (OpenAI, Google Gemini, Anthropic Claude, or OpenRouter) and whether the key is stored locally or managed through WordPress AI Connectors, plus which screen or feature you were using (a specific generator, the Product Editor, Automation, the AI Shop Assistant).
Steps to reproduce
What you clicked, in order, and what you expected versus what actually happened. If it only happens on one product or one content structure, say which one.
For a developer-level diagnosis
If you can reach your site's admin area, GET /wp-json/aipt/v1/diag (while logged in as an administrator) reports, per provider, whether a key is configured and the last recorded failure, plus a same-site connectivity check useful for spotting a firewall or security plugin blocking the plugin's own requests. Pasting its output into a support email can skip a round of back-and-forth for a connection problem.
What happens next
A report with the information above goes straight to someone who can act on it. The team does not publish a fixed response-time guarantee; if a ticket needs more detail, the reply will ask for exactly what is missing.