# Overview Profiles enable you to customize the sender's identity, including the name and photo that recipients see. By using Profiles effectively, you can tailor your messaging to different audiences or scenarios within Threadly. Here's an example: ![In this example, the user would see that Bill Gates sent the message.](https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/01934168-f217-77b4-b5f5-8ebbf6ca5d71.png) {% hint style="warning" %} Profiles are only available when sending messages to channels or channel-based conversation groups. When sending to a direct message, your profile is used and shown. {% endhint %} ### Benefits of Using Profiles * Branding: Create a consistent, recognizable sender identity across messages * Trust: Use personalized sender names and photos to improve recipient recognition * Professionalism: Represent different departments, teams, or roles with distinct profiles * Engagement: Increase open and response rates by making messages feel more personal * Flexibility: Easily switch between different sender identities for various communication needs ### Practical Use Cases * Customer support teams can use individual representative profiles * Marketing teams can create branded sender identities * Sales teams can personalize outreach with individual team member profiles * Different business units can maintain unique communication styles The core value is transforming generic, impersonal messaging into more targeted, recognizable, and trustworthy communication. --- # Agent Instructions: 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: ``` GET https://threadly.gitbook.io/threadly/profiles/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.