Connections from HCL Technologies (formerly from IBM, acquired by HCL in 2018) is a collaboration tool and employee digital workspace with key features like social analytics, blogs, document management, and a social network.
N/A
Pigeon Messengr
Score 8.6 out of 10
N/A
Based in New York City, Pigeon Messengr is a business communication platform that offers teams the flexibility to communicate their way. Pigeon Messengr provides businesses of all sizes with an integrated suite of communication tools to help streamline business communications. Employees can text, chat, set up video calls or voice calls, have private or group discussions, and more! The platform connects conversations across voice, video, and messages so you can pick up right where you…
$7
per user
Pricing
HCL Connections
Pigeon Messengr
Editions & Modules
No answers on this topic
Starter
$7
per user
Professional
$14
per user
Business
$25
per user
Enterprise
$40
per user
Offerings
Pricing Offerings
HCL Connections
Pigeon Messengr
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Pricing is per user per month. Contact Pigeon Messengr for more information on pricing for your team.
More Pricing Information
Community Pulse
HCL Connections
Pigeon Messengr
Features
HCL Connections
Pigeon Messengr
Communication
Comparison of Communication features of Product A and Product B
HCL Connections
-
Ratings
Pigeon Messengr
9.2
Ratings
15% above category average
Chat
00 Ratings
9.80 Ratings
Notifications
00 Ratings
8.10 Ratings
Discussions
00 Ratings
9.70 Ratings
File Sharing & Management
Comparison of File Sharing & Management features of Product A and Product B
IBM Connections is possibly most suited for larger organizations where bigger teams are able to have more people to share with. Also, it may be less appropriate when there is so much security that it would hinder the anytime, anywhere access capabilities and prevent users from being able to enjoy sharing content with each other.
I would recommend this to anyone looking for a solid work chat. It has been super reliable and easy to use for everyone. It may be less suited in a much bigger company where I could see messages being buried if there are too many people in one channel.
Search in connections is incredibly poor. It's commonly joked that once data goes into Connections, you never find it again, unless you have a direct link. This alone kills usability for Connections.
Embedded content in wiki pages in connections is poorly implemented. While the content displays, you can't interact with it, or edit it reasonably, and it's really slow to load.
The "social" features in Connections are pretty lame, and no self-respecting user spends any time trying to build their profile. It's just disappointing.
Sometimes a message will get broken up and I am unable to view it all at once.
It would be nice if it had a way to select a message as being unread. I like to leave messages unread as reminders but sometimes need to just read them first.
It won't allow me to upload a picture because it has to be of a very small size. Would be more personal if I could use a picture on my profile.
Connections has continued to more than meet our needs from a collaboration point of view and we are currently working on integration with our IBM Websphere portal platform to provide an integrated collaboration solution. This scenario will provide our users the best both products have to offer in a single interface.
Connections combines all the most useful abilities from various social networks. This makes it useful of course, but it also reduces user adoption time initially by allowing users to get comfortable with basic features. Once they are comfortable, it's easy for users to start exploring. They find new people in the organization to contact, new sources of information, etc. Before you know it, about half of the users are contributing back in some form -- and all with little or no training needed by IT.
Once Connections was installed, patched, etc. it was ALWAYS up. We only had to bring it down for OS updates to the servers. That seems to be typical of anything that runs on WebSphere; it's bulletproof and could probably run for months and years if the underlying OS didn't require constant patching.
IBM Connections web UI, mobile app (data sync to / from the device), and file transfer speeds were almost always very fast. It was rare for a slow-down of any kind, even when doing searches.
IBM Support has ALWAYS been quick to respond, regardless of the product. Even first level techs seldom provide "canned" responses and they really try to help. If they can't help, they don't wallow around but engage the right person immediately. It's very rare that the first level tech needs to escalate, and even more rare when they do escalate and the next person engaged cannot solve it. We have been more than satisfied with IBM support's quick and professional responses to our issues.
Try to understand you will never find a product which suites all your end user for 100%. IBM Connections is the best of all breeds but if you go look on each functionality on its own there are better example out there. But as IBM COnnections delivers it all in just one platform makes it the best example about integration of different functionality into one platform.
IBM Connections offers a complete package of tools that can be useful but it doesn't integrate well with other services. Competitors like Yammer offer slightly fewer features but are cheaper and much easier to maintain. If we were making a decision today we probably would choose a combination of Yammer, Slack, Microsoft Teams, and other Microsoft or Google Tools.
Slack: Pigeon Messengr isn't as well known but does have many of the same features at a lower price point. Miro: I had actually used Miro in a previous position, but I expressed to my leadership that I very much thought it was the wrong kind of functionality for what we were doing. We typically just send messages and files and did not need the level of interaction that the Miro whiteboard provided.
Scaling UP is never an issue with IBM's core technologies like WebSphere, DB2, etc. as long as you have or can find the technical resources to implement it. Where IBM seems to fail is scaling DOWN for smaller organizations. Connections 5.0 on-premises would have required us to create 7 servers -- yes, they would be virtualized, but still that's 7 OS licenses, 40 virtual CPU cores, 80GB RAM, and a few TB of hard disk space. All to replace Quick which runs on 1 server with 1 OS license, 4 cores, 8GB RAM and 600GB of disk. Granted, there are major differences in capabilities between the two, but how do you get a CFO understand why features like a mobile app, file sync, and social sharing require 10x the back-end resources?