Product demo and AI voiceover script

90 second short version

Variants by audience

Transcript

Use this text for reviewed captions and the published transcript.

CX Command product demo transcript

Scene 1: Opening frame
On screen: CX Command landing page; Hero statement and product strip; Primary action: Start a session
Narration: CX Command is a source-grounded Oracle CX workspace for teams that need more than a chatbot. It helps account managers, solution architects, pre-sales, delivery teams, sales, service teams, and executives clarify issues, review evidence, surface risks, and generate usable outputs grounded in Oracle documentation and case-specific sources.

Scene 2: Guided intake
On screen: Start a new session from the landing intake form; Inquiry Context section opens in the workspace; Select product, inquiry type, role, and environment; Enter a one line goal statement
Narration: Every session starts with guided intake. Instead of asking users to drop a vague question into a blank chat, CX Command captures product context, inquiry type, role, environment, and the goal of the request. That helps the system route the work correctly before the answer is drafted.

Scene 3: Add evidence and trusted sources
On screen: Attach a file from the composer; Add an Oracle documentation URL; Add a public reference URL; Sources panel populates with trust labels
Narration: Users can add Oracle documentation, Oracle community references, uploaded files, screenshots, logs, and public URLs. CX Command treats these as grounding sources, not training data, and it keeps Oracle documentation as the primary source for general product behavior.

Scene 4: Structured workspace output
On screen: Session brief panel with four cards; What I heard; Missing context; Watchouts; Suggested next steps
Narration: Instead of responding with a generic wall of text, CX Command structures the result. It reflects back what it heard, identifies what is still missing, surfaces risks and watchouts, and proposes next steps. This makes the assistant feel more like a workbench for Oracle CX decisions and delivery than a simple chat interface.

Scene 5: Product-specific help
On screen: Product set to Oracle Eloqua; Ask a deliverability or campaign question; Answer returns with inline citations and source badges
Narration: Here, the user is working on an Eloqua issue. CX Command answers within the selected product context, cites the source of factual claims, and separates grounded guidance from interpretation. That gives the user traceability and makes the answer easier to verify before action is taken.

Scene 6: Requirements generation
On screen: Change inquiry type to User Requirements; Generate a requirement list, then a requirement table
Narration: CX Command also supports delivery work. If the user selects User Requirements, it can turn source material into clear, testable requirement statements. That is useful for solution architects, pre-sales teams, and delivery teams who need structured requirements rather than generic notes.

Scene 7: Unit testing and integration testing
On screen: Change inquiry type to Unit Test Cases; Unit test case table appears; Change inquiry type to System Integration Testing; SIT scenario table with interface type and validation points
Narration: The same workspace can generate unit test cases, system integration scenarios, acceptance criteria, and related testing artifacts. Unit tests stay narrow and component focused. Integration scenarios capture system boundaries, interface type, test data, validation points, and expected outcomes. That makes CX Command useful not only in discovery and pre-sales, but also in implementation and quality assurance.

Scene 8: Customer-facing drafting
On screen: Select the scoping or drafting inquiry type; Studio panel generates a customer-facing appendix or briefing
Narration: For customer-facing work, CX Command can draft scoped artifacts from approved source documents. Examples include scoping appendices, briefs, frequently asked questions, and implementation notes. The goal is not to invent scope, but to convert approved source material into clear, commercially safe outputs.

Scene 9: Save, start fresh, and forget session
On screen: Save workspace; Start fresh; Forget current session; Delete workspace
Narration: Users also control memory. A session can be saved as a reusable workspace, or it can be cleared entirely so the next interaction starts fresh. This matters for privacy, for unrelated workstreams, and for teams that need explicit control over retained context.

Scene 10: AI voice interaction
On screen: Voice interaction control in the composer; Spoken request transcribed into the intake or chat field; Structured answer returns in text with citations
Narration: CX Command can also support AI voice interaction. A user can speak a request, have it transcribed into the workspace, and then let the system respond with the same grounded, structured output used in text workflows. Voice acts as another input channel, not a separate product. Users can still review the text, the citations, and the generated output before acting.

Scene 11: Closing value statement
On screen: Workspace showing sources, structured outputs, and next steps; Subtle zoom on the final polished state
Narration: CX Command brings Oracle product guidance, case evidence, structured reasoning, and delivery-ready outputs into one workspace. It helps teams move from unclear questions to grounded next steps with stronger traceability, better collaboration, and more usable deliverables.