> 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.md). # Email Send and receive requests by email.


Send emails from Siit	Send Siit emails from your company domain, either with a custom From name and address verified via Postmark or with a fully authenticated domain using DNS records	Send emails from Siit
Forward emails to Siit via Gmail	Find your team Siit email address in Channel settings and set up Gmail forwarding from a shared inbox so incoming emails become Siit requests, including Google verification	Forward Gmail emails to Siit
Submit requests via 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	Submit requests by email

--- # 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.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.