> ## Documentation Index > Fetch the complete documentation index at: https://docs.trilo.chat/llms.txt > Use this file to discover all available pages before exploring further. # Threads and Replies > Keep conversations organized with threaded discussions Threads help you organize conversations by grouping related messages together. Instead of cluttering the main channel, detailed discussions can happen in their own thread. ## What Are Threads? A thread is a focused conversation attached to a specific message. When a topic needs deeper discussion, moving to a thread keeps the main channel clean while preserving the conversation in context. ### Thread Benefits * **Organization**: Related messages stay together * **Focus**: Discuss one topic without distracting others * **Context**: Thread stays connected to the original message * **Notifications**: Control who gets notified ## Creating a Thread ### Starting a Thread Locate the message you want to discuss further. Hover over the message and click the thread/reply icon. Type your message in the thread view. Press Enter to add your reply to the thread. ### When to Use Threads Use threads for: * Detailed follow-up discussions * Questions that need back-and-forth * Side conversations that branch from main topic * Technical discussions with lots of detail * Feedback and review conversations ## Viewing Threads ### Thread Indicator Messages with threads show: * Reply count ("3 replies") * Participant avatars * "View thread" link ### Opening a Thread Click on: * The "X replies" link * The thread icon * Any part of the thread indicator The thread opens in a side panel. ### Thread Panel The thread view shows: * Original message at the top * All replies below * Message input at the bottom * Option to close and return ## Participating in Threads ### Adding Replies 1. Open the thread 2. Type your message 3. Press Enter to send Your reply is added to the thread conversation. ### Using All Features Thread messages support: * Rich text formatting * File attachments * Reactions * Mentions * Code blocks Everything you can do in the main channel works in threads. ### Following Threads When you participate in a thread, you automatically follow it and receive notifications for new replies. ## Thread Notifications ### Who Gets Notified By default: * Thread participants receive notifications * The original message author is notified * Mentioned users are notified ### Notification Behavior Thread notifications are separate from channel notifications: * You might mute a channel but still get thread notifications * Unfollow specific threads you're no longer interested in ### Managing Thread Notifications To unfollow a thread: 1. Open the thread 2. Click the settings icon 3. Select "Unfollow thread" ## Threads vs. Main Channel ### When to Reply in Channel * Brief acknowledgments ("Thanks!") * Messages relevant to everyone * New topics unrelated to existing messages * Quick reactions ### When to Start a Thread * Detailed responses to a specific message * Questions that might generate discussion * Technical deep-dives * Feedback on specific items * Anything that needs back-and-forth ## Thread Best Practices Each thread should be about one topic. If the conversation shifts, consider starting a new thread or moving to the main channel. If you're responding to something specific, use a thread. Don't clutter the channel with follow-up messages. After a long thread discussion, post a summary in the main channel so everyone knows the outcome. Before starting a new discussion, check if there's an existing thread on the topic. Mention someone in a thread if they specifically need to see it. Not everyone in the channel needs every thread notification. ## Thread Examples ### Question and Answer **Main channel:** ``` Sarah: Has anyone used the new API for authentication? ``` **Thread:** ``` Mike: Yes, I integrated it last week. What do you need to know? Sarah: How do you handle token refresh? Mike: You need to catch the 401 error and call /refresh endpoint... [continued discussion] ``` ### Code Review **Main channel:** ``` Alex: Here's the PR for the login feature #142 ``` **Thread:** ``` Jordan: Line 45 has a potential memory leak Alex: Good catch! I'll fix that Jordan: Also consider using async/await on line 78 Alex: Updated. Can you take another look? Jordan: Looks good now! Approved. ``` ### Decision Making **Main channel:** ``` Project Lead: We need to decide on the database - PostgreSQL or MySQL? ``` **Thread:** ``` Dev 1: PostgreSQL has better JSON support Dev 2: But MySQL might be easier to manage Dev 1: True, but we have complex queries... [vote and decision] Project Lead: Decision: PostgreSQL. Updating the main channel. ``` ## Finding Threads ### Search Threads are included in search results: * Search terms find thread content * Results show thread context * Click to jump to the thread ### Browsing Look for thread indicators: * "X replies" under messages * Participant avatars showing activity * Bold indicators for unread threads ## Thread Permissions ### Creating Threads Anyone who can post in a channel can start threads. ### Replying to Threads If you can see the original message, you can reply in its thread. ### Deleting in Threads * Delete your own thread messages * Admins can delete any thread message * Deleting the original message may affect the thread ## Troubleshooting * Search for keywords from the thread * Look for the original message it was attached to * Check if the original message was deleted * Make sure you're following the thread * Check notification settings * Verify you haven't muted the thread or channel * Try clicking the reply count directly * Refresh the page * Check for browser extensions that might interfere ## Next Steps Take conversations to real-time calls. Learn more about channel communication.