# Reports and analytics

> Interpret platform reports without confusing delivery, processing, and business outcomes.

Canonical: https://help.spacebrain.ai/platform/reports-and-analytics/

**Reports** is a platform-wide surface. Several modules also expose their own analytics, including CRM, workflows, voice, sites, webinars, social media, SEO, and reputation.

## Manage dashboards

Open **Reports** to search the dashboard collection. Dashboards are grouped by age, while favorites appear in their own section. Star frequently used dashboards so operators can reach the shared view quickly.

Create a blank dashboard when you have a defined reporting question or choose a template to start from an available set of cards. Give it a name that states audience and purpose, such as “Weekly pipeline health,” rather than “Sales dashboard 2.”

Before deleting a dashboard, confirm who uses its URL or exports. Deleting a dashboard removes its configured collection of reports; it does not delete the CRM records that contributed to those reports.

## Build a report card

Open a dashboard and add a report. The builder guides you through the dataset and the supported measures, grouping, filters, and display. Available choices depend on the selected report type and workspace data.

Use this design order:

1. Write the decision the card should support.
2. Choose the dataset that owns the underlying records.
3. Select a measure that represents the intended quantity.
4. Add grouping only when the categories can be interpreted.
5. Add explicit filters and verify the remaining scope.
6. Choose a display—number, line, bar, pie, or funnel—appropriate to the relationship.
7. Save, then compare the result with known records.

Use the card menu for supported edit, rename, duplicate, CSV export, or delete actions. Give duplicated cards a distinct name before changing their definition.

## Arrange the dashboard

Reports appear as cards on the dashboard canvas. Arrange them so context flows from headline measures to trends and diagnostic breakdowns. Do not place visually similar cards with different filters side by side without making that difference explicit.

## Dashboard time filter

The dashboard-level time filter is applied when report definitions run; it does not rewrite the saved report definition. Verify which date field a dataset uses. “Created during the period” and “closed during the period” answer different questions.

## Read a report correctly

1. Confirm the active workspace and module scope.
2. Check the date range, timezone, filters, and comparison period.
3. Determine whether the metric represents an attempted action, accepted action, provider delivery, customer interaction, or business outcome.
4. Open the underlying record or execution when a total looks unexpected.
5. Allow for processing delays before comparing a real-time provider view with an aggregated report.

Where a chart supports contributing records, open the drill-down drawer to inspect the rows behind a point, category, number, or funnel step. The drawer is the fastest way to catch an unexpected filter or record state. Export only when your access and data policy permit it.

## Common interpretation mistakes

* Treating “sent” as “delivered,” “delivered” as “read,” or a clicked review link as a completed review.
* Comparing reports with different timezones or date boundaries.
* Counting retries as new business outcomes.
* Assuming a provider’s total and Spacebrain’s recent synchronized window represent the same retention period.
* Ignoring filters for channel, owner, campaign, workflow, or workspace.

## Build an operating review

For each important workflow, choose a small set of measures:

* Volume entering the workflow.
* Completion or success rate.
* Failure and retry count.
* Time to response or completion.
* Human handoff or follow-up backlog.
* Cost or usage where relevant.
* A business outcome from the system of record.

Use module reports for diagnosis and a platform report for cross-module context. Export data only when your role and data-handling policy allow it.

## Refresh and troubleshoot

If a card is empty or fails:

1. Confirm workspace and dashboard URL.
2. Remove or widen one filter at a time.
3. Verify the dataset has records in the selected period.
4. Check whether required pipelines, stages, or fields still exist.
5. Refresh after the underlying data is available.
6. Open a contributing record from a working comparison card.

A dashboard refresh can update results but cannot repair missing source data. Correct the record or connection in its owning module, then rerun the view.