Create Contact Lens rules using the Amazon Connect admin website

Words or phrases: Choose from Exact match, Pattern match, or Semantic match to trigger an alert or task when keywords are uttered.

Agent: Build rules that run on a subset of agents. For example, create a rule to ensure newly hired agents comply with company standards.

To see agent names so you can add them to rules, you need Users - View permissions in your security profile.

Queues: Build rules that run on a subset of queues. Often organizations use queues to indicate a line of business, topic, or domain. For example, you could build rules specifically for your sales queues, tracking the impact of a recent marketing campaign or alternatively rules for your customer support queues, tracking overall sentiment.

To see the queue names so you can add them to rules, you need Queues - View permissions in your security profile.

Contact attributes: Build rules that run on the values of custom contact attributes. For example, you can build rules specifically for a particular line of business or for specific customers, such as based on their membership level, their current country of residence, or if they have an outstanding order.

You can add up to five contact attributes to a rule.

Sentiment - Time period: Build rules that run on the sentiment analysis results (positive, negative, or neutral) over a trailing window of time.

For example, you can build a rule for when customer sentiment has remained negative for a set period of time. If the participant joined the contact later, the time period set here applies to when participant was present.

When rules are applied to contacts that don't have sentiment data, neutral sentiment is used.

Sentiment - Entire contact: Build rules that run on the value of sentiment scores over an entire contact. For example, you can build a rule when customer sentiment has remained low for the entire contact, you can create a task for a customer experience analyst to review the call transcript and follow-up.

When rules are applied to contacts that don't have sentiment data, neutral sentiment is used.

Interruptions: Build rules that detect when the agent has interrupted the customer for more than X times. This feature applies to calls only.

Non-talk time: Build rules that run when periods of no talk time are detected. For example, when a customer and agent have not spoken for over 30 seconds which may indicate unnecessary customer wait time or highlight a customer services process that would benefit from optimisation. This feature applies to calls only.

Response time: Build rules to identify contacts where the participant had a response time longer or shorter than what was expected: Average or Maximum.

For example, you can set a rule on the Agent greeting time, also known as First response time: after the agent joined the chat, how long until they sent the first greeting message. This will help you to identify when an agent took too long to engage with the customer.

Create Task: this option is not available for real-time chat

Send email notification

Generate an EventBridge event