Skip to content

Support

Updated View as Markdown

Start with the guide for the feature you are using. If you still need help, choose the support route that fits your question and include enough detail for someone to understand what happened. Keep provider keys, passwords, and private site information out of public posts.

Choose where to ask

What you need Where to go
Help with installation, provider setup, tools, sessions, or Content Studio Check Frequently asked questions and Troubleshooting first.
Ask a product question or report a problem Post in the MazeGraph support forum on WordPress.org. Forum posts are public, so remove private details before submitting.
Report a possible security vulnerability Follow the private reporting instructions on the MazeGraph security page. Do not publish vulnerability details in the support forum.
Export or erase MazeGraph data from your WordPress site Ask your site administrator to follow Export and erase personal data.
Contact MazeWP about privacy information held after you contact us, partnerships, or another site matter Use Contact MazeGraph or read the privacy policy.

Prepare a useful product report

A short, reproducible report is easier to investigate than a broad description such as “the AI is broken.” Say what you were trying to do, what you saw, and what you already checked. If you do not know the cause, say so rather than guessing.

Include the relevant details:

  • What happened? Name the page or feature, describe the steps that led to the issue, say what you expected, and include the exact error message.
  • What was the reason? If you know what caused it, explain why; if not, say what you checked and that the cause is still unknown.
  • What was the solution? List the setting or step you changed, whether it resolved the issue, and any workaround that helped.
  • What was the learning? Say whether the issue affects one person or the whole site, whether it happens every time, and what should be prevented or investigated next.
  • Which versions and connections are involved? Include MazeGraph, WordPress, and PHP versions, plus the provider connector and model if relevant.

For a missing or refused tool, include the tool name and selected assistant. For a draft hand-off issue, include the post type and status, but do not include the draft text. For a provider problem, include the connector and model names, never the key.

Copy installation diagnostics

For technical issues, an administrator can open MazeGraph → Settings → About, then choose Copy diagnostics under Installation diagnostics. The summary includes software versions, AI and provider status, model availability, tool state, selected limits, context strategy, retention, and MCP sharing status. It does not include provider keys or conversation text.

Review the copied summary before sharing it. It still describes settings and connection status for your site. If a screenshot helps, crop it to the relevant control and hide site names, customer information, private content, and other details that do not help explain the issue. The Troubleshooting guide has more steps for collecting details safely.

Keep private information private

Never post provider API keys, WordPress passwords, generated MCP connection passwords, authentication tokens, private customer or user information, or private post content. Do not send a full conversation when a short, redacted example will explain the problem. Support staff do not need your credentials to understand a report.

If you accidentally share a secret, revoke or rotate it in the service that issued it, then remove the public post content if the forum allows it. Contact the site administrator if private WordPress data was exposed.

Learn more

Was this page helpful?

Your feedback helps us improve these docs.

Documentation

Type to search…

↑↓ navigate↵ selectEsc close