> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/broadcast-list/get-started-with-broadcast-list/how-to-check-broadcast-summary.md).

# How to Check Broadcast Summary

Learn how to check the broadcast summary on DoubleTick. Get insights into delivery rates, engagement, button/link clicks, call analytics, and response metrics of your campaign.

The broadcast summary gives you a complete picture of how a campaign performed — delivery, engagement, button clicks, and call activity — all in one place.

#### What's covered

* [Delivery and response metrics](#delivery-and-response-metrics)
* [Button and link engagement](#button-and-link-engagement)
* [Call analytics for broadcasts using the Call on WhatsApp CTA button](#call-analytics-for-call-on-whatsapp-broadcasts)
* [Key takeaways](#key-takeaways)
* [Frequently asked questions](#frequently-asked-questions)

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FDuC6FvKNZfFxkhWGpPsO%2Fimage.png?alt=media&amp;token=385231c8-d48c-43db-9dca-530771db5bf1" alt=""><figcaption></figcaption></figure>

#### Delivery and response metrics

The broadcast summary provides a comprehensive overview of the broadcast, including counts and percentages of the following metrics:

* **Sent** — The total number of contacts the message was sent to.
* **Delivered** — The total number of contacts the message reached successfully.
* **Unread** — The total number of contacts who have yet to read the message.
* **Read** — The total number of contacts who have opened/read the message.
* **Replied** — The total number of contacts who have replied.
* **No Response** — The total number of contacts who did not respond to the message.
* **Failed** — The total count of contacts where the message failed to send.

<div align="center"><figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FQiQy5MDYLX9CBBlTOkll%2Fimage.png?alt=media&#x26;token=58df2731-cc4b-4401-9635-824d0241bcec" alt="" width="317"><figcaption></figcaption></figure></div>

In the broadcast list above, there are a total of 498 members. Out of these, the broadcast message was successfully delivered to 329 members, approximately 66.1%. However, the message failed for 158 members, which is approximately 31.7% of the total.

#### Button and link engagement

The broadcast summary also lets you track engagement with the specific elements inside your template — the buttons and links customers can tap. You can monitor how many customers clicked on each button or link embedded in the message, which helps you gauge the effectiveness of your call-to-action buttons or linked content and make informed decisions for future campaigns.

<div align="center"><figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FOZOlBo1CmgxH9hYJT3Je%2Fimage.png?alt=media&#x26;token=184e6ed1-f443-4995-9b7a-d2f92d8d98e5" alt="" width="307"><figcaption></figcaption></figure></div>

In this broadcast, there are three buttons included in the message — "Interested," "Not Interested," and "Stop" — along with one call-to-action button labeled "Visit website," which redirects to the website when clicked.

* In the broadcast summary, you can see how many members who read the message have responded by clicking on any specific button.
* You can view the total number of members who clicked on the "Interested," "Not Interested," or "Stop" button, as well as the number of members who clicked the "Visit website" button.

<div align="center"><figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2F5QJ2t7Ip3izJq3odOzA7%2Fimage.png?alt=media&#x26;token=9e0ac4ec-b6d8-4e53-8db2-0f0959c479f5" alt="" width="319"><figcaption></figcaption></figure></div>

#### Call analytics for broadcasts using the Call on WhatsApp CTA button

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FBycRG066WiSFzSQQ23bW%2FUntitled%20design%20-%202026-09-18T170023.417.gif?alt=media&amp;token=302528fd-c7fc-4813-b1e7-951ccd7e98a7" alt=""><figcaption></figcaption></figure>

If your broadcast template includes a **Call on WhatsApp** button, the broadcast summary also shows how those calls went:

To create one, see [How to Add a Call on WhatsApp Button to a Template](/whatsapp-calls/incoming-whatsapp-calling-api-your-complete-guide/how-to-add-a-call-on-whatsapp-button-to-a-template.md).

* **Calls answered:** Calls your team picked up.
* **Calls missed:** Calls nobody picked up.
* **Calls declined:** Calls your team declined.
* **Calls received**: All calls received from that broadcast template.

These numbers update live as customers call in. When you download the broadcast report, it now includes a separate list of every call — who called, their number, whether it was answered, missed, or declined, when they called, and how long the call lasted. This makes it easy to call back everyone you missed.

#### Key takeaways

* The broadcast summary covers Sent, Delivered, Unread, Read, Replied, No Response, and Failed counts.
* You can track how many customers clicked each button or link in your template.
* Templates with a Call on WhatsApp button also show Answered, Missed, Declined, and Total call counts, updating live.
* Downloaded broadcast reports include a full per-call breakdown for Call on WhatsApp templates.

#### Frequently asked questions

<details>

<summary>What metrics does the broadcast summary show?</summary>

Sent, Delivered, Unread, Read, Replied, No Response, and Failed counts and percentages for the broadcast.

</details>

<details>

<summary>Can I see how many people clicked a specific button?</summary>

Yes. The broadcast summary shows click counts for each button and link in your template.

</details>

<details>

<summary>Does the broadcast summary track calls?</summary>

Yes, if your template has a Call on WhatsApp button. It shows Answered, Missed, Declined, and Total calls, updating live.

</details>

<details>

<summary>Can I get details of individual calls?</summary>

Yes. Download the broadcast report to get a full list of every call, including the caller's number, outcome, time, and duration.

</details>

#### Related articles

* [How to Send and Schedule Broadcast Messages](/broadcast-list/send-and-schedule-broadcasts/how-to-send-and-schedule-broadcast-messages.md)
* [How to Re-Target Your Customers](/broadcast-list/send-and-schedule-broadcasts/how-to-re-target-your-customers.md)
* [How to Add a Call on WhatsApp Button to a Template](/whatsapp-calls/incoming-whatsapp-calling-api-your-complete-guide/how-to-add-a-call-on-whatsapp-button-to-a-template.md)
* [Get started with broadcast list](/broadcast-list/get-started-with-broadcast-list.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.doubletick.io/broadcast-list/get-started-with-broadcast-list/how-to-check-broadcast-summary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.