1. Check the guide
Installation, activation, configuration and workflow documentation answer the most common questions.
Explore section ↓CUSTOMER SUPPORT
Start with the relevant guide or release note. If the issue remains, send the context our support team needs to reproduce it.
Installation, activation, configuration and workflow documentation answer the most common questions.
Explore section ↓Confirm the installed product version and review recent fixes or compatibility changes.
Explore section ↓Include the product, version, WordPress and PHP versions, expected result and exact error behaviour.
Explore section ↓SEARCH THE SUPPORT CENTER
POPULAR HELP TOPICS
Download the correct product from My Products, upload it in WordPress, activate the plugin and use the licence shown beside that product.
Open My account ↗My Products shows production, staging and development usage, active domains and the last licence check. Copy your key or deactivate an old website there—without exposing a full key in a public form.
Manage licence and websites ↗Use your own supported provider account. Save keys server-side, choose the model and test the connection before enabling customer-facing or automatic workflows.
Connection guides ↗Confirm WordPress, PHP and WooCommerce requirements on the product page, then read the release note before updating.
View releases ↗Copy the exact error, affected job or diagnostic status. Remove API keys and customer data before sharing technical context.
Open troubleshooting FAQ ↓Use the account created for the purchase. Your orders, downloads, product-specific keys and licence usage remain together.
Open My account ↗SUPPORT FAQ
These answers cover the first diagnostic step. Product-specific walkthroughs live as editable Guides so the same knowledge can later ground the support AI.
Sign in to My account and open My Products. Download the ZIP shown under the correct product and licence.
Use the key displayed beside that exact product in My Products. Assistant and Publisher licence keys are not interchangeable.
Confirm the selected provider, saved key, model access, provider billing status and outbound connectivity from WordPress. Never paste a full key into a support message.
Deactivate the licence on the previous website first. If the previous installation is unavailable, use the account or support route documented for activation recovery.
Check that automation is enabled, a future schedule exists, approved work is available and WordPress cron or Action Scheduler is processing jobs.
Publisher keeps work as a draft when the configured review mode or quality threshold requires it. Open the report to see the quality result and warnings.
Confirm the source is published, included in the selected knowledge scope and indexed. Re-index changed content and check diagnostics before testing again.
Sign in, open My Products and select the purchased product. The licence card separates production, staging and development usage and lists active websites with their latest check time.
A public checker could allow key enumeration and disclose customer website information. Licence usage is therefore visible only inside the authenticated account that owns the purchase.
Use the environment selector in the plugin when activating. The account displays environments separately; the exact allowance is governed by the purchased plan and licence service rules.
Open My Products and deactivate the obsolete website from the licence card. If the activation cannot be identified safely, send the order and masked key ending to support—never the complete key.
Make a tested backup, read the matching release note, update from WordPress when offered, then clear site caches and run the product connection or diagnostic check.
No. Every product has its own download, version entitlement and licence key. Always copy the key from the matching product card.
NextlerAI does not include third-party AI usage. You connect your own supported provider account and remain responsible for its access, limits, billing and data-processing terms.
Publish the source change, rebuild or refresh the relevant knowledge index, check the diagnostics and then test with a fresh conversation so cached context does not mask the update.
Open Publisher settings, change the approval or automation mode, save it, and inspect queued jobs. Pause or cancel work carefully because an API request already in progress may finish.
Product and version, WordPress/PHP/WooCommerce versions, reproducible steps, expected result, actual result and the exact safe-to-share error text.
STILL BLOCKED?
Use this only after searching the Support Center. Include reproducible technical context and never include passwords, complete API keys or customer-sensitive data.