Tell us what is happening, where it is happening, and what you have already tried. The clearer the context, the faster we can isolate the issue and point you toward the right fix.
Tell us exactly where the problem occurs.
What should happen, and what happens instead?
Screenshots, errors, steps to reproduce and environment details help.
The request is reviewed against the product, project and support scope.
Select the closest match. We will carry that context into the support form below.
Choosing the exact product makes it easier to route your ticket and interpret the setup you are describing.
A short ticket is not always a fast ticket. Reproduction steps, exact error text and environment details often remove an entire round of questions.
If temporary access is required, it should be handled through a secure access process rather than plain-text credentials in the ticket.
Support works best when the request stays tied to the Nelx product, custom implementation or agreed project scope.
New features, unrelated custom development, redesign work or substantial scope changes should start as a project enquiry rather than a support ticket.
Go to ContactYour request is captured with product, environment and issue context.
We determine whether it is a product issue, configuration problem, compatibility question or project-specific matter.
We reproduce or inspect the issue using the evidence and environment details provided.
You receive a fix, configuration guidance, workaround, update path or the next information needed.
No. Do not place passwords, private keys or other sensitive credentials in the message. If access is required for investigation, it should be arranged through a safer temporary-access process.
Include the exact steps that trigger it, what you expected to happen, what happened instead, the product version, WordPress/PHP versions and any relevant error message or screenshot.
You can describe a feature idea, but substantial new development or work outside the current product/project scope may need to move to a project enquiry rather than remain a support ticket.
Choose the product most closely involved and explain what changed before the issue appeared. If another plugin, theme or server change might be related, include that detail as well.
Use the Contact page for new builds, redesigns, migrations, optimization work, partnerships and other new project discussions. Support is intended for existing products, systems and active project issues.
A clear ticket helps us spend less time reconstructing the problem and more time addressing it.
Submit a Support Ticket
