BMC Helix Enterprise Service Management Reviews

My main use case for BMC Helix Enterprise Service Management is to align the incidents for the company and create dashboards for the company to easily handle technical issues.

BMC Helix is commonly used in my company to modernize the enterprise with complex hybrid and multi-cloud environments. The core capabilities that I implement include ITSM, so incident, problem, change, request, and asset management, AIOps, event correlation, root cause analysis, and noise reduction. In the Digital Workplace, I created the self-service portal, the knowledge base, and chatbots. I also implemented automatic discovery of the infrastructure and dependencies from the company with the Discovery and CMDB. The dashboards and reports provide real-time visibility for IT operations and management, and I believe the dashboards are one of the strongest features of BMC Helix Enterprise Service Management. They provide real-time and historical visibility into IT performance.

With my experience, a company with 42,000 users uses BMC Helix Enterprise Service Management to manage IT support and infrastructure operations as part of the daily routine for the service desk. The dashboard shows the open incidents by priority, including P1 and P4, the tickets assigned by technical teams, and SLA counters for incident backlog trends. An example is that the dashboard detects repeated storage latency alerts across multiple servers, and BMC Helix Enterprise Service Management correlates the events and suggests a single root cause.

The best features BMC Helix Enterprise Service Management offers are ITSM and the dashboards.

What I appreciate about the ITSM and dashboards is that they help the company become more efficient. It is an enterprise ITSM and AIOps platform that combines IT process automation and real-time capabilities. When comparing BMC Helix Enterprise Service Management versus ServiceNow, which is a very common interview question, basically in IT operations, it correlates the events from servers, networking, and applications. Noise reduction and root cause suggestions come from AI. The dashboard detects repeated storage latency alerts across multiple servers; BMC Helix Enterprise Service Management correlates the events and suggests a single root cause. This results in the incident being created automatically, the change request being triggered, and downtime being avoided before users are impacted.

BMC Helix Enterprise Service Management includes core ITIL-aligned service management capabilities such as incident management, problem management, change and release management, service request management, knowledge management, and service catalog. In the Digital Workplace, we can modernize the self-service portal for end users, knowledge base, and FAQs, as well as virtual agents for request tracking and approvals. This reduces service desk workload and improves the user experience. The dashboards and reporting, including real-time dashboards, SLA and KPI tracking, custom widgets, and role-based viewing, are crucial. AIOps and artificial intelligence provide event correlations and noise reduction alongside root cause analysis suggestions. Predicted analysis and automatic incident creation help IT teams move from reactivity to proactive operations.

BMC Helix Enterprise Service Management has had a very positive impact on our organization, especially in terms of efficiency, response time, and visibility across IT services. From an operations perspective, automation and AI-driven capabilities significantly reduce manual efforts. For example, automated ticket categorization and assignment help us reduce initial incident handling time by around 25-30%, allowing the service desk to focus on higher-value tasks instead of repetitive work. Thanks to AIOps and event correlation, we also see a reduction in incident noise, where multiple alerts are consolidated into a single actionable incident, contributing to a faster mean time to resolve (MTTR). In some critical services, MTTR improves by 20% or more. On the service management side, dashboards and real-time reports give us clear visibility into KPIs such as SLA compliance, backlog trends, and recurring issues. As a result, SLA compliance has increased from 90% to 96%. We are able to identify recurring incidents and proactively address root causes through problem management. The self-service portal and the knowledge base also have a measurable impact. After enabling self-service requests and automation for common use cases such as access requests and password-related issues, we observed a 30-40% reduction in low-complexity tickets, which improves user satisfaction scores, particularly due to faster resolution and transparency in request tracking. Overall, BMC Helix Enterprise Service Management helps us move from a reactive support model to a more proactive and data-driven IT operation, delivering faster resolution times, better user experience, and measurable efficiency gains.

We have seen clearly tangible and measurable improvements after implementing BMC Helix Enterprise Service Management. Instant response time has improved significantly, with automated ticket categorization and assignment helping reduce time to first response by around 25-30%, especially for P2 and P3 incidents. The mean time to resolve (MTTR) has decreased by approximately 20%, mainly due to better incident prioritization, AIOps-driven event correlation, and faster escalation paths. SLA compliance has increased from around 90% to 95%, thanks to real-time SLA dashboards and proactive monitoring. Ticket volume has reduced through self-service after enabling the digital workplace portal and knowledge articles, resulting in a 30-40% reduction in low-complexity tickets such as requests and common user issues. User satisfaction is the most important metric for me; post-resolution surveys show an increase of 10-50% in CSAT scores, mainly due to faster resolution times and better communication through the portal. The cost savings and efficiency gains, while not always directly labeled as cost savings, manifest in reduced manual work, faster escalations, and lower incident volume, translating into better resource utilization and reducing the need for additional headcounts. Overall, BMC Helix Enterprise Service Management delivers strong measurable results in response time, SLA performance, and user satisfaction.

Regarding areas for improvement and challenges, complexity and learning curve are significant considerations. The platform is highly configurable, but this also means a steep learning curve, especially for administrators and new users. Proper training is essential. The initial setup and customization efforts for implementing workflows, dashboards, and integration can be consuming without clear process definitions. There is a risk of over-customization. The user interface has improved over time, but some areas of the platform are still not fully consistent, which can initially impact user adoption. We also encounter limitations with report customization; while dashboards are highly advanced and customizable, creating reports sometimes requires additional efforts and external tools.

