Oracle CX Sales Reviews

My main use case for Oracle CX Sales is that we use it but not on a daily basis. When we do use Oracle CX Sales, it is for the CRM customer engagement application from Oracle that helps organizations manage sales, marketing, customer services, commerce, and customer data. For sales, we use Oracle Sales Cloud, and for service, we use Oracle Service Cloud, and for marketing, we use Oracle Eloqua. For commerce, we use Oracle Commerce. Then for CPQ, we use Oracle CPQ. For customer data platform, we use Oracle Unity.

The best features of Oracle CX Sales include the Customer 360 view, allowing us to have all customer information in one place, including account, contact, opportunity, activities, and service history linked together. Another key feature is lead and opportunity management, tracking leads from creation to conversion, managing the entire sales pipeline and deal stages, and performing sales forecasting, which helps predict revenue and track performance. Managers can monitor team performance and pipeline health, utilize AI-powered recommendations to suggest next best actions, identify high-priority opportunities and potential risks, along with workflow automation, reporting, and dashboards.

In Oracle CX Sales, we actively use core features such as lead management, account managing, contact managing, opportunity management, and we track activities like calls, emails, meetings, sales forecasting, territory management, and pipeline management. We also use advanced features like the Customer 360 view, AI-based opportunity scoring, and next best action recommendation, although there are other available features that we do not rely on much.

Oracle CX Sales has improved visibility into the sales pipelines, standardized our sales process, and provided a single source of truth for customer data. Sales teams can track leads and opportunities more effectively, managers gain better forecasting capabilities, and workflow automations reduce manual efforts. The AI-driven capabilities also help prioritize high-value opportunities and improve sales productivity.

The biggest friction point I have encountered with Oracle CX Sales has been user adoption, as sales teams are accustomed to using separate sheets, emails, or legacy CRMs, making it difficult to run and maintain data consistency. Data migration issues arise when customer data comes from multiple systems, leading to duplicates, incomplete, or inconsistent records that need to be cleaned. Additionally, the integration complexity of connecting with ERP, marketing, and other enterprise applications requires ensuring real-time synchronization, addressing varying business needs, and reaching agreement during workshops can take time. Change management is also challenging, as users often resist change and require additional communication and training to stabilize processes.

If I could change one thing about Oracle CX Sales to make my workflow easier, it would be to simplify some of the configuration and customization projects. While Oracle CX Sales is very powerful, certain customizations and integrations can require advanced expertise, increasing implementation times and complexity. I would also simplify the user interface to enhance the experience for occasional users, as new users sometimes need additional training.

I have been familiar with Oracle CX Sales for around two or three months.

Before our team adopted Oracle CX Sales, we were using various CRMs. As an Oracle CX functional consultant, I conducted requirement gathering workshops with business users, configured lead, account, contact, and opportunity processes, designed sales processes and approval workflows, configured directory sales stages and forecasting, and created reports and dashboards. I also supported user acceptance testing (UAT) and user training, and assisted with go-live and post-production support. As an Oracle CX technical consultant, I developed integrations using REST/SOAP APIs, worked with Oracle Integration Cloud, created custom objects and fields, developed Groovy scripts for validation and automation, performed data migration and data loading, and managed security roles and user provisioning.

When our team first implemented Oracle CX Sales, it took around two to three months for small basic projects, four to six months for medium projects, and six to twelve months for large projects. The implementation timeline depends on the size and complexity of the projects. For requirement gathering, we take two to four weeks to understand the sales process, identify customization and integration needs, and design and configure the system. We configure leads, accounts, opportunities, set up security and workflows, integrate with ERP and marketing systems, develop Groovy scripts and custom objects, and for data migration, it typically takes two to six weeks to import accounts, contacts, opportunities, and historical data.

When our team was getting started with Oracle CX Sales, people needed formal training. The workshops during the requirement gathering phase can take longer than the actual configuration work, with the typical background for the discovery workshop taking four to twelve weeks, configuration development from four to eight weeks, and testing and training from two to six weeks. Workshops take time because the team needs to understand the current sales project, identify gaps, define the future state processes, and agree on workflow and approval processes.

