transfer_contact
¶
transfer_contact(
instance_id: InstanceId,
contact_id: ContactId,
contact_flow_id: ContactFlowId,
*,
config_overrides: Optional[ConnectClientConfig] = None,
queue_id: Optional[QueueId] = None,
user_id: Optional[AgentResourceId] = None,
client_token: Optional[ClientToken] = None,
) -> TransferContactResponse
Transfers TASK or EMAIL contacts from one agent or queue to another agent or queue at any point after a contact is created. You can transfer a contact to another queue by providing the flow which orchestrates the contact to the destination queue. This gives you more control over contact handling and helps you adhere to the service level agreement (SLA) guaranteed to your customers.
Note the following requirements:
-
Transfer is only supported for
TASKandEMAILcontacts. -
Do not use both
QueueIdandUserIdin the same call. -
The following flow types are supported: Inbound flow, Transfer to agent flow, and Transfer to queue flow.
-
The
TransferContactAPI can be called only on active contacts. -
A contact cannot be transferred more than 11 times.
Parameters:
-
instance_id(InstanceId) –The identifier of the Connect Customer instance. You can find the instance ID in the Amazon Resource Name (ARN) of the instance.
-
contact_id(ContactId) –The identifier of the contact in this instance of Connect Customer.
-
queue_id(Optional[QueueId], default:None) –The identifier for the queue.
-
user_id(Optional[AgentResourceId], default:None) –The identifier for the user. This can be the ID or the ARN of the user.
-
contact_flow_id(ContactFlowId) –The identifier of the flow.
-
client_token(Optional[ClientToken], default:None) –A unique, case-sensitive identifier that you provide to ensure the idempotency of the request. If not provided, the Amazon Web Services SDK populates this field. For more information about idempotency, see Making retries safe with idempotent APIs.
Raises:
-
AccessDeniedException–You do not have sufficient permissions to perform this action.
-
IdempotencyException–An entity with the same name already exists.
-
InternalServiceException–Request processing failed because of an error or failure with the service.
-
InvalidRequestException–The request is not valid.
-
ResourceNotFoundException–The specified resource was not found.
-
ServiceQuotaExceededException–The service quota has been exceeded.
-
ThrottlingException–The throttling limit has been exceeded.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_connect/_services/connect.py
24791 24792 24793 24794 24795 24796 24797 24798 24799 24800 24801 24802 24803 24804 24805 24806 24807 24808 24809 24810 24811 24812 24813 24814 24815 24816 24817 24818 24819 24820 24821 24822 24823 24824 24825 24826 24827 24828 24829 24830 24831 24832 24833 24834 24835 24836 24837 24838 24839 24840 24841 24842 24843 24844 24845 24846 24847 24848 24849 24850 24851 24852 24853 24854 24855 24856 24857 24858 24859 24860 24861 | |