> For the complete documentation index, see [llms.txt](https://help.slidespilot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.slidespilot.com/general/contact-us.md).

# Contact Us

If you have questions about SlidesPilot, you'll likely find answers to most of them in this help center. Searching for solutions here is often much faster than contacting us.

* To manage or cancel your subscription, please visit the [Manage Subscription page](/plans-and-billing/manage-subscription.md).
* Please visit our [Refund Policy page](/plans-and-billing/refund-policy.md) for information about requesting refunds before contacting us.

### Contact Us for Help

If you need additional assistance, you can contact us at <help@slidespilot.com>.

Due to high volume of requests and time zone differences, our response time may be 2-3 working days.

{% hint style="warning" %}
Before contacting us, please ensure you're using the same email address you registered with SlidesPilot, or inform us which email address you're using with SlidesPilot.&#x20;

**Please verify your email address before contacting us.**
{% endhint %}

### Looking for Collaboration Opportunities

We welcome meaningful connections and collaboration opportunities. If you'd like to have a conversation, you can connect with us through [LinkedIn](https://www.linkedin.com/company/slidespilot/) and [X](https://x.com/stephen_huang).


---

# 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://help.slidespilot.com/general/contact-us.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.