We observe that after implementing Oracle CX Sales, there is approximately a 15% to 20% improvement in lead conversion, a 20% to 30% increase in sales, and around a 30% to 40% reduction in manual reporting effort. Forecast accuracy has significantly improved because managers have real-time insights into the pipeline.

Before choosing Oracle CX Sales, we considered other common CRMs that were used before migrating, such as Salesforce, Microsoft Dynamics 365, Siebel CRM, SAP CRM, SugarCRM, and a legacy in-house CRM. The organization was using Salesforce and Dynamics before implementing Oracle CX Sales, which was selected to better align with the company's Oracle systems, improve integration with ERP systems, and provide a unified customer and sales management platform.

For someone considering Oracle CX Sales who has a workflow similar to mine, I would advise focusing on strong lead and opportunity management, the Customer 360 view, AI-driven forecasting and insights, robust reporting and analytics, and ensuring excellent integration with Oracle ERP and the Oracle ecosystem. I would rate my overall experience with Oracle CX Sales as an 8 out of 10.

The main use case for Oracle CX Sales is helping teams manage customer interactions, sales pipelines, and reporting in one centralized platform. For example, in analytics-driven environments, sales and operational teams need visibility into customer activity, opportunities, forecasts, and performance metrics. The platform helps organize that information and makes it easier to track pipelines, progress, and generate insights. A practical example would be using dashboards and reporting features to monitor sales performance and support forecasting decisions.

The best features of Oracle CX Sales that got used most were definitely the dashboarding, pipeline tracking, and reporting features. I appreciated being able to quickly see customer activity, opportunity status, and overall workflow process without digging through spreadsheets or separate updates. That visibility made day-to-day coordination much easier. The reporting side was also really useful, especially for tracking trends and supporting forecasting discussions. Since my background is more analytics-focused, I probably used the reporting and data visibility features the most. Another feature that helped considerably was centralized activity tracking because everyone could work from the same information instead of relying on scattered emails or manual updates.

Oracle CX Sales has impacted my organization by improving visibility and better coordination across workflows. Before using a centralized platform, many customer updates, reporting, and tracking were handled manually through spreadsheets and separate communication channels. With this solution, the teams had a single place to manage customer information, pipeline updates, and reporting, which made collaboration much smoother. It also reduced manual reporting effort and made forecasting discussions more data-driven because the information was more organized and easier to access in real-time. From a day-to-day perspective, it helped teams respond faster, stay aligned, and spend less time chasing updates or reconciling data from different sources.

The biggest friction point or frustration I encountered with Oracle CX Sales is the complexity at times, especially when navigating deeper workflows or trying to customize reports and processes. The platform is powerful, but can be challenging to work with in these areas.

The adoption of Oracle CX Sales was more at the team and department level, especially among groups involved in sales operation, reporting, and workflow management, rather than the entire organization using it the same way. There were definitely different levels of users. Some users were more casual users who mainly updated customer information, tracked activities, or viewed dashboards. Other users were more advanced or power users who handled reporting, workflow customization, and deeper operational processes. In my case, I interacted with the platform more from the analytics and reporting side. I was working more with dashboards, workflow visibility, and data-related processes rather than just CRM updates. Overall, adoption improved over time as teams became more comfortable with the workflows and started seeing the value of having centralized customer and operational data in one platform.

Before implementing Oracle CX Sales, many things were handled through spreadsheets, email updates, and separate reporting files. For example, teams were manually tracking customer interactions, updating sales progress, sharing status updates, and compiling reports from different sources. That made it harder to keep everything consistent and up-to-date, especially where multiple people were involved. A big challenge was information visibility because the information was spread across different tools and files. Reporting and forecasting took more manual effort, and people had to spend extra time following up for updates or reconciling data between systems. With Oracle CX Sales, much of that has become more centralized. Customer information, pipeline tracking, reporting, and workflow updates were all available in one place, which reduced manual coordination and improved overall efficiency.

