Team Norms and Response Expectations for Slack, Written as a Short Guide
Agree how a team uses Slack so it supports focus.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a one-page Slack guide for [TEAM]. Work patterns and time zones: [WORK_PATTERNS]. Problems we have (noise, urgent messages, long threads, missed requests): [PROBLEMS]. Channels we have: [CHANNELS]. Include: what goes where (a table of channel types and purposes), response expectations by channel and urgency (for example urgent via direct message and a call, normal within one working day), how to write a good request (what, by when, who), when to use threads, when to use @channel (rare), status and do-not-disturb habits, handling decisions (post the decision and owner in a channel and pin it), and how to move to a call or document when a thread exceeds ten messages. Add examples of a good and a poor message for each of three situations and an onboarding checklist for new members. Provide a review date and a feedback method. Features such as huddles, pins and notification settings differ by plan; mark them [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.