> For the complete documentation index, see [llms.txt](https://help.orderdesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orderdesk.com/start-here/getting-started-video-series/how-order-desk-helps-you-video.md).

# How Order Desk Helps You Video

Order Desk is a robust and versatile order management app that will help you organize and optimize your ecommerce business. This series of demo videos explains what Order Desk does and shows how you can begin to use and customize it to fit your business workflow.

If what you’re looking to do with Order Desk isn’t covered in this demo video series, chances are good that it’s still possible—the customized nature of the app makes the possibilities absolutely infinite.

As you watch these videos, keep notes about any questions you have that may not be answered here. Email your questions to our support team and we can help you decide if Order Desk is right for your business.

{% embed url="<https://player.vimeo.com/video/601795734?dnt=1&amp;app_id=122963>" %}

<a href="/start-here/getting-started-video-series/integrations-video.md" class="button secondary" data-icon="arrow-right">Next video</a>


---

# 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.orderdesk.com/start-here/getting-started-video-series/how-order-desk-helps-you-video.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.
