> 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/request-management/request-and-service-management-email/email-request.md). # Submit requests by email Submit requests to a Siit team by email at its dedicated siit-mail.com address, and reply to the email status updates to add new messages to an existing request Use a unique e-mail address to submit a request for one of your teams Each team that uses Siit has a specific e-mail address that turns all e-mails received there into requests. If you organization is **Acme**, and you want to submit a request, you would use an address **** to submit requests.

### Add more information to your request through e-mail **Ask a question, follow-up, or just let the teams know that they're doing an awesome job!** If you use e-mail as your notification channel you get periodic updates about the status of your request through e-mail. If you want to add information to the request or respond to a mail, you can simply **reply** to one of the updates and the text will be added as a message to the request. --- # 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/request-management/request-and-service-management-email/email-request.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.