> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reply.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Decide what to scale or fix

> Turn raw reporting data into decisions — what to scale, pause, or rewrite.

**Outcome:** a performance readout (delivered, opens, replies, interested, meetings) with a
diagnosis and one or two recommended actions.

## Best interface

<Note>
  **CLI for reporting agents** — [`reply api`](/cli/overview#raw-api-access) with `--json` makes the
  reporting endpoints pipeable and cron-able. **MCP for Q\&A-style analysis** — "compare Q3 sequences"
  resolves to `reply_compare_sequence_performance` in one call.
</Note>

## Steps

<Steps>
  <Step title="Pull the account-level overview">
    Both endpoints take a `filters` object; `dateRangePreset` accepts `lastWeek`, `lastMonth`,
    `lastYear`, or `allTime`.

    ```bash theme={null}
    reply api /v3/reporting/emails/overview \
      --body '{"filters":{"dateRangePreset":"lastWeek"}}' --json
    reply api /v3/sequences/stats \
      --body '{"filters":{"dateRangePreset":"lastWeek"}}' --json
    ```
  </Step>

  <Step title="Drill into per-sequence stats">
    ```bash theme={null}
    reply api /v3/sequences/12345/stats \
      --body '{"filters":{"dateRangePreset":"lastMonth"}}' --json
    ```

    MCP: `reply_get_sequence_stats` (one sequence, custom date window) or
    `reply_compare_sequence_performance` (up to 25 side by side — align by SequenceId, treat
    missing rows as no data).
  </Step>

  <Step title="Diagnose">
    Benchmark deliverability (bounces), copy (opens vs replies), and targeting (replies vs
    interested). Flag stalled or degraded sequences. The
    [`performance-analysis` skill](/skills/catalog#performance-analysis) packages this diagnosis.
  </Step>

  <Step title="Act — with confirmation">
    Pausing sequences or editing copy are production changes: recommend, confirm, then execute
    ([Manage sequences](/guides/improve-sequences) has the loop).
  </Step>
</Steps>

## Availability notes

* Reports, per-sequence stats, and comparisons: **available today**.
* Stats endpoints can throttle earlier than CRUD endpoints — budget calls accordingly
  ([Rate limits](/api-reference/rate-limits)).
* Meetings are booked via Reply's in-app scheduler; the API **reports** them (meetings ledger) but
  can't book them.

## Related

* [Improve sequences every cycle](/guides/improve-sequences) — acting on the diagnosis
* [Skill: `performance-analysis`](/skills/catalog#performance-analysis)