# Unified inbox and analytics

Handle supported conversations from one queue and report provider-supplied performance without inventing missing data.

[العربية](/inbox-analytics)

## [Unified inbox](#unified-inbox)

The unified inbox brings supported comments, mentions, replies, and direct messages into one workspace with the source-post context beside the conversation. It is a paid-plan feature.

**Current coverage:** the public product contract covers Facebook, Instagram, and Threads conversations delivered through provider webhooks. Other networks should appear as unavailable rather than as an empty queue that looks broken.

### [Team controls](#team-controls)

- **Assignment** gives one teammate responsibility for the conversation.
- **Resolve and reopen** distinguishes completed work from a conversation that needs another response.
- **SLA queues** surface overdue or soon-due items.
- **Internal notes** keep team discussion separate from customer-visible replies.
- **Search and filters** narrow by account, conversation type, status, or text.

Do not paste private messages into public incident tickets or AI prompts. Record opaque conversation identifiers and state transitions when operational evidence is enough.

## [Analytics](#analytics)

| Area       | What it can show                                                      |
| ---------- | --------------------------------------------------------------------- |
| Overview   | Provider-supplied reach, impressions, engagement, and follower change |
| By network | The metrics available for one provider and account                    |
| Top posts  | Comparable posts under the selected definition and window             |
| Hashtags   | Available hashtag-level performance                                   |
| Best times | Account-specific activity signals where the provider exposes them     |

Definitions, permissions, and reporting delay vary by network. A missing value is not zero. Keep **reported zero**, **unavailable**, **delayed**, and **unknown** as separate states. Edited, deleted, or moderated posts can change the eligible content set after the first collection.

## [Export and sharing](#export-and-sharing)

- Export available report rows as CSV for a defined period.
- Create a read-only report link for a client without granting workspace access.
- Deliver the weekly report to the team and receive the documented `report.weekly` webhook event.

An export is a snapshot, not necessarily a final ledger. Store the account identity, provider, metric definition, time zone, reporting window, collection time, and generation time beside it. Mark a report preliminary until the agreed provider-lag window has passed and a final refresh is complete.

Only provider-backed values

Naasher does not manufacture estimates for metrics the provider does not supply. When a network or granted scope does not expose a value, the report should preserve that absence instead of filling it with a synthetic number.

Use the [analytics definitions and lag guide](https://naasher.com/en/guides/analytics-metrics-lag) before combining networks, and [Webhooks](/en/webhooks) when a system needs signed state notifications.

[Compose and schedule postsHow the composer, calendar, publishing queue, per-target results, and approval flow work.](/en/publishing)[REST APIAPI keys, OAuth, least-privilege scopes, endpoints, errors, and lifecycle rules for Naasher API v1.](/en/api)

---

Canonical URL: https://docs.naasher.com/en/inbox-analytics