When I first implemented Oracle CX Sales, the initial setup and onboarding process took a few weeks before workflows were fully stable and integrated into day-to-day operations. Basic functionality and user access were available fairly quickly. However, configuring workflows, integrations, and reporting structures and getting teams comfortable with the platform took additional time. A lot of that timeline depended on the customization required and how many existing processes needed to be connected into the system. Overall, getting the core platform running was relatively straightforward, but optimizing workflows and adoption was more gradual over time.

Oracle CX Sales required formal training for my team, so there was definitely some learning involved. Formal onboarding and training were helpful in the beginning. Basic tasks were fairly easy to pick up, especially for users focused mainly on dashboards, reporting, or day-to-day workflow updates. Because Oracle CX Sales has many features, workflows, and customization options, teams needed some time to fully understand how to use it effectively. From my experience, once people got familiar with the interface and workflows, it became much more comfortable to use. Overall, it was not extremely difficult, but initial training definitely helped ensure adoption and efficiency.

While I do not have exact company-wide numbers for Oracle CX Sales, there were definitely noticeable efficiency improvements. From the workflows I was involved with, having centralized tracking and reporting probably saved the team several hours every week that would otherwise be spent manually updating spreadsheets, reconciling information, following up across emails, and separate systems. For reporting and operational coordination, I estimate workflow efficiency improved by around twenty to thirty percent, mainly because the information became easier to access and updates were more consistent across teams. It also reduced delays in reporting and forecasting decisions since teams were working from the same real-time data instead of manually compiling updates from different resources.

When evaluating options, there were discussions around other CRM and sales workflow tools, including lighter CRM systems and more spreadsheet-based processes that the teams were already familiar with. The main evaluation criteria was how well the platform could handle centralized customer management, reporting, workflow visibility, and integration with analytic processes. Oracle CX Sales stood out more from an enterprise perspective because it offered stronger workflow management, reporting capabilities, and scalability for larger operational environments. Compared to more manual or lighter solutions, it provided better visibility across teams and reduced the amount of disconnected tracking and reporting work.

From a day-to-day perspective, Oracle CX Sales helps in my work by having centralized sales and customer data that made reporting and collaboration much more efficient instead of teams relying on separate spreadsheets or disconnected updates. From a workflow perspective, it helped teams respond faster because information was easier to access and monitor. In analytics-focused work, having cleaner and more organized data improved reporting quality and forecasting accuracy in my day-to-day work.

The scope of what I was doing in Oracle CX Sales was more of a team-wide workflow rather than something running completely on my own. From my side, I mainly interacted with it through reporting, automation, and operation workflows connected to analytics and data processing. Different teams were involved in various parts of the workflow, including reporting, operations, and data handling. The platform helped coordinate tasks and keep processes centralized. My involvement was more around automated workflows, monitoring processes, and using the outputs for reporting and analysis rather than owning the entire platform myself.

What made my team choose Oracle CX Sales specifically over the other tools considered was the combination of workflow visibility, reporting, and scalability. Some of the other options felt either too basic or too dependent on manual tracking. Oracle CX Sales seemed better suited for environments where multiple teams needed access to the same customer and operational data in one place. Since much of the work involved reporting, forecasting, and coordination across workflows, having stronger analytics and centralized tracking made a significant difference. It felt more organized and easier to scale as workflows became more complex.

During implementation of Oracle CX Sales, some advanced features did not get used as heavily as the day-to-day ones. For example, some of the deeper customization and advanced configuration options were mostly handled by specific admin or operational users rather than everyone on the team. There were also some automation and advanced analytic capabilities that we did not fully utilize because the team mainly needed practical visibility and workflow coordination rather than complex customization. Overall, the core CRM and reporting features got the most consistent use while some of the most advanced enterprise-level capabilities were only used by a smaller group of power users.

Oracle CX Sales has changed how my team collaborates by centralizing workflows and customer data, which became much smoother because everyone had access to the same information in real time. It also made meetings and reporting discussions more productive since teams could focus more on discussions and next steps instead of spending time validating data or gathering updates. From my perspective, it created a more organized workflow overall and improved communication between the operation, reporting, and customer-facing teams. I would rate this review as positive overall based on the improvements in efficiency and collaboration achieved through this solution.

