Slack is a group messaging or team collaboration app that aims to simplify communication for businesses. Features include open discussions, private groups, and direct messaging, as well as deep contextual search and message archiving, and file sharing. Slack integrates with a number of other tools, such as MailChimp, Dropbox, and Google Drive. Slack was acquired by Salesforce in December 2020.
The product is free to use, and also has paid plans with more features and greater controls.
The…
$0
Zenhub
Score 7.3 out of 10
N/A
ZenHub is a project management solution that runs native within GitHub with collaboration boards, file sharing, and pipeline selection.
$0
Pricing
Slack
Zenhub
Editions & Modules
Free
$0
Pro
$7.25*
per month per user
Business+
$12.50*
per month per user
Enterprise
Contact Sales
Free
$0
Growth
$8.33
per month per user
Growth
$8.33
per month per user
Enterprise
Contact us
Enterprise
Contact us
Offerings
Pricing Offerings
Slack
Zenhub
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
*Per active user, per month, when paying once a year.
Pro is $8.75 USD per active user when paying month to month. Business+ is $15.00 USD per active user when paying month to month.
The listed prices are per user, per month when billed annually.
Slack was more of a company directive. Teams has its strengths. But Slack definitely seems more mature in terms of features that engineering teams love. Video conferencing is much better in teams.
I think it stacks. I haven't seen those products in the last few years, but I feel like the way Slack has evolved and how much integration it has with Salesforce. I don't think any of the other tools I've seen do that.
In my opinion, the closest to Slack in terms of UI is Discord. But Slack is much more professional with more functionalities that doesn't require very technical knowledge (good for our older staff who began their digital journey within the last decade). In terms of workflow …
better price and less spam with Slack. It was the best decision to switch to this communication platform for our company. We would do it again if given the opportunity.
Teams has an edge over Slack as teams is also a meeting platform Copilot by teams is very well integrated tot eams making it super easy to use AI without extra steps and additional integrations Teams is also great with long messages / rewording messages and any vocabulary …
The other platforms have valuable features (like progress kanbans and storage for big files) but none of them work on their own. Slack is the central hub that we use for all communications, discussions, and meetings.
Slack excels at versatility and ease-of-use. Everyone knows …
In comparison to Teams, I think Slack is a much nicer platform to use. If your technology department allows you to integrate third party applications, it can work really well paired with zoom, sharepoint etc. I think for many mid sized businesses it can be a good fit to enhance …
Slack is better suited for actual work teams rather than communities, so it wins against Discord. About HipChat - in my opinion, it was a dinosaur that is not discounted, and it's obvious why, considering the type of product Slack delivered!
From a corporate standpoint, I don’t really have another example. On a personal level, the closest comparisons would be WhatsApp, Messenger, or KakaoTalk. To me, it feels like — as I said — the corporate WhatsApp. Not that Salesforce wants it to be compared that way or used …
No, I use many. I use Google Meet, I use teams, I use many others. Again, it's the same, not many things, but if I'm repeating myself, it's all about sharing the information, how quickly it's effective, the quality is good, the huddle is fine, you can share all the, so all the …
Microsoft Teams feels clunky in comparison to Slack. Slack feels more versatile and intuitive, and much more tech minded then Microsoft Teams does. I would say Microsoft Teams may have the advantage if your business is fully with Microsoft (ie the full Office suite), but other …
I've dabbled with Microsoft Teams and Zoom's chat features in past roles at startups. Teams integrates well with Office but feels clunky for quick searches and daily chats. Zoom is great for video but lacks robust file sharing and app integrations.
Slack wins for us with its …
Teams and Slack both have Pros and Cons. We use both for communicating. Microsoft Teams is good from the prospective that you can set up Distribution Groups and Private Groups for sharing out links from One Drive and Sharepoint. The integration is built in so that all the …
Slack holds up fairly well with the others. They all have the same basic features. Where they do differ is the execution. You can tell that for Teams and Discord, they had Slack in mind when they were designing their system. These two would be the closest to Slack, even in …
The applications i have used earlier is not much user friendly, I can not do video calls in groups and tagging system is not available accross the company. Feedback and survey or process updated delivery feature makes Slack different than other companies. Slack is really time …
I like Slack better than ClickUp, because I would spend 30-60 minutes a day updating my ClickUp tasks. The way ClickUp was used was very micromanaging. I billed by the hour, so I was willing to put in the time to alert the boss what tasks I was working on.
Teams is better to schedule meetings with and integrates with Outlook well, but that leads to duplicate notifications for things, which is distracting and a waste of time. Messaging in Teams not great compared to Slack, and has the potential to have people outside your …
Ease of use is a game-changer. Slack works so intuitively. People started collaborating automatically, and digital communities started to appear. We haven't seen that kind of engagement with other tools or workflows. It makes working together fun, and that is something that …
It's just an actual messaging soft ware to use, compard to other that can be underwhelming or just not useful when your company is growing, Slack keep unity and option for communication that caters anyone, depending on what they feel comfortable and with what type or works they …
Slack offers great user interface that is easy to navigate through. Customer support team are very user freindly and helpful. The pricing of Slack is fairly affordable compared to other product. Great integration capabilities with other products and the search feature is …
Zenhub is purpose built for Github users and provides just the tools you need to run Agile sprints without any extra complexity or fluff. Azure is a much more "enterprise" solution in which you drown in all of the available options, very similar story with Jira (pricing is also …
Zenhub partners with Github and it's nice to use both in tandem, ultimately Zenhub has the project management capabilities we were looking for. Additionally Zenhub has a really user-friendly platform that is intuitive and not much training was required for any of the team …
The only other program we tried that had somewhat seamless integration with our GitHub projects is GitKraken's Globoards. Globoards has a long way to go to compete, though it does have a read-only option for boards so it can be displayed corporately as an information radiator …
I have used Workfront in the past, which in my experience, is best with a traditional waterfall methodology, similar to Microsoft Project and the other more traditional project management software projects. ZenHub is truly designed around the agile methodology. Other products …
Way better than competition if you use github because it seamlessly integrates without doing anything. You don't need to duplicate your issues, etc. As long as your devs already use github and github issues this will be a no brainer and simple to implement. With JIRA or Trello …
Slack is ideal for Scrum and agile teams that need continuous communication during sprint planning, daily stand-ups, backlog refinement, testing, and retrospectives. Slack is well-suited for maintaining team knowledge through searchable conversations and dedicated channels, where experienced team members help onboard new QA analysts.
Zenhub is incredible for the below areas: Burndown Charts, Release Reports, Velocity Tracking, Control Points Charts, Cumulative Flow Diagrams And if there is a bottleneck in your workflow, ZenHub identifies it. The most important aspect is serving as a collaboration tool for areas that are impeding implementation projects. For example when working with non-standard ERPs and having to document ERP integrations this tool is very helpful
ZenHub continually adds to its reporting suite-- that truly allows you to track forward motion and see what issues may be the cause of any delays.
Both our technical and non-technical staff can understand and use the functionality.
We like the flexibility of being able to provide labels to our stories that can be customized to the way our company does things--- such as knowing if an epic is part of a module or a stream.
We also like the flexibility of the number and labeling of the pipelines--- again, very adaptable to our organization.
The filtering is very useful--- with and/or conditions, and allows people on different projects, doing different functions, an easy way to view what is important to them.
Would love a better integration with GitHub. For example, notifications when your PR is updated, when review is requested, @-mention in comments, etc.
Improved "Later" tab, for example the ability to create to-do lists or making the "Later" tab into a more powerful to-do list (annotate items with notes)
More powerful integrations, e.g. Google Calendar could render a calendar view within Slack, rather than sending the daily schedule
Sometimes, updates to a GitHub project can get lost if they're made through ZenHub. You do need to open the GitHub project occasionally, as you don't have exactly the same ability to modify issues and milestones from within ZenHub.
It's great to be able to see your projects from within ZenHub, but sometimes you'll need to check in on the GitHub project itself, as well.
I've run into some problems with updates getting lost on occasion. I think this happens when you do the update from within ZenHub instead of from GitHub itself. I also don't have quite as much control over my issues or milestones from within ZenHub.
Slack sitll lacks in functionality. It's better than Skype for Business in many ways, but it is still another chat/message board app. It has limits in free version and paid versions. Also Windows app has errors that bother me, for example, I see number on one of my team's icons. It suggests that one of channels has unread messages; I check all channels - no unread messages, but that "1" still appears
My rating was 7. Its intuitive interface and user-friendly features like channels, threads, and integrations make it excellent for team communication and onboarding. However, its usability is held back by the resource-intensive desktop app and cluttered feeling in large workspaces. The mobile app's performance and unreliable notifications have also been noted as weaknesses.
Once it's up and running it's easy to use. It needs a little consideration to get set up perfectly for your own needs, but that is the same for any feature-rich software.
Yes, the app works 24/7. I don't even recall having any period that we could not use since the implementation. Even the maintenance periods are barely noticeable and our work is not impacted by it when it happens.
Slack is a soft app, we don't have many issues with it. I recall one or two people complaining about something during our usage period, but I didn't have a bad experience. When the app is slow, usually the problem is with my computer or my internet. The app works just fine.
Whenever I've had to troubleshoot an issue with Slack (which, to be honest, has not happened very often), their online documentation has been easy to locate, easy to understand, and effective in resolving my issue. Slack's ever-growing popularity also means that there's a large community of practice out there that can be depended upon.
Support is good, but quite honestly, I haven't needed any support since 2015. As I remember, I was required to open a ticket and had to wait a few days for resolution. I give it a rating of 8 because of the lag in getting a solid resolution, but it was resolved adequately.
Teams and Slack both have Pros and Cons. We use both for communicating. Microsoft Teams is good from the prospective that you can set up Distribution Groups and Private Groups for sharing out links from One Drive and Sharepoint. The integration is built in so that all the Microsoft apps run natively with each other. Slack benefits from organizing different topics in channels that are all under one overarching project. These channels are easily created or destroyed depending on the coding issue at hand.
Way better than competition if you use github because it seamlessly integrates without doing anything. You don't need to duplicate your issues, etc. As long as your devs already use github and github issues this will be a no brainer and simple to implement. With JIRA or Trello we were doing everything twice, things got dropped, etc.