I have been using BMC Helix Enterprise Service Management for around five years.

My main advice to organizations considering BMC Helix Enterprise Service Management is to treat it as a strategic platform, not just a ticket tool. First, we need to invest time in defining our IT processes clearly before implementation, as BMC Helix Enterprise Service Management is highly configurable and without well-defined incident, change, and request processes, there is a risk of over-customization or inconsistent workflows. Second, I recommend starting with a phased rollout, focusing initially on core ITSM capabilities and then gradually enabling advanced features such as AIOps, automation, and self-services. Third, leverage dashboards and KPIs from day one. We use real-time dashboards to monitor SLA compliance, MTTR, ticket backlog, and recovery issues, as this visibility demonstrates value early and drives continuous improvement. Fourth, prioritize user adoption and training. I am a specialist in adoption, so we provide proper training for service desk agents, administrators, and end users. The digital workplace and self-service portal deliver major efficiency gains but only if users know how to use them. Fifth, plan integrations carefully. BMC Helix Enterprise Service Management delivers the most value when integrated with an identity system, monitoring tools, and asset discovery solutions, so make sure integration requirements are understood early in the process. Lastly, assign strong ownership and governance. Having clear platform owners, change control, and documentation ensures the solution remains maintainable and scalable over time. I would rate this solution highly based on the measurable improvements and strategic value it has delivered to our organization.

My main use case for BMC Helix Enterprise Service Management involves handling hundreds of jobs that are scheduled day in and day out for 24-hour critical applications. Those applications work on schedules, conditions, and various factors like whether a file comes late. Everything is automated, and if it fails, the support team quickly gets alerts, takes action, reviews it, and works with required teams.

BMC Helix Enterprise Service Management offers the best features, including cloud-based access. As long as you have internet, you can access it via Wi-Fi without needing installations on laptops or servers, making it easy to use quickly from anywhere.

The easy cloud access and not needing installations with BMC Helix Enterprise Service Management greatly enhance my team's productivity and flexibility. It provided us with significant flexibility, reducing the number of team members needed, and I was able to train multiple people across the globe within my team with this quick, easy, and intuitive system.

BMC Helix Enterprise Service Management has impacted my organization positively by being quick, fast, and easy to use. There are fewer maintenance windows, and everything operates behind the scenes, allowing us to quickly take care of issues without large outages.

Measurable improvements I have noticed with BMC Helix Enterprise Service Management include a significant reduction in maintenance and increased productivity. We were able to respond quickly while working with fewer team members since everything is in the cloud, and the alerting mechanisms have improved a lot, helping to reduce our hours and some positions.

In terms of improvements for BMC Helix Enterprise Service Management, I have observed that some processes within the GUI are slightly quirky, leading to freezes occasionally. I think they need to continue looking at these issues to make the system more intuitive and user-friendly.

Regarding needed improvements, I believe that training and documentation should be made easier so people can easily see how jobs and conditions are set up. Setting up training or user use cases would be very helpful in presenting demonstrations and more effectively guiding users.

I have been using BMC Helix Enterprise Service Management for almost eight and a half years with Sears, and it is one of the best tools that is quick and easy.

BMC Helix Enterprise Service Management has been stable from the very beginning.

The scalability of BMC Helix Enterprise Service Management is straightforward. As long as you talk with Licensing, you can easily scale your resources in the AWS marketplace, expanding or retracting as needed.

I find the customer support for BMC Helix Enterprise Service Management to be great. I really enjoy working with both BMC folks and AWS folks.

Before BMC Helix Enterprise Service Management, I used an on-premises Control-M from BMC, along with CronTab and other schedulers.

My experience during migration was that it was very easy and quick.

BMC helped my team respond to critical issues during migration, as I worked directly with BMC's contractors. We encountered some issues while migrating from legacy to cloud-based, and there were conditions I could not figure out. However, with their help, we figured out different paths as legacy versus the automations on the host cloud-based.

I have seen a return on investment with BMC Helix Enterprise Service Management, as it required fewer employees. Overall, it was easy and faster to access, leading to considerable savings over time on installations, licensing, and other expenses.

Regarding pricing, setup cost, and licensing for BMC Helix Enterprise Service Management, I find it reasonable. It was not that costly, and we noticed significant cost improvements over time, allowing us to save money.

In evaluating other options before choosing BMC Helix Enterprise Service Management, I was familiar with BMC Control-M and other tools, and I believe it was the best decision to implement BMC, especially due to the quick turnaround during migrations from legacy to cloud.

My advice for others looking into using BMC Helix Enterprise Service Management is that if you want an enterprise solution for scheduling jobs and related tasks, this product can interact with mainframes, servers, Unix, Linux, and more. You can leverage it across your systems with proper dependencies in place. I would rate this product a 9 out of 10.

My main use case for BMC Helix Enterprise Service Management is service management. We have different OEMs and platforms to manage their services, and we are using BMC Helix Enterprise Service Management for our OEMs.

A specific example of how I use BMC Helix Enterprise Service Management with my OEMs includes incident management and change management in RPA. Whatever incidents are raised on a day-to-day basis involve incident management and change request management for whatever changes are required in the current existing production bot to get them up and running. These two use cases are what we are currently using.

