Prompt Library

ChatGPT Prompts for Slack (Channels, Etiquette, Workflows)

20 copy-paste prompts

20 copy-paste ChatGPT prompts for Slack: channel architecture, message etiquette, async culture, integrations, and the workflows that prevent Slack from becoming a productivity sink.

Channel Architecture

4 prompts

Channel Structure Design

1/20

Design Slack channel structure for [team / org]. Output: prefix conventions (#proj-, #team-, #help-), naming pattern, public vs private rules, when to spin new channel vs use existing, archive policy. Prevent channel sprawl.

Designs Slack channel structures.

💡

Pro tip: Default Slack = channel sprawl in 3 months. Naming convention + governance = manageable. 50 channels finable; 500 = chaos.

Channel Description Standards

2/20

Standard channel description template. Output: 1-line purpose, when to post here vs elsewhere, owner, related channels, on-topic vs off-topic. Empty descriptions = newcomers lost.

Standardizes channel descriptions.

💡

Pro tip: New member joins channel + sees no description = lurks confused. Description with purpose + posting norms = onboards in 30 sec. Channel-quality lift.

DM vs Channel Decision

3/20

Decision rule: DM vs channel post. Channel = topic-relevant + multiple-people-benefit. DM = ad-hoc + narrow audience. Default: channel. DMs hide knowledge; channels share.

Decides DM vs channel.

💡

Pro tip: DM-heavy culture = knowledge silos. Channel-heavy = team learns. Pattern over months matters more than individual messages.

Private Channel Use Cases

4/20

When private channels appropriate. Examples: HR matters, M&A discussions, deal-sensitive client work, executive coordination. NOT for: "I just don't want X to see." Latter = political channel.

Decides private channel use.

💡

Pro tip: Private channels appropriate for: HR, legal, M&A, executive. Inappropriate: "we don't want them seeing." Latter = toxic political channels. Reset.

Prompts get you started. Tutorials level you up.

A growing library of 300+ hands-on AI tutorials. New tutorials added every week.

Start 7-Day Free Trial

Message Etiquette

4 prompts

Thread vs New Message

5/20

When to use threads vs new messages. Reply to existing topic = thread. New topic = new message. Most reply-alls should be threads. Threading prevents channel chaos.

Decides thread vs new message.

💡

Pro tip: New top-level reply for related convo = breaks thread. Thread reply = keeps related convo together. Default: thread for replies; new top-level for new topic.

@channel vs @here vs @user

6/20

@user = expect that person's attention. @here = active members' attention. @channel = everyone's attention. Calibrate: @user sparingly, @here for time-sensitive, @channel rare.

Calibrates @mentions.

💡

Pro tip: @channel for every post = team ignores. @here for genuinely time-sensitive only. @user for action expected. Mention scarcity preserves urgency.

Message Length Guidelines

7/20

Message length norms. Long doc-like messages = blog post or doc instead. Slack = chat-format messages. If exceeding 3 paragraphs, consider canvas or doc link. Wall-of-text Slack messages ignored.

Builds message length norms.

💡

Pro tip: 3-paragraph Slack message = unread. Canvas / doc link + brief Slack message pointing = read. Format matches medium.

Working Hours Messaging Etiquette

8/20

Off-hours messaging etiquette. Output: schedule send for working hours, urgent vs non-urgent distinction, "no expectation of response" disclaimer, manager modeling. Off-hours pings = burnout culture.

Builds off-hours messaging norms.

💡

Pro tip: Manager pings at 11pm = team feels obligation. "Schedule send for 9am next day" = same content, different signal. Habits compound; manager modeling matters.

Async Culture

4 prompts

Async-First Messaging

9/20

Build async-first culture in Slack. Output: when sync (real-time required) vs async (most things), expected response time (4-24 hrs typical), how to flag urgent, how NOT to flag urgent. Default async = sustainable.

Builds async-first culture.

💡

Pro tip: Sync expectation everywhere = always-on culture = burnout. Async with clear urgency escalation = sustainable + better outcomes (more thoughtful responses).

Status + Profile

10/20

Slack status + profile etiquette. Output: status meanings (in meeting, focusing, OOO), working hours configured, profile completeness, photo norms. Status communication = expectation setting.

Builds Slack status norms.

💡

Pro tip: Always-available status = always-interrupted. Status discipline (focus / meeting / OOO) = expectations clear. Most users leave default; the discipline is the unlock.

Daily Standup via Slack

11/20

Async daily standup in Slack. Output: dedicated channel, format (yesterday / today / blockers), bot vs manual, time-window for posting, response from team. Replaces sync standup for distributed.

Builds async standups.

💡

Pro tip: Sync daily standups across timezones = brutal. Async (write 9am local time, read whenever) = inclusive + asynchronous-respecting. Bot tools (Geekbot, Standuply) automate.

Pull-Based Communication

12/20

Shift from push (DMs, @mentions) to pull (channel posts, canvas docs). Output: when push appropriate (genuinely action-needed), pull benefits (focus protection, search), training team. Pull = mature async.

Shifts to pull-based comm.

💡

Pro tip: Push-heavy = constant interruption. Pull-heavy = focus + intentional engagement. Mature teams shift toward pull. Junior teams default to push.

Like these prompts? There are full tutorials behind them.

Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.

Try AI Academy Free

Integrations + Power Use

4 prompts

Integration Audit

13/20

Audit Slack integrations. Output: connected apps, who installed each, security review (data access), business value vs noise, candidates to remove. Integrations sprawl over time.

Audits Slack integrations.

💡

Pro tip: Old integrations linger forever. Annual audit catches: unused apps, security risks, channel-spam from forgotten bots. Without audit = noise + risk accumulation.

Workflow Builder

14/20

Build Slack Workflow for [process — onboarding new hires, triaging requests, intake forms]. Output: trigger, steps, who handles, completion. No-code automation in Slack.

Builds Slack Workflows.

💡

Pro tip: Workflow Builder (built-in Slack feature) = no-code automation. Most teams ignore. Form-like intakes, auto-replies, scheduled messages = doable. Underused.

Slack Search Mastery

15/20

Master Slack search. Output: from:, in:, has:link/file, before:/after:, modifier syntax, examples for common needs. Slack search powerful but underused.

Masters Slack search.

💡

Pro tip: Slack search syntax (from:bob in:#channel after:2024-01-01) = specific finds. Most users browse-search; operators are speed + specificity.

Reactions as Workflow

16/20

Use emoji reactions as workflow signals. Examples: ✅ acknowledged, 👀 reviewing, ✋ blocked, 🔥 urgent. Output: convention list, when each appropriate. Reactions = lightweight signals.

Uses reactions as workflow.

💡

Pro tip: Reactions > "got it" replies = less noise + same signal. Convention-based reactions = consistent meaning. Most teams react randomly; the convention is the productivity gain.

Channel Health + Maintenance

4 prompts

Channel Audit

17/20

[List my channels]. Audit: active vs dormant, redundant (overlapping purpose), needing renaming, candidates for archiving. Quarterly cleanup = manageable.

Audits Slack channels.

💡

Pro tip: Channels accumulate. Quarterly audit (1 hour) + archive 20% = sustainable. Without audit = 10x channels in 2 years; 90% inactive.

Onboarding to Slack

18/20

New team member onboarding to Slack. Output: which channels to join, etiquette norms, key bot commands, where to find docs, who to DM for what, first-week checklist. Most onboarding skips Slack basics.

Onboards new members to Slack.

💡

Pro tip: New member dropped into Slack = lost. Channel tour + norms + key channels = productive in week 1. 1-hour onboarding = weeks of saved confusion.

Slack Burnout Detection

19/20

Detect Slack-induced burnout signals on team. Patterns: constant DMs, off-hours activity, stress reactions in messages, increasing escalations. Behavioral signals matter.

Detects Slack burnout.

💡

Pro tip: Slack overuse = real burnout driver. Pattern recognition (manager noticing always-on team members) = intervention point. Without active management = silent burnout.

Slack Detox Strategy

20/20

Help team reduce Slack overload. Output: notification tuning, status discipline, async-first norms, focus blocks, no-Slack times. Personal + team practices.

Plans Slack detox.

💡

Pro tip: Slack-as-day = no deep work. Detox practices (notifications off during focus, status = focus, scheduled checks) = reclaimed deep work. Compounds.

Frequently Asked Questions

Slack: better thread UX, app ecosystem, search, simpler. Teams: deeper M365 integration, video first-class, included with M365 (cost-saver). Tech/startups often Slack; enterprises often Teams. Both work for most teams.

Notification tuning (mute non-essential channels), status discipline (focus mode), async-first norms, working hours respected, scheduled checks (not constant). Default Slack = burnout fuel.

Channels for: team-relevant, decisions, knowledge that should be findable. DMs for: 1:1 conversations, sensitive matters, ad-hoc casual. Default to channel = team learns.

Use search operators (from:, in:, after:). Channels you're not in = invisible. Some message types (DMs you weren't in) = invisible. Most "missing in search" = scope issue.

Quarterly audit + archive inactive. Naming conventions enforced. Provisioning approval. Cap on channels per team. Without governance = sprawl in 12 months.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial Explore AI for Teams

7-day free trial. Cancel anytime.

Browse All Prompt Collections