Supplemental Slack info for you and your team.Tips and tools for beginners and experts alike.Get familiar with Slack Enterprise Grid for large organizations.If you're curious about what's new in Slack — and what's changed — you're in the right place.Develop your skills and prepare to become Slack Certified!Launching a new team or joining one for the first time?
Our easy-to-read guides help your team work better, together, from day one.Ready to level up? Browse our time-saving tricks and practical tips for
making Slack work for you.All kinds of teams thrive with Slack — take a look at our department-specific guides.
More coming soon!Learn how Slack works, from top to bottom!Want to learn more about setting up your team? Look no further!Welcome to Slack! We're so glad you're here. Let's get started!Adjust your profile and preferences to make Slack work just for you!Simplify your daily work with apps and tools.Tips and tools for beginners and experts alike.
Slack is experiencing some connectivity issues — please stand by. Check
If your role requires you to prioritize and respond to requests in a timely fashion, you know how tough it is to track issues that pop up unexpectedly. From customer support tickets to billing inquiries, we’ll show you how to use channels to organize incoming tasks efficiently. ✅
Clarify ownership by increasing visibility
Reduce time spent assigning duties and updating external issue trackers
Create a searchable history of past requests and how they were handled
Step 1: Create #triage channels
Create public channels using the #triage- prefix and designate their function. For example, use #triage-billing for questions about invoicing and payments. The prefix signals to everyone that the channel will be used to sort and prioritize incoming messages on that subject. Making the channel public lets your whole workspace see what issues are pending and what’s been resolved.
Step 2: Share guidelines
It’s important to set expectations for how the channel is meant to be used. Create a post that explains how you’d like members to make requests and report issues. Here are a few suggestions for these guidelines:
Indicate priority with emoji. Choose a set of emoji that classify how quickly a message should be addressed.
🔴 :red_circle: emoji means the issue is urgent. 🔵 :blue_circle: emoji denotes a question or problem. ⚪️ :white_circle: emoji shows something is feedback.
Include a brief description. Outline the information members need to include in their request.
Assign and claim tasks with reactions. Select emoji reactions that tell others what’s being worked on and by whom.
👀 :eyes: emoji reaction means "I’m looking at this for you". ✅ :white_check_mark: emoji reaction means "I’ve fixed the issue".
Follow up in threads. Make it clear to whoever is working on the request that they should leave comments in a thread if the issue requires additional input, revision, or approval.
If your triage channel gets a lot of action, developers can build a bot that scans the channel at preset times of day for specific emoji reactions to messages. This will help your team to track any outstanding issues.
You can also connect your triage channel to external tools or dashboards that your team uses to manage incoming requests. For example, you can install Jira server alerts to track issues that arise with your product development team. Or use the Stripe app to view charges, invoice payments, and subscriptions as they roll in.
In some cases, it’s beneficial to assign someone to monitor the channel and keep things running smoothly for a set period of time — a triage captain, if you will. 👩✈️
The triage captain is in charge of making sure all incoming messages get the attention they need. They can also help make tough judgment calls when it comes to prioritizing issues and outsourcing for help. When their shift is over, they can hand over the reins to the next person on duty.
Update the channel topic to let everyone know who’s on duty for the hour, day, week, or month. We recommend rotating your captain on a regular basis to prevent burnout.
Thanks so much for your feedback!
Thanks for your feedback.
If you’d like a member of our support team to respond to you, please send a note to email@example.com.
Oops! We're having trouble. Please try again later!