> 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/message-templates.md).
# Create message templates
Create message templates in Settings, Requests to reuse answers to common questions, personalized with variables like the recipient name and with articles or attachments
Use message templates to write, personalize, and send answers to common questions while keeping your messages personal.
Message templates let you save commonly used templates, snippets, and answers that you don't want our bot to send automatically.
To create and manage message templates, go to **Settings → Requests → Message templates.** You can create a new one using the **+ New** button or edit existing ones by clicking on the list.
Customize each message template to fit your team or organization's needs. This ensures consistent, on-brand messages and saves admins time and effort, allowing them to focus on other important tasks.
### Personalize your message
To make your message more personalized and engaging, you can incorporate variables like the recipient's name or office location. Adding articles or attachments can also make your message more informative and helpful. Personalizing your message and providing value can increase the chances of it resonating and achieving your desired outcomes.
### Using message templates
Find and select a message template when sending replies, internal notes, or approvals directly from the message box.
---
# 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/message-templates.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.
