Sales Command Center

The Sales Command Center reorganizes the Oracle CX Sales experience around the four questions a Sales User asks every morning, which deals need me today, which meetings am I walking into, which customers need attention, and which programs are heating up in my territory. The workspace presents these as four interconnected panels, Priority Opportunities Requiring Immediate Action, Pre-Meeting Briefs and Follow Up, My Customers, and Programs in My Territory. Each panel leads with a written summary in business language, not raw fields, so a rep understands deal context, meeting intent, account momentum, and program performance at a glance. Selecting any item opens a drill-down agentic view where the seller sees an orchestrated narrative summary, account or opportunity insights, engagement progress, customer attendees with sentiment and influence, talking points, objection handling, intended outcomes, and the right prioritized actions surfaced as cards. The workspace ships with an embedded conversational assistant called Ask Oracle, so any question about a panel or drill-down can be answered without leaving the page. A Priority Actions sidebar focuses the rep on opportunity-level recommendations distilled by the AI, keeping the action queue clean and free of agent noise. From any drill-down, the seller can have the agent send and track emails through Outlook Exchange, generate a tailored presentation for the deal or account, download it, and share through email or other channels. The Sales Command Center is configured by your administrator as the rep's default landing experience and works out of the box on standard Oracle CX Sales data, with no custom integrations or external data lake required.

  • More selling time, less context assembly: Sales Users walk into every conversation already prepared, reclaiming hours each week that were going to research, tab switching, and pre-meeting prep.
  • Earlier visibility into renewals, expansion, and risk: Account-level signals and program engagement are surfaced as written narratives in the workspace, so renewal exposure and expansion openings are seen weeks earlier and acted on sooner.
  • Higher pipeline velocity and meeting yield: With prioritized opportunities, pre-meeting briefs, and one-click follow-up actions in one place, deals progress between meetings instead of stalling, and follow-ups go out the same day.

Steps to enable and configure

Part 1: Enable and Configure Sales Orchestration

Sales Orchestration must be enabled and configured before SCC can function. Complete all of the following.

1.1 Configure the Dispatcher Service

The Dispatcher Service routes users to the new Sales Orchestration pages. Configure it so that sellers landing in the Sales work areas are directed to the orchestration experience rather than the legacy pages.

Outcome: users navigating to the relevant Sales work areas are routed to the Sales Orchestration pages.

1.2 Configure Content Management (Oracle Knowledge Management)

Oracle Knowledge Management (Oracle KM) must be configured within the customer environment to support sales enablement content access. This is what lets agents and sellers retrieve the right enablement material in context.

Outcome: sales enablement content is published and retrievable inside the orchestration experience.

1.3 Create and Configure Sales Plays

Create Sales Plays using the Sales Play setup functionality in the Administration workspace. Sales Plays define the structured guidance and recommended motions that the agents apply to opportunities.

Outcome: Sales Plays exist and are available to drive recommendations and guided selling.

1.4 Define and Configure Sales Motions

Define Sales Motions using the Sales Motion setup functionality in the Administration workspace. Sales Motions describe the selling approach (for example new business versus expansion) that agents reason over.

Outcome: Sales Motions are defined and mapped so agents can align actions to the correct motion.

1.5 Configure Data Capture

Configure Data Capture using the Data Capture setup functionality in the Administration workspace. Data Capture enables automated engagement and activity documentation, which removes manual logging and feeds the agents accurate engagement signals.

Outcome: engagement and activity are captured automatically and recorded against the right records.

1.6 Configure Web Conference Captures (Zoom and Microsoft Teams)

To capture Zoom and Microsoft Teams meetings automatically, set up the out-of-the-box integrations. Without this, meeting capture for web conferences is not automated.

Reference for the Microsoft Teams setup: https://docs.oracle.com/en/cloud/saas/sales/famst/overview-of-microsoft-teams-collaboration-in-the-redwood-user-experience.html

Outcome: Zoom and Teams meetings are captured automatically and associated with the relevant opportunities and accounts.

1.7 Configure Microsoft Exchange Email and Calendar Integration

