AWS connect documentation change
Summary
Updated documentation about in-progress contact search capabilities across different channels
Security assessment
Change describes functional capabilities rather than security controls or vulnerabilities. No security implications identified in the diff.
Diff
diff --git a/connect/latest/adminguide/search-in-progress-contacts.md b/connect/latest/adminguide/search-in-progress-contacts.md index 817090581..8085b078a 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 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. +The ability to search for in-progress contacts varies by channel (see [Contact events data model](./contact-events.html#contact-events-data-model) for reference): @@ -19 +19,5 @@ The permissions needed to search for in-progress contacts are the same as those - * **For in-progress chats, tasks, and email contacts** : The **Contact search** page displays all in-progress contacts after they are initiated. + * **Voice** : You can search for contacts after they have been either connected to an agent, or have been disconnected. Queued in-progress contacts including queued callbacks are not shown on the **Contact search** page. + + * **Chat** : You can search for contacts after they are connected to system, queued, connected to an agent or disconnected. + + * **Tasks** and **Email** : You can search for all in-progress after they are initiated.