I give the solution an eight out of ten.

I'm wondering if it's possible to use cloud-based eCommerce with our on-premise system. Is there a way to integrate the two, or are they incompatible?

I'm going to standardize everything and not go for a lot of software or a lot of solutions from different vendors. I prefer just scalable solutions. We cannot deny that all things, CRP included, have some weaknesses. This is easy to implement using Oracle, but that's why we can complement this weakness with one from some other vendors who have the domain in manufacturing in a specific industry.

Our eCommerce module needs to be seamlessly integrated with other modules, taking into account our huge product inventory and the fact that we have customers both from the B2B and B2C sectors because our B2B sector is the largest. We also have other considerations, like getting products from suppliers.

I am unsure at this point in time whether I will be able to provide any recommendations regarding Oracle CRM.

Based on the performance and satisfaction experienced by those who use Oracle CRM, while also considering whether there are multiple issues reported frequently or not, I rate the overall tool an eight out of ten.

It is one of the top CRM applications of all time. It covers most of the CRM activities. When you implement Oracle CRM, you will get good benefits.

I would rate it a nine out of 10.

Oracle is focusing on Fusion CRM. Overall, I rate the product a seven out of ten.

I rate the overall solution a seven out of ten.

Oracle CRM has become an old technology in the market, so most of our company's customers have moved on to products offered by Salesforce.

I recommend the solution to those who plan to use it.

I rate the overall solution a seven out of ten.

We would recommend the solution only for enterprise clients. It is not suitable for small and medium businesses. It is a good solution. Overall, I rate the product an eight out of ten.

I would rate the solution a nine out of ten. 

I'm not sure which version of the solution we're using. We have a team that maintains it directly. I am simply an end-user.

I'd rate the solution seven out of ten.

Oracle technical developers and function skill sets are required for the solution's maintenance and project deployment.

I would not recommend Oracle CRM to other users because it is outdated.

Overall, I rate Oracle CRM a four out of ten.

I recommend Oracle CRM for large-scale organizations. I rate it an eight out of ten.

I would recommend Oracle CRM, as it is a user-friendly solution. I rate it eight out of ten.

I rate Oracle CRM an eight out of ten.

I recommend the product, but only if you are planning to have a longterm contract.  I understand that there are other solutions on the market and they might be cheaper but if you like to have a long-term contract and you like to integrate Oracle is the best option.
Furthermore, If you don't have the intention to integrate with any ERP, then this is one of the best options, together with Salesforce. In our case, we prefer to have the product for the same vendor. That's why we didn't choose Salesforce, even though Salesforce might have a better recommendation or a better ranking. Both of them, Salesforce and CX are on the top five worldwide and in the Cloud.

We are planning to put CX in another plant during this next year, 2021. And we are very happy with the product.

I rate Oracle CRM a nine out of ten.

We choose this solution because we use the Java language for our Oracle database and having our CRM be from Oracle would have beneficial integration to ensure stability.

My advice to others is they should use the solution, it is priced well and Oracle is a good company.

I rate Oracle CRM a nine out of ten.

I would definitely recommend Oracle CRM to anybody thinking of using it, and I would rate it eight out of ten.

• Identify one or more key ‘super users’ for leading the implementation or managing the product. These would be your go-to people for expert help.

• If you need to bring in outside help for the implementation, then do so. This will help in getting you the best help at the time you need it most.

• Prepare and train your organization for the change.

During the selection process for a CRM product, something that I have witnessed first hand, sufficient attention must be given to how the CRM application integrates with the back end applications. While it is important to consider the capabilities of the CRM applications in its own specialized areas, at some stage in the process the transactional information will have to be passed on to back end or other applications to complete the processing cycle - for Sales it would be Orders, for Service it would be service requests and tasks. At the heart of it all is integration with customer master data. A key aspect here is whether organizations are factoring in the cost of this integration with the other applications in the flow.

I will illustrate my point with the following case scenarios - from ideal to not-so-ideal

Case 1: In this case the selection process evaluates the CRM application for features and capabilities to their specific needs. The selection process includes considerations for integrating the CRM application data with the other applications to complete the end-to-end process flow and for master data, and including the folks in IT in the discussions to identify the integration that will be necessary for a sustainable on-going operation, and factors this cost and time into the overall cost of the CRM application. The estimation is realistic and considers all aspects of the applications involved in the flow. The cost aspects include one-time costs as well as ongoing costs for sustained operations. This would be the ideal scenario.

