Enable Amazon Connect Contact Lens

You can enable Amazon Connect Contact Lens in a few steps. Add a Set recording and analytics behavior block to a flow, and configure it to enable Contact Lens for voice, chat, or both.

The following image shows a block that's configured for call recording, and Contact Lens speech analytics and chat analytics. The Call recording option is set to Agent and customer. In the Analytics section, the options are selected for speech and chat.

The procedures in this topic describe the steps to enable Contact Lens for call or chat analytics.

Important things to know

• Collect data after transferring a contact: If you want to continue using Contact Lens to collect data after transferring a contact to another agent or queue, you need to add another Set recording and analytics behavior block with Enable analytics enabled for the flow. This is because a transfer generates a second contact ID and contact record. Contact Lens needs to run on that contact record as well.

• When you select Enable Contact Lens conversational analytics, you must choose to enable speech or chat analytics. Otherwise, your flow will display an error when you publish it.

• Where you place the Set recording and analytics behavior block in a flow affects the agent's experience with key highlights. For more information, see Design a flow for key highlights.

Enable call recording and speech analytics

1. In the Set recording and analytics behavior block, under Call recording, choose On, Agent and Customer.

   Both agent and customer call recordings are required to use Contact Lens for voice contacts.

2. Under Analytics, choose Enable Contact Lens conversational analytics, Enable speech analytics.

   If you don't see this option, Amazon Connect Contact Lens hasn't been enabled for your instance. To enable it, see Update instance settings.

3. Choose one of the following:

   1. Post-call analytics: Contact Lens analyzes the call recording after the conversation and After Contact Work (ACW) is complete. This option provides the best transcription accuracy.

   2. Real-time analytics: Contact Lens provides both real-time insights during the call, and post-call analytics after the conversation has ended and After Contact Work (ACW) is complete.

      If you choose this option, we recommend setting up alerts based on keywords and phrases that the customer may utter during the call. Contact Lens analyzes the conversation real-time to detect the specified keywords or phrases, and alerts supervisors. From there, supervisors can listen in on the live call and provide guidance to the agent to help them resolve the issue faster.

      For information about setting up alerts, see Alert supervisors in real-time based on keywords and phrases mentioned during a call.

      If your instance was created before October 2018, additional configuration is needed to access real-time call analytics. For more information, see Service-linked role permissions for Amazon Connect.

4. Choose the language. For a list of available languages for various Contact Lens features, see Supported languages.

   For instructions on using an attribute, see Use contact attributes.

5. Optionally, enable redaction of sensitive data. For more information, see the next section, Enable redaction.

6. Choose Save.

7. If the contact is going to be transferred to another agent or queue, repeat these steps to add another Set recording and analytics behavior block with Enable Contact Lens for conversational analytics enabled.

Enable chat analytics

1. In the Set recording and analytics behavior block, under Analytics, choose Enable Contact Lens conversational analytics, and Enable chat analytics.

   Note

   By choosing this option you will receive both real-time and post-chat analytics.

   If you don't see this option, Amazon Connect Contact Lens hasn't been enabled for your instance. To enable it, see Update instance settings.

2. Choose the language. For a list of available languages for various Contact Lens features, see Supported languages.

   For instructions on using an attribute, see Use contact attributes.

3. Optionally, enable redaction of sensitive data. For more information, see the next section, Enable redaction of sensitive data.

4. Choose Save.

5. If the contact is going to be transferred to another agent or queue, repeat these steps to add another Set recording and analytics behavior block with Enable Contact Lens for conversational analytics enabled.

Enable redaction of sensitive data

To enable redaction of sensitive data in a flow, choose Redact sensitive data. When redaction is enabled you can choose from the following options:

• Redact all personally identifiable information (PII) data (all PII entities supported).

• Choose which PII entities to redact from the list of supported entities.

If you accept the default settings, Contact Lens redacts all personally identifiable information (PII) it identifies, and replaces it with [PII] in the transcript. The default settings are shown in the following image because the following options are selected: Redact sensitive data, Redact All PII data, and Replace with placeholder PII.

Select PII entities to redact

Under the Data redaction section, you can select specific PII entities to redact. The following image shows that Credit/Debit Card Number is going to be redacted.

Choose data redaction replacement

Under the Data redaction replacement section, you can choose the mask to be used as data redaction replacement. For example, in the following image, the Replace with placeholder PII option indicates that PII will replace the data.

For more information about using redaction, see Use sensitive data redaction.

Review sensitive data redaction for accuracy

The redaction feature is designed to identify and remove sensitive data. However, due to the predictive nature of machine learning, it may not identify and remove all instances of sensitive data in a transcript generated by Contact Lens. We recommend you review any redacted output to ensure it meets your needs.

Important

The redaction feature does not meet the requirements for de-identification under medical privacy laws like the U.S. Health Insurance Portability and Accountability Act of 1996 (HIPAA), so we recommend you continue to treat it as protected health information after redaction.

For the location of redacted files and examples, see Output file locations.

Dynamically enable Contact Lens using contact attributes

