Customer Intelligence Hub: A Single Pane of Glass for Customer Insight and Action

For most go-to-market (GTM) teams, understanding what’s really happening with a customer right now is harder than it should be. Usage data lives in one system, renewals in another, support escalations somewhere else—and field notes are scattered across tools and docs. By the time someone pieces together a full picture, it’s already out of date.

As we began using our own data platform internally, this fragmentation became impossible to ignore. We realized the core problem wasn’t just data access; it was prioritization. Teams weren’t lacking dashboards; they were lacking clear, shared views of what changed, what mattered, where risk emerged, and where expansion opportunity existed.

The Customer Intelligence Hub (CIH), sometimes referred to as the Intelligence Hub or Account Intelligence Hub, is an internal Confluent application and an early learning initiative. It’s not a finished product or a polished external solution. It’s our attempt to explore what happens when customer intelligence is treated as a continuous stream of meaningful change and paired with grounded AI to improve both risk detection and whitespace visibility across the portfolio.

What Is CIH?

In one sentence: CIH gives sales, customer success, support, and GTM teams a single prioritized view of each customer account, focusing on change detection and next-best action, not just aggregation.

It brings together customer signals, AI-driven insights, and operational workflows into an account-centric experience for field and GTM teams. Instead of swiveling between multiple systems, CIH centralizes key signals and surfaces what changed and why it might matter.

At a high level, CIH:

• Centralizes customer signals from Salesforce, Zendesk, product telemetry, billing, Jira, CommonRoom, Quartr, Crossbeam, and more

• Provides both portfolio-level and account-level views, so users can scan their entire books of business or dive deep into a single account

• Surfaces a real-time activity feed and priority signals, explicitly focused on highlighting meaningful changes and where action may be required

• Includes generative artificial intelligence (GenAI) capabilities (AccountIQ), so users can ask natural-language questions and receive contextual summaries that are grounded in CIH data

• Remains read-only, scoped by account and user authorization, and protected by Okta single sign-on (SSO) and backend authorization controls

The intent is simple but ambitious: Reduce the cognitive load of stitching together context and increase clarity about what deserves attention now.

What CIH Is Not

It’s important to note that CIH is not:

• A replacement for source systems such as Salesforce or Zendesk

• A generic reporting layer or static dashboard

• A system of record

It’s read-only relative to its source systems, and it’s designed to sit on top of them while highlighting cross-system signals and surfacing insights that are hard to see when data is siloed.

Who Uses CIH and Why?

CIH is designed for the people on the front lines of customer engagement.

Account Executives (AEs) and field sellers

• Prioritize outreach based on meaningful activity and risk/opportunity signals.

• Quickly understand usage, renewals, and escalation context before a meeting.

Customer success

• Monitor account health at scale and focus attention on accounts in which signals indicate risk or expansion potential.

Support and technical field teams

• Triage issues faster with richer account context (usage patterns, recent changes, prior incidents).

GTM strategy and operations

• Use a consolidated, account-centric lens to inform programs, coverage, and customer plays.

The core value is simple: less time hunting for data, more time acting on insights. Instead of reading raw telemetry or combing through tickets, users see prioritized events, trends, and summaries that directly support sales motions, renewals, and customer outcomes.

How It Works Under the Hood

Customer signals from multiple internal and external systems are ingested into Apache Kafka® topics in Confluent Cloud. These systems contain critical information about customer usage, renewals, support activity, engagement, and more.

The flow looks like this:

• Ingestion into Kafka (Confluent Cloud)

• Data from Salesforce, Zendesk, Mothership, Jira, and other systems is streamed into Kafka topics. Kafka serves as the durable backbone for all customer intelligence events.

• Stream Processing and Enrichment With Apache Flink®

• Apache Flink normalizes and enriches events, correlates cross-system signals, and generates semantic embeddings for AI use cases.

