Skip to content

feat(contact-center): initial changes for implementing get suggested response feature#4952

Open
Kesari3008 wants to merge 2 commits intowebex:task-refactorfrom
Kesari3008:Get-Suggested-Response-Implementation
Open

feat(contact-center): initial changes for implementing get suggested response feature#4952
Kesari3008 wants to merge 2 commits intowebex:task-refactorfrom
Kesari3008:Get-Suggested-Response-Implementation

Conversation

@Kesari3008
Copy link
Copy Markdown
Contributor

@Kesari3008 Kesari3008 commented May 5, 2026

COMPLETES #< INSERT LINK TO ISSUE >

This pull request addresses

Implementation for Get Suggestions feature

by making the following changes

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

< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

I certified that

  • I have read and followed contributing guidelines
  • I discussed changes with code owners prior to submitting this pull request
  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the documentation accordingly

Make sure to have followed the contributing guidelines before submitting.

@Kesari3008 Kesari3008 added the validated If the pull request is validated for automation. label May 6, 2026
@Kesari3008 Kesari3008 marked this pull request as ready for review May 7, 2026 08:04
@Kesari3008 Kesari3008 requested a review from a team as a code owner May 7, 2026 08:04
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f171b6631e

ℹ️ 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".

Comment on lines +179 to +181
const eventName = context
? AIAssistantEventName.ADD_SUGGESTIONS_EXTRA_CONTEXT
: AIAssistantEventName.GET_SUGGESTIONS;
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Derive suggestion event from trimmed context

getSuggestedResponse() chooses ADD_SUGGESTIONS_EXTRA_CONTEXT based on the raw context value, but sends context?.trim() to the backend. If callers pass whitespace-only input (common from text fields), this emits the “add extra context” event with an empty context payload, which can be rejected or ignored by the AI service instead of issuing a normal GET_SUGGESTIONS request.

Useful? React with 👍 / 👎.

Comment on lines +104 to +106
case CC_EVENTS.POST_CALL_SUMMARY:
case CC_EVENTS.MID_CALL_SUMMARY:
break;
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Emit summary RTD events instead of dropping them

This switch now explicitly swallows POST_CALL_SUMMARY and MID_CALL_SUMMARY RTD messages. Before this change, RTD payload types were re-emitted to the task, so these events would reach SDK consumers; after this commit they are silently discarded, which prevents any listener from receiving summary payloads even though these event constants were added to CC_EVENTS in the same change.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 48f08b217c

ℹ️ 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".

Comment on lines +101 to +103
case CC_EVENTS.SUGGESTED_RESPONSE_ACKNOWLEDGE:
// TODO: Handling this event
break;
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Emit suggested-response acknowledge events to tasks

CC_EVENTS.SUGGESTED_RESPONSE_ACKNOWLEDGE was added as a task event, but this switch currently swallows it instead of re-emitting on the task. In environments where clients wait for an acknowledge before updating UI/request state, those listeners will never fire, so consumers cannot observe the backend acknowledgment despite the event being part of the exported event surface.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

validated If the pull request is validated for automation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant