sent-analytics

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Sent Analytics

已发送消息分析

Use

numbers.lookup

dashboard.messages_sent

dashboard.deliverability

, and

dashboard.contacts

for read-only analytics.

使用

numbers.lookup

、

dashboard.messages_sent

、

dashboard.deliverability

和

dashboard.contacts

进行只读分析。

Establish context

建立上下文

Use client-managed OAuth 2.1/PKCE. Never request or expose a token, API key, authorization header, client ID, or secret. Identify the active organization and Sender Profile when the client exposes them. If the requested scope differs, reauthorize through the client rather than adding credentials or hidden scope fields.

Minimize sensitive output: mask phone numbers, aggregate where possible, and omit contact, KYC, account, and message-body data that is not needed to answer the question.

使用客户端管理的OAuth 2.1/PKCE。切勿请求或暴露令牌、API密钥、授权标头、客户端ID或密钥。当客户端暴露时，识别活跃组织和发送者配置文件。如果请求的范围不同，请通过客户端重新授权，而非添加凭据或隐藏范围字段。

尽量减少敏感输出：屏蔽电话号码，尽可能进行聚合，省略回答问题不需要的联系人、KYC、账户和消息正文数据。

Look up a number

查询号码

Use

numbers.lookup

to obtain available capability, formatting, type, or routing signals for the supplied number. A lookup describes capability; it is not evidence of opt-in, consent, ownership, identity, or permission to message. State that distinction whenever the result could be used to plan outreach.

使用

numbers.lookup

获取提供号码的可用功能、格式、类型或路由信号。查询结果仅描述号码功能，并不代表用户已选择加入、同意、拥有该号码、身份验证或发送消息的权限。每当结果可能用于规划触达时，需明确说明这一区别。

Query dashboard metrics

查询仪表板指标

Resolve an explicit date range and timezone before calling a dashboard tool. If the user omits either, ask or clearly state the assumption.
Use
```
dashboard.messages_sent
```
for sent-volume metrics.
Use
```
dashboard.deliverability
```
for aggregate acceptance and delivery outcomes.
Use
```
dashboard.contacts
```
for aggregate contact metrics.
Keep comparisons on the same organization, Sender Profile, date range, timezone, channel, and aggregation grain unless the user explicitly requests otherwise.

Every result must state the date range and timezone used. Label accepted, sent, delivered, failed, and unknown states according to what the response actually establishes; never collapse accepted into delivered.

在调用仪表板工具前，确定明确的日期范围和时区。如果用户未提供其中任意一项，请询问用户或明确说明假设条件。
使用
```
dashboard.messages_sent
```
获取发送量指标。
使用
```
dashboard.deliverability
```
获取聚合的接收和送达结果。
使用
```
dashboard.contacts
```
获取聚合的联系人指标。
除非用户明确要求，否则比较时需保持同一组织、发送者配置文件、日期范围、时区、渠道和聚合粒度。

每个结果必须说明所使用的日期范围和时区。根据响应实际确定的状态，标记接收、已发送、已送达、失败和未知状态；切勿将接收状态合并到已送达状态中。

Choose aggregate analytics or diagnosis

选择聚合分析或诊断

Use this skill for dashboard totals, rates, and trends. Use

messaging-performance-analyzer

when the request involves message-level delivery records, funnel drop-off, error-code clustering, or root-cause diagnosis. A deliverability dashboard can locate a change; it does not by itself prove the operational cause.

使用本技能获取仪表板的总数、比率和趋势。当请求涉及消息级别的送达记录、漏斗流失、错误码聚类或根本原因诊断时，请使用

messaging-performance-analyzer

。送达率仪表板可以定位变化，但本身无法证明运营原因。