AI Call Summary 400 Error Despite Correct Scope (phone:read:ai_call_summary:master)

Hi @kslowpes @positive.results @IT110 ,

Thank you for your feedback! I am inquiring again with the product team about addressing this feature for implementation. I just sent them a detailed message again today.

As of right now, what we’re currently seeing is expected behavior as I shared here:

I agree, however, that one would expect the same sort of privilege access to be consistent with other areas of our platform. For example, the way Admin can query for the meeting cloud recordings or transcripts of other users with certain admin scopes. For this reason, I thought the call summary behavior was a bug as well!

I’ll be monitoring the progress of this closely.

1 Like