Merge rtt with next by Kesari3008 · Pull Request #666 · webex/widgets

Kesari3008 · 2026-04-01T13:13:39Z

COMPLETES

This pull request addresses

Merging the feature branch created for rtt with next

by making the following changes

Merging the feature branch created for rtt with next

Change Type

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update
Tooling change
Internal code refactor

The following scenarios were tested

The testing is done with the amplify link
< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

Checklist before merging

I have not skipped any automated checks
All existing and new tests passed
I have updated the testing document
I have tested the functionality with amplify link

Make sure to have followed the contributing guidelines before submitting.

…t-with-next

aws-amplify-us-east-2 · 2026-04-01T13:19:29Z

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-666.d1b38q61t1z947.amplifyapp.com

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f75a3c08dc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-04-01T13:19:41Z

packages/contact-center/task/src/helper.ts

+    return transcriptLines.map((line, index) => {
+      const payload: RealtimeTranscriptionData = {
+        messageId: line.messageId,
+        conversationId: line.conversationId,
+        role: line.role,


Filter realtime transcript lines by current task

useRealtimeTranscript receives currentTaskId but maps every item in realtimeTranscriptLines without task/conversation filtering. Since the store subscribes transcription events on each task, multi-task sessions will show utterances from other interactions in the currently selected task transcript, which can leak cross-call content and corrupt the UI. Filter by the selected task (or store a task identifier on each line) before mapping.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-04-01T13:19:41Z

...contact-center/cc-components/src/components/task/RealTimeTranscript/real-time-transcript.tsx

+          aria-selected={activeTab === 'live'}
+          className={`real-time-transcript__tab ${activeTab === 'live' ? 'real-time-transcript__tab--active' : ''}`.trim()}
+          onClick={() => onTabChange?.('live')}
+          data-testid="real-time-transcript:live-tab"
+        >


Add an IVR tab trigger to the transcript tablist

The component models two tabs ('ivr' | 'live') and has separate IVR rendering, but the tablist renders only a Live tab and its handler only emits 'live'. In the default state, users have no in-component way to switch to IVR content, so ivrTranscript is effectively inaccessible unless a parent forces activeTab='ivr' externally.

Useful? React with 👍 / 👎.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5c933ce8eb

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-04-09T10:36:25Z

widgets-samples/cc/samples-cc-react-app/src/App.tsx

  CallControlCAD,
  store,
  OutdialCall,
+  RealtimeTranscript,


Import RealTimeTranscript using the exported symbol name

@webex/cc-widgets now exports the widget as RealTimeTranscript, but this sample imports RealtimeTranscript (lowercase t in Time). In environments that type-check or validate ESM named imports, this causes a build/runtime failure (RealtimeTranscript is undefined), so the new sample toggle cannot render the transcript widget.

Useful? React with 👍 / 👎.

mkesavan13

I went back to SDK PR#4794 to realize that the transcripts are being started always based on certain events:

export const TRANSCRIPT_EVENT_MAP = {
  [CC_EVENTS.AGENT_CONTACT_ASSIGNED]: 'START',
  [CC_EVENTS.AGENT_CONSULTING]: 'START',
  [CC_EVENTS.AGENT_CONSULT_CONFERENCED]: 'START',
  [CC_EVENTS.AGENT_WRAPUP]: 'STOP',
  [CC_EVENTS.AGENT_CONSULT_ENDED]: 'STOP',
  [CC_EVENTS.PARTICIPANT_LEFT_CONFERENCE]: 'STOP', 
};

However, what if the developer doesn't want to enable transcript from SDK or in this case, the RTT widget isn't included by the developer?

‼️ Also, let's change the PR title to match semantic-release format

mkesavan13 · 2026-04-10T10:27:36Z

...-center/cc-components/src/components/task/RealTimeTranscript/real-time-transcript.style.scss

Shouldn't it still be "transcripts" because it is not one transcript you get?

feature says real time transcript and everywhere we are keeping without s so to make it consistent I changed

mkesavan13 · 2026-04-10T11:08:59Z

.github/workflows/deploy.yml

Can we remove this file change? Looks like they're only quotes and spacing change that's unnecessary

mkesavan13 · 2026-04-10T11:10:30Z

...contact-center/cc-components/src/components/task/RealTimeTranscript/real-time-transcript.tsx

+    <section className={`real-time-transcript ${className || ''}`.trim()} data-testid="real-time-transcript:root">
+      <div className="real-time-transcript__content" data-testid="real-time-transcript:live-content">
+        {sortedEntries.length === 0 ? (
+          <div className="real-time-transcript__empty">No live transcript available.</div>


Should this be behind a constant so that we can do i18n later?

mkesavan13 · 2026-04-10T11:20:21Z

packages/contact-center/store/src/storeEventsWrapper.ts

+    const normalizedRealtimeData = {
+      ...data,
+      role,
+      caller,
+      content: (payload?.content || data.content || '').trim(),
+      publishTimestamp: Number.isNaN(publishTimestamp) ? Date.now() : publishTimestamp,
+    };


Couldn't we have encapsulated this normalization in the SDK itself so that other SDK users also benefitted from it?

We could have the raw data but also the normalized one?

Or better, we handle this whole merging of transcripts at the SDK itself and just send the new list of transcripts to Widgets?

This is to be able to provide control to the consumers. As of now we do not know how each consumer would like to handle these event data so that's why I have kept it in widgets.

Kesari3008 · 2026-04-10T15:39:16Z

I went back to SDK PR#4794 to realize that the transcripts are being started always based on certain events:
export const TRANSCRIPT_EVENT_MAP = {
  [CC_EVENTS.AGENT_CONTACT_ASSIGNED]: 'START',
  [CC_EVENTS.AGENT_CONSULTING]: 'START',
  [CC_EVENTS.AGENT_CONSULT_CONFERENCED]: 'START',
  [CC_EVENTS.AGENT_WRAPUP]: 'STOP',
  [CC_EVENTS.AGENT_CONSULT_ENDED]: 'STOP',
  [CC_EVENTS.PARTICIPANT_LEFT_CONFERENCE]: 'STOP', 
};
However, what if the developer doesn't want to enable transcript from SDK or in this case, the RTT widget isn't included by the developer?

‼️ Also, let's change the PR title to match semantic-release format

AGENT_CONTACT_ASSIGNED is an event that happens for any incoming call and for consult offer, it is going to be CONSULTING so transcriptions are basically supposed to start for any incoming accepted task. RealTime transcription enablement is actually dependent on if the feature is enabled from control hub setting

Shreyas281299 and others added 4 commits March 23, 2026 15:07

tooling(deploy): add rtt in branch allow list

1e79df7

tooling(pull-request): remove target branch in pull-request workflow

90879db

fix(store): change to publish all widgets (webex#659)

b067344

feat(ccwidgets): Real Time Transcript Widget Implementation (webex#653)

f75a3c0

Kesari3008 requested a review from a team as a code owner April 1, 2026 13:13

Kesari3008 added 2 commits April 1, 2026 18:45

Merge branch 'next' of https://github.com/webex/widgets into merge-rt…

83e5bf8

…t-with-next

feat(ccwidgets): merge rtt feature branch

e9acd6c

Kesari3008 added validated Indicates that the PR is ready for actions run_e2e Add this label to run E2E test for meeting and CC widgets labels Apr 1, 2026

chatgpt-codex-connector bot reviewed Apr 1, 2026

View reviewed changes

feat(ccwidgets): cleanup

5c933ce

chatgpt-codex-connector bot reviewed Apr 9, 2026

View reviewed changes

mkesavan13 requested changes Apr 10, 2026

View reviewed changes

Conversation

Kesari3008 commented Apr 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

COMPLETES

This pull request addresses

by making the following changes

Change Type

The following scenarios were tested

The GAI Coding Policy And Copyright Annotation Best Practices

Checklist before merging

Uh oh!

aws-amplify-us-east-2 bot commented Apr 1, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

mkesavan13 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mkesavan13 Apr 10, 2026

Choose a reason for hiding this comment

Uh oh!

Kesari3008 Apr 10, 2026

Choose a reason for hiding this comment

Uh oh!

mkesavan13 Apr 10, 2026

Choose a reason for hiding this comment

Uh oh!

mkesavan13 Apr 10, 2026

Choose a reason for hiding this comment

Uh oh!

mkesavan13 Apr 10, 2026

Choose a reason for hiding this comment

Uh oh!

Kesari3008 Apr 10, 2026

Choose a reason for hiding this comment

Uh oh!

Kesari3008 commented Apr 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Kesari3008 commented Apr 1, 2026 •

edited

Loading

mkesavan13 left a comment •

edited

Loading