HipChat (discontinued)

We used HipChat within our department initially before rolling it out to the company. Within our company we use it to track and comment on JIRA tickets as they progress, manage our standup tracking, and informally poll on new features or what to have for lunch. The wider business use it to keep project discussions all in once place and out of emails.

Our development team is spread across a large building and using HipChat allows us to interact with one another quickly and efficiently. By using the one on one chat we can reach out to one another and not be as intrusive as a phone call might be to our neighbors. HipChat is easy to use, install, and manage.

We use Hipchat across the organization. In Engineering, we use it to publish build results and track deployment logs. Scrum teams use it to communicate generally and also to publish standup status. We use Hipchat to coordinate work during incident response; we often use the history to quickly come up to speed during handoff to other teams.

HipChat is being used across the organization, especially by software development. It is used to allow us to quickly collaborate with one another so that we can work with geographically dispersed teams more easily and get answers from people when they're not at their desks.

We use Hipchat to quickly communicate with the our immediate teams, and to assist us in collaboration with other departments. Things we wouldn't put in e-mail we instead put into Hipchat.

We use it across most of the organization. Some people opt to use other communication means that tie into our Video chat system. It helps out engineering group work collaboratively and to tag each other in order to call attention to things. We also can use it to tie in our ticketing system.

We use it in our organization to keep the engineers in communication with each other. Since we moved the engineers between two floors of our building and as we increase in size it becomes harder and harder to communicate effectively with each other. Hipchat makes it convenient to get in contact with someone form the comfort of my own desk, especially when trying to get in contact with my manager.

We are a software design/development agency. We use HipChat with one client to facilitate communication within teams and one-to-one. Members of these teams are on at least two continents and spread across 8 or more time zones.

We use Hipchat to manage projects, send links, and funny gifs. It also provides a way to set up meetings seamlessly. The entire company uses it to stay connected. We have employees worldwide so it solves the issue of having a central hub for contact.

It is used across the organization as the official communication channel.

We use HipChat across our entire organization: marketing, creative, engineering, etc. It's a great way for the team to work together collaboratively across projects/initiatives. We have channels (rooms) set up for each team and then a company-wide team. We also have several bots set up in rooms to output key company performance data so we can stay abreast of the company's day-to-day KPIs.

Our team is using HipChat as the main collaborative platform. We have rooms for users to log support requests for our team as well as we have an internal room to discuss our own affairs. It's also used to bridge a connection with remote employees. It’s very helpful to be able to send files, video chat and regular chat all in one platform. Github integration is also key. Our entire organization has migrated to Hipchat. However, there are still some engineering teams using Slack.

I have used HipChat in the past with both technical teams (software developers) and non-technical teams (graphic designers and content authors). In each case HipChat was used as a private communication tool for coworkers to interact in a more synchronous (instant) and distributed (group focused) manner. For developer collaboration HipChat offered features that made the tool feel incredibly native and extensible. For non-technical users it delivered messages in near real-time, with consistency, and did not obfuscate key messaging features behind an overly simplified user interface. HipChat not only solved the problem with team collaboration/communication, in each case it improved the communication between the technical and non-technical teams. Support ticket response times decreased by 10%, and many support requests ended up migrating to HipChat for "triage" before hitting the ticket system. This resulted in dramatic reductions in help ticket requests freeing up core-developer time for responding to tickets that actually represented bugs. It also resulted in a higher quality software and design deliverables simply due to the fact that developers where more involved in understanding the needs and problems of the users and customers working with the tools they build on a daily basis.

HipChat is used among by all members of our technology team. We have a series of private and public rooms dedicated to various projects. We've integrated our instance of HipChat with other Atlassian products such as Bamboo and JIRA in order to keep track of builds and code changes to our product lines.

HipChat is being used for the engineering department at my company. We have chat rooms for each team which are used for cross-team collaboration. It helps members of the same team coordinate, as well as easily find members of other teams.

HipChat was being used only in our department and not the whole organization. HipChat is used to keep the whole department's communication together, for the purpose of calling meetings or querying about the work task. Managing issues from JIRA and keeping track of when commits have happened in Bitbucket was easier with HipChat.

Hipchat is being used for real-time communication across our entire company. Through the use of rooms and private conversations it allows our entire workforce to effectively communicate with each other and keep up to date with company wide discussions. The many features of Hipchat, like document and link sharing, bots and mentions support our day to day activities in the software industry and allow remote team members to be part of the conversation.

HipChat is being used by various teams. In our team we are leveraging JIRA and Jenkins integrations and considering using it as a link in a semi-automated workflow. HipChat would notify the team that data is ready and team members would approve publishing data by sending a message in HipChat.

I run an online business management company where I provide professional services to a number of different clients. HipChat enables me to communicate with team members on numerous projects at once. By using HipChat we have cut down on the endless email conversations that occur throughout the day, and we can get immediate updates when needed.

HipChat has long been a very solid standard for prompt business communication. It's full of features, both used to improve workflow with various integrations, and also to provide humor and provide a more human emotion to the standard text communication of chat. On the surface it's really great, and fairly reliable (there are bugs like any software), however the lack of proper message syncing on the back end commonly leaves me looking for a better tool. Push notifications for direct user conversation (@username) is great, but opening up their mobile app and having no room or user badges is a huge disappointment. Especially considering so many other chat providers (free and paid) have done this from their inception. I started using HipChat in 2011, and it's surprising that in 2016, this still isn't a feature. If I don't have a computer left online and logged into HipChat constantly, I miss a lot of important conversations and have no great way of knowing they occurred unless I go looking through our (>100?) rooms. Such a great tool with lots of capability, yet this single feature which seems so common place is severely limiting it's potential.

Hipchat is used across the whole organization in my company. It is used to exchange with collaborators, pinging them or sending funny links, to more serious use where we talk about the current jobs and current situations. This is done by creating rooms and calling the affected people. It is extremely valuable because it leaves a trace of these conversations, the search feature is then very useful to find already solved problems.

We use hipchat as a collaboration tool between the different departments in our firm. That covers our front end devs, back end devs, technical support, and stakeholders to our client facing consultants.

Hipchat has been a great way to communicate in office without interrupting others. Without it we would be much less efficient. It is user friendly, rarely has problems, and we all like the features of sending pictures or gifs.

Everyone in our company uses HipChat. It's the way we communicate with each other through Instant Chat. I've used other chat programs at other companies, but I like how you can set up a chat room and it's always available for use. Also, if you are offline, the chat messages get sent to your email.

Pros:
- Chat Rooms
- Chats are auto-saved, and you can just scroll up to see entire history of chat
- URL links show preview of site
- There is a search
- There is a video functionality, although I haven't used it yet
- There is a file section that shows all files between you and the person

Cons:
- Sometimes the program shuts down on me or freezes and I have to re-login
- It doesn't save my user login and password. So I have to re-enter it every time I login
- Program has become unavailable sometimes
- There is a search history functionality which would be a pro, except I can't get it to work

HipChat is used throughout the company to communicate, to coordinate work within teams and to coordinate the teams themselves. It is used to share office updates, report errors, share code snippets and get help with the dev environment.