> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/communication/broadcast-message.md).

# Broadcast Message

## Purpose

Deliver a templated message to multiple recipients in one operation.

## Who this is for

Operators and supervisors running segmented or file-based campaigns.

## Prerequisites

* Approved template in [Template Gallery](/syntphony-messaging-portal/messaging-tools/construction/template-gallery.md).
* Configured sender number and source.
* Recipient data as **CSV file** or **existing group** from [Planning](/syntphony-messaging-portal/messaging-tools/planning.md).

## Audience sources

* **CSV upload:** Import recipients from a file prepared for the broadcast (include country code in phone columns).
* **Existing groups:** Reuse groups created in [Group Manager](/syntphony-messaging-portal/messaging-tools/planning/group-manager.md).

## Steps

1. Open **Communication** and go to **Broadcast Message**.
2. Select sender number and approved template.
3. Choose recipient source:
   * Upload CSV, or
   * Select an existing group.
4. Map or validate template variables for the audience.
5. Review recipient count and preview message content.
6. Confirm and dispatch the broadcast.
7. Monitor results in [Outbound History](/syntphony-messaging-portal/messaging-tools/analysis/outbound-history.md) and [Dashboard](/syntphony-messaging-portal/dashboard.md) **Message Stats**.

## Validation

* Recipient count matches file or group selection before confirm.
* Delivery states (delivered, read, pending) appear in Outbound History after dispatch.

## Troubleshooting

* **High failure rate:** Validate phone format in CSV and template variable completeness.
* **Group empty:** Refresh group in Group Manager or adjust Contact Manager filters.

## Expected outcome

A bulk delivery is created and can be monitored from Analysis pages and the dashboard.

## Related pages

* [Communication](/syntphony-messaging-portal/messaging-tools/communication.md)
* [Planning](/syntphony-messaging-portal/messaging-tools/planning.md)
* [Group Manager](/syntphony-messaging-portal/messaging-tools/planning/group-manager.md)
* [Outbound History](/syntphony-messaging-portal/messaging-tools/analysis/outbound-history.md)
* [Dashboard](/syntphony-messaging-portal/dashboard.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/communication/broadcast-message.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.