My main use case for Oracle CX Sales is for forecasting and AI-driven automation. When I open Oracle CX Sales, the first thing I do is read the dashboard, where I get the data for forecasting and pass that data into our AI-driven automation tool, using that information to determine what other things we can integrate into our system. Those dashboards provide all the forecasting data, and based on that we can make business decisions.

The workflow with Oracle CX Sales is team-wise, and we use it on a daily basis because our company makes business decisions based on that data.

During implementation, we are not using other features as a team because we only need the features for dashboard reading and data integration into our AI automation tool.

Oracle CX Sales has significantly impacted my organization by making it easy to interact with the cloud, providing access to data through APIs, allowing us to get all the datasets we require, and integrating with our AI automation tool, making the process very easy.

The best features of Oracle CX Sales include the dashboard UI, which looks very unique. Every day we use the dashboard UI for forecasting data and preparing the data.

The biggest friction point with Oracle CX Sales is that sometimes it goes down. When the server gets down, we do not get real-time data, which happens occasionally.

If I could change one thing about Oracle CX Sales, it would be to remove the five-minute data delay so we could get real-time data by the second.

I have not deeply researched features I wish Oracle CX Sales had, but whatever features we require right now are available, so we are satisfied.

I have been familiar with Oracle CX Sales for around four years.

The biggest friction point with Oracle CX Sales is that sometimes it goes down. When the server gets down, we do not get real-time data, which happens occasionally.

I decided on Oracle CX Sales specifically over other alternatives because it is easy to use, cost-effective, and has great technical support.

Before Oracle CX Sales, I worked manually and also used other tools such as Microsoft Dynamics 365 Sales and HubSpot, so I have experienced those kinds of feature tools as well.

When I first implemented Oracle CX Sales, the setup was somewhat complex, taking around one week to get up and running because we have different users in different locations and various terms to consider. Generally, we prefer the cloud to integrate in the cloud, and from the cloud, we access the Oracle CX Sales dashboard.

Our team needed to prepare formal training on Oracle CX Sales. The core team prepared one Confluence document for that purpose. If any new employees or junior staff come on board, they can refer to the document, but senior people do not need it because they already have experience with it.

I can quantify that my team is saving time by saying it feels like a ten out of nine because whatever dataset we require, we get from Oracle CX Sales.

In the team, collaboration has improved because everyone is using Oracle CX Sales.

The other tools I considered were Microsoft 365 and HubSpot CRM.

On a scale of one to ten, I would rate Oracle CX Sales overall as a nine out of ten because whatever we require and whatever things we are looking for from these tools, it fulfills our requirements. My advice to someone considering Oracle CX Sales with a similar workflow is that if you need good forecasting data, a good dashboard, and low cost, I totally recommend it. The overall review rating is nine out of ten.

At El Sewedy Electric, we have a company subsidiary called PSP, which specializes in building power plants. The business development team uses Oracle CX Sales to automate the sales process, including leads, qualification, and go or no-go decisions, all implemented through Oracle CX Sales.

Before implementing Oracle CX Sales, our process was entirely manual, involving contracts, approvals, emails, client proposals, and opportunities all managed through Excel sheets or paper approvals. This marked a substantial upgrade from our manual processes since 2015.

Our team needs formal training to get started with Oracle CX Sales. We provide test cases and user acceptance testing for end-users, including all scenarios and flows. Although the implementation was initially a vanilla-like approach with minimal customization, training remains important for understanding the system even if it is intuitive.

Oracle CX Sales features robust analytics and dashboards, which are essential for management as they provide intuitive interfaces for data visualization. The customization of apps allows for quick enhancements to sales processes in just a few minutes or hours.

Oracle CX Sales significantly impacts the organization by improving approval workflows, reducing manual work, providing visibility of opportunities to management, streamlining sales processes, and enhancing quota forecasting.

Oracle CX Sales changes how teams collaborate through its chat-like embedded feature, allowing them to communicate efficiently regarding specific deals or accounts. We can even use the sleek mobile app for updates and approvals.

