---
title: "Customer Agent event data reference"
description: "You will learn about the four specific metrics Klaviyo tracks for Customer Agent interactions. Understanding these events allows you to build segments based on customer interaction or conversation outcomes. These segments can be used for targeting in your campaigns and flows to re-engage shoppers who interacted with your Customer Agent."
canonical_url: "https://help.klaviyo.com/hc/en-us/articles/44813293727131"
markdown_url: "https://help.klaviyo.com/hc/en-us/articles/44813293727131.md"
locale: "en-us"
category: "Customer Agent"
section: "Analyze"
updated: "2026-11-12"
---

# Customer Agent event data reference

## You will learn

Learn what events Customer Agent emits to your Klaviyo account, what data each event carries, and how to use those events to build segments and flows.

## How Customer Agent events work

The built-in events listed below fire automatically — there’s no configuration needed. When linked to a profile, events show up alongside your other Klaviyo profile activity. You can use them to build segments, trigger flows, and reference in reports.

Klaviyo associates events with shoppers using the available email address, phone number, profile ID, or anonymous ID. If no shopper identifier is available, no event is recorded. This profile information is separate from the event properties listed below.

To view Customer Agent events, navigate to **Analytics > Metrics**, search for Customer Agent, and select a metric. Open its **Activity feed** to see recent events.

To see events for a specific shopper, open their profile’s **Activity log**.

## Events

| **Event** | **Fires when** | **Key properties** |
| --- | --- | --- |
| Started Customer Agent Conversation | Customer Agent starts handling a shopper’s message in a new conversation | Conversation ID, Channel, Initial skill |
| Resolved Customer Agent Conversation | A conversation is closed and classified as resolved by AI | Conversation ID, Channel, Final skill, Tags |
| Escalated Customer Agent Conversation | Customer Agent triggers a handoff or a conversation is routed to your team | Conversation ID, Channel, Escalation reason, Tags |
| Received Product Recommendation from Customer Agent | Customer Agent surfaces product recommendations | Conversation ID, Channel, Products |

### Started Customer Agent Conversation

Fires when Customer Agent starts handling a shopper’s message in a new conversation.

**Properties:**

- Conversation ID

- Channel (web chat, email, SMS, WhatsApp)

- Initial skill (initial_skill): the skill detected at the start of the conversation



### Resolved Customer Agent Conversation

Fires when a conversation is closed and classified as resolved by AI. This classification does not require the shopper to confirm that their issue was solved.

**Properties:**

- Conversation ID

- Channel

- Final skill (final_skill): the last detected skill before the conversation closed

- Tags



### Escalated Customer Agent Conversation

Fires when Customer Agent triggers a handoff, such as for an escalation rule or a shopper request, or when a conversation is routed to your team. A handoff can trigger this event before the shopper accepts it.

**Properties:**

- Conversation ID

- Channel

- Escalation reason (escalation_reason): a category such as knowledge_gap, explicit_ask, or custom_guidance

- Tags



### Received Product Recommendation from Customer Agent

Fires when Customer Agent surfaces product recommendations to a shopper.

**Properties:**

- Conversation ID

- Channel

- Products (products): a list that includes each recommended product’s ID, title, and URL



## Custom events from skills

A custom workflow can record an event using the Send Event tool (beta). For the skill-based setup described in the linked guide, insert and configure the tool in a custom skill and review its permission in Connectors. Send Event uses an existing metric, requires an authenticated shopper, and records the properties you configure from the agent’s responses, fixed values, or supported profile fields.

Find these events under the metric name you selected in the tool, in Analytics > Metrics or the shopper’s profile Activity log. Use that metric to trigger a flow or create a segment, and use its custom event properties to narrow the audience or personalize follow-up. The properties shown for the built-in events above are not automatically added to your custom event.

For prerequisites, setup steps, an example, and testing, see “Record custom events from a skill” in [Customer Agent profile tools](https://help.klaviyo.com/hc/en-us/articles/50972391959835.md).

## Example segments

For the 3 segment examples below, use **What someone has done (or not done)** to add each event condition.

### Re-engage shoppers who got a product recommendation

> Profile has at least 1 *Received Product Recommendation from Customer Agent* in the last 14 days **AND** has placed an order zero times in the last 14 days

Use this segment to trigger a follow-up flow with a soft nudge or discount. It excludes shoppers who placed any order in the last 14 days, including before they received a recommendation.

### Exclude recently escalated shoppers from automated outreach

> Profile has at least 1 *Escalated Customer Agent Conversation* in the last 7 days

Add this segment as an exclusion to your campaign targeting to avoid contacting shoppers with recent escalation activity. This segment does not show whether their service conversation is still open.

For flows, add a profile filter requiring *Escalated Customer Agent Conversation* zero times in the last 7 days.

### Identify purchasers with resolved conversations

> Profile has at least 1 *Resolved Customer Agent Conversation* in the last 30 days **AND** has placed an order in the last 30 days

Use this as a positive signal for VIP segmentation. The 2 conditions are checked independently, so an order may have occurred before the conversation. This segment does not measure post-conversation conversion.

## Next steps

- **Build segments** in Klaviyo using these events — see [Segmentation in Klaviyo](https://help.klaviyo.com/hc/en-us/articles/115005237908.md)

- **Trigger flows** off Customer Agent events for follow-up messages

- **Review the dashboard** for aggregate trends — see [*Understanding the performance dashboard*](https://help.klaviyo.com/hc/en-us/articles/37659376435483.md)

## Additional resources

- [Getting started with Customer Agent](https://help.klaviyo.com/hc/en-us/articles/37659268052635.md)
  Learn how to activate Klaviyo's Customer Agent, an AI-powered tool that provides instant support to your website visitors. Customer Agent ingests information from your Shopify store, and learns any additional information you provide, to answer shopper inquiries across web chat, email, SMS, and WhatsApp.
- [Understanding the performance dashboard](https://help.klaviyo.com/hc/en-us/articles/37659376435483.md)
  Learn how to use the performance dashboard to analyze your Customer Agent’s performance and monitor its interactions.
- [Segment conditions reference](https://help.klaviyo.com/hc/en-us/articles/115005062847.md)
  Learn more about segment conditions, including how to filter your conditions and more. When building segments in Klaviyo, conditions are the building blocks that you customize to either include or exclude certain sectors of your audience. In a nutshell, profiles will only appear in your dynamic segments when they meet the specific conditions you make when creating the segment. 
