> For the complete documentation index, see [llms.txt](https://faq.growsensor.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.growsensor.co/customer-support/what-support-does-grow-sensor-offer-for-professional-growers.md).

# What support does Grow Sensor offer for professional growers?

Grow Sensor provides comprehensive support tailored to professional growers, including access to a detailed online FAQ hub, [blog resources](https://www.growsensor.co/blog), and direct email support via <support@growsensor.co>.

You can also receive ongoing product updates and best practices via our newsletter.

For advanced needs, Grow Sensor offers one-to-one support for environment-based challenges, optional annual calibration services, on-site installation, and custom API integrations for unique setups.&#x20;

Whether you need help optimising a large-scale grow or have specific technical requests, our team is here to assist.

Got a question? Reach out—we’re happy to help!

<br>

<br>


---

# 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://faq.growsensor.co/customer-support/what-support-does-grow-sensor-offer-for-professional-growers.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.
