[IC3 ACS Cross Platform Messaging ] API Review

[azure-sdk]

New API Review meeting has been requested.

Service Name: IC3 ACS Cross Platform Messaging Review Created By: Chi Liu Review Date: 01/30/2025 04:00 PM PT Release Plan: PR: Hero Scenarios Link: Not Provided Core Concepts Doc Link: Not Provided

Description: ACS Unified Messaging Threaded Conversation enables customer to manage their conversations in threads for messaging platforms like SMS / WhatsApp / Email / etc. With Threaded Conversation, customer will be able to have agent management, retrieve message history, and run message analysis on a conversation. WhatsApp is the first supported platform.

Detailed meeting information and documents provided can be accessed here For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

[azure-sdk]

Meeting updated by Chi Liu

Service Name: IC3 ACS Cross Platform Messaging Review Created By: Chi Liu Review Date: 01/30/2025 04:00 PM PT Release Plan: PR: https://github.com/Azure/azure-rest-api-specs/pull/32411 Hero Scenarios Link: here Core Concepts Doc Link: Not Provided

Description: ACS Unified Messaging Threaded Conversation enables customer to manage their conversations in threads for messaging platforms like SMS / WhatsApp / Email / etc. With Threaded Conversation, customer will be able to have agent management, retrieve message history, and run message analysis on a conversation. WhatsApp is the first supported platform.

Detailed meeting information and documents provided can be accessed here For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

[mikekistler]

Notes from API Review 1/30/25

• Why is create conversation not a create TypeSpec operation ?
  • Because create may include the first message
• AI Summary should be a ResourceAction operation
  • ResourceCollectionAction is an action on all conversations
• Recommend better doc on "internal only"
• Be careful with "internal" vs "external" enum -- could be difficult to extend.
• Create operation typically returns the resource that was just created
  • Recommend adopting this pattern, but if you need something different, create service-specific typespec operation templates to establish the service pattern
• Consider renaming Delete to terminate, since it does not delete the resource
  • And use ResourceAction (POST)
• And consider providing a true Delete operation to delete the resource
• Pls document when query parameters are needed and what takes precedence when both are provided.
• Should the message be polymorphic? To allow content other than string?
• Consider having options to select what AI to perform on the conversation
• We're trying to move away from HMac, try to avoid it if possible.

TypeSpec only allows auth at the service level, but some operations are one or the other.

This looks good for preview. Please consider the items above as you work towards your next preview.