> For the complete documentation index, see [llms.txt](https://threadly.gitbook.io/threadly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://threadly.gitbook.io/threadly/sending-messages/how-to-send-a-message-with-threadly/message-settings.md).

# Message Settings

Threadly provides several ways for you to personalize your messages. While drafting your message, you can click **Message Settings** beneath the editor to set your preferences.

<figure><img src="/files/pM76Mr6N7TO0oBBzrObe" alt=""><figcaption></figcaption></figure>

### Message Format

By default, messages are sent in a **text > image > action** format. You can change the format:

* Message > Action(s) > Image
* Message > Image > Action(s)

### Link Previews

By default, messages that include links will preview the link, as per [Slack's API guidelines](https://api.slack.com/reference/messaging/link-unfurling).

### Tagline

To ensure account security, messages sent through Threadly using a Bot token will always include an identifying tagline. On our free plan, this tagline indicates the message was sent via Threadly. If you're on our paid plan, this Threadly tagline is removed.

Regardless of your plan, either your name or your workspace's name will always appear at the bottom of your messages. You can manage this preference with this setting.

{% hint style="warning" %}
If you require complete removal of the tagline, please contact our team. We'd be happy to review your request on an individual basis.
{% endhint %}

### Token Type

While most of the customization requires messages to be sent with a Bot token, you can choose to use a User token if you'd like responses to come to you. Learn more about [How Threadly Sends Your Messages](/threadly/faqs/how-threadly-sends-your-messages.md).

<figure><img src="/files/q6GOkATLekAsBmLqJIXM" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://threadly.gitbook.io/threadly/sending-messages/how-to-send-a-message-with-threadly/message-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.