> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/getting-started/customer-support.md).

# Customer Support

Dedicated support for all Roadmap clients and partners

Roadmap is run by humans, with the goal of providing human support.

All brands on Roadmap can access direct custom support via the intercom chat within the Roadmap app at the bottom right of their window.

Our New Zealand team is online between 9am-6pm NZT and if there is any urgent support needed, we are available to provide video, phone, and email support.

The Roadmap platform is a partnership business, not a faceless VC SaaS venture where only the top 3% of brands are looked after.

### Strategic Support

Roadmap is run by our strategic ecommerce team with the goal of not just providing technical support, but also strategic support.

Please keep an eye on the change log tab above and the upcoming "Paths" tab that will start to house strategic implementation resources, walkthroughs and strategies.


---

# 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.roadmap.so/getting-started/customer-support.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.