As someone who implemented Oracle CX Sales, one of my biggest friction points is the lack of customization features prior to the introduction of Redwood, which was less advanced compared to competitors such as Salesforce.

The lack of comprehensive documentation was frustrating during my time with Oracle CX Sales, as it was not similar to the Trailhead platform and posed a steep learning curve for beginners.

I have been using Oracle CX Sales for about four years.

The implementation of Oracle CX Sales at El Sewedy Electric takes around seven to eight months in total to get everything fully up and running.

While supporting a large proposal team and the business development team, I handle the implementation of Oracle CX Sales solo, although we do use an implementation partner for some specific customizations. This makes the initiative large in scope because automating a process might take up to six months, including all approvals, such as CEO approvals for go or no-go decisions.

Alongside Oracle CX Sales, we consider other tools and CRMs because our corporate team proposes it as a pilot solution for PSP. We later decide to keep it while rolling out Salesforce due to my experience with Oracle CX Sales, which leads to my transition to the corporate team as CRM Application Section Head. I am now a 17-time certified Salesforce expert in just four years.

After the implementation of Oracle CX Sales was carried out and we went live, the first thing I did was enhance the process in terms of reporting, as well as utilizing it for sales plans, target versus achievement, and commitment.

Given it was a vanilla implementation, we actually utilized all the configured features and ensured that the platform was used optimally.

I provided a review rating of 7 for Oracle CX Sales.

We use Oracle CX Sales for our sales functions, including generating leads, managing campaigns, creating opportunities, and creating quotes. We also use the document management system to upload contracts, which forms part of our sales process.

Oracle CX Sales is workflow-driven, aligning with best practices in our sales process. The efficient workflow eliminates the need for multiple entries; data flows seamlessly from sales accounts to projects to quotes. The solution also offers robust analytical capabilities, enabling us to analyze reasons for wins or losses and strategically adjust our approach.

The address fields can be limiting on a global scale, with issues like long addresses and different styles for pin codes. Customization of field length and width to accommodate geographical requirements would be beneficial.

This is the fourth year we have been using Oracle CX Sales.

The solution is very stable, with no issues observed. I rate stability as ten out of ten.

I rate scalability as ten out of ten because it is inherently scalable.

We do not directly interact with Oracle for technical support. We communicate with our internal IT team, who then handle issues with Oracle or their support team.

Neutral

The initial setup is very complex. Being part of a multinational organization, the implementation was handled by our Norway team through an Oracle implementation partner.

The implementation was carried out by an Oracle implementation partner in collaboration with our team.

Salesforce is a comparable product to Oracle CX Sales. I have not extensively used Salesforce but noted its effective sales stage and funnel tracking capabilities during some implementations.

I suggest Oracle allow customization of field lengths to fit geographical needs. I would rate the solution ten out of ten overall.

The main use case is to enable customer self-support and simplify processes. We use Oracle CX Sales to make it very easy for customers to perform their actions while tracking their data. It also allows sales reps to track the data easily.

Basically, we streamline the data flow for sales reps, making things easier for them. We also make the application user-friendly. We gather requirements from customers and design solutions within the application to improve the flow between user applications and benefit the sales reps tracking those customers.

The best thing is we can customize it. For example, there are some standard procedures in CRM, the opportunity that is standard. Other than that, we can create customized software on a business-to-business basis. So, if I don't want to follow any standard upgrade of CRM, I can customize it the way I want, create my own CRM, and create a new closed integration with everything. I can make my own CRM.

The analytics in Oracle CX Sales are good. We can use ODA (Oracle Digital Assistant) to track data. There are some out-of-the-box reports for things like currency exchange data or product lists. These features are there by default.  If you need to create new custom reports, it's possible to do so.

They've been lagging behind the visual builder recently, but the product has improved.

They've been lacking in creating customization from scratch and in sales. But recently, they have introduced a new component or DBCS. So, they've been lacking compared to Salesforce for a long time, but they have added it now. So we can easily create a password as well. Initially, there was some lagging, but now it's going good.

I have been using it for almost three years now. It is deployed on Oracle cloud. 