• Vectorization and Search (OpenSearch plus Vertex AI)

  • Enriched facts and embeddings are streamed into OpenSearch via managed connectors.

  • When a user asks a question:

• A query embedding is generated.

• Similar facts are retrieved via vector similarity search.

• Grounding facts are passed into the large language model (LLM) prompt.

• Grounded AI Response

  • The model generates a response based only on retrieved, account-scoped facts, reducing hallucination risk and preserving authorization boundaries.

This architecture supports real-time answering of questions with account-level authorization checks enforced at the backend.

Platform Use Cases

This platform currently serves three primary internal use cases:

• AccountIQ inside CIH (GTM-facing AI chatbot)

• Executive account summary generation

• GTS support team’s AI tool for contextualized troubleshooting and escalation insight

By centralizing ingestion, enrichment, embedding, and grounding into a shared streaming architecture, we avoid duplicating AI pipelines for each use case.

Key Capabilities Inside CIH

1. Account Center: Your Portfolio in One View

The Account Center is the homepage of CIH. It shows a table of all accounts in your portfolio with key usage, billing, and health metrics so that you can scan your book at a glance.

From here, you can:

• See which accounts have non‑zero usage or recent activity—and which don’t

• View consumption trends, average billings, and recent changes across core products such as Kafka, Kafka Connect, ksqlDB, Flink, and Stream Governance

• Drill into an account-level view with cards for streaming projects, renewals, and a detailed activity feed

This is where many AEs and managers start their day: a portfolio view that immediately highlights where attention is needed.

2. Whitespace View: Identifying Expansion Opportunities at a Glance

In addition to the standard portfolio view, CIH includes a Whitespace View—an alternative Account Center layout that replaces the legacy T360 “Territory Overview.”

While the primary portfolio view focuses on usage trends, renewals, and recent activity, the Whitespace View shifts the lens toward expansion potential.

It shows each account’s data streaming platform (DSP) adoption and pipeline by product—including Stream Governance, Kafka Connect, Flink, ksqlDB, and Tableflow. 

This allows sellers and customer success teams to quickly understand:

• Where a customer is not yet using DSP capabilities

• How much active pipeline exists in each product area

• Where whitespace opportunity remains across the portfolio

3. Real-Time Activity Feed: Signals Over Noise

At the heart of CIH is the Customer Intelligence Activity Feed, a real-time stream of events from product usage, support, field feedback, renewals, and more.

The feed includes events such as:

• Confluent Cloud product events: cluster creation/deletion, connector events, Flink pools and statements, schema registry milestones, throughput anomalies, abandoned resources, first use of key capabilities, and more

• Renewal and commercial milestones: upcoming renewals at 45/90/180 days and key billing changes

• Support signals: Zendesk ticket created/resolved, Jira field feedback opened/resolved, and other indicators of friction

• Engagement and external signals: partner overlaps (Crossbeam), market engagement (6sense), and earnings transcript updates (Quartr)

Users can:

• Toggle between "All Events" and "Priority Events" to reduce noise and focus on high-impact changes

• Filter by category, such as Connect, Support, Kafka, Stream Processing, Field Feedback, Account, or Customer Success

• Click through to the system of record (Salesforce, Zendesk, Jira, etc.) when deeper investigation is needed

The design principle here is signal over noise: CIH focuses on the changes and events that actually drive action, not a firehose of raw telemetry.

4. AccountIQ: GenAI for Customer Context

AccountIQ allows users to make requests such as:

• “Summarize this customer’s engagement with Confluent over the last 90 days.”

• “What are the most recent support issues, and how severe are they?”

• “Where are we seeing growth in usage, and where is it flat or declining?”

The outcome is faster preparation and richer context for customer conversations—without manually stitching together dozens of data points.

5. Executive Account Summaries at the Push of a Button

Many account teams and executives rely on executive account summaries before key meetings, quarterly business reviews, or internal reviews. CIH integrates with the Exec Summary Doc Generator to make this nearly one-click. This capability turns what used to be hours of prep into a repeatable, automated workflow.

