> For the complete documentation index, see [llms.txt](https://docs.industryapps.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.industryapps.net/onboarding-to-industryapps/onboard-application/configure-application/terms-of-use.md).

# Terms Of Use

Its important to provide basic details in terms of SLA and Consulting / Support rates to your customers. This information will be visible to the customer if they require any additional support from you. Target is to make this process transparent and clear. No additional negotiations.

IndustryApps will be centrally managing support and SLA.&#x20;

A monthly support performance document will be send to customers with details of number of tickets raised and if SLAs were met. Support is critical component for Industrial solutions, <mark style="color:green;">your support performance is a critical factor for sales growth.</mark>&#x20;

{% hint style="info" %}
Contact details are mandatory - Please ensure there a min of two contact person information.&#x20;
{% endhint %}

![](/files/m9gmRaj9evW09xGPDfqP)


---

# 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://docs.industryapps.net/onboarding-to-industryapps/onboard-application/configure-application/terms-of-use.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.
