Enterprise Knowledge Search · Sales Automation
IBM's client-facing teams were losing time switching among disconnected sales, support and planning tools, leaving them without a timely, shared account view when preparing for customer interactions.
Reported impact
IBM deployed the pilot in 6-8 weeks, rolled it out to about 70 accounts, and gave account teams a faster way to get up to speed, coordinate with teammates and respond to client questions without manually stitching context together.
The IBM Chief Information Office organization built an Account 360 Slack application on its internal Hybrid Cloud platform to reduce the time client-facing teams spent hunting across disconnected sales, support and planning tools. The solution aligns account identifiers across source systems, combines quote documents, support tickets, account plans, company profiles and other client records, preprocesses them and stores the result in IBM Cloud Object Storage. The application is written in Python and hosted on Red Hat OpenShift on IBM Cloud, while IBM watsonx.ai generates summaries and answers natural-language questions over the aggregated account material. Slack is the serving layer, exposing one-click access to relevant resources and teammates from desktop or mobile devices. This creates a cross-silo retrieval and collaboration layer where normalized account data is stored once and surfaced inside the tool where sellers, customer success managers and support staff already work.
Sales, support and planning data is aligned by account identifier, combined and preprocessed into IBM Cloud Object Storage, then served by a Python application on OpenShift; Slack exposes the output while watsonx.ai summarizes account documents and answers account questions.
"IBM uses its watsonx.ai AI studio as the summarization tool"
"The application was written in Python and hosted within IBM's internal Hybrid Cloud platform built on Red Hat OpenShift on IBM Cloud."
"The tool pulls data and information from across multiple tools and repositories"
"the company plans to add all its commercial signature and strategic accounts into the tool"
"the organization was able to serve the application directly"
Review how this reference was scored and trace each normalized claim back to its documented source.
Scoring methodology
Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.
Traceability
Field coverage shows which facts each source supports. Dates are shown only when documented by the source.
Related
IBM Sample Jan 15, 2026 IBM IBM needed to reduce the time employees spent on repetitive work across HR, procurement, IT, supply chain, tax, and sales while creating a repeatable enterprise blueprint for scaling AI, automation, and hybrid-cloud… 15K AI agents proposed by employees during the 2025 IBM watsonx Challenge IBM Apptio · IBM Turbonomic · IBM Watson Discovery 
MongoDB Sample May 18, 2026 LekoTech LekoTech needed to digitize millions of unique car parts to promote reuse but faced latency of up to 35 seconds with its existing search system. LekoTech needed to digitize millions of unique car parts to promote reuse but faced latency of up to 35 seconds… MongoDB Atlas · MongoDB Atlas Search · MongoDB Atlas Vector Search MongoDB Sample Apr 29, 2026 Tenali AI Tenali AI needed to help enterprise sellers answer deeply technical questions during live calls in under one second by searching Slack, PDFs, CRM data, and prior meeting content without the latency and synchronization… After switching embedding models, sales reps actively using Tenali's answers on live calls increased by over 40%. MongoDB Atlas · MongoDB Vector Search · Voyage AI 