HipChat [EOL] Reviews

The basic version is free to use. We also like setting up automatic notifications to different chat rooms. It is easy to set up new rooms and invite new users. Emoticons are fun and the mobile app is great too.

Our entire organization uses this as our default messaging app, not just our software engineering teams. It drastically helped improve our communication across departments once we got everyone on. Plus, we use it as our “Chat Ops”-type tool to monitor systems and software development applications.

Third-party integrations are continuing to grow, which is good, but sometimes the integration is rocky and not very usable. Being able to trigger Jenkins builds from within HipChat would be great for software developers and testers.

I have used it for over two years.

We use HipChat Plus (cloud based). Atlassian is the vendor. Version number unknown, but we’re always on the latest since we’re a cloud-based account.

We have not had stability issues.

We have not had scalability issues.

Support is very fast, helpful, and friendly.

We used multiple products, such as Skype, Spark, and HipChat as well. We dropped Skype and Spark because they had less features and we wanted to simplify our chat tool across the organization. Plus, we use other Atlassian products like BitBucket, JIRA, and Confluence which HipChat talks to directly.

Setup is straightforward. Go to the website, create an account (if your company is brand new to HipChat), get the token and integrate it with JIRA, as well, if you use that product. Administering users is easy, as well.

It’s fairly inexpensive to upgrade to HipChat Plus. If you need to store chat histories indefinitely and could use a video conferencing with screen share tool, then it’s worth the price.

We were using both HipChat and Skype and previously another IM tool called Spark. We dropped them both in favor of HipChat.

Identify a couple of administrators in your company to manage the application and dig into its cool features. It’s extremely easy to use. You don’t need to be highly technical to be an admin on it either.

It is a communicator for partners and clients. We use it internally.

We get quick responses amongst employees.

I would like HipChat to be more stable. It crashes pretty often on Windows OS.

Hipchat for windows sometimes acts weird basically. I’ve fixed many times this issue reinstalling the application for many users.

- Loading errors

- Keeps crashing and freezing

- Delay in response when you select new rooms or conversations

I’m using Mac for the last 2 months and I haven’t had any issue so far. It may be only windows.

I have used HipChat for four years.

We had stability problems with the system on Windows.

We did not have scalability problems.

I would give technical support a rating of 5/10.

HipChat was the first choice and we are keeping it.

The initial setup was pretty smooth because we were a startup company.

I am not sure about pricing and licensing. We pay per user. In our case, this is 250 users.

We didn't look at other systems. Right now, we are using Jabber as well.

If it is a small or medium size company, then I recommend it.

• Unlimited group chat rooms
• Group video chat
• Screen sharing
• Security
• Persistent messaging
• Seamless integration with other products

HipChat allows us to do video calling and screen sharing with up to twenty users, whereas its major competitor Slack, can only support eight participants.

For a company like us with offices in different locations, this is an invaluable feature, as it increases our team collaboration and efficiency.

We have distributed teams, as well as remote teams in our organization in different geographic locations. After HipChat was introduced, the team collaboration and coordination improved drastically.

HipChat helped us to get rid of never ending email chains. It's a fun tool with lot of emoticons and our teams enjoy using it.

Our users love using the HipChat mobile app. This has increased our team’s productivity. The product has a great UX across multiple platforms and is user-friendly.

Currently, one email ID is linked to one HipChat cloud group. As a user and an administrator who may manage multiple HipChat groups, this is restricting my work.

I have been using HipChat for around two years.

HipChat's a reliable product. Up to now, we have not faced any issues with the product’s stability other than a few bugs which were fixed in a timely manner.

We use HipChat extensively in our organization. I have also worked with multiple clients who use HipChat with user tiers ranging from 51-100 users to 5000+ users. Scalability was never an issue with any of these customers.

Atlassian has an impressive technical support team who has fixed our issues within the agreed SLA.

We have used Lync/Skype for Business previously and had constant issues with these products.

The initial setup was hassle free. It was pretty straightforward.

HipChat offers the most competitive pricing among the enterprise chat solutions in the market.

We have used Lync/Skype for Business and evaluated Slack before procuring HipChat licenses.

If your organization is struggling with team collaboration and never ending email chains, HipChat is the perfect solution for your problems.

It’s a fun tool with great features like high quality video calling and the pricing is the most affordable among other products in the market.

Organizations using other Atlassian products like JIRA, Confluence, and Bitbucket should definitely consider giving it a try.

HipChat can further improve your team’s efficiency and productivity.

• Internal private and group chatting
• Upload and download of shared files
• Team collaboration

It allows our team to communicate easily and collaborate despite our geographic locations.

I don't know about any area that needs improvement.

