Overall Satisfaction with HipChat
We've been using Slack for a year or so because of its integration possibility with other systems. So at that time it won over HipChat. While the team was growing we started to use more and more Atlassian products (like Jira, Confluence, Bamboo) and noticed that the integrations could be done even better with HipChat. Just recently we had to add something like 30 people in a subsidiary to the team so we took the time to evaluate again. Meanwhile HipChat evolved and is almost at the level of Slack, but with a lower price. Even though they improved the functionality of the system, the apps for mobile devices are still far away from Slack. At the end the price range and the Jira integration were the main reason to switch and even though there are some complaints from my colleagues, we're a lot faster in communicating with them.
- Jira integration to show ticket changes in rooms
- Possibility to open rooms from tickets
- User mentioning
- Clumsy chat view. Especially when there are a lot of movements in tickets. Those should be in a side list.
- Hangout integration sometimes doesn't work.
- Difficult to find unread messages in apps. Should be better structured. It's even worse for the Mac App where you close chats with CMD+w and you get no notice until you're directly mentioned in the room.
- Ediint of messages is too complex.
- Slack and Google Hangouts
Jira integration.
Closed team, so there is only work related people in HipChat (difference to hangout)
Price (vs Slack)
Closed team, so there is only work related people in HipChat (difference to hangout)
Price (vs Slack)
HipChat (discontinued) Feature Ratings
Evaluating HipChat and Competitors
Yes - Slack
Due to price and Jira integration
Due to price and Jira integration
- Price
- Existing Relationship with the Vendor
We had to add 30 new collaborators to our chat ( which was Slack at that time) that had been using Mail and phone before to communicate. The task was not just to introduce a new communication tool, but to widely replace the old communication channels and introduce new, more efficient workflows.
We intoduced it just some months ago and are still doing well after some initial acceptance problems, so I would not change it at all.