I have another team also building the production bot, and we are looking forward to using BMC Helix Enterprise Service Management for project and process management.

In my experience so far, the best features BMC Helix Enterprise Service Management offers are its ease of implementation and user-friendliness. No past experience is required, and one person new to the platform can start using it from scratch.

What makes BMC Helix Enterprise Service Management user-friendly is its UI and overall design; it is very user-friendly and self-explanatory. That is a key strength of it.

BMC Helix Enterprise Service Management has positively impacted my organization due to our incident management tracking, which has been quite impressive so far. We can analyze our incidents, such as which particular area has more incidents coming in, and we can drive our data analysis from the incidents that arrive day-to-day to manage the area where these incidents are occurring, trying to reduce their counts.

Regarding the data analysis part, we submitted incidents from around the last six months, and from that data we discovered that approximately 50 percent of incidents are related to infrastructure. We managed our infrastructure more effectively by setting up DR and HA in place for production support, and that is how it reduced from 50 percent to 40 percent at the initial stage. We are looking forward to reducing it to 0 percent in a couple of years because infrastructure is key to executing any RPA bots.

An improvement needed for BMC Helix Enterprise Service Management would be to have assisted guides or templates on how to use the application or the best-suited applications to carry out the use cases, which would help other teams implement BMC Helix Enterprise Service Management.

I have recently started using BMC Helix Enterprise Service Management, so it is quite new to me.

BMC Helix Enterprise Service Management is quite stable, and we do not face any challenges or issues while using it.

BMC Helix Enterprise Service Management is scalable in terms of managing four OEMs now; if we have to use it for 10 OEMs, it would be scalable for us.

Customer support for BMC Helix Enterprise Service Management is great; we receive time-to-time responses, and we get responses within 24 hours.

Positive

Previously, we were using Snow Service Now, and we switched to BMC Helix Enterprise Service Management because it was difficult to manage all four OEMs in that platform, which was not user-friendly and easy to use.

In terms of return on investment, managing production bots allowed us to reduce our 20 to 30 L1 team members managing the production bot down to 10 resources, focusing on RCA, the root cause of the incident, and how we can reduce incidents while also reducing the FTE count in managing production bots.

My experience with the pricing, setup cost, and licensing for BMC Helix Enterprise Service Management is that it is manageable, and we are comfortable onboarding vendors; it is not significant in terms of cost.

Before choosing BMC Helix Enterprise Service Management, we did not evaluate other options since this was the only one for us to evaluate.

My advice for others looking into using BMC Helix Enterprise Service Management is to start managing their services, especially if they have multiple services, with the help of BMC Helix Enterprise Service Management since it offers ease of use and requires no training. It is user-friendly and self-explanatory. I rate this product a 7 out of 10.

For the past three years, I have been using BMC Helix Enterprise Service Management in my current organization, Blue Yonder, where I utilize BMC Discovery management solution for discovering the multi-cloud workloads deployed for Blue Yonder, and in HSBC, I have used BMC Helix IT Service Management along with BMC agents for monitoring servers spread across 60+ countries for HSBC Global IT infrastructure.

My main use case for BMC Helix Enterprise Service Management in my current organization involves discovering the cloud workloads deployed in Microsoft Azure, VMware on-premise private cloud, GCP cloud, and OCI cloud, for listing resources provisioned in the cloud as well as in the on-premise environment, where I use ServiceNow as my IT CMDB, and BMC Discovery performs the discovery and scanning, sending the data to my ServiceNow CMDB.

The integration of BMC Helix Enterprise Service Management with ServiceNow is seamless; I am able to discover all the cloud-native products, and the experience is fantastic with a seamless integration.

The best features BMC Helix Enterprise Service Management offers include scalability, robust ITIL service management, and excellent discovery for the multi-cloud infrastructure, particularly excelling in change problem management.

In terms of features, particularly around change management, the product works very well, allowing me to create multiple kinds of changes such as normal change, expedited change, emergency change, and I can track the changes by logging into the respective portals.

BMC Helix Enterprise Service Management has a positive impact on my organization by greatly improving workforce productivity; it creates dashboards for different personas within the organization, including the IT service management leadership team and the infrastructure operations engineering team, which is very useful for the day-to-day ITSM process.

Specific metrics showing productivity improvement include our ability to reduce the number of incidents; since cloud workloads are always dynamic, BMC Discovery discovers the products every 24 hours, allowing me to get newly provisioned resources in any cloud platform used in Blue Yonder, which truly helps the infrastructure operations and engineering teams to easily track incidents and the recently provisioned resources.

Regarding my main use case or how BMC Helix Enterprise Service Management works with cloud environments, I believe it needs more interoperability and integration with data platforms such as Salesforce, Snowflake, and Databricks, which requires improvement.

To improve BMC Helix Enterprise Service Management, the integration with data cloud platforms such as Salesforce, Snowflake, Databricks, and Redis Cache needs to be enhanced as these modern data cloud platforms require more attention from BMC.

In terms of needed improvements, particularly regarding user experience, I believe more integration options are necessary within data cloud platforms, and the implementation timelines should be reduced.

I have been working for over 19 years in IT infrastructure management and cloud infrastructure management.

BMC Helix Enterprise Service Management is very stable based on my experience.

The scalability of BMC Helix Enterprise Service Management is impressive; we run close to 22,000 workloads in Microsoft Azure and 10,000+ virtual machines in the VMware on-premise environment, making the product very scalable for multi-cloud platforms, on-premise virtual infrastructure, and physical infrastructure, with support for legacy mainframe systems and IBM AIX systems as well.

The customer support for BMC Helix Enterprise Service Management is excellent.

I would rate the customer support a perfect 10.

We have not used any different solution before BMC Helix Enterprise Service Management.

The setup cost and licensing experience are straightforward, with minimal challenges encountered.

I have seen a return on investment with BMC Helix Enterprise Service Management by reducing the MTTR by up to 30%, and while I cannot comment on money saved, the solution reduces the number of support staff required to manage a larger infrastructure for a SaaS organization such as Blue Yonder.

My experience with pricing, setup costs, and licensing for BMC Helix Enterprise Service Management indicates that the pricing is high compared to competitors available in the market, such as ServiceNow or Jira.

Before choosing BMC Helix Enterprise Service Management, I evaluated other options such as ServiceNow and Jira Service Management from Atlassian.

My advice for global enterprise organizations considering an IT service management product is to evaluate BMC Helix Enterprise Service Management product features and capabilities regarding AIOps, self-healing, AI and machine learning functionalities, and interoperability with existing tools and monitoring solutions; it is definitely worth the time spent in evaluating the product for enterprise needs.

BMC Helix Enterprise Service Management is truly an enterprise-class product that assists global enterprises in day-to-day incident, change, and problem management, improving workforce productivity while being scalable and resilient, supporting all multi-cloud infrastructure platforms. I would rate this product 9 out of 10.

I use BMC Helix Enterprise Service Management primarily for incident management, setting up priorities based on business impact, tracking SLA compliance, and coordinating with application, database, and infrastructure teams. This includes all investigations, updates, logs, and resolution details recommended in the ticket for audit and traceability.

Additionally, I use BMC Helix Enterprise Service Management for change requests, such as production deployments and configuration changes, which includes raising tickets with attached implementation and rollback plans, obtaining approvals, and tracking post-implementation reviews to ensure changes are implemented successfully without impacting business operations.

BMC Helix Enterprise Service Management has impacted our organization positively in multiple areas. From an efficiency perspective, automated ticket routing, SLA tracking, and standardized workflows have reduced manual effort and improved response and resolution times, especially for high-priority incidents. This has helped teams focus more on issue resolution rather than coordination and follow-ups.

Regarding compliance and governance, the centralized system, approval workflows, and detailed audit trail ensure that all incidents, changes, and requests are properly documented. After using BMC Helix Enterprise Service Management, we have observed a noticeable reduction in incident resolution time, especially for high-priority tickets, mainly due to automated ticket routing, better prioritization, and faster coordination between teams. On average, MTTR has improved by around 20% to 30% for recurring or well-known issues.

There is also a visible reduction in manual errors, such as incorrect ticket categorization or missed SLAs, because of predefined workflow templates and SLA alerts. This has helped improve overall ticket quality and consistency. From a compliance and audit perspective, the complete audit trail and standardized change processes have resulted in smoother audits with fewer observations related to documentation gaps or approval tracking. Overall, these measurable improvements have positively impacted operational efficiency, stability, and service quality.

BMC Helix Enterprise Service Management helps significantly coordinate between application, database, and infrastructure teams by providing a single, centralized platform for communication and tracking. During an incident, all teams are working on the same ticket, which helps avoid duplicate efforts and miscommunications. I can assign the tickets to the appropriate support group, and key details will be in work notes, attached logs, and screenshots. I can tag the relevant team, set SLA timing, and establish escalation rules to ensure the right team is engaged on time, especially for a critical issue. Since updates are visible to all stakeholders in real-time, communication becomes smoother and more transparent.

In addition to incident and change management, BMC Helix Enterprise Service Management streamlines my daily tasks by providing clear workflows, visibility, and accountability. Features including automated notifications, SLA tracking, and predefined templates reduce the manual workflow and ensure nothing is missed. The dashboard and reporting capabilities also help in tracking recurring issues, workload, and overall team performance, which improves planning and coordination across teams.

BMC Helix Enterprise Service Management offers powerful features for automating repetitive tasks such as ticket classification, routing, and incident prediction using AI and machine learning, which reduces manual work and speeds up resolution. The AI-driven features in BMC Helix Enterprise Service Management have noticeably improved my workflow in several key ways. For example, AI-assisted ticket classification and routing help ensure incidents and service requests are categorized and assigned to the right team more quickly and accurately than manual triage. This has reduced the turnaround time for critical tickets and cut down on manual efforts needed to correct misrouted issues.

Additionally, the AI suggestions during ticket updates, such as recommended solutions based on similar past incidents, have helped accelerate troubleshooting instead of digging through past logs manually. I can review suggested resolutions and apply the one that is most relevant, so issues get resolved faster and more consistently. One feature that I find particularly helpful and sometimes underrated is the integrated audit trail and visibility that BMC Helix Enterprise Service Management provides. Having all actions, updates, approvals, and handoffs captured in a single timeline makes it much easier to track ownership, review past incidents, and support audits or post-incident analysis. This is especially valuable in a production environment where traceability and compliance are important.

Another useful aspect is the flexibility of workflows and templates, which allows teams to standardize processes while still adapting them to specific operational needs. This consistency helps reduce errors and improve collaboration across teams. Overall, these features may not always stand out immediately, but they add significant value in day-to-day operations.

BMC Helix Enterprise Service Management is powerful, but there are areas where I think it could be improved, such as user interface simplification, faster AI learning, and context awareness. While the platform is robust, some users find parts of the interface complex or cluttered, especially for occasional users or business teams outside of IT. A more intuitive, modern UI with simplified navigation could improve adoption.

The AI features are valuable, but in some cases, they can be inconsistent in suggesting the most relevant knowledge articles or resolutions, especially for rare or highly specific incidents. Enhancing context sensitivity and learning speed could increase accuracy. The mobile experience requires enhancement; while the mobile app and mobile interface are usable, performance and responsiveness could be better, particularly when working with large attachments or complex forms on a phone or tablet.

I have been using BMC Helix Enterprise Service Management for four years and one month.

For those considering BMC Helix Enterprise Service Management, I would offer the following advice: Understand and map your processes first. Mapping out your incident, change, and requirement workflows before implementation ensures the platform is configured efficiently and matches your organization's needs. Leverage AI and automation by taking full advantage of the AI-driven ticket routing, predictive insights, and automated workflows to reduce manual effort and improve resolution time.

Invest in training and adoption to ensure teams, including non-IT departments, are trained on the platform to maximize adoption and consistent usage. Start small and scale gradually, beginning with critical IT processes first and then expanding to other business units like HR or facilities, helping in a smooth deployment and avoiding overwhelming users. Finally, monitor and optimize continuously by using the dashboards and reporting to track SLAs, compliance, recurring issues, and team performance, refining workflows regularly for better efficiency.

Overall, I find BMC Helix Enterprise Service Management to be a powerful and comprehensive platform that has significantly improved incident resolution, team coordination, and service delivery in our organization. While there are areas that could be further improved, such as simplifying the user interface, enhancing mobile performance, and making AI suggestions more context-aware, the platform's automation, dashboards, and cross-team visibility make it a valuable tool for both IT and non-IT teams. I would recommend it to organizations looking for a scalable, flexible, and efficient enterprise service management solution. I would rate this product a 9 out of 10.

We are using BMC Helix Enterprise Service Management for raising tickets, handling incidents, handling work orders, and we are using problem and change models as well to manage BAU issues or project-related infrastructure tickets. We are managing all of this through both the DWP and Smart IT portal. It is a very good application.

We have multiple teams, such as level one, level two, and level three. Once a user submits a request from DWP or raises an incident from DWP, the ticket lands to the level one team. Level one team assesses the ticket and assigns it to the concerned teams, or if it is a first level issue, they call the user, assist them, and close the incidents. We have many service requests with workflows already defined for those service requests, allowing them to go directly to the concerned teams without coming first to the level one team.

We have been using BMC Helix Enterprise Service Management for a long time. Even for changes across the organization, whether required at the network level, database level, or any application layer, we are using BMC Helix Enterprise Service Management. We raise change and release modules and use problem management if there are any recurring issues.

Time is saved because of the workflows defined in BMC Helix Enterprise Service Management, and fewer employees are needed.

Earlier we were using HPSM. The challenge we were facing was that we did not have workflows defined. We could not define any workflows in HPSM. We had to do all tickets manually. We had to perform categorization and assign tickets to the concerned teams manually. Now in BMC Helix Enterprise Service Management, we can define a lot of workflows. We can add approval workflows. Many features are available.

The big improvement in BMC Helix Enterprise Service Management is that in HPSM we did not have the mechanism to configure workflows or add approval flows. All tickets and all processes used to have email approvals attached to tickets. I believe that is the big improvement we obtained.

Since we did not have workflows defined earlier, level two was struggling significantly because all service requests were coming to the queue and they needed to assess and categorize them, which took time. Now that we started using BMC Helix Enterprise Service Management and created many workflows and approvals, everything is automatically getting assigned for service requests. It is very helpful for my team because they do not need to assess all service requests. They just need to check the incidents and reassign tickets if necessary.

The main problem I found in BMC Helix Enterprise Service Management is that once a user submits a request, for example, let us say a user has one request for software installation and submits an incident instead of that, it lands in our queue. Since the user raised the incident, it will be incorrect if we resolve it after installing and resolving it as an incident because this is a service request. The main problem that I found is that once we receive the incident, we cannot change it to a work order. That is not possible at all in BMC Helix Enterprise Service Management. However, in HPSM, we had the option to change from service request to incident or incident to service request based on the ticket details. That option is not available here, but still because the workflows are defined, I believe it is more often necessary to educate the users. We need to give the end users training about that. Only then will the wrong categorization of tickets be reduced because our organization has seen a high rate of cancellation tickets because of the wrong catalog.

We started using BMC Helix Enterprise Service Management just two years back.

BMC Helix Enterprise Service Management is stable in my experience.

BMC Helix Enterprise Service Management has good scalability.

The customer support team is great.

Negative

I believe the only other option was ServiceNow before choosing BMC Helix Enterprise Service Management.

To be honest, I have seen and used ServiceNow earlier, and I have learned a lot about that. I believe that has more features than BMC Helix Enterprise Service Management. It would have been easier for the end users as well.

Recently we enabled proactive problem management and incident correlation in BMC Helix Enterprise Service Management. We are still learning, and I believe it will be a very useful tool. I believe HelixGPT is still in the implementing phase. Those things we are testing are currently in the testing phase. Once it is set, I believe it will be great to use.

