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

# Talk to Us

Find out how to contact Nalpeiron for product support, feedback, billing inquiries, or to set up a 1:1 discussion with your account manager.

We'd love to hear from you! Here's how to contact us for assistance, feedback, and other topics!

### Get Support <a href="#get-support" id="get-support"></a>

To get support, follow the **Help** menu in the product, where you can raise a **Support Ticket**.

### Product Feedback <a href="#providing-feedback" id="providing-feedback"></a>

We would love to hear your feedback on our products. It helps us improve them.

Please go [here](https://feedback.nalpeiron.com/) to share your ideas, bug fixes, requests for new features, docs improvements, and anything else that can help us improve our platform.

Thanks for helping make The Nalpeiron Growth Platform better for everyone!

<https://feedback.nalpeiron.com/>

### Billing

For billing inquiries, please get in touch with our accounts department at <accounts@nalpeiron.com>

### Anything else

Let's jump on a call and discuss how we can help. Contact your account manager today.

[Set up a 1:1 discussion](https://nalpeiron.com/book-a-meeting)


---

# 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.nalpeiron.com/about-nalpeiron/talk-to-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.