Senior Manager / IT Planning & Architecture Services at a comms service provider with 10,001+ employees
Real User
Top 20
2024-08-20T13:26:00Z
Aug 20, 2024
The only challenge was that we implemented it in our on-premise data center instead of using it in the cloud. That was a little bit of a challenge. But it was overcome with the help of SugarCRM company, and it was implemented. And we are moving ahead, using it. I would appreciate it if SugarCRM could support us in on-premise implementation also because we are using their product. They are the principal vendors, so they should be able to support us whether we are using it in the cloud or on-premise.
One area where SugarCRM could improve is its UI. While it is already user-friendly, a slight enhancement in UI design, especially in terms of color combinations, could make the platform more visually appealing and comfortable to use. This would help create a more engaging and pleasant user experience without changing its excellent features. I don't have any specific ideas for new features in the next SugarCRM release because the platform is already very flexible. Users can create their own solutions like field services and quality management, making it suitable for a wide range of needs.
Sugar Enterprise could improve by removing bugs and glitches. For example, a comment was made but in the comment section, it was never displayed. However, the problems we faced might not be the fault of the solution. In order to export graphics or add tasks, it could at times be more difficult than other functionality. In the next release, the color scheme of the interface could be better. I found it bland and it could be better.
There are no aspects really lacking in the solution. We are quite satisfied with how we are able to use it with Jira. At the moment, there is a complicated flow in regards to the user's permissions and what they can see. For example, if a broker has multiple NTDs and you want to distinguish your employees to see specific customers, this is not a default with Sugar. It means that your developer needs to create custom teams and give custom permissions. You cannot include all your entities under one instance at the moment.
SugarCRM is a versatile CRM solution that facilitates communication and organization within a company. Its primary use case includes call and comment logging, account relation, customer detail storage, verification handling, transaction tracking, marketing material management, and payment transaction handling. The most valuable functionalities include customizable exports of graphics, statuses, complaints, and tasks, as well as its scalability, stability, and low cost. It integrates well with...
The only challenge was that we implemented it in our on-premise data center instead of using it in the cloud. That was a little bit of a challenge. But it was overcome with the help of SugarCRM company, and it was implemented. And we are moving ahead, using it. I would appreciate it if SugarCRM could support us in on-premise implementation also because we are using their product. They are the principal vendors, so they should be able to support us whether we are using it in the cloud or on-premise.
One area where SugarCRM could improve is its UI. While it is already user-friendly, a slight enhancement in UI design, especially in terms of color combinations, could make the platform more visually appealing and comfortable to use. This would help create a more engaging and pleasant user experience without changing its excellent features. I don't have any specific ideas for new features in the next SugarCRM release because the platform is already very flexible. Users can create their own solutions like field services and quality management, making it suitable for a wide range of needs.
Sugar Enterprise could improve by removing bugs and glitches. For example, a comment was made but in the comment section, it was never displayed. However, the problems we faced might not be the fault of the solution. In order to export graphics or add tasks, it could at times be more difficult than other functionality. In the next release, the color scheme of the interface could be better. I found it bland and it could be better.
There are no aspects really lacking in the solution. We are quite satisfied with how we are able to use it with Jira. At the moment, there is a complicated flow in regards to the user's permissions and what they can see. For example, if a broker has multiple NTDs and you want to distinguish your employees to see specific customers, this is not a default with Sugar. It means that your developer needs to create custom teams and give custom permissions. You cannot include all your entities under one instance at the moment.
It lacks customization, and this is the main reason that we are switching to a different solution.
The interface could be more user-friendly. I would like to see more integration on a mobile platform in the next release.
In the next release, I would like to see personalization of information about customers or specific businesses or opportunities.