> For the complete documentation index, see [llms.txt](https://docs.onlymonster.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onlymonster.ai/members-features/legacy-message-templates-scripts.md).

# Legacy Message Templates/Scripts

<mark style="color:red;">This page describes a legacy Message Templates feature. Support for this functionality will be discontinued soon. Please refer to the new</mark> [<mark style="color:red;">Message Template</mark> ](/members-features/message-templates.md)<mark style="color:red;">documentation for the most up-to-date information.</mark>

<mark style="color:$info;">Create an</mark> <mark style="color:$info;"></mark><mark style="color:$info;">**extensive library of templates**</mark><mark style="color:$info;">, each containing relevant text, media, and pricing options. This allows you to maintain a consistent tone and style in your communications and deliver the right content to your fans</mark>

<mark style="color:$info;">Use</mark> <mark style="color:$info;"></mark><mark style="color:$info;">**Template Tags**</mark> <mark style="color:$info;"></mark><mark style="color:$info;">to quickly and easily locate the templates you need. These tags act as organizational tools, functioning like folders, to help you categorize and manage your template library efficiently.</mark>

<mark style="color:$info;">Incorporate</mark> <mark style="color:$info;"></mark><mark style="color:$info;">**notes within each template**</mark> <mark style="color:$info;"></mark><mark style="color:$info;">to provide clear instructions or guidelines on how to use them. This helps reduce errors and misunderstandings, ensuring that chatters send the right content to fans.</mark>

<mark style="color:$info;">Assign a</mark> <mark style="color:$info;"></mark><mark style="color:$info;">**Sorting Number**</mark> <mark style="color:$info;"></mark><mark style="color:$info;">to each template to control the order in which they appear in your chat with fans. This prioritization system helps you divide media sets into smaller messages/scripts, making them easier to find and use within your workflow.</mark>

<mark style="color:$info;">The Message Templates feature is an essential tool for streamlining your messaging strategy, offering</mark> <mark style="color:$info;"></mark><mark style="color:$info;">**seamless synchronization**</mark> <mark style="color:$info;"></mark><mark style="color:$info;">across all team members with a premium OnlyMonster plan.</mark>

<mark style="color:$info;">This feature facilitates collaboration by allowing team members to share and access templates, fostering a cohesive messaging strategy across your fanbase. Provides flexibility for chatters to adapt and customize templates on the fly, ensuring personalized and relevant content for each fan.</mark>


---

# 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.onlymonster.ai/members-features/legacy-message-templates-scripts.md?ask=<question>&goal=<user_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.