> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/settings-and-plans/contact-support.md).
# Contact support
How to reach the Samita support team from inside the app or by email.
## Inside the app
* **Live chat**: click the chat bubble in the bottom-right corner of any app page.
* **Contact us** in the app menu opens a form. **Your name**, **Your email**, **Subject** and **Message** are required.
Contact us
The form also asks for a **Collaborator request code**. This is the code from **Shopify admin › Settings › Users › Security › Collaborators**. Sharing it lets our team request collaborator access to your store so we can look at the task with you. Never share your Shopify password; the optional **Password** field is only for a temporary staff account you may have created for us.
## By email
Write to .
## What to include
* The **task ID** (the # number in the Tasks list) and the task name.
* What you expected and what happened, with a screenshot of any error banner.
* If products look wrong, please contact us **before** pressing **Revert now**, so we can inspect the current state.
---
# 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.samita.io/bulk-price-editor-sami/settings-and-plans/contact-support.md?ask=&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.
