Skip to content

/AWS1/IF_CNT=>TRANSFERCONTACT()

About TransferContact

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 TASK and EMAIL contacts.

  • Do not use both QueueId and UserId in the same call.

  • The following flow types are supported: Inbound flow, Transfer to agent flow, and Transfer to queue flow.

  • The TransferContact API can be called only on active contacts.

  • A contact cannot be transferred more than 11 times.

Method Signature

IMPORTING

Required arguments:

iv_instanceid TYPE /AWS1/CNTINSTANCEID /AWS1/CNTINSTANCEID

The identifier of the Amazon Connect instance. You can find the instance ID in the Amazon Resource Name (ARN) of the instance.

iv_contactid TYPE /AWS1/CNTCONTACTID /AWS1/CNTCONTACTID

The identifier of the contact in this instance of Amazon Connect.

iv_contactflowid TYPE /AWS1/CNTCONTACTFLOWID /AWS1/CNTCONTACTFLOWID

The identifier of the flow.

Optional arguments:

iv_queueid TYPE /AWS1/CNTQUEUEID /AWS1/CNTQUEUEID

The identifier for the queue.

iv_userid TYPE /AWS1/CNTAGENTRESOURCEID /AWS1/CNTAGENTRESOURCEID

The identifier for the user. This can be the ID or the ARN of the user.

iv_clienttoken TYPE /AWS1/CNTCLIENTTOKEN /AWS1/CNTCLIENTTOKEN

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.

RETURNING

oo_output TYPE REF TO /aws1/cl_cntxfercontactrsp /AWS1/CL_CNTXFERCONTACTRSP

Domain /AWS1/RT_ACCOUNT_ID
Primitive Type NUMC

Examples

Syntax Example

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->/aws1/if_cnt~transfercontact(
  iv_clienttoken = |string|
  iv_contactflowid = |string|
  iv_contactid = |string|
  iv_instanceid = |string|
  iv_queueid = |string|
  iv_userid = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_contactid = lo_result->get_contactid( ).
  lv_arn = lo_result->get_contactarn( ).
ENDIF.