AWS connect documentation change
Summary
Clarified contact search behavior by separating voice contact rules from chat/task/email contacts
Security assessment
Change improves documentation clarity about contact visibility in UI but contains no security-related content or references to vulnerabilities
Diff
diff --git a/connect/latest/adminguide/search-in-progress-contacts.md b/connect/latest/adminguide/search-in-progress-contacts.md index 5293600b8..817090581 100644 --- a//connect/latest/adminguide/search-in-progress-contacts.md +++ b//connect/latest/adminguide/search-in-progress-contacts.md @@ -17 +17 @@ The permissions needed to search for in-progress contacts are the same as those - * For voice and chat contacts, the **Contact search** page shows only in-progress contacts after they are connected with an agent. Contacts that are queued (including queued callbacks) are not displayed on the **Contact search** page. + * **For in-progress voice contacts** : The **Contact search** page shows only in-progress contacts after they are connected with an agent. In-progress contacts that are queued (including queued callbacks) are not displayed on the **Contact search** page. @@ -19,5 +19 @@ The permissions needed to search for in-progress contacts are the same as those - * For in-progress voice and chat contacts, contacts that are queued (including queued callbacks) are not displayed on the **Contact search** page. - - * For tasks, the **Contact search** displays all in-progress contacts after they are initiated. - - * For email, the **Contact search** displays all in-progress contacts after they are initiated. + * **For in-progress chats, tasks, and email contacts** : The **Contact search** page displays all in-progress contacts after they are initiated.