Give WordPress AI Engineer a precise problem report so it can investigate the correct website and compare the result with a clear expected outcome. Useful context reduces unnecessary exploratory steps and makes the final verification easier to judge.
IN THIS ARTICLE
01 Collect the essential facts
- The affected page or action, using its exact URL where appropriate.
- What you expected and what actually happened.
- When the issue began and whether it affects everyone or a particular browser or login state.
- Recent changes such as a plugin update, theme edit, migration or new integration.
- The business impact and any workflow that must remain available during investigation.
02 Start the investigation
- Open the intended NabWP service and select the correct website in its WordPress Manager.
- Open AI Engineer and check that you are working on the intended live or staging site.
- Submit the concise problem report and ask for diagnosis before changes.
- Keep Run changes without asking off while reviewing the proposed work.
- Read the findings and supply missing non-sensitive context when the Engineer asks for it.
What does a useful request look like?
For example: “On the staging site, submitting the Contact form shows an error after the latest form-plugin update. The page opens normally and the problem happens while logged out. Please inspect the relevant logs and requests, explain the likely cause, and propose the smallest fix before changing anything.” Replace the example with your real observations.
Should I paste passwords or customer records?
No. The Engineer works through the tools available to the selected service. Provide error messages and relevant identifiers without passwords, API secrets, full payment information or unnecessary personal data. Redact a screenshot or log excerpt before sharing it.
03 Define success before approving a fix
State the test that should pass, such as one successful form submission to an approved test inbox. Ask the Engineer to explain which files or settings would change and what recovery method applies. After the work, repeat the original failing action yourself. A confident explanation is useful, but the real task is complete only when the intended behaviour is verified or the remaining limitation is clearly documented.