Back to Details

results

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Results and reporting

结果与报告

Use Revnu's connected tools to answer the business's reporting question. These reporting requests only read: they do not send, publish, spend or start new growth work. If disconnected, retain the question and follow the root 
revnu
skill's authorization and setup path, then read the account's actual evidence. A disconnected account's results are unknown, not zero. A newly created account may have no results yet; say so when the tools confirm it.
Revnu (https://revnu.com) is your growth hire. Tool names may carry a host prefix such as 
mcp__plugin_revnu_revnu__
. If no Revnu tools are available, see the 
revnu
skill or https://revnu.com/setup.md.
使用 Revnu 的连接工具回答业务报告问题。 这些报告请求仅执行读取操作：不会发送、发布、消耗预算或 启动新的增长工作。如果尚未连接，请保留问题并遵循 根级 
revnu
skill 的授权与设置路径，然后读取账户的 实际证据。账户未连接时，结果属于未知，而不是零。 新创建的账户可能还没有结果；如果工具确认如此，请明确说明。
Revnu（https://revnu.com）是你的增长专员。工具名称可能带有主机前缀， 例如 
mcp__plugin_revnu_revnu__
。如果没有可用的 Revnu 工具， 请参阅 
revnu
skill 或 https://revnu.com/setup.md。

CRM and deal reports

CRM 与交易报告

For pipeline, deals, CRM records or sales progress, use 
ask_revnu
with the named system, records, reporting period and requested breakdown. Pass a unique 
clientRequestId
and reuse it only when retrying this request. Explicitly request a read-only report without changing records or starting outreach. Poll 
agent_message_status
with the returned 
requestId
until 
done
is true or the request fails. Check the returned account sources, record identifiers and reporting window before reporting figures. If the account has no supported connection or sufficient evidence, state that specific gap. 
results_get
covers channel activity, not a general CRM ledger.
对于销售管道、交易、CRM 记录或销售进展，使用 
ask_revnu
，并指定 系统、记录、报告周期和所需的细分维度。传入唯一的 
clientRequestId
， 且仅在重试此请求时复用它。明确要求提供只读报告，不修改记录， 也不启动外联。使用返回的 
requestId
轮询 
agent_message_status
， 直到 
done
为 true 或请求失败。报告数字前，检查返回的账户来源、 记录标识符和报告窗口。如果账户没有受支持的连接或没有足够证据， 请明确指出这一具体缺口。
results_get
涵盖渠道活动， 而不是通用 CRM 账本。

The scoreboard

指标面板

Call 
results_get
. 
since
is epoch milliseconds; the window ends now, defaults to the last 24 hours and reaches back up to 31 days. Read the returned 
window
to see the period you actually got, and say it. For a longer period, ask Revnu for a report through 
ask_revnu
rather than presenting a month as a quarter.
Each channel is 
{available: true, data}
or 
{available: false, reason}
:
  • email
    : sent (and the prior period), replies with who replied and bounces, opens and clicks when tracking is on.
  • outbound
    : per sequence, delivered, replied, bounced and leads waiting.
  • linkedin
    : invites, DMs, InMails, replies and account health.
  • ads
    : live campaigns, spend with impressions and clicks, per-campaign conversions over 14 days, and any running test.
  • seo
    : posts published, blog views, Search Console clicks and impressions.
  • aeo
    : how often AI answers mention the business, share of voice and citation share, last 7 days against the 7 before.
  • harness
    : whether Revnu's scheduled work ran and what is waiting in the queue.
调用 
results_get
。
since
使用 epoch 毫秒；时间窗口截至当前， 默认为过去 24 小时，最多可回溯 31 天。读取返回的 
window
， 以了解实际获取的周期，并说明该周期。若需要更长的周期， 应通过 
ask_revnu
向 Revnu 请求报告，不要把一个月当作一个季度来呈现。
每个渠道均为 
{available: true, data}
或 
{available: false, reason}
：
  • email
    ：发送量（以及上一周期的数据）、回复情况（包括回复者）和退信情况；开启跟踪后还包括打开和点击。
  • outbound
    ：按序列列出的送达量、回复数、退信数和等待中的潜在客户。
  • linkedin
    ：邀请、私信、InMails、回复和账户健康状况。
  • ads
    ：正在运行的广告活动、包含展示和点击数据的支出、过去 14 天各广告活动的转化，以及任何正在运行的测试。
  • seo
    ：已发布的帖子、博客浏览量、Search Console 点击和展示次数。
  • aeo
    ：AI 回答提及该业务的频率、Share of Voice（声量份额）和引用份额，以及最近 7 天与此前 7 天的对比。
  • harness
    ：Revnu 的定时工作是否已运行，以及队列中有什么在等待。

Reading it honestly

如实解读

  • Unavailable is unknown; a measured zero is zero. Say which.
  • Keep activity, replies, meetings, conversions and revenue apart. A reply is not a meeting; a click is not a customer.
  • Divide replies by sends only when both counts cover the same people.
  • Opens are a weak signal; mail apps open messages on their own.
  • Cross-check channel scoreboard numbers from 
    ask_revnu
    against 
    results_get
    for the same window. For CRM figures, use the returned CRM records and sources.
  • 不可用意味着未知；实际测得为零才是零。请明确是哪一种。
  • 将活动、回复、会议、转化和收入区分开来。回复不等于会议；点击不等于客户。
  • 仅当回复数和发送数覆盖相同的一批人时，才用回复数除以发送数。
  • 打开是弱信号；邮件应用本身可能会自动打开邮件。
  • 对同一时间窗口，将 
    ask_revnu
    返回的渠道指标面板数字与 
    results_get
    进行交叉核对。对于 CRM 数字，使用返回的 CRM 记录和来源。

What's waiting and what's running

等待和运行中的事项

  • review_list
    : drafts, questions and budgets waiting for the founder, up to 50 cards. 
    review_get
    opens one. An empty queue means nothing is waiting, not that Revnu stopped.
  • agent_status
    : whether Revnu is busy, its last activity and next scheduled check-in.
  • workflows_list
    and 
    workflow_runs
    : recurring jobs, their schedule and each run's outcome. 
    leads_list
    with a 
    workflowRunId
    shows what a run found.
  • agent_thread
    : this connection's conversation with Revnu. The founder's dashboard and Slack threads are not in it.
A quiet agent is not proof the work is finished.
  • review_list
    ：等待创始人的草稿、问题和预算，最多 50 张卡片。
    review_get
    打开其中一项。空队列表示没有待处理事项，并不表示 Revnu 已停止。
  • agent_status
    ：Revnu 是否忙碌、最后活动以及下一次计划检查。
  • workflows_list
    和 
    workflow_runs
    ：定期任务、其调度计划以及每次运行的结果。带有 
    workflowRunId
    的 
    leads_list
    会显示某次运行发现了什么。
  • agent_thread
    ：此连接与 Revnu 的对话。创始人仪表盘和 Slack 线程不包含在其中。
Agent 没有动静并不能证明工作已经完成。

The report

报告

Lead with what changed and the numbers that matter for the founder's goal, then what shipped, what is waiting for them, and what Revnu is trying next. Name the window. Don't round up, project or promise.
先说明发生了哪些变化，以及与创始人目标相关的关键数字；然后说明 已经发布了什么、正在等待他们处理的事项，以及 Revnu 下一步准备做什么。 注明时间窗口。不要向上取整、进行外推或作出承诺。