Supplemental Slack info for you and your team.
Tips and tools for beginners and experts alike.
Slack Enterprise Grid
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.
Getting More Out of Slack
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!
Your Profile and Preferences
Adjust your profile and preferences to make Slack work just for you!
Add Tools to Your Workspace
Simplify your daily work with apps and tools.
Tips, tricks, & More
Tips and tools for beginners and experts alike.
activity, accessibility, add an app, Add members, Add to Slack, administrators, all passwords, analytics, android, announcement, announcements, App Directory, app icon, Apple Watch, archive, Asana, Automation apps, badge, billing details, billing, Bitbucket, bot user, box, browse, calls, Calls !pobeta!pc, changes, channels, channel instantly, channel management, channel notification, claim domains, close, company culture, compliance exports, compose, computers, connect, connected accounts, connecting, copy messages, create, customization, customize, custom SAML, custom, customer support teams, data exports, data security, deactivate, default channels, delete, deletion, deploy slack, desktop, direct messages, directory, disable, discover and join, display name, DMs, Do Not Disturb, domain, domains, dropbox, edit, editing, education, email address, email, emoji, emoticons, Enterprise Grid, Enterprise Mobility Management, executives, export, failed payments, Fair Billing, faqs, finding, format, formatting, free trials, general, getting started, giphy, github integration, github organization, github, glossary, google apps, google calendar, google drive, guests, highlights, human resources, import, Incoming WebHooks, integrations, ios, invite, IT teams, JIRA, join, Keep up, keyboard layout, keyboard shortcuts, Keychain Access, keyword notifications, language, languages, leave, loading, limits, links, linux, mac, manage a workspace, manage apps, manage members, marketing, mention, merge, message display, microsoft products, mobile, mobile push, move channels, moving workspaces, multiple, mute, name, names, noise, nonprofits, OneDrive, onboard, owners, password, permissions, phones, pin, plan, plans, plus plan, polls, primary ownership, privacy policies, prioritize tasks, private channel, private notes and files, project management, public channel, purpose, Quick Switcher, quote, reactivate, read, recruitment, referrer information, reminder, remove, rename, retention, Request a new workspace, role, roles, RSS, sales, Salesforce, SAML, SCIM, SCIM provisioning, screen reader, search, send, session duration, share messages, share, shared channel, shared channels, sign in, sign out, signup mode, single sign-on, Slack Day, Slack for Teams, Slack notifications, Save notes and files, Service Level Agreements, slack status, slackbot, slash commands, snippet, snooze, software developers, star, statistics, sync, tablets, tax, threads, time zone, tips, to-do lists, topic, triage channels, Terms of Service, Trello, troubleshoot, trouble receiving, tour, twitter, two-factor authentication, unread messages, updates, upgrade, upload, username, user groups, URL, Vendor and remittance, video, voice call, voice, what is, what's important, whitelisting, windows phone, windows, working in, workspace creation requests, workspace discovery, workspace's settings, wunderlist, zoom
Rory – Engineer
Rory is responsible for building and maintaining the codebase for the company’s Android app. Six months ago,
his team adopted Slack. Explore below to see how it changed the way they work.
🔍 Finding answers
Support reps at MoneyMe regularly need engineering help to diagnose and fix customer issues.
Before Slack, : when a support rep would receive a complaint about the app, they would
Ping whatever engineer was online and hope they were familiar with the code.
Provide the customer a response to the best of their knowledge without engineering input.
Often, something that could have been fixed easily would go unresolved, resulting in a negative experience for MoneyMe’s customers.
📂 Next up: Click the 'After Slack' tab
Using Slack, : Rory's team is able to centralize bug reports from MoneyMe’s users, resulting in faster, more accurate responses
They have a rule to
search first before asking a question in Slack. They have a
public channel called #triage-android, where reps can raise customer problems.
When an engineer is looking at a problem, they emoji react with 👀 , to let the rep know they're looking into it, and a ✅ when resolved. Team members use
mentions to call attention to subject-matter experts.
🎉 You're done! Move onto the next workflow.
👥 Reducing time in meetings
Rory's team works in two week sprints, and they need to stay aligned each day.
Before Slack, : the team held a daily standup to touch base; however, Rory found these meetings tended to drag on and eat into his team’s productivity
The team was remote and it was hard to find a time that worked for everyone.
Team members would have their heads buried in their phones when others were speaking.
Rory needed a way to keep everyone on the same page, without burdening colleagues who live in different timezones.
Using Slack, : Rory's team is able to provide their update at the beginning of their day, and are able to focus more time on writing code
For daily standups, the team has a weekly
that triggers every day at 9am. Slackbot reminder When it's necessary to meet in person, the meeting lead shares an agenda as an
editable Post in the #android-team channel ahead of time.
🎯 Getting feedback
Rory's team works closely with Design, and they often need to ask designers for clarification about desired behavior.
Before Slack, : when one of Rory's engineers needed clarification, they could
Send them an email with their question.
Try to find them and have an in person discussion.
Because conversations lived in silos, it would be extremely challenging to gain context if the project had to be passed off to a new engineer.
Using Slack, . Rory's team is able to work cross-functionally with ease, while keeping everyone in the loop
They have a
called #design-eng where the teams can public channel quickly ask questions of each other.
When engineering poses a question, a designer to the requests, to let emoji reacts to let them know they’re looking at it.
Back and forth conversation happens in threads, keeping things organized and easily to reference.
📰 Keeping informed
Service interruptions to the tools Rory's team relies on can be a huge disruption; it’s important that his team can plan around them.
Before Slack, service interruptions seemed to get buried in the mix of daily communication at MoneyMe. They were sent:
Via an email sent to a large distribution list.
Through updates to the service status site on MoneyMe’s intranet.
Rory's team would often miss updates surrounding service disruptions, and thus get hit with them at inopportune times.
Using Slack, : service updates are clearly communicated and targeted to the right audience
Each department has an
for important updates, with a strict #announcements channel reactions only policy. Service alerts are
to the channel for easy reference, and then unpinned when complete. pinned
🙇 Centralizing information
Rory likes to know what his team is up to in case they need support, but doesn’t want to add any friction to their workflow.
Before Slack, : in order to get a handle on the work his team was doing, Rory had a couple of options
He could jump around in the different tools his team uses, and check on the status of different projects.
He could ask the team to provide regular status reports.
Rory lost a great deal of productivity because of all the context switching he was doing between tools.
Using Slack, : Rory's team feeds all status updates directly into Slack
The team has a dedicated channel to track commits, pull requests, issues, and deploys, with they set up using the . Slack App Directory
🏆 Get Certified
Get Certified! The next step is to get certified through an interactive experience in Slack. . Click here to begin