
Unthread
Slack inbox for customer support teams
Slack is a great way to communicate in real-time. As more companies adopt Slack, it has become an even better way to communicate cross-company in a way that's faster and more flexible than email. We do all of our support via shared Slack channels (using Slack Connect), and we'll walk through why we do it.
β± Faster response times
People are >60% more likely to respond and respond >80% faster to messages that come into Slack when compared to email. For a full report on responsiveness of Slack vs. email, subscribe above to get access to our publication.
π€ Dynamic messages and improved collaboration
While emails are inherently static, Slack messages can be dynamic and update in real-time. You can easily upload a file, share a code snippet, and start a video call all from a single message. This is even more powerful when you integrations like Dropbox, Zoom, Figma, and more that let you share content directly without downloading & reuploading files.
π Improved security
Slack reduces the risk of phishing and other cyber attacks by verifying the sender and receiver of each message. Emails can be subject to spoofing and put you at risk of sharing confidential information with a hacker.
π€ Automation
Slack has a rich ecosystem of over 2,000 apps & integrations that add new automations to your conversations. For example, you can find apps that automatically create support tickets when new messages are created in a shared Slack channel and assign them to team members.
Some best practices for using Slack for support:
Keep it casual
There's no need for a "Dear so-and-so", or "To whom it may concern" when talking to customers in Slack. Slack is a chat interface, and you should be talking to customers in a chatting context (though still keep it professional!)
Get to the point
People can sometimes be juggling hundreds of Slack channels at a given time, and it's important that they can easily navigate through the noise. Keep your messages poignant with the most important content in your first sentence.
Respond quickly
Slack can be a double-edged sword. While you'll see higher engagement from customers, there is also a higher expectation of quick response times. To prevent messages from getting lost, implement Service Level Agreements (or SLAs) that guarantee response times, and stick to them. The best way to stick to these is to use an app like Unthread for assigning messages and alerting if you take too long to provide customer responses.
βββ
Conclusion
Slack is a great new way to reach customers in real-time on the app that they use most often. Once you have the right tools and processes in place, your Slack support can become a competitive advantage that keeps customers happier and keeps them for longer.
Most of us have read Paul Graham's "How to get startup ideas" post (and if you haven't, it's here: http://paulgraham.com/startupideas.html). In it, he says: "The place to start looking for ideas is things you need. There must be things you need."
My cofounder and I were originally running a SaaS company called Everyspace, an internal communication platform for companies to host events and build community for their employees.
We set up the typical customer support stack β an Intercom widget for in-app chat and a Google Group for support emails. The problem was that customers kept circumventing these tools and adding us to Slack channels where they would submit support tickets.
Quickly this became overwhelming with dozens of Slack channels pinging us with different issues with no way to keep track.
A few issues that we noticed:
β’ Slack threads did not have an assigned owner. There was a diffusion of responsibility and it wasn't clear who would response
β’ Slack threads can't be "closed". It was difficult to track how many open issues there were at a time.
β’ Issues were being forgotten about. Once you read a message, you need to either "mark unread" or set a reminder to be sure you don't forget to go back to it.
We struggled with this even as a tiny company, and wanted to see if other folks had a better solution.
Turns out, they didn't. So we built one.
We ran the idea and a beta product past several other startup founders and saw immediate adoption and incredible feedback on how the product was saving them time and improving customer relationships.
Today, we do all of our support over Slack with our own product, and we're happy customers!
1 Like
Comment
About
My cofounder and I were running a previous SaaS company, and customers wanted to add us to shared Slack channels to submit bug reports. We found this difficult to scale and built a tool to do customer support from Slack.

9 Comments
Sharing really helps, I'll be thinking about using Slack for creating feedback groups or delivering important information to specific customers.
I'm using Crisp to talk to customers on the Shopify platform with the Fordeer: Invoice Order Printer product. A pretty decent business tool with the features needed when it comes to solving customer support team issues.
Thank you for a valuable share.
Awesome, let me know how it goes!
Crisp is a chat application that integrates many sub-applications inside. If I had to introduce, it would be a lot, I will talk about Crisp who helped Fordeer application and customer care work on Shopify as follows:
Those are some of the key features from Crisp that we're using for support. Find out more at Google if you need more information,
In the near future, when our Fordeer product completes the big update, please use it and give us your comments.
Thank
Product Link: https://apps.shopify.com/fordeer-data-export?st_source=autocomplete
This is really useful input. I've used private slack channels (via slack connect) for enterprise clients and consulting engagements. This works really well as long as the client/customer is already using Slack (which many are). If they aren't using Slack, it can be more difficult, because you are trying to onboard them into two things at once. However, the engagement and value add when clients/customers are already slack users is amazing!
I think Discord also provides a pretty good case for communication. It can help solve a lot of problems
This is a great idea. How do customers interface with Slack? Do you have to invite them into a channel, is there a front end you embed on your site... I'm curious to learn how you do it.
We invite them to a channel via Slack Connect. We wrote up a blog post on this too (link) but we add their email address from Slack which sends them an invitation, and then we welcome them in the channel and recommend that they communicate with us in there
Awesome. Thanks the extra link @bachonk
I use Discord a lot more because of the lack of limits around messages/timing, and also being able to identify roles of who is staff, who is an active community member, etc!
This comment was deleted 4 years ago