# How to Find Your Brand Voice Your **communication style** is more than just a tone of voice — it’s an essential part of your **brand identity**. Some creators prefer a strict and professional tone, while others choose a warm and friendly approach. The key is consistency and respect for your audience, so every post sounds confident and recognizable.

#### 😄 Add Emotion and Humor (But Keep It On-Brand) Genuine emotions and light irony make your texts feel alive. A touch of humor or a well-placed emoji can break the ice, but make sure it matches your brand personality and doesn’t distract from the main idea. #### 🗣️ Write the Way You Speak Imagine having a coffee with a subscriber and telling them about your work. This **conversational writing style** feels authentic and natural: * Avoid complex terms and heavy constructions. * Use vivid words and short sentences. * Let your personality and tone shine through. #### Experiment to Find Your Perfect Balance 🔄 Mix different tones depending on your topic, but never lose your **authentic voice**: * **Formal + Sincere + Responsible** — great for educational and expert content. * **Informal + Humorous + Energetic** — perfect for inspiration and light content. Stay authentic, follow your chosen communication style, and adapt your tone to the context. This way, your audience will remember you as either a trusted expert or a passionate creator they want to connect with on [Polee.me](https://polee.me). --- # 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://polee.me/help/en/blog/how-to-find-your-brand-voice.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.