> For the complete documentation index, see [llms.txt](https://flapjax.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flapjax.gitbook.io/docs/reporting/communications.md). # Communications The **Communications** page is a live log of the individual messages your workspace has sent. Every row is one **sendout**: one message, one recipient, one channel. Rows are not templates or campaign definitions. An automation that emails 500 people produces 500 rows, each with its own delivery status and engagement history. Use this page to answer questions such as "did this person receive our email?", "how many SMS messages bounced last week?" and "what did that Slack alert actually say?" ### Who can see it The Communications page belongs to reporting and uses the **same permission as your reports and dashboards**. Any team member who can view reports can view communications. Anyone without that permission never sees the page. *** ### KPI Cards A row of summary cards at the top gives you the headline numbers for the messages matching your current filters: * **Sent**, how many messages went out * **Delivered**, how many reached the recipient * **Opened** and **Clicked**, unique engagement counts, on channels that report them such as email * **Bounced**, **Unsubscribed**, **Spam** and **Failed**, the outcomes worth watching Each card carries a **change indicator** against the immediately preceding period of the same length, so a trend shows at a glance. The cards refresh every 30 seconds on their own. The totals stay current as you work, with no reload. *** ### Filters The filter controls at the top narrow the log. Active filters appear as chips you can dismiss one at a time. * **Channel** picks which channel you look at. The selectable ones are **Email**, the default, plus **SMS**, **Slack**, **Telegram** and **Teams**. Switching channels resets the status filter and reloads the log, since a message selected on one channel means nothing on another. * **Date range** sets the time window. It defaults to the last month. * **Application** filters by the integration connection that sent the messages, say one particular email or SMS provider. Leave it on "All applications" for everything. * **Campaign** filters to messages tagged with a specific [campaign](/docs/settings/workspace/campaigns.md), and a campaign group if you want. It appears once you have campaigns set up. * **Consent** filters to messages sent under a specific [consent](/docs/settings/workspace/consents.md), which lets you compare delivery and engagement per purpose. It appears once you have consents set up. A **status filter** above the table drills into a delivery state for the channel you are viewing. Email and SMS carry their own status sets. Slack, Telegram and Teams share a simpler message set, since those channels either deliver or fail at send time. > **Note:** WhatsApp and push notifications count as message channels internally, and neither appears as a selectable filter here. The channel picker offers Email, SMS, Slack, Telegram and Teams. *** ### The message log The main table lists each sendout as its own row, newest first, loading more as you scroll. Every message shows: * **Recipient**, the person the message went to, with their avatar and a link to their profile * **Status**, the current delivery state, colour-tagged * **Campaign**, the campaign tag where the message carries one * **Engagement**, a compact set of funnel icons for how far the message got: sent, delivered, opened, clicked * **Sent time**, a relative timestamp such as "3 hours ago" New messages arriving as you read raise a **"N new messages"** pill. Click it to pull the latest sendouts in. The list never reshuffles under you until you ask. *** ### Message detail Click any row to open the **message detail** panel on the right. It is read-only and covers that single sendout: * **Details**, the message ID you can copy, its channel, the provider that delivered it and its current status * **Lifecycle**, a timeline chart of the message's journey through its stages: sent, delivered, opened, clicked, plus any bounce, unsubscribe or failure * **Content**, the message as sent. The rendered email with subject and body, the push title and body, or the text of an SMS, Slack, Telegram or Teams message This is the fastest way to confirm what a recipient received, and when. *** ### Exporting **CSV Export** downloads the messages currently loaded in the table. The export reflects what sits on screen, so scroll to load more rows first if you want them in the file. *** ### Acting on recipients Select rows, or "select all matching", to run bulk actions against the **people** behind those messages. Add a label, send a follow-up, update an attribute. The action targets the recipients of the selected messages, under whatever channel, status, date, application and campaign filters you have applied. The count shows distinct people, since one person can appear several times in the log. *** ### Understanding the delivery rate The **delivery rate on the KPI card** sometimes differs from the canonical delivery rate reported elsewhere. That is intentional, and it comes down to what each number measures. * The **KPI card** divides **delivered by sent**, so "758 of 850 sent" reads as roughly 89%. It is built so the percentage matches the two totals beside it. * The **canonical delivery rate**, used in the underlying analytics, divides **delivered by the messages handed to the sending provider**. With nothing handed off, it shows no rate at all. That baseline includes messages accepted for dispatch that had yet to be marked "sent" at the time of measurement. Different denominators, so slightly different numbers. Neither is wrong. The card reads cleanly against its own figures. The canonical rate measures delivery against everything that entered the pipeline. Use the rate reported in the summary when you need the canonical figure. *** ### Related * [Reporting overview](/docs/reporting/reporting.md), covering reports, data sources and dashboards * [Report Types & Chart Options](/docs/reporting/report-types-and-chart-options.md) · [Building Reports](/docs/reporting/building-reports.md) · [Data Sources & Metrics](/docs/reporting/data-sources-and-metrics.md) · [Managing Dashboards](/docs/reporting/managing-dashboards.md) * [Campaigns](/docs/settings/workspace/campaigns.md), the campaign tags behind the campaign filter