> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/getting-started/useful-information/advocacy.md).

# Advocacy

### Your opinion matters to us... shape the future of Highlight

We value your input and want to improve Highlight to make your job easier. Members of the Highlight Advocacy Board:

* Get an early insight into new features
* Help define features during development
* Ensure Highlight does what you need it to do

Users, managers and influencers are all welcome on the Highlight Advocacy Board. Contact us by email or phone to register your interest.

We will contact you for online meetings with our Account Manager and/or a member of the Product team. Your commitment is flexible - approximately one hour per quarter.

### Email

<support@highlight.net>

### Phone

+44 (0)1483 209972


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.highlight.net/getting-started/useful-information/advocacy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
