[IC3 ACS Chat ] API Review

New API Review meeting has been requested.

**Service Name**: IC3 ACS Chat
**Review Created By**: Andrei Giurgiu
**Review Date**: 06/29/2023 04:00 PM PT
**Onboarding Record**:
**PR**: https://github.com/Azure/azure-rest-api-specs/pull/24243
**Hero Scenarios Link**: [here](https://microsoft.sharepoint-df.com/:p:/t/IC3SDK-Chat-Private/EXhTjnKRh5xFt6XpCEOz3vUBm11Qe5F6XojfNkCZVSK6jw?e=1MQ6LG)
**Core Concepts Doc Link**: Not Provided

**Description**: With these API changes, we are giving developers the ability to store additional contextual information about chat threads and chat participants. This metadata can give the flexibility to our customers to implement logic specific to their use cases and systems. For example, customers could link different related chat threads to each other and specify the thread types according to their own scenarios.

This metadata could also be used to pass in contextual information that other chat participants - call center agents, bots - can use to communicate on the chat threads (e.g. locale and timezone).

Special considerations: The Participant API doesn't have a PATCH yet. It will be added in a future API version. This is an existing problem for updating Participant display names.

Detailed meeting information and documents provided can be accessed [here](https://web.powerapps.com/apps/e41c69de-ef96-44ba-b287-0e012e7c13ae?view=edit&event=8cadd512-a000-ee11-8f6e-000d3a341a24)
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation [here](https://aka.ms/azsdk/onboarding/restapischedule)

Start with PR #24243 and the API review requirements and scheduling documentation linked in the issue. The issue provides meeting and design context but no source file, test, or standalone implementation task; the review outcome would need to be established before defining what done means.

Written by the indexing model from the issue text.