Proactive problem management in BMC Helix Enterprise Service Management will help not only my team. We have multiple teams with around 1000 users in IT and multiple workgroups. It will help for all the workgroups. I believe it will help to identify recurring issues in real time. Incident correlation will also help us to identify if there is any major incident. HelixGPT depends on the agents as well. Some agents we came across have knowledge creator and navigation features. I believe BMC Navigator will be helpful for both IT users and end users. It will be easier for end users once they get the Navigator option. They will be able to locate and track issue tickets easily. Using HelixGPT, I believe it will be easier for them to understand where the ticket is exactly or what could be the issues. Maybe after HelixGPT, if there are any operational queries and knowledge articles are already created, they might refer to those instead of raising tickets. I believe it will be helpful.

BMC Helix Enterprise Service Management is a very good tool and it will be very helpful for your organization. We have many options in this tool. BMC Helix Enterprise Service Management has many features and is not a limited feature set. They are adding many features, and I believe every update they provide has very good features. I would rate this product a 7 out of 10.

My main use case for BMC Helix Enterprise Service Management is for ticketing and asset management, as well as for change management requests. I have also been optimizing other features on BMC Helix Enterprise Service Management.

For example, I use BMC Helix Enterprise Service Management when there is an issue from the user's point of view, whether on the user's side, the store, or the headquarters. Users will create a ticket and log it, and then I follow up on the issue using BMC Helix Enterprise Service Management to track it. For assets, I use it to track asset movement and to correlate any tickets if they are regarding the asset.

BMC Helix Enterprise Service Management has positively impacted my organization so far, especially for ticketing. In fact, for ticketing, I am still using it as a point of benchmark on how I service the user, whether in the stores or in the headquarters. For assets, I am still populating the data and ensuring that the asset is being properly logged and monitored.

I have seen changes in response time, efficiency, and user satisfaction since I started using BMC Helix Enterprise Service Management. I can monitor my tickets and services, and I am currently trying to minimize breaches in my SLA. I get a lot of benefits from the platform.

Almost more than ninety percent of the tickets are properly within my SLA. That is not good, as I expect ninety-nine percent of SLA, but I am slowly improving.

BMC Helix Enterprise Service Management can be improved because it has a legacy system that needs enhancement. The interface needs improvement because it is not very user-friendly. I have access to so many interfaces that sometimes it is confusing. Additionally, the AI needs to be improved as well.

The AI is still new, and how it can monitor the whole system is not as advanced as I expected. I take note mostly on the interface, because there are so many front-ends, especially for BMC Helix Enterprise Service Management. The company needs to improve it.

I have been using BMC Helix Enterprise Service Management for more than two years.

BMC Helix Enterprise Service Management is stable.

BMC Helix Enterprise Service Management's scalability is very scalable, and I can add more as needed.

The customer support is adequate and within their set SLA, but they need to be more communicative and quicker in responding to my queries.

I previously used a different solution, but it was a small one. I switched because I needed more capabilities on IT service management.

I think the experience with pricing, setup cost, and licensing is quite easy. The pricing is quite fair, but perhaps because I actually buy the whole module, I think for the starter, it is quite expensive. I think the company needs to separate the modules as I need them. Setup cost is acceptable, and licensing is quite easy.

I have not seen a return on investment yet because I am still in development, so I do not see any return on investment. However, I do see some monitoring capabilities. I can monitor my performance, which is quite important for me.

I did not evaluate other options before choosing BMC Helix Enterprise Service Management. I tried to use BMC Helix Enterprise Service Management.

My advice to others looking into using BMC Helix Enterprise Service Management is to first know what you need from BMC Helix Enterprise Service Management, and then it is better to learn about the features so that you can optimize it. I would rate this product an eight out of ten.

My main use case for was for Incident/Request Management, Change Management and Knowledge Base. 

In Incident Management, when an internal user reports a service disruption or system malfunction; either via phone or by sending an email to the IT service desk, a case is logged as an incident. The assigned IT support team then analyzes the incident, performs troubleshooting, and works toward service restoration.

A ticketing system is critical as it captures all incident related communications, actions, and status updates, creating an auditable history linked to the user and/or  device. This historical data supports trend analysis, root cause investigation, and continuous service improvement.

In the context of change management, maintaining proper records was critical. Various IT teams regularly submitted change requests; however, these changes could sometimes have a significant impact on other teams or ongoing operations. For instance, the network team might plan an upgrade of Ruckus switches while the support team is simultaneously supporting a major event.

Change management ensures that when a change request is raised, all relevant teams are notified and given the opportunity to review the proposed change and provide input. If no concerns or queries are raised, the change can proceed through automatic approval. If concerns are identified, cross-functional discussions are conducted to assess risks, dependencies, and scheduling conflicts.

Documenting each step of the change process is essential for auditability, historical reference, and rollback purposes in the event that a change causes service disruption.

BMC Helix Enterprise Service Management positively impacted our organization by improving visibility, control, and coordination across teams. Its strong reporting and categorization enabled better analysis of incidents and requests, helping us identify trends and allocate resources more effectively.

The platform enhanced SLA tracking through clear dashboards, resulting in fewer breaches and improved service uptime. It also reduced incident resolution times by helping us quickly identify service-wide issues and prioritize responses. Overall, BMC Helix helped us manage services more efficiently and deliver more reliable outcomes.

