Fuze is a cloud-based unified communications platform that includes IP PBX voice service, video conferencing, and collaboration tools such as content sharing and instant messaging capabilities. It also integrates with a wide range of popular CTI, CRM, and click-to-call solutions.
$15
per month
HCL Connections
Score 9.0 out of 10
N/A
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
Pricing
Fuze
HCL Connections
Editions & Modules
US Outbound
$0.02
Per Minute
Fuze Meetings
$15
Per User/Per Month
No answers on this topic
Offerings
Pricing Offerings
Fuze
HCL Connections
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Required
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Fuze
HCL Connections
Features
Fuze
HCL Connections
Cloud PBX
Comparison of Cloud PBX features of Product A and Product B
Fuze
5.5
111 Ratings
37% below category average
HCL Connections
-
Ratings
Hosted PBX
5.178 Ratings
00 Ratings
Multi-level Interactive Voice Response (IVR)
6.073 Ratings
00 Ratings
User templates
5.060 Ratings
00 Ratings
Call reports
6.192 Ratings
00 Ratings
Directory of employee names
5.1107 Ratings
00 Ratings
Call Management
Comparison of Call Management features of Product A and Product B
Fuze
6.5
107 Ratings
25% below category average
HCL Connections
-
Ratings
Answering rules
7.099 Ratings
00 Ratings
Call recording
6.089 Ratings
00 Ratings
Call park
7.073 Ratings
00 Ratings
Message alerts
6.193 Ratings
00 Ratings
VoIP system collaboration
Comparison of VoIP system collaboration features of Product A and Product B
Fuze
7.1
91 Ratings
11% below category average
HCL Connections
-
Ratings
Video conferencing
7.077 Ratings
00 Ratings
Audio conferencing
7.190 Ratings
00 Ratings
Mobile apps
Comparison of Mobile apps features of Product A and Product B
Fuze has way more capability than we need for our small office so it might be best suited for large installations, call centers, and complex environments. Our office is small and our needs [are] minimal, so when we need support we are challenged to understand the support person due to our lack of technical sophistication. We sometimes feel like we should switch to a solution more geared for consumers or SOHO. Nevertheless, Fuze provides reliable service at [a] reasonable cost that meets our needs, and because support is rarely needed we are happy with them most of the time, i.e. when support isn't needed.
IBM Connections is well suited for larger organizations that need an internal social networking tool and are willing to deal with IBM and the complexity of the software. It is less appropriate for smaller organizations and those who don't want to deal with the complexity, or IBM's awful customer service and prices.
Support Team - the best I have ever worked with. They help 24/7 on any issue I could come across. Usually it is an item I could fix myself and they fix it and show me how to fix the same issue if I have it in the future.
Contact Center - We do Commercial Collections involving Sales and Collections. We have 50 people on the phone at one time. Contact Center lets a Manager listen live and gives help if the rep needs help selling or collecting.
Pandemic 2020 - without Fuze we would have been unable to work for 3 months. They saved our "rears" since we already had all their services up and running for years.
The plugin for MS Office/Explorer has made saving and sharing working documents extremely convenient for me and my close colleagues
The newsfeed feature conveniently aggregates updates from the communities/people you follow. It's nice not to have to jump from community to community to see what's going on in the organization
The various apps can be used for several purposes. A little creativity goes a long way when establishing what type of information the apps can be useful for communicating
The lack of a note-taking tool became a bigger and bigger issue as time went on. Our pilot users felt Connections was a natural place to take and share meeting notes – including photos, drawings, recorded audio, etc. – and were always frustrated that there was no easy, organized way to do that. We tried using a Blog, Wiki, etc. but nothing really resonated as a good solution for this.
The Wiki tool is weak, providing rigid structure but with few options. A Community can only have a single Wiki, for instance. Wikis are weak in the mobile app as well; they’re not even easy to navigate. Users ended up ignoring Wikis completely despite our efforts to get them to convert documents like guidelines, policies, procedures, handbooks, etc. into Wiki form.
The Windows Explorer plug-in was useful but required a lot of manual intervention to setup. For instance, once a user joins a Community in Connections, the Community also has to be manually added to the Explorer plug-in so the user can find, open and edit files with it. We felt this process should be much more automated.
Tagging is only relevant in the web UI and, to a lesser extent, in the mobile app. However, in the Windows Explorer plug-in, Tags are not usable at all making it difficult to find things that were easy to find in the web UI.
IBM Docs was not included in the on-premises deployment; it was an additional license so we did not test it. Documents, mainly Microsoft Office files, are still the single most common way our user community creates, shares, edits and presents information. That proved to be a major gap for our users, and slowed user adoption considerably. We considered testing it, but IBM Docs would only work for about half of our users so we found ourselves wondering if we really wanted to support two document editing platforms. IBM Docs also offers no way to work offline as far as we could tell. This also meant we would need to keep licensing Microsoft Office which is not cheap.
Consulting costs are high because the back-end environment is complex. Installing, administrating and even patching Connections is a fairly complex process. We needed to hire consultants to install our test environment and any major upgrades would’ve required additional consulting fees. Any 3rd party add-ons we looked at were highly technical in nature meaning…you guessed it, more consulting costs.
Administrating IBM Connections requires editing XML files in a specific, secure way that is typically done in a console. I love consoles as much as the next admin, but when you only use a console once every 2 months it means looking up all the documentation and re-educating yourself. A single change could take me 2 hours to implement. 3rd party admin dashboards do exist, at an additional cost, but IBM really should provide a much easier way to manage the environment.
The lack of in-person or online training courses, materials, videos, etc. really discouraged a lot of users. The only decent training we could find (marketing videos aside) was a single video series on Lynda.com which, of course, was an additional cost. In the end that video didn’t really help our users much beyond introductory concepts.
IBM includes reporting, but it’s a massive Cognos system requiring some serious hardware and Cognos expertise. We had neither, and would have ultimately opted for a 3rd party add-on for reporting and statistics.
An often overlooked concern is eDiscovery. Our contracted eDiscovery service extensively works with various ECMs, but had no idea how they would handle Connections data. The cloud version of Connections offers an add-on for eDiscovery, but as far as we could tell IBM offered nothing for on-premises deployments.
Fuze is a solid application that is a great asset to the business for our sales staff to make daily calls to clients and candidates. Managers can monitor call data and times to keep up to date with team performance, as well as monitor calls for users on their team. The Fuze/MS Teams integration is an exciting prospect that would be very beneficial to us as a business, for seamless integration between the 2 platforms.
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.
Fuze was built with the end-user in mind. It was built to have a common interface on mobile and desktop. Fuze Web is new, and it also has the exact same interface as the desktop and mobile, and they are still working on the ability to make phone calls from the browser itself, currently it can do meetings just fine. Everything about Fuze was built with the end-user in mind.
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.
We've had a few outages over the past year. More than other vendors I've used. They usually have outages fixed within an hour. The downside is they do not provide root cause of outages. If they do at takes them at least a month to get it to you
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.
Since Fuze runs across multiple devices and platforms they really strived to make a lightweight interface that is optimized for phone calls, chat, and collaboration. The web client loads fast, the chat is always up-to-date, phone calls arrive on-time. The desktop client is the most feature rich and basically it just adds desktop sharing functionality as well as VoIP for calling, and the mobile client doesn't consume a lot of battery, and it stays running to get phone calls, chats, and can do meetings over Wifi, Cellular Data, or Cellular voice.
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.
Our experience with Fuze support has been overall very positive. Their technicians seem to be well trained and able to handle a variety of requests and issues without unnecessary delays or extensive troubleshooting. Fuze allows enough customer access to avoid the need to call support for every little issue but is ready to assist when issues are beyond our capabilities to resolve.
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.
At many of our sites with more than 50 users, Fuze sent someone onsite to train. This worked surprisingly well, as the trainer allowed the users to set the pace and answered TONS of questions. Fuze has a very streamlined training process, their staff is very professional, very knowledgeable and very engaging.
Fuze has vast amounts of training videos and guides on how to use its products and services. There are literally endless-hours of training and I often point end-users to a particular video which addresses the specific needs of the user, for example: how to check voicemail. Or, how to share your desktop, etc.
Personally, I didn't have any trouble getting started with Fuze. It was installed on my computer on my first day and I was good to go! Little to no hiccups. I was not with the company when they first adapted Fuze so I can not speak to the implementation as a whole.
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.
Fuze was far more expensive and more complicated to set up. Our current platform took a few days to set up with SSO. Our contact center took a bit longer but works amazingly.
From the few times that I have used MS SharePoint, I can say that it doesn't seem to hold a candle to the robust features of IBM Connections. The out-of-the-box capabilities of IBM Connections are amazing and are more easy to access and use than what I've seen with MS SharePoint.
Fuze does have scalability limits but most of that is how many end-points they can put on a virtual PBX, or VCX as they call them, I THINK its limit is somewhere between 2,000 and 5,000, but we've not had issues with that because we have put users into various VCXs some by location, some by department or function. Either way, we have 7,000 currently deployed, and are going to end up with over 15,000 when we are done, Fuze is VERY scalable.
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?