> For the complete documentation index, see [llms.txt](https://docs.skyledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyledge.com/knowledge-base/articles/how-to-submit-an-awesome-ticket.md).
# How to submit an awesome ticket
Please submit only one issue per ticket for effective resolution.
To Access Sky Ledge Ticket Submission:
1. [Sign in to the Sky Ledge platform](https://platform.skyledge.com).
2. At the top of the screen, click **Help**.
3. Within the Help & Learning modal, click on "Contact Support"
4. Select your request type (Support or Information request) from the dropdown menu
5. Complete the request form as applicable.
6. Click **Send**.
**CRITICAL INFORMATION TO ADD TO YOUR TICKET:**
* **Subject Line**: Provide a clear, brief, summary in your subject line.
* **Ticket Description**: Provide a detailed description of the issue including when it started, which users are affected, and wherein the product it is occurring.
* **Troubleshooting Steps**: Outline the troubleshooting steps performed prior to contacting support, and include screenshots or screen recordings if possible.
* **Urency**: Provide the impact level of the challenge you are experiencing.
* **High**: Main services are not functioning, causing mission-critical business operations to be non-operational. No workaround is available.
* **Med**: Issue in the platform, causing impairment. No workaround is available.
* **Low**: Just a small issue, or bug
---
# 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.skyledge.com/knowledge-base/articles/how-to-submit-an-awesome-ticket.md?ask=&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.