One of the strongest features of BMC Helix Enterprise Service Management was its reporting module, which stood out as the most valuable capability of the platform. The solution offered nine distinct categorization layers, including operational and product-based categories, which could be combined to generate highly meaningful reports. This structured categorization, together with the reporting module, significantly simplified our work.

During the launch of our ERP system, which included multiple modules such as HR, Finance and Supply Chain, we leveraged these product categories effectively. The hierarchy was structured with the Business Application as the primary category, followed by ERP, and then Oracle. The operational category further classified items into issues or requests. Under issues, we categorized items such as dashboards, reports, how-to requests, and queries, with an additional tier for specific dashboards. This multi-tier categorization proved extremely useful during reporting, as it gave us clear visibility into areas with the highest number of issues or requests, enabling us to allocate resources more effectively.

Additionally, the user interface allowed us to enable cost tracking, effort hours, and tier services into categories such as Gold and Silver, which added significant operational value.

At the individual team level; whether IT support, infrastructure, network, or security, the impact was minimal, as these teams were already collaborating effectively. However, the real value emerged in cross-team coordination. With BMC Helix in place, all teams had full visibility, and tasks and subtasks could be assigned across teams to support broader organizational objectives. This became even more effective when we onboarded HR modules into the system. We were able to add HR services and agents with restricted visibility, ensuring that IT managed the system while HR retained ownership of policies.

Incident resolution and SLA management became far more controlled due to the platform’s dashboards. Managers and CIOs had clear, real-time visibility into SLA performance, including the ability to track potential breaches within defined timeframes. As a result, we achieved fewer SLA breaches, maintained ninety-nine percent service uptime, and significantly improved service reliability.

BMC Helix Enterprise Service Management also excelled in accelerating service restoration, reducing incident resolution time, and maintaining service availability. When multiple incidents were raised across different locations, the system helped us quickly identify service-wide outages and focus our efforts where they were most needed. Rather than reducing resources, the platform enabled us to manage them more efficiently, which was one of its greatest strengths.

From my perspective, the main area for improvement in BMC Helix Enterprise Service Management was the separation between incident and service request records. These were maintained as two distinct tables with different ticket numbers. If a common or linked ticket number had existed, it would have been much easier to relate incidents to service requests or convert one into the other. In practice, closing an incident and raising a service request resulted in a new ticket number, which often caused confusion as users would continue following up on the original ticket while updates were being made on the new one. Having interchangeability or a stronger linkage between incidents and requests would have been a valuable enhancement.

I rated the solution seven out of ten. Aside from the lack of interrelated incident and service request records, I had no major concerns from a user perspective.

The rating was also influenced by licensing considerations, as other tools in the market offered more flexible licensing models, such as concurrent usage. At the time, BMC Helix Enterprise Service Management did not allow reducing the concurrent session timing below ten minutes, which could have improved cost efficiency within the pricing model.

2 Years

In my personal experience, I have never experienced any downtime or reliability issues with BMC Helix Enterprise Service Management.

BMC Helix Enterprise Service Management was pretty scalable. As I mentioned earlier, we added the HR module under the same tenant, and it was pretty much scalable. They have scaled it up higher to finance and other modules already.

We had our local partner in the UAE, Magnoos Services. If we had any issues or new requests, we would reach out to them. I think they were very good partners, and we generally did not reach out to BMC Helix Enterprise Service Management directly.

I joined the organization when BMC Helix Enterprise Service Management was already in place, and it remained the same throughout my tenure; there was no system transition during that time. However, I have personally been exposed to and worked with other ITSM solutions.

I am really not sure how BMC Helix Enterprise Service Management was deployed in my organization as this was before I joined. I joined as an admin, and these deployments were mostly handled with the infrastructure team.

Yes, BMC Helix improved efficiency, reduced SLA breaches, and maintained ~99% service uptime, enabling faster issue resolution and better resource allocation.

From what I heard from procurement and management, BMC Helix Enterprise Service Management overall is a costly setup. However, since I am in the support and administration team, I do not have much visibility over the cost.

I think the competitor BMC Helix Enterprise Service Management was evaluated against was ServiceNow.

The only advice I would give from my experience is to categorize the nine available categories properly, as they will be very helpful for reporting.

We are a partner for OpenText and BMC, and this is our main professional service delivery. We are the professional service delivery arm for both of them.

I am responsible for the ITSM products, such as OpenText SMAX, Helix ITSM, and others.

It is not only ITSM, it is an ESM as well.

It is mainly the DWP. And the ITSM modules, IAM, incident, request, change, and others. Mainly for the ESM, the most beneficial layer is the interfacing layer of the DWP, the Digital Workplace. And actually the advanced service catalog.

The underlying work orders and workflows of the service catalog are a mainly critical point for the ESM and even the interface for the ITSM tool as well.

Recently, it is good. It is promising. It is still not totally amazing. Even for BMC, for OpenText, for ServiceNow, for all the vendors, it is a booming technology. And all vendors are trying to integrate it inside their ITSM tools. Still, there are some limitations, especially related to the Arabic language, especially for the Middle East. The LLM language model and LLM models are not supporting Arabic for most of the tools. So this is a weakness. However, I can see some vendors are still working on this point right now because there are LLM models in the market supporting Arabic.