Oracle CX Sales is a stable product in terms of its offerings.

It's generally stable.  I haven't encountered many bugs, though occasionally, there are minor Oracle-side issues with out-of-the-box features.

I would rate the stability a seven out of ten, since there's room for improvement on Oracle's side. Some features should be added to Sales Cloud.

Compared to Salesforce, the number using CX Sales is small. Most companies implement Salesforce for CRM and integrate Oracle directly from their endpoint. However, I think CX Sales will catch up. It's a good CRM right now.

I've contacted them a few times regarding multiple issues. For example, I needed to migrate a sandbox. The configuration is time-consuming – it takes eight to ten hours.

That feature isn't available in Oracle Sales Cloud, so I had to configure everything from scratch on another instance. I've submitted a feature request to Oracle, so hopefully, they'll implement it in the future.

Positive

The initial setup is really easy. Even before the installation, it's really easy. You're maintaining instances and giving access; we use a configuration module that makes it very easy to create users, manage access to the objects the cutomers want, and track them. I can provide only the roles they need. 

We can even customize roles based on specific access requirements. So, maintaining, installing, and creating – it's all easy. We can do it in minutes.

It's expensive, but worth the money. Ultimately, the choice depends on your priorities.

Oracle has some limitations, and it's a bit higher in price compared to other CRM technologies. Many clients find that their key requirements aren't met effectively. Salesforce provides more features, but Oracle is trying to catch up. 

In terms of functionality, security, and built-in ability, no one can beat Oracle. However, Salesforce is superior in terms of customization. 

So, for a standard implementation, I prefer Oracle – even with the higher cost, they provide strong delivery support. If you want a cheaper solution, I suggest Salesforce.

First, I'd point you to the Oracle documentation. They provide standard implementation guides that include basic setup instructions. 

If you need any customizations or features that aren't included out-of-the-box, bulk changes can sometimes be tricky. That's why I recommend going through the documentation thoroughly before starting, especially if you're considering upgrading the Oracle platform. If you're aiming for a standard implementation, the provided guides usually suffice.

If a beginner understands the entire business flow, then anyone can use CX Sales. However, if they need to customize areas, they should refer to Oracle's support documentation. Understanding the analytics, detail forms, and vendor flow within CRM is also beneficial. With that knowledge, I think someone could learn the basics in three to four days. After that, exploring more advanced features, like self-loading and such, requires more time and experience.

Overall, I would rate the solution an eight out of ten. Oracle is adding lots of new features with quarterly updates. That's good. They've changed a lot. Since I started using CX Sales Cloud, it's become much more advanced and is growing rapidly.

In my experience, the most valuable feature of Oracle CX Sales varies depending on the vertical of the business you're in. Oracle offers industry-specific products tailored to different sectors. However, the sales cycles and methods remain largely consistent across the board.

The tool extends across various user roles within the sales hierarchy, including sales reps and managers. The application doesn't just focus on sales; it initiates a journey that begins with marketing, connects to lead generation, progresses to opportunity management, and finally integrates with post-sales processes such as incentive management. The tool, including Incentive Compensation Management, forms a complete cycle encompassing marketing, sales, service, and incentives. Thus, users perceive it as a package.

Improvements for Oracle CX Sales include enhancing the user interface (UI) to meet modern standards. Many clients prefer a more optimized UI over the classic one. The market is moving towards better UI and UX design coupled with functionalities. Oracle has a tool called VBCS that can help improve the UI. With VBCS, the look and feel of the application can be completely transformed. For example, Oracle CX Sales has been implemented for Ferrari, a top automotive industry player. 

I have been working with the product for seven years. 

Oracle CX Sales is stable and has few bugs. As a cloud application, it offers good speed, efficiency, and reliability. However, pricing discussions might arise, and Oracle needs to address those. Migrating between different instances, like test, dev, and production, is easy.

Various teams work on different projects, including consultants, associates and senior managers. 

I am happy with the tool's support. 

