> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/commercial-lending/help/feedback.md).

# Give feedback on a page

Tell the docs team whether a page helped you, and add details so it can be improved.

Every page has a feedback form. Use it to tell us whether the page helped you, and what was missing or unclear.

## Location

The feedback form is on the right side of every page, below **On this page**. It starts with the question **Was this helpful?**

## Give feedback

{% stepper %}
{% step %}

### Choose a reaction

Under **Was this helpful?**, select the reaction that matches your experience.

| Reaction      | Meaning     |
| ------------- | ----------- |
| Smiling face  | Yes, it was |
| Neutral face  | Not sure    |
| Frowning face | No          |
| {% endstep %} |             |

{% step %}

### Add details

A comment box opens. In **Anything you'd like to add?**, describe what helped, or what was missing or unclear.
{% endstep %}

{% step %}

### Submit

Select **Submit**.
{% endstep %}
{% endstepper %}

## Feedback use

Feedback goes to the team that maintains these docs. When it shows that a page needs to change, the page is updated.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Help Center</strong></td><td></td><td><a href="/commercial-lending/help.md">Help Center</a></td></tr><tr><td><strong>Troubleshooting</strong></td><td></td><td><a href="/commercial-lending/help/troubleshooting.md">Troubleshooting</a></td></tr><tr><td><strong>FAQs</strong></td><td></td><td><a href="/commercial-lending/help/faqs.md">FAQs</a></td></tr></tbody></table>

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://2424445642-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoNOfYlgbuwiWKkdQsRIp%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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.uptiq.ai/commercial-lending/help/feedback.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.