Case 2: In this case the selection process evaluates the CRM application for features and capabilities to their specific needs, but only with the relevant end users, for eg. with predominant opinion of Sales or Marketing users only. This process does not list out the potential integration with other applications, does not include IT or other team members to evaluate the requirements or effort and leaves these aspects as a post-implementation effort. With such a process only the immediate needs of the CRM application are considered. As it becomes evident later, the need for adding on integration with other applications are brought up and dealt with as and when the need arises, many a time overwhelming the resources of IT or other resources and discovering blind alleys of integration, with incompatible interfaces, ad-hoc methods to back file such requirements, leading to a very messy after-thought for building consistent and efficient business processes. I have witnessed these myself in more than one implementation. Not only have I seen such after-thought Integration of transactional data, I have even worked on efforts to integrate master data, such as customer data, exposing weaknesses of both applications. There was one case where the CRM application was set operational with one-time setup of customer master data from the back-end application with no thought given to ongoing processes for continuous synchronization of data between the two systems - the CRM application and the back end Order fulfillment application with customer master data.

Case 3: This case is just a more extreme variation of Case 2. In this case the selection process evaluates the CRM application on its own, as in Case 2. There is no effort to list out the potential integration or even the need for integration. The administration staff are left to manage the integration with manual maintenance of data on the related applications and doing manual synchronization. This is a very poor use of technology.

Case 4: This case is becoming more and more an attraction to the people in Sales and Marketing areas. In this case the selection process evaluates the CRM application for features and capabilities with an eye on all the third party integration solutions to the core CRM product - the 'app' attraction. The 'app' era has led to third party solutions, the ultimate version of best-of-breed - the core CRM solution for customer and contact data, an app for emailing solutions, an app for data mining, an app for social app integration and so on. The integration aspects of such solutions are considered on an ad-hoc basis with no forethought to process consistencies. With data and processes in such diverse environments it is anyone's guess whose job it is to manage the different flows of data, if that is even possible by the company's IT. One recent case I came across where the company engaged with a third party to manage its diverse applications on the cloud! In conclusion, fully integrated platforms with CRM applications are at the one end of the spectrum of integrated solutions while the CRM cloud applications with third party integrating applications are at the other end. Each organization needs to evaluate which point in the spectrum makes most sense for it, not just in the short run, but in the long run also, before jumping in to settle down on the solution. Making a choice that is short sighted hides the long term cost of use and short changes business objectives while costing the organization in never ending efforts to shuttle data between systems to achieve key business visibility to what is really happening

I installed the demo six months ago. I was using some variance of version 12. Eighter 12.0.8, 0.2, 0.8 or 0.9.

I recommend solutions according to the client's business needs. If they need something that is more flexible and giving them all that they need on-premise, I will advise them to get it. If they are needing a lot of functionality that's related to other products, or clouds, I will recommend other options that aren't Oracle.

I'd rate the solution nine out of ten.

I would rate this solution a nine out of ten.

I suggest people try using the product to see if it fulfills their needs. Oracle CRM can be a good solution for people with many end users and a lot of data they need to process. Overall, I rate the solution a seven out of ten.

If you are looking for a solution to be deployed on-premise and need a scalable solution for a Silicon Valley, telecon or banking company, I would recommend Oracle. This is because Oracle offers stability, plug and play functionality and integration to billing systems. 

If you are looking for solution for a medium-size e-commerce company or OEM, I would recommend Salesforce or SAP. Before deciding on the right solution, it is important to map out all of your requirements and the level of customization needed. 

I would rate this solution an eight out of ten. 

The product has very good quality to price, has a stable and powerful configuration, and allows your business to fulfill the required processes.

I wouldn't recommend Oracle CRM for everybody, but it's good for those with big requirements. I would rate CRM as eight out of ten.

I rate the solution an eight out of ten. The solution is good, but the pricing could be cheaper.

I would recommend this solution. I would rate this solution 7 out of 10.

It is a good product with broad functions and industry-specific coverages.

I don't know if we plan to keep using this solution. I know our company likes the product and wants to use it. 

I would recommend this solution. It is a really solid and useful product, but to really take full advantage of this solution, you should be a really big sized company. It is an excellent product for big companies that manage so much data. It is not a cheap solution, so be sure that your company size is aligned with this kind of product.

I would rate Oracle CRM a nine out of ten.

I rate Oracle CRM a seven out of ten.

I would rate Oracle CRM a nine out of ten.

I would rate Oracle CRM an eight out of ten.