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

# Metrics glossary

> What Accepted, Delivered, Failed, Blocked, Spend, and Handset rate mean — and where to find them.

# Metrics glossary

Who this is for: operators and agents who need the same definitions the product uses in **Insights**, **Live / Flight Deck**, and **Billing**.

BizBionic uses **attempt-based** messaging billing: you pay when the **messaging network accepts** a send, not only when the handset shows delivered. Details: [Usage, wallet, and invoices](/billing/usage-and-wallet).

## Core delivery terms

| Term          | Meaning                                                                                                                                                   |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Accepted**  | The messaging network accepted the send (submit succeeded). Counts toward usage **Spend**. Includes messages later marked delivered.                      |
| **Delivered** | Handset-confirmed delivery (delivery receipt). Already counted under Accepted when status moved from accepted/sent.                                       |
| **Failed**    | Terminal failure — network rejected the submit, or delivery later failed / unreachable. **Unreachable after accept is still billed** (not auto-refunded). |
| **Blocked**   | Stopped by consent, compliance, quiet hours, cancel, or preflight **before** send. **Not billed.**                                                        |
| **In-flight** | Queued, leased, or still dispatching — not yet a final outcome.                                                                                           |

## Rates and money

| Term             | Meaning                                                                                                                                            |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Handset rate** | Delivered / (delivered + failed) when both sides are known. **Not** the same as “accepted rate.” Use it for delivery quality, not for “did I pay?” |
| **Spend**        | Retail wallet debits for **network-accepted** attempts. Not Stripe top-ups. Not refunded when a handset is later unreachable.                      |

**Simple reconstruction:**

```text theme={null}
wallet balance ≈ money you added − SMS usage (accepted attempts)
campaign spend  = sum of charges for accepted messages on that mission
```

## Time windows

Every KPI should carry a window label. Common windows:

| Window             | Meaning                                            |
| ------------------ | -------------------------------------------------- |
| **24h**            | Last 24 hours                                      |
| **7d / 30d / 90d** | Rolling days                                       |
| **Mission**        | Scoped to one campaign / mission                   |
| **Custom**         | Explicit `from` / `to` (or range pair for compare) |
| **All time**       | No range filter (where the skill allows)           |

Insights **Compare** uses two ranges (A vs B). Live / Flight Deck is usually short-window ops; Insights is for deeper ranges and trends.

## Where to find these numbers

| Place                  | What you see                                                                                   |
| ---------------------- | ---------------------------------------------------------------------------------------------- |
| **Insights**           | Overview, deliverability, failures, engagement, destinations, compare, export — deep analytics |
| **Live / Flight Deck** | In-flight mission detail: accepted / delivered / failed and usage cost for that send           |
| **Account → Billing**  | Wallet balance, history, top-ups; usage trail for reconstruction                               |
| **Compose preflight**  | Estimated cost and balance check **before** launch                                             |

Agents call the same numbers via A2A (`analytics.*`, `billing.*`) — [API Reference](/api-reference) and [A2A RPC](/connect/a2a-rpc).

## Common questions

**Why is Spend higher than “Delivered × rate”?**\
You pay on **Accepted**. Some accepted messages never get a handset confirmation (or fail later) and still count as usage.

**Why is Handset rate not 100% when everything looks fine?**\
Handset rate only uses delivered vs failed when both are known. In-flight and pure “accepted, waiting for receipt” volume are not the same metric.

**Did a Blocked row cost me money?**\
No. Blocked never left the gate.

**Where is line-by-line SMS on my Stripe invoice?**\
It is not. Stripe funds the wallet; SMS usage debits the wallet. See [Usage, wallet, and invoices](/billing/usage-and-wallet).

## Related

* [Usage, wallet, and invoices](/billing/usage-and-wallet) — when SMS is charged
* [Operator Studio](/connect/operator-studio) — faces and modes (Insights, Live, Account)
* [Trust Setup](/compliance/trust-setup) — first-send readiness including credits
* [API Reference](/api-reference) — `analytics.*` and `billing.*` skills