> For the complete documentation index, see [llms.txt](https://docs.actirise.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.actirise.com/wordpress-plugin/getting-help/support.md).

# Support

## **Before contacting support**

To ensure a smooth and efficient resolution, please check the following before reaching out to our support team:

1. **Update your plugin** – Many issues are resolved simply by [updating to the latest version](/wordpress-plugin/getting-started/updating-actirise-plugin.md). Please make sure your Actirise WordPress plugin is up to date before troubleshooting further.
2. **Initial setup** – If your issue is related to the initial configuration of the Actirise WordPress plugin, please refer to the [dedicated section](broken://pages/22K7se2cQitLiKkUGnpQ) in our documentation.
3. **Feature configuration** – If you’re experiencing an issue with a specific feature, check its corresponding documentation for setup and troubleshooting guidance.
4. **Known issues** – Your issue might already have been encountered and resolved. Take a look at the [Troubleshooting](broken://pages/VRnl368OFJcz9hLtTofu) section for possible solutions.
5. **Frequently Asked Questions** – Many common questions are already answered in our [FAQ](/wordpress-plugin/getting-help/faq.md) section.

If you’ve gone through these steps and still need assistance, feel free to contact our support team! We’re here to help.

## **Contact support**

If you’ve ensured **your plugin is up to date** and **checked the** [**Before Contacting Support**](/wordpress-plugin/getting-help/support.md#before-contacting-support) **section without finding a solution**, our support team is here to help!

{% hint style="warning" %}
Regardless of the method you choose, please provide as much information as possible. This is mandatory to ensure a quick and effective resolution:

* **Diagnostic information (MANDATORY)** – You **must** enable the `Diagnostic` function in the plugin’s `Settings` tab. If any details appear in the `Diagnostic Information` section, include them in your message. **Please keep the Diagnostic function active until your issue is resolved.**
* **WordPress Site Health Report (MANDATORY)** – In your **WordPress dashboard**, go to `Tools > Site Health`, navigate to the `Info` tab, and click the "`Copy site info to clipboard`" button. Please paste this information into your support request.
* **The issue you are experiencing** – A clear description of the problem.
* **Steps to reproduce the issue** – Detailed instructions on how we can replicate the problem.
* **Relevant technical details** – Such as your browser, operating system, or server environment.

The more details you provide, the faster we can diagnose and resolve your issue!
{% endhint %}

We offer multiple ways to get in touch, depending on the nature of your request. Please choose the most appropriate contact method to ensure a quick and efficient resolution.

* **Contact us via email** at [**support-wp@actirise.com**](mailto:support-wp@actirise.com) – Our team will be notified and will get back to you as soon as possible.
* **Reach out through the** [**WordPress support forum**](https://wordpress.org/support/plugin/actirise/) – Create a new topic so our team can assist you directly (*please note that you need to create a WordPress account first in order to post a new topic).*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.actirise.com/wordpress-plugin/getting-help/support.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.