- 최신
- 최다 투표
- 가장 많은 댓글
If you know the ContactId (which you can save via a process of writing the ContactId to a location like DynamoDB) then use this API call
https://docs.aws.amazon.com/connect/latest/APIReference/API_StopContact.html
You can then create a process that reads from DynamoDB and stops the contacts. Keep in mind API limits, so build into this back off timers etc.
There's no way to manually remove specific contacts from a callback queue in Amazon Connect. You can either answer the callback contact, or wait until Amazon Connect removes the contact automatically after 7 to 14 days.
To remove all contacts from a callback queue, you can do any of the following:
Note: These are the only ways you can remove all contacts from a callback queue.
-
Manually answer the contacts in the queue.
-
Wait 7 to 14 days for Amazon Connect to remove the contacts automatically.
-
Deactivate the callback queue. Then, create a new callback queue to replace the deactivated queue. After you create the new callback queue, make sure that you do the following:
-
In the contact flow that you're using for queued callbacks, make sure that you change the Set working queue parameter to the new queue. For instructions, see Create a contact flow for queued callbacks.
-
Important: If you choose option 3, keep in mind the following:
Deactivating the callback queue doesn't remove the contacts from the queue. Deactivating the queue only prevents new contacts from being added to the queue.
If you don't change the Set working queue parameter in the associated contact flow to the new queue, then Amazon Connect doesn't create new callback contacts.
Any APIs that use the previous queue's Amazon Resource Name (ARN) must be updated with the new callback queue's ARN. For example: the GetMetricData action.
For more information, see Set up routing in the Amazon Connect Administrator Guide.
That's well articulated.
Update: A contact can be removed from Callback queue: https://docs.aws.amazon.com/connect/latest/adminguide/setup-queued-callback.html "To manually remove a callback from the queue, use the StopContact API."
Please refer to this Knowledge Center article: https://repost.aws/knowledge-center/connect-remove-callback-queue-contacts
Record every callback requests into the DynamoDB along with the callback contact ID. So you can go back and use the StopContact API to drop those requests.
관련 콘텐츠
- AWS 공식업데이트됨 4달 전
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 2년 전
Pretty sure the StopContact function wont work. When a contact is transferred to a callback queue, a new Contact is created, with an initiationMethod of "Callback". The very first thing on the reference above says the following:
Ends the specified contact. This call does not work for the following initiation methods: CALLBACK DISCONNECT TRANSFER QUEUE_TRANSFER
I have been trying to find a way to do this for some time now, due to customers calling back a higher priority line and being answered by agents before they receive their callback.
I wish AWS would enable a method of stopping a Callback contact, purely to help with wait times being blown out from this specific circumstance
Hi Vito! This ability to use the StopContact API for callbacks was released earlier this month. You can now use the StopContact API to remove callbacks from a queue if you have the Contact ID.
In order to use the StopContact API to remove a callbacks from the queue, I need to know the contact identifier for the queued callback. How do I get the contact identifier for the queued callback?