收藏仪表板或报告后，它将列在您的 **已收藏仪表板** 或 **已收藏报告** 选项卡中，以便轻松访问。
## 日志
CX 分析日志为单个互动或事件及其关联详情提供原始行级数据。使用这些日志排查问题或分析一段时间内的趋势。可用日志类型定义如下：
* **互动日志**：捕获已关闭互动的所有详细信息，包括时间线和关键事件，为跟踪和分析提供清晰记录。
* **客服人员状态日志**：捕获所有客服人员工作会话，以及客服人员在这些工作会话中经历的各个事件。
* **客服人员选择加入/退出日志**：跟踪客服人员及其关联队列的所有选择加入/退出操作。
* **Zoom Phone 和呼叫中心呼叫旅程**：为同时使用 Zoom 呼叫中心和 Zoom Phone 的用户提供整合视图，从而能够无缝跟踪跨两个系统的完整客户旅程。
## 订阅
CX 分析订阅仅适用于报告，不适用于仪表板。它们可在指定时间段内自动发送呼叫中心绩效快照。如果您需要定期获取历史数据，订阅可免除手动生成报告的需要。
您可以订阅任何默认报告或您创建的自定义报告。选择报告后，您可以应用可选筛选器来细化数据。例如，您可能希望筛除某些队列、频道或客服人员，以专注于呼叫中心绩效的特定细分。
配置筛选器后，您将设置发送设置。这些设置允许您选择时区，并定义接收报告的时间和方式。您可以指定发送频率、发送报告的确切时间以及首选格式。目前提供两种发送格式：CSV (.csv) 和 Excel (.xlsx)。报告仅通过电子邮件发送，单个订阅最多可添加 300 位电子邮件收件人。
{% hint style="info" %}
如果您应用筛选器来细化报告数据，通过电子邮件接收的文件将遵循这些筛选器。
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://library.zoom.com/technical-library/zh/shang-ye-ban-fu-wu/zoom-contact-center/zoom-customer-experience/analytics-and-reporting/cx-analytics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
