No more typing reviews! Try our Samantha, our new voice AI agent.

CA Unified Communications Monitor vs Loom Systems comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

CA Unified Communications M...
Ranking in IT Infrastructure Monitoring
65th
Average Rating
6.6
Number of Reviews
2
Ranking in other categories
Unified Communications Monitoring (3rd), Network Monitoring Software (87th)
Loom Systems
Ranking in IT Infrastructure Monitoring
61st
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (5th)
 

Mindshare comparison

As of March 2026, in the IT Infrastructure Monitoring category, the mindshare of CA Unified Communications Monitor is 0.6%, up from 0.1% compared to the previous year. The mindshare of Loom Systems is 0.5%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Mindshare Distribution
ProductMindshare (%)
Loom Systems0.5%
CA Unified Communications Monitor0.6%
Other98.9%
IT Infrastructure Monitoring
 

Featured Reviews

reviewer1605927 - PeerSpot reviewer
Sr.Solutions Engineer | Project Manager at a tech services company with 11-50 employees
Meets the needs of the customer but all of the features need improvement
I do not choose the solution. The client does. I am an implementer. We are systems integrators. It is worth mentioning that the solution should be easy to install and offer the user exhibition capabilities. Also, a data sheet should be used to gather information about the product, to facilitate easy and simple implementation. I rate CA Unified Communications Monitor as a five out of ten.
Keerthi Kumar Sangaraju - PeerSpot reviewer
Technology Manager at a tech services company with 10,001+ employees
Stable, easy to set up, flexible, and has multiple functionalities, but needs to define priority levels for each incident
What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"We use the solution to meet the needs of the customer."
"For us, it's very key to know the voice quality of the total solution, which is based on many components across many domains."
"We use the solution to meet the needs of the customer."
"Good end-to-end monitoring"
"What I like best about Loom Systems is that you can use it for infrastructure monitoring. I also like that it's a flexible solution."
"The solution is very scalable; a company wouldn't have any issues expanding it if they needed to, and we have a few thousand users on the solution."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring and that it's a flexible solution."
"Bringing Loom in ensures that the incident process, request process, change, all of these processes are improved."
"The solution is absolutely scalable."
"The RFS portion of the solution is the product's most valuable feature."
"You can develop your own apps within Loom, and they can be configured very simply."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
 

Cons

"The solution should have automatic baseline detection."
"All the features and functions of the solution can be improved, specifically the user experience."
"All the features and functions of the solution can be improved."
"The solution should have automatic baseline detection."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy, especially in the initial setup which can take six months of work, especially when you have a large estate that you're dealing with."
"What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The reporting is a bit weak."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"What's lacking in Loom Systems is the level of priority for each incident."
"The reporting is a bit weak. They should work to improve this aspect of the product."
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
885,311 professionals have used our research since 2012.
 

Also Known As

CA UC Monitor
No data available
 

Overview

 

Sample Customers

BBVA Compass
Citrix, Amdocs, Sysaid, Hexaware, Effibar, Revtrak, Taptica
Find out what your peers are saying about CA Unified Communications Monitor vs. Loom Systems and other solutions. Updated: March 2026.
885,311 professionals have used our research since 2012.