Share your experience using Saleswhale

My main use case for Outreach is conducting cold calls and sending cold emails to prospects in my company's book of business in order to generate outbound pipeline.

A specific example of how I use Outreach for cold calls and emails is that it excels at building multi-channel sequences. Step one is an email, then three days later I receive a task to call that person, and then three days after that I receive another task to email that person.

Outreach is an essential tool for doing outbound work and speeds up my workflow significantly.

The best features Outreach offers include the ability to build multi-channel sequences and the capability to mark phone numbers as verified. When I find a good phone number, I can click thumbs up and mark it as a good phone number so that when someone else tries to call that person, if the person has multiple numbers, we can call the correct one.

These features help me day-to-day because the phone number verification saves me time as I do not have to remember which number I called that was correct.

Outreach positively impacts my organization as my team books meetings and generates outbound pipeline, which then generates revenue.

Outreach can be improved because its AI features are not strong.

Regarding the needed improvements, especially with the AI features, it would be beneficial if the AI conducted research and provided recommendations for what to write.

I have been using Outreach for about a year.

Outreach is stable.

I did not previously use a different solution as my company only purchased Outreach.

Before choosing Outreach, we evaluated SalesLoft, but we chose Outreach because it had better reviews.

My advice to others looking into using Outreach is that it is a good product and I recommend using it. I would rate this product a seven out of ten.

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.