You can dynamically enable Contact Lens and the redaction of the output files based on the language of the customer. For example, for customers using en-US, you may want only a redacted file whereas for those using en-GB, you may want both the original and redacted output files.

• Redaction: choose one of the following (they are case sensitive)

  • None

  • RedactedOnly

  • RedactedAndOriginal

• Language: Choose from the list of available languages.

You can set these attributes in the following ways:

• User defined: use a Set contact attributes block. For general instructions about using this block, see How to reference contact attributes. Define the Destination key and Value for redaction and language as needed.

  The following image shows an example of how you can configure the Set contact attributes block to use contact attributes for redaction. Choose the Use text option, set Destination key to redaction_option, and set Value to RedactedAndOriginal.

  Note

  Value is case sensitive.

  

  The following image show how to use contact attributes for language. Choose the Use text option, set Destination key to language, set Value to en-US.

  

• Use a Lambda function. This is similar to how you set up user-defined contact attributes. An AWS Lambda function can return the result as a key-value pair, depending on the language of the Lambda response. The following example shows a Lambda response in JSON:

  {
     'redaction_option': 'RedactedOnly',
     'language': 'en-US'
  }
  

Design a flow for key highlights

Transcripts are visible to agents using the Contact Control Panel (CCP) depending on whether Contact Lens analytics is enabled in the Set recording and analytics behavior in the inbound flow, and/or a transfer flow.

This section provides three use cases for enabling Contact Lens analytics in the Set recording and analytics behavior block, and describes how they affect the agent's experience with key highlights.

Use case 1: Contact Lens analytics is enabled in an inbound flow only

• A contact enters the inbound flow, and there are no call transfers. Following is the agent experience:

  The agent receives the full transcript during After Contact Work (ACW). The transcript includes everything said by the agent and the customer, from the moment the agent accepts the initial call, until the call has ended, as shown in the following image.

  

• A contact enters the inbound flow, and there is a call transfer. Following is the agent experience:

  • Agent 1 receives a call transcript after they leave the conference/warm transfer, during ACW.

    The transcript includes everything said by agent 1 and the customer, from the moment the agent accepts the initial call, until the agent 1 leaves the conference/warm transfer portion of the call. The transcript includes the flow (transfer/queue flow) prompt messages, as shown in the following image.

    

  • Agent 2 receives a call transcript at the time of accepting the conference/warm transfer call from agent 1.

    The transcript includes everything said by agent 1 and the customer, from the moment agent 1 accepts the initial call until the agent 1 leaves the conference/warm transfer portion of the call. The transcript includes the flow (transfer/queue flow) prompt messages, and the warm transfer conversation, as shown in the following image.

    

    Because Contact Lens is not enabled in the transfer flow, agent 2 doesn't see the remainder of the transcript when the call has ended and they enter ACW. The following image of ACW for agent 2 shows the transcript is empty.

    

Use case 2: Contact Lens analytics is enabled in an inbound flow and a transfer flow (quick connect)

• A contact enters the inbound flow, and there are no call transfers. Following is the agent experience:

  • Agent 1 receives a full call transcript (unredacted) during ACW.

    The transcript includes everything said by agent 1 and the customer from the moment the agent accepts the call, until the call has ended. This is shown in the following image of the CCP for agent 1.

    

• A contact enters the inbound flow, and there is a call transfer. Following is the agent experience:

  • Agent 1 receives a call transcript after they leave the conference/warm transfer, during ACW.

    The transcript includes everything said by agent 1 and the customer from the moment agent 1 accepts the call, until agent 1 leaves the conference/warm transfer portion of the call. The transcript includes flow (transfer/queue flow) prompt messages.

    The full call transcript until warm transfer is shown in the following image.

    

  • Agent 2 receives a call transcript at the time of accepting the conference/warm transfer call from agent 1.

    The transcript includes everything said by agent 1 and the customer, from the moment agent 1 accepts the call, until agent 1 leaves the conference/warm transfer portion of the call. The transcript includes the flow (transfer/queue flow) prompt messages.

  • Because Contact Lens is enabled in the transfer flow, agent 2 receives a call transcript after the call is completed, during ACW.

    The transcript includes only the remaining portion of the call between agent 2 and customer, after agent 1 has left the call. The transcript includes everything said by agent 2 and the customer, from the moment they are conferenced/warm transferred in, until the call has ended. An example transcript is shown in the following image.

    

What if the flow block fails to enable Contact Lens?

It's possible that the Set recording and analytics behavior block can fail to enable Contact Lens on a contact. If Contact Lens isn't enabled for a contact, check the flow logs for the error.

Multi-party calls and Contact Lens

Contact Lens supports calls with up to 2 participants. For example, if there are more than two parties (agent and customer) on a call, or a call is getting transferred to a third party, the quality of the transcription and analytics, such as sentiment, redaction, categories among others, can get degraded. We recommend you disable Contact Lens for multi-party or third-party calls if there are more than two parties (agent and customer). For information on disabling Contact Lens for a contact, see Flow block: Set recording and analytics behavior.