We need to assess whether the product aligns with your specific business requirements. Many CRM products are available in today's market, like Oracle CX Sales, Microsoft Dynamics, and Zoho CRM, among others. Oracle offers specific functionalities that may be beneficial, but it's essential to understand your needs first. Based on your requirements, we can evaluate whether the out-of-the-box functionalities suffice or if additional customization is necessary.

Pricing is based on licensing. They offer three different levels: basic, advanced, and enterprise. While I haven't checked the pricing recently, they often provide good discounts on the product.

If you have a data centre within your country or region, that can be beneficial because Oracle provides good support for its products. They offer support at both technical and consulting levels, so it's a cloud-based application.

Whether Oracle CX Sales is easy or difficult for a beginner to learn depends on your background and experience as a consultant or coder. If you have. But even if you haven't, watching Oracle training videos and taking classes can help. You need to invest time in the solution. 

I would rate the product an eight out of ten. The main reason is its compatibility and ease of use for sales users. You can customize it according to your business needs, which is a big plus. However, like any product, it has its limitations, and we must work within those boundaries.

Sales teams use the product. The sales teams use it for leads and opportunities.

The lead and opportunity management features are valuable.

Customers usually do not prefer the solution over Sales Cloud. Support is very poor.

I have been using the solution for almost five years.

The tool is stable.

The tool is scalable since it is a cloud solution. I have seen very few clients using the solution. Oracle claims that the product is for enterprises. However, I have seen small and medium-sized businesses using the product.

The initial support is very straightforward. It is deployed on the cloud. Depending on the use cases, it takes five to seven months to deploy the solution.

The product is pricey. It is not worth the money.

Salesforce Sales Cloud is a proven product. It is the market leader. The way Salesforce has established its product is unmatchable.

There is not much difference in usability between the product and Sales Cloud. I would recommend Sales Cloud to people. Overall, I rate the solution a five out of ten.

Our order processing and the entire sales process is on Oracle Sales Cloud. For example, the data for getting inquiries, giving quotations, and getting orders are entered into Sales Cloud.

Account management is a very good feature. It is conceptualized very well, and we can look at all the projects under one account. The data for those accounts remain there throughout.

It gives multiple entries for the same data because if you enter it once, it has to populate all other fields that are relevant.

I've been using it for almost two years.

It is stable.

It's quite scalable. You can always buy more space and scale it accordingly.

We have more than 10,000 users globally.

We used CBL CRM.
Oracle CX Sales is more process oriented than CBL CRM. You will not get access to anything that is not required for your roles. The process is totally automated in Oracle. Whereas in CBL, everything was available to everybody, including sensitive information.

The initial setup was a little bit complex because we were using CBL CRM and then migrating from CBL CRM to Oracle. So, it was complex for our skillset, and I would give it a three out of five.

We used a third party integrator for deployment.

It's more costly, and I would give it a two on a scale from one to five with one being expensive and five being competitive pricing.

I would rate Oracle CX Sales at eight on a scale from one to ten.

One of the solution's most beneficial features is its mobile-enabled functionality. This allows users to access the system seamlessly on various mobile devices, such as phones, tablets, and computers.

They could provide more integrated AI features as part of the platform rather than as a separate offering.

We've been utilizing Oracle CX Sales for approximately two to three years.

Stability depends on the implementation, but overall, it's quite high.

Our clientele for the product ranges from small businesses to large enterprises. I rate the scalability an eight out of ten.

The initial setup could have been more straightforward, as some complexities were involved. This was mainly due to the integration of the system with existing AI infrastructure and another ERP system that had been in use for approximately nine years.

While there were specific considerations to monitor, it was simple, particularly for those familiar with technology, both from an external customer perspective and internally within the business sales environment.

The deployment model for Oracle CX Sales typically involves a hybrid approach. However, it can vary depending on specific requirements and preferences. I've encountered both CX Plus deployments and more generalized ERP setups. I've also served as a solution architect, recommending Oracle Tech Cloud as a deployment option.

The product has significantly impacted some clients, increasing sales revenue and cost savings.

The product pricing is reasonable compared to other solutions in the market.

Oracle CX Sales's analytics capabilities work great for standalone systems. I would recommend it, depending on the company's specific needs and preferences. I rate it a nine.