# FUN with Slack In this section, we will describe our best practices when using Slack. ## Asynchronicity Slack is used: * for real-time discussion when two or more persons are actively connected at the same time, * to replace emails when sharing information or for asynchronous conversation. When you post a message to someone on Slack, you should not expect them to answer synchronously. In other words, consider your messages like emails: * communicate the whole point before pressing "Enter" and not just "hello are you here?" or "are you available to talk?", * if the person answers straightaway, it means that he or she may be available to chat, but you should not expect it to be the case by default, * give the person some time to answer: at least a few hours, unless the matter is unusually urgent. They can decide how fast they need to answer you, because you have given them the whole information in your message, right? ## Threads We want technical discussions to happen in public channels as much as possible and not in private/group channels: * someone else may have a good idea, * someone else may learn something by reading your discussion. In order to limit the noise for people not directly interested in your topic, switch to a "thread" as soon as you notice that a conversation is initiating. --- # 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://handbook.openfun.fr/slack.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.