> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-communication/slack-request-info.md).
# Add details to a request from Slack
Add information to a request you submitted by replying in the Slack thread Siit starts for it, with Siit confirming each message with a check mark reaction
Ask a question, follow-up, or just let the teams know that they're doing an awesome job!
### Adding a new message to your request
If you use Slack as your default notification channel, once you submit a request Siit will send you a confirmation message with details about your request.
To follow-up on the request you can simply add a message to the thread that Siit automatically starts for each request.
* To open the thread simply click on **1 reply below the message, or use the 💬 icon** that appears when you move your mouse over the message.
* The thread will open on the right side of the screen and you can send your messages there.
* Siit will confirm that your message was received by adding a ✔️ reaction to it.
---
# 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.siit.io/guides/integrations/integrations-communication/slack-request-info.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.
