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.
BMC Helix Enterprise Service Management is a strong enterprise platform. There is no doubt about that. However, there are areas where it could improve. One key area is usability and simplification of configuration. For new users or teams onboarding the platform, the learning curve can be somewhat steep due to the depth of customization available. Improving UI responsiveness and making certain administrative tasks more intuitive would enhance the overall user experience. Additionally, clearer documentation and more guided configuration templates could help organizations implement best practices faster. These improvements would make the platform even more accessible while maintaining its enterprise-grade flexibility. I provided a rating of nine out of ten because, while BMC Helix Enterprise Service Management is a robust, scalable, and feature-rich enterprise platform with strong automation workflow capabilities, there is still room for improvement in areas such as usability, UI experience, responsiveness, and onboarding simplicity.
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.
IT Systems & Support Engineer at a comms service provider with 501-1,000 employees
Real User
Top 20
Jan 17, 2026
BMC Helix Enterprise Service Management could use improvements on the dashboard; having a ready-to-use dashboard that just needs asset information instead of building one from scratch would be helpful. The lack of templates for dashboards and limited email notification customization are also areas needing attention.
Manager, Information Technology Support & Service Delivery at a university with 1,001-5,000 employees
Real User
Top 10
Jan 15, 2026
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.
Learn what your peers think about BMC Helix Enterprise Service Management. Get advice and tips from experienced pros sharing their opinions. Updated: March 2026.
There are several areas where BMC Helix Enterprise Service Management could be improved. Currently, ServiceNow has an edge when it comes to the ease of discovering Configuration Items (CIs). In BMC Helix, there are issues with the Configuration Management ( /categories/configuration-management ) Database (CMDB ( /categories/configuration-management-databases )), such as duplicate entries and problems with reconciliation. The recently introduced dashboard tool in Helix, which replaced Smart Reporting ( /categories/reporting ), has several issues. Reporting ( /categories/reporting ) has been a consistent problem in BMC, and it would greatly benefit from enhancements.
BMC Helix Enterprise Service Management offers intelligent automation, customizable workflows, and improved SLA management with seamless communication in IT service management, enhancing ticket classification and routing efficiency.BMC Helix Enterprise Service Management integrates AI-driven automation and supports multi-cloud infrastructure discovery, improving operational efficiency and reducing manual errors. It enhances collaboration and decision-making with robust change and incident...
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.
BMC Helix Enterprise Service Management is a strong enterprise platform. There is no doubt about that. However, there are areas where it could improve. One key area is usability and simplification of configuration. For new users or teams onboarding the platform, the learning curve can be somewhat steep due to the depth of customization available. Improving UI responsiveness and making certain administrative tasks more intuitive would enhance the overall user experience. Additionally, clearer documentation and more guided configuration templates could help organizations implement best practices faster. These improvements would make the platform even more accessible while maintaining its enterprise-grade flexibility. I provided a rating of nine out of ten because, while BMC Helix Enterprise Service Management is a robust, scalable, and feature-rich enterprise platform with strong automation workflow capabilities, there is still room for improvement in areas such as usability, UI experience, responsiveness, and onboarding simplicity.
I have not identified any features that would be required at the moment for BMC Helix Enterprise Service Management.
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.
BMC Helix Enterprise Service Management could use improvements on the dashboard; having a ready-to-use dashboard that just needs asset information instead of building one from scratch would be helpful. The lack of templates for dashboards and limited email notification customization are also areas needing attention.
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.
There are several areas where BMC Helix Enterprise Service Management could be improved. Currently, ServiceNow has an edge when it comes to the ease of discovering Configuration Items (CIs). In BMC Helix, there are issues with the Configuration Management ( /categories/configuration-management ) Database (CMDB ( /categories/configuration-management-databases )), such as duplicate entries and problems with reconciliation. The recently introduced dashboard tool in Helix, which replaced Smart Reporting ( /categories/reporting ), has several issues. Reporting ( /categories/reporting ) has been a consistent problem in BMC, and it would greatly benefit from enhancements.