transfer_contact
async
¶
transfer_contact(
instance_id: InstanceId,
contact_id: ContactId,
contact_flow_id: ContactFlowId,
*,
config_overrides: Optional[AsyncConnectClientConfig] = 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/async_connect.py
25124 25125 25126 25127 25128 25129 25130 25131 25132 25133 25134 25135 25136 25137 25138 25139 25140 25141 25142 25143 25144 25145 25146 25147 25148 25149 25150 25151 25152 25153 25154 25155 25156 25157 25158 25159 25160 25161 25162 25163 25164 25165 25166 25167 25168 25169 25170 25171 25172 25173 25174 25175 25176 25177 25178 25179 25180 25181 25182 25183 25184 25185 25186 25187 25188 25189 25190 25191 25192 25193 25194 25195 | |