Overview

The CopilotVoiceTranscripts block is a companion to the Copilot Chat & Voice block. It renders a structured, scrollable transcript log of voice interactions between the user and the AI assistant. Each transcript entry shows the speaker (User or Assistant), the recognized or generated text, and an optional timestamp. The block can be placed on the same page as the Copilot block, on a separate summary page, or in an audit panel accessible to supervisors.

Note: The Copilot Voice Transcripts block reads from the transcript state of a sibling Copilot block on the same page. Voice mode must be enabled on the Copilot block, and the user must grant microphone permission. Text-only Copilot interactions do not generate transcripts visible in this block.

Properties Reference

Binding Expressions

The Copilot Voice Transcripts block exposes its transcript data as bindable state. Use these expressions in other blocks on the same page:

Setting Up a Voice Audit Panel

1. Add a Copilot block with voice mode: Ensure a Copilot block is on the page (or in a global layout) with Voice Mode = enabled. Note its block ID (e.g. copilot1).

2. Add the CopilotVoiceTranscripts block: Drag CopilotVoiceTranscripts onto the page. In the Content inspector, set Copilot Ref to copilot1 (the Copilot block's ID).

3. Configure display options: Enable Show Timestamps = true, Show Speaker Labels = true, Searchable = true. Set Text Size = md. Enable Downloadable = true for the compliance export button.

4. Restrict visibility (optional): If the transcript is for supervisor review only, add a Visibility condition: {{ currentUser.role === "supervisor" }}. Regular agents see the Copilot block but not the transcript panel.

Examples

Example: Call center audit log

Place the CopilotVoiceTranscripts block in a supervisory view alongside a Data Table of active calls. Bind a separate Typography block to {{ transcripts.latest.text }} to show the real-time last utterance. Set Max Entries = 200 to cap memory usage for long calls, and enable Downloadable = true for post-call QA review.

Example: Voice command history panel

Show only the User-side utterances (voice commands) in a compact panel. Bind a Repeatable to {{ transcripts.all.filter(e => e.speaker === "user") }} and render each item as a Tag block with the command text. This gives users a visual confirmation of the commands the system recognized during their session.

Frequently Asked Questions

Does the transcript persist after the user navigates to a different page?

Transcript data is stored in the Copilot block's session state, which is scoped to the browser session and the page the Copilot block lives on. If the Copilot block is placed in a global layout (shared across pages), the transcript persists across page navigations. If the Copilot block is page-scoped, navigating away and back resets the transcript. To persist transcripts across sessions, wire the onNewEntry event from the Copilot block to an API action that saves each entry to your backend.

Can multiple CopilotVoiceTranscripts blocks reference the same Copilot block?

Yes. Multiple transcript blocks can reference the same Copilot block's ID. They all read from the same transcript state, so they stay in sync. This is useful for displaying a compact "last utterance" widget and a full scrolling log simultaneously in different parts of a layout.

Does the Download button produce a structured format I can parse?

The default download produces a plain .txt file with one line per entry formatted as [HH:MM:SS] Speaker: text. For a machine-readable export, use a Button block with an Export as JSON action bound to {{ transcripts.all }} — the full array of { id, speaker, text, timestamp } objects — and export it via the Export File action targeting a JSON format.

Related Pages