Reports aggregates activity over a date range. Where the Dashboard shows recent activity, Reports answers questions about a period you specify.

​
Run a report

1

Set the date range

Use the From and To pickers. The range defaults to the last 30 days.
2

Choose the grouping

Group by determines the granularity of the breakdown: hourly, daily or monthly.Match the grouping to the range. Hourly over three months produces more rows than is useful; monthly over a single week produces one.
3

Select the tab you need

The filters apply across all five tabs, so you can compare outbound and billing figures for the same period without re-entering the range.
4

Export if you need the underlying data

Each report has a matching export that returns the same figures as a file, using the same filters.

​
Which tab answers which question

​
Separating automated traffic from your own

The Outbound report can be filtered by channel, which is the practical way to separate what your team sent from what the platform sent on your behalf.
If your volume is higher than your team expected, filter by channel first. Calendar reminders and keyword auto-replies both generate messages without anyone pressing send, and both are charged.

​
Choosing the right source

Reports aggregate across a period, which makes them the right tool for trends, volumes and billing totals. For the outcome of one message or one campaign’s recipients, use SMS Management, which holds per-message and per-recipient status. To reconcile a specific charge, use the transaction history on Billing and usage, which records the part count applied to each message.

​
Troubleshooting

Confirm the date range covers the activity you expect. The range defaults to the last 30 days, so activity older than that needs the From date moving.
Filter by channel. Automated sources — calendar reminders, keyword auto-replies and API integrations — contribute to the total alongside messages your team sent.
Messages are charged per part, not per message, so longer messages and non-Latin alphabets consume more credits for the same message count. See Message encoding.