For automation, you have multiple tools depending on the vendor. For example, for OpenText, we have an OO integration, Operation Orchestration with SMAX. For BMC, we have Control-M as well, and can automate some items. All vendors as well inside their portfolio are considering the automation. It is not a native function inside the tool, but actually within the portfolio with seamless integration. It fits for purpose.

It is perfect, unless there is the support of the Arabic language. Supporting the Arabic language is the critical point, especially for ESM more than ITSM. Because for the ITSM, most of the IT staff can handle the English or any language besides Arabic. But when you are targeting the ESM, you are targeting the HR team, the finance team, the maintenance team. Not all these teams treat with English terminologies or report their cases with English. At this moment, the Arabic language or their native Arabic language should be considered and it will be more important inside the chatbots. I would prefer to chat with my own language.

Enhancing AI support for the Arabic languages, enhancing the automation of the ticket, and automation of the ticket workflows would make it simpler for implementation and simpler for enhancements. Adding more capabilities for adding more flexibility of the customization is important. This is not only for BMC, even for OpenText, even for ServiceNow. As long as you are moving to a low-code platform, you are limiting my capability to customize. The solution will be fit for purpose perfectly for a low-customization environment. However, it is a limitation for the low-code environments. All low-code environments have limitations when customizing. When you compare, for example, in OpenText, when you compare SMAX to the legacy Service Manager, Service Manager has more capabilities for customization, more than SMAX. This is the same between Helix and Remedy. Overall, BMC still has a very powerful way to customize. It still has a very good customization capability.

For the last 10 years.

All vendors have several plans for support, for supporting models. From premium to standard, advanced. It depends on the supporting package you purchased. For example, if you are talking about premier support in OpenText or BMC or whatever, and you have a dedicated resource, the response time will be much better. The initial phases of investigation will be very short because you have a dedicated, assigned resource who is understanding your environment, already knows your environment, already knows your understanding and your needs, so it will be much better.

Also, for the support of BMC, especially for BMC Helix on cloud as a software-as-a-service, the support will be faster than the response in investigating an on-prem solution. This is crucial for the troubleshooting of the infrastructure or a bug. For example, if a system is down totally, I am not talking about software enhancements or an issue inside the tool itself, but talking about if a system is down or if you have a critical ticket, BMC Helix SaaS is very good for support, more than support for on-prem. This is the same for ServiceNow, same for OpenText, same for everything. It is about the SaaS supporting model because the resource is already understanding or well-understanding the infrastructure deployment that happened on the cloud, on their cloud.

Negative

All vendors can compete with their pricing. All vendors for the same class, for example, if you are talking about the world-class such as BMC, ServiceNow, OpenText, all of them can compete in front of each other. I am not talking about the same price for medium-scale such as ManageEngine or smaller tools. But for the same scale of the vendors, almost all of them are near to each other.

In my last company, during a tenure of around one year, I used BMC Helix Enterprise Service Management where I explored this functionality and went through many improvements.

As I was in the infrastructure management team, my team and I utilized BMC Helix Enterprise Service Management for ticketing purposes. Similarly, I was the system analyst, so I used to explore some reports and export import functionality.

At the starting of my career, I utilized ServiceNow. Then I moved to Mahle, where I got to know about BMC Helix Enterprise Service Management. Based on our regular operations, ticketing handling and asset management, we used this tool. This was a very fantastic experience for me in my last company with this tool.

BMC Helix Enterprise Service Management has really shaped Mahle, my last company, and their IT operations support system in a very formal way. The entire Mahle global team has adopted this tool. BMC has also given an excellence award to the Mahle team.

I noticed the resolution time improved because once the ticket falls into the bucket of the engineer, the engineers proactively contact the user. The communication mode became a very good option for this. Users are satisfied because they do not have to contact any person directly. They only have to create a ticket and someone from the IT team will reach out to them directly. This is a very good result and response from the users.

The ticketing system in BMC Helix Enterprise Service Management has a user interface. Once the user submits a ticket, the ticket is created and automatically routed based on the category that the user has selected. Since we were the on-site IT team, if the issue is related to on-site IT, it directly falls into our bucket. Once it is in our bucket, we acknowledge that ticket and assist the user. Similarly, every day, I used to export the whole open tickets and on-hold tickets, and I used to give a quick review of why the ticket is pending and how long the SLA is.

BMC Helix Enterprise Service Management provides a good and user-oriented interface. From the data perspective, it is also very useful to easily create and export the reports whatever you want. Overall, the interface, as well as the reporting and the operation inside, front end and back end is very good.

In a company, the non-tech people always want a very user-friendly portal where they can create a ticket regarding their issue. BMC Helix Enterprise Service Management has provided that user-friendly interface for the non-tech people. Similarly, for us as tech people, whatever we use, minor or major information, we are getting properly.

All functionality that is available in BMC Helix Enterprise Service Management is very good. What they can do is enhance some AI tool so that the entire system can easily move into automation.

In my last company, during a tenure of around one year, I used BMC Helix Enterprise Service Management.

At the starting of my career, I utilized ServiceNow. Then I moved to Mahle, where I got to know about BMC Helix Enterprise Service Management.

Being a technical person and a non-technical person as well, what I actually used to get from a portal related to ITSM made me give BMC Helix Enterprise Service Management a perfect score. I rate BMC Helix Enterprise Service Management with a score of 10 out of 10.