> 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/profiles/overview.md).

# Overview

Threadly Profiles set the sender name and photo recipients see on your channel messages. Send as your brand, a team, or a persona.

Profiles let you customize the sender recipients see, meaning the **name and photo** on your message. Use them to send as *Product Team*, *IT Help Desk* or *Customer Success* instead of as yourself.

Here's an example:

![In this example, recipients see the message as sent by the profile's name and photo.](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/01934168-f217-77b4-b5f5-8ebbf6ca5d71.png)

{% hint style="warning" %}
Profiles work for messages to **channels** and channel Segments. **Direct messages** are always sent as you. Messages sent with a profile post through Threadly's bot, so replies go to Threadly rather than to you.
{% endhint %}

### How to use a profile

In the message editor, on the **Destination & Sender** screen, open **Who is this from?**, choose **Custom profile** and pick one. You can also click **➕ Create New Profile** right there. See [Create a Profile](/threadly/profiles/create-a-profile.md).

### Benefits of profiles

* **Branding:** a consistent, recognizable sender across messages
* **Trust:** people recognize who's messaging them
* **Professionalism:** separate identities for different teams and roles
* **Engagement:** messages feel more personal, so more people respond

### Practical use cases

* Customer support teams sending as a named support persona
* Marketing sending branded announcements
* Sales and CS sending as the account's owner or team
* Different business units keeping their own voice

Learn how recipients can tell who really sent a message in [How Threadly Prevents Impersonation](/threadly/profiles/how-threadly-prevents-impersonation.md).