Customer Zero: Why We’re Using It Ourselves

Confluent is currently using CIH internally as a Customer Zero initiative. We chose to deploy this for a simple reason: If this approach truly improves prioritization and early risk visibility, we should see it first in our own GTM motions.

As part of that, the first thing we needed to validate was adoption—before attempting to measure deeper workflow impact. The metrics below provide early validation that teams are not just aware of CIH but are actively using it.

Since launch, adoption has grown meaningfully:

• 731 unique authenticated users

• 1,389 sessions in the last month

• 137 new users in the last 90 days

Usage patterns suggest that CIH is becoming embedded in the daily workflows of certain teams. Some segments show significantly higher sessions-per-user ratios:

• Account management: 13.5 sessions per user

• Global scale management: 15.3 sessions per user 

• IT: 22 sessions per user

This tells us that CIH is not just being tried; in some roles, it’s becoming a repeat-use workflow tool. Early user feedback reinforces this trend. Teams consistently highlight CIH’s value during account transitions and ramp periods when consolidating context quickly is what matters most.

As Maddie Kokos, Account Manager, shared, “CIH is an invaluable tool for account transitions and takeovers. It gives new team members a single place to quickly understand key highlights, recent activity, and overall account context.”

Moshe Blumber, Customer Success Technical Architect, described a similar experience, noting that CIH made ramping up on a new account significantly easier by clearly surfacing product usage, consumption trends, and overall health during a transition.

An AE also described CIH as a complementary layer alongside Salesforce and Tableau C360, helping round out the full account picture during handoffs.

What This Architecture Is Helping Us Learn

Because this is a shared intelligence and AI platform, using it internally as Customer Zero gives us leverage beyond one workflow.

We’re not only testing whether AEs prioritize better, whether prep time decreases, and whether risk signals surface earlier. We’re also testing architectural hypotheses:

• Can a streaming-first architecture meaningfully improve AI grounding quality?

• Does embedding generation inside Flink simplify operational complexity?

• Can a shared ingestion and vectorization layer support multiple GTM and support use cases without fragmentation?

• How does real-time enrichment compare to batch-driven AI pipelines in perceived usefulness?

Early internal usage has already shaped adjustments:

• Refining which facts are embedded versus kept structured

• Tightening similarity search thresholds to reduce irrelevant grounding

• Improving authorization boundaries to ensure account-level isolation

• Rebalancing which signals flow into embeddings versus remaining filterable metadata

In this sense, Customer Zero is as much about validating architectural patterns (streaming + Flink + vector search + grounded AI) as it is about validating workflow outcomes.

What We’re Watching Next

As engagement and adoption continue to grow, we’re measuring:

• Earlier visibility into customer risk or expansion signals

• Reduced prep time for executive and quarterly business review workflows

• Clearer portfolio prioritization

• Improved signal-to-noise ratio

So far, we’ve validated sustained adoption and growing engagement. We’re still measuring workflow impact, including reduced prep time, earlier risk detection, and clearer prioritization. Those outcomes remain active areas of tracking as Customer Zero continues.

We’ll share outcome metrics as they mature.

CIH is still in its early stages. But one lesson is already clear:

When customer data is treated as a continuous stream of meaningful change rather than a set of static reports, AI becomes grounded, contextual, and actionable.

We’ll continue publishing what we learn as adoption grows and impact metrics become measurable. Stay tuned! In the meantime, please explore CIH internally, start incorporating it into your daily account workflows, and tap into AccountIQ to create context-rich customer interactions.

To learn more about how we’re using streaming plus AI to power initiatives such as CIH, explore how Confluent’s data streaming platform underpins real-time, context-aware AI here.

Apache®, Apache Kafka®, Kafka®, Apache Flink®, and Flink® are registered trademarks of the Apache Software Foundation. No endorsement by the Apache Software Foundation is implied by the use of these marks.