> For the complete documentation index, see [llms.txt](https://help.stockcharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stockcharts.com/learning-more/policies-and-limitations/customer-support-policies.md).

# Customer Support Policies

## Expected Response Time <a href="#expected_response_time" id="expected_response_time"></a>

Most customer support requests will be responded to within one business day (often much sooner). If there is a site-wide problem that generates a large volume of requests, we may choose to respond via [our Twitter feed](http://twitter.com/stockcharts), instead of individually.

## Scope of Support <a href="#scope_of_support" id="scope_of_support"></a>

As a website operator, we are limited in the kind of technical problems that we can troubleshoot and provide help with. In general, we are only able to provide support concerning the use of the tools on our website. We are not able to provide direct help for problems that are specific to an individual computer's configuration or Internet connection, although we may be able to provide general guidance on how to narrow down such problems.

Additionally, we are unable to provide financial advice, chart interpretations or indicator recommendations. We are not financial advisers or counselors.

## Abusive Behavior Restrictions <a href="#abusive_behavior_restrictions" id="abusive_behavior_restrictions"></a>

While the vast majority of our customers abide by our policies above, people that consistently violate those policies may be banned from receiving Customer Support replies in the future.


---

# 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://help.stockcharts.com/learning-more/policies-and-limitations/customer-support-policies.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.