Set up the Microsoft Exchange email integration with the email option set to Microsoft Office 365 so the out-of-the-box email and calendaring functionality works correctly. This is what powers email send, tracking, and calendar features inside the seller experience.

Reference for the Exchange integration: https://docs.oracle.com/en/cloud/saas/sales/faeml/exchange-email-integration-for-digital-sales.html

Setup spans three areas, and all three must be completed.

  1. Microsoft Azure: register an application for the integration and grant the Mail.ReadWrite and Mail.Send application permissions, then grant admin consent for the tenant.
  2. Microsoft Exchange admin center: create a mail flow rule that matches a hidden keyword in the subject or body and adds your global address to the bcc, then set the rule priority to the highest.
  3. Oracle Sales: use the Manage Microsoft 365 task to enter the Application ID, Application Key, the integration address, and the keyword, then enable email integration.

Set the email option to Office 365. In the Manage Administrator Profile Values task, set the Digital Sales Email Options Enabled profile option (ORA_ZCA_DS_EMAIL_OPTIONS) to the MS Exchange Office 365 UI value so the email flow routes through Microsoft Exchange and uses Microsoft 365 (Outlook) as the client. Run the Microsoft Exchange Email Sync scheduled process so inbound emails appear in the activities list.

Outcome: sellers send and track email through Microsoft 365, and calendar and appointment functionality is supported.

If Exchange integration is not set up

The following limitations apply and should be communicated to any environment that skips this step.

  • Email engagements have to be logged manually using the Log an Interaction functionality.
  • Appointments and calendaring functionality cannot be supported.

Part 2: Enable and Configure Sales Command Center

Complete this stage only after the 26B foundation in Part 1 is in place and verified. SCC reuses the Sales Orchestration agents, content, and integrations, so confirm Part 1 first.

2.1 Confirm the Foundation

Verify that Sales Orchestration is enabled, the Dispatcher Service routes correctly, Oracle KM content is published, Sales Plays and Sales Motions exist, Data Capture is active, and the Exchange and web conference integrations are working. SCC surfaces the output of these capabilities, so each one must be confirmed before enabling the SCC layer.

2.2 Route Users to the Sales Command Center Pages

Configure the Dispatcher Service to route users to the Sales Command Center pages, in the same way it routes to the Sales Orchestration pages in 26B.

2.3 Configure the Backend Agents

SCC runs the Sales Orchestration agents in the backend to generate opportunity and account summaries, recommendations, and the priority score and health that the panels display. These agents must be configured so a customer can apply their own rules rather than relying on hardcoded logic.

For prioritization specifically, the customer prioritization logic should be provided as an input to the Opportunity Health agent rather than embedded by cloning the agent. Supplying the logic as configuration lets the environment keep receiving new features and enhancements in later releases. Cloning the agent to inject custom logic blocks those upgrades and should be avoided.

Outcome: each backend agent applies customer-specific rules, and priority and health scores reflect the customer prioritization logic.

2.4 Configure the Sales Command Center Panels

Enable and configure the primary SCC panels for the sales rep persona:

  • Priority Opportunities, driven by the priority score and health from the backend agents.
  • Meeting Prep and Follow-Ups, driven by meeting and engagement capture.
  • My Customers, driven by account summaries and recommendations.

Configure the workspace goals and summary priorities for each panel so the agents proactively address the questions that matter most to the customer when a seller opens the app.

2.5 Configure Ask Oracle

Enable the embedded conversational experience (Ask Oracle) that connects the panels and lets sellers ask questions and trigger next steps in context.

2.6 Configure Agentic Actions

SCC supports agentic actions, including email send and tracking and AI-generated content. Confirm the supporting integrations and validate the scope of each action for the release before enabling it.

  • Email send and tracking depends on the Microsoft Exchange Office 365 integration from step 1.7. Validate the tracking scope for the release before exposing it to sellers.
  • AI-generated PowerPoint creation should be validated for release scope and any packaging or gating that applies before it is turned on.

Key resources

Access requirements

Users must have access to the CX Sales FSM task Enable Generative AI Features in CX Sales to manage opt-in status.