The only thing, that I can think of, is to either integrate other apps/software or maybe, enable screen-sharing and video conference. However, I think that is more of an enhancement of the app, rather than an improvement.

I’ve been using HipChat for three years.

Occasionally, there were stability issues with uploads and downloads. I can’t be certain if it was the internet connection.

I don’t know of any scalability issues.

The initial setup was simple and the instructions are user-friendly.

We evaluated Microsoft Teams.

I would strongly recommend this product.

Real time chat organized into channels with archival and search capabilities was a complete game changer for how I work. HipChat ended up supplanting e-mail in my workflow. With the addition of a custom Bot which interacted through the service using the API, it revolutionized how I provide my expertise to my colleagues.

The base product of the software as a real time communication tool really helped teams collaborate since we were geographically separated. It made it very easy to interact with remote teams. But the real value was achieved when we hooked up a Bot framework since this allowed all staff to self-serve a wide range of tasks which had originally required either myself of our Operations staff to manually handle tasks. This is the Bot framework we used: https://github.com/skoczen/will.

The search is terrible. They keep changing how it's integrated with the desktop client which is bad enough, but the results you get back are often poor and makes it very difficult to find "old" things. You might vaguely remember having a conversation with someone about something, but trying to locate that thread is very difficult.

I used the product many hours a day for almost three years.

We had some stability issues. We were actually evaluating a move from HipChat to Slack at my last job out of frustration related to repeated downtime with the service. Since we were managing so many things through HipChat in our effort to use a "ChatOps" footing for more of our work, when the service was down, it was extremely hard to function. This was happening for hours every other month and it was extremely frustrating. When I found out how cheap HipChat was compared to Slack, I was willing to let it go of this issue.

We had no issues with scalability. We never had more than about 200 users on our set up and things seemed to work well enough excluding the outages with the service, but those weren't related to our use.

Technical support was okay. I felt like it took a long time for issues to get resolved and they seemed to get resolved "invisibly". As an example, I reported an issue with how copy/paste of messages from inside the client broke and the problem eventually got fixed. I think it took two or three client releases so maybe a month or two. After the initial bug report, I never got an update that the fix would be appearing in the client. I just discovered that it was working again one day by accident.

I have used tools like IRC at previous jobs.

I wasn't involved in this aspect of our HipChat installation, but creating an account for our company was pretty straightforward.

It's pretty cheap especially when compared to Slack.

It's cheap and it works most of the time. If you're looking at Slack and having sticker shock, HipChat is a perfectly serviceable alternative. If you are already using Atlassian's suite of products, there are all sorts of integrations. However, I was surprised at how poor some of these integrations were considering it's from the same company.

Now that I'm using a similar product (FlowDock), I look back FONDLY on HipChat's broken search. In FlowDock, there's no indexing of private conversations. Another area which annoyed me is notices about new messages to you. I don't know why, but it seems like none of these products (HipChat, FlowDock,Slack, Let's Chat, and Mattermost) seem to differentiate between messages in a channel with are directed to everyone in the channel versus to me directly. I want to know if someone has tried to ask me a question personally versus if the question was directed to everyone on the team. I don’t want to be distracted if it's not directed to me personally. I will catch up with it later. Theoretically, this would be simple to fix, but I don't know enough about the internals of the software to judge whether this is actually true. Something I didn't know I wanted until I used FlowDock was threaded conversations. They took a bit of getting used to, but being able to separate out each topic within the channel is handy. Unfortunately, not everyone remembers to use it so it loses some of its utility.

We use a robot integrated with JIRA and BitBucket, a customized robot, and hubot.

We receive instant alerts from HipChat on iPhone. As a system engineer, we need to get the notification immediately to update tickets from JIRA and update the code from BitBucket on mobile. We could check this from email, but there are a lot of emails that we would just ignore. For HipChat, we can create a specific channel for the update. We communicate with teammates instantly within the channel, which helps us to be productive.

What I had dealt with hipchat was integrating hipchat with our operational server (hubot + jenkins) at the backend. Thus, we could run some non-critical operation on top of the mobile, such as resource check, availability check, owner check. Due to the security reason, we should not allow to run some crucial cmd like reboot. There are some build-in feature for JIRA and bitbucket helping us to send out notification to hipchat room. Therefore, we can directly give a instant response via the room instead of sending out massive emails.

I have been using HipChat for two years.

There was some problem with the company firewall. It was not stable in some versions.

I did not have any scalability issues.

The technical support was slightly above average.

Before HipChat, we used Lync without a built-in robot.

The initial setup was straightforward. The installation was simple. I did it without reading the manual.

We evaluated Slackbecause it is free for basic usage.

Study customized robots for further automation.