ClickUp Chat
Setup Toolkit
Channel naming templates, communication norms you can copy-paste, a migration checklist, and the decision framework for Chat vs comments vs email - from ClickUp's #1 Solutions Partner.
Recommended Channel Structure
Core Internal Channels
Use numbered prefixes to control sort order. ClickUp Chat sorts channels alphabetically, so numbers let you pin the most important ones to the top.
External / Client Channels
#[yourcompany]-[clientname] - for example, #zenpilot-acme zenpilot-ppcagency not zenpilot-ppc-agency)
ClientName | ServiceName | Launch Date Project Channels
#proj-[shortname] - for example, #proj-churnbuster Communication Norms Template
Post this as a pinned message in your #01-general channel on day one. Edit to match your team's specific expectations before posting.
Response Times
- Client-facing messages: Acknowledge within 2 hours, resolve within 1 business day
- Internal @mentions: Reply or acknowledge within 1 hour
- General channel messages: Same business day
- Task comments: When you work on the task
@Mention Rules
- @person: When you need their specific input
- @channel / @all: Only for high-priority items requiring everyone's attention
- Directing at someone: @mention at the beginning of your message
- CC-ing someone: @mention at the end of your message
Thread Rules
- Use threads to keep channels clean
- Think of the first message as an email subject line - make it descriptive
- If a thread goes quiet but is unresolved, turn it into a task
- Keep threads on-topic - new topic means new message
Deep Work
- Communicate when you're going heads-down
- Mark it on your calendar
- Get coverage for client channels if needed
- Post in your around/status channel
- Specify when you'll be available again
DMs
- Default to channels for visibility
- Use DMs for: personal check-ins, quick links during calls, private feedback
- "Praise in public, correct in private"
- If you're DMing the same group about the same topic, create a channel
Notification Settings
- Keep notifications on during business hours
- Use Do Not Disturb outside of working hours
- Recommended: Notifications for DMs and @mentions only, mute FYI-only channels
- Consider turning off sounds (keep visual notifications)
Slack-to-ClickUp Chat Migration Checklist
Most teams complete this in 3-4 weeks. The technical work is fast - the harder part is changing habits and deciding which channels to carry over versus sunset.
Setup
- Map your current Slack channels (which ones does the team actually use daily?)
- Create your channel structure in ClickUp Chat (start with core channels only)
- Set channel topics and descriptions
- Post your communication norms as a pinned message in #general
- Run the Slack importer to bring over your message history
- Brief the team: here's why we're switching, here's what to expect
Parallel Run
- All new conversations happen in ClickUp Chat
- Slack stays open for reference
- Migrate your top 3-5 Slack integrations to ClickUp
- Daily check: is the team actually posting in Chat? Follow up if not
- Collect feedback weekly - what's working, what's frustrating?
Integration Migration
- Move remaining integrations from Slack
- Update any Make/Zapier automations that post to Slack
- Test all notification flows end-to-end
The Switch
- Set the cutover date (announce 2 weeks in advance)
- Archive all Slack channels on cutover day
- Update Slack status: "We've moved to ClickUp Chat"
- Keep Slack read-only for 30-60 days for history search
- Cancel Slack subscription after 60 days
Chat vs. Comments vs. Email Decision Guide
The biggest communication problem in ClickUp isn't channel structure - it's knowing which tool to use for which conversation. Use this as your team's default reference.
| If the conversation is about... | Put it in... |
|---|---|
| A specific task or deliverable | Task comments |
| A quick question for the team | ClickUp Chat |
| A project update for stakeholders | ClickUp Chat channel |
| Feedback on someone's work | Task comments (or DM if sensitive) |
| An external client communication | Email (or shared Chat channel) |
| Something contractual or legal | |
| A team announcement | ClickUp Chat #general |
| Social / fun stuff | ClickUp Chat #random |
The rule of thumb: if a conversation is directly tied to a piece of work, it belongs in the task. If it's team communication that's not task-specific, it belongs in Chat. Email is for external communication and anything that needs a paper trail.
Want help implementing this?
We've helped 3,100+ clients design their ClickUp workspace from the ground up - channel structure, communication norms, and all.