> ## Documentation Index
> Fetch the complete documentation index at: https://help.kampp.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Send an announcement to many athletes

> One message, sent to everyone, to a team or to a tag — and you follow the send as it goes out.

Need to tell everyone the gym is closed on the holiday, open a new group, or remind
everybody to send this month's photos? Instead of copying and pasting into every
conversation, use a **broadcast**.

## How to send one

<Steps>
  <Step title="Open the broadcast">
    In **Chat**, click the **megaphone** icon at the top of the conversation list (**Send
    an announcement to athletes**).
  </Step>

  <Step title="Write the message">
    Type the announcement into the **Message** field.
  </Step>

  <Step title="Break it into parts, if you want">
    Click **Add another message** to send the announcement in blocks (up to 10). They
    arrive in sequence, one after another — just like when you send several messages in a
    row day to day.
  </Step>

  <Step title="Attach a file (optional)">
    Each block takes one attachment — image, video or document, with the same limits as
    regular chat. Use **Attach file**.
  </Step>

  <Step title="Choose who gets it">
    In the **Send to** field, pick:

    * **All active athletes** — your entire roster.
    * **A team** — only the people on that team.
    * **A tag** — only the people with that tag.
  </Step>

  <Step title="Check the total and send">
    At the bottom, Kampp shows how many people will receive it. Check it and click **Send
    announcement**.
  </Step>
</Steps>

<Note>
  The audience is always **everyone**, a **team** or a **tag** — you can't tick athletes
  one by one. If you keep sending to the same specific group, create a team for it.
</Note>

<Warning>
  The **Tag** selector may come up empty, and there's a reason for it: athlete tags are
  **not applied by hand** — tagging is done by a [Kampp Flow](/en/flow-what-is) automation.
  Without a flow that tags someone, there's no tag to pick. See [Tags](/en/tags).
</Warning>

## Two switches worth understanding

* **Only people who opened the app recently** — sends only to those who showed up in the
  last 30 days. It keeps you from spending an announcement on a dormant account.
* **Notify on the phone** — on by default. With it, the athlete's phone pings right away.
  Without it, the message waits until they open the app.

## Follow the send

The broadcast doesn't all go out at once: it goes into a queue and is sent in batches. At
the top of the conversation list you get a tracking card with:

* the **progress bar** and the text *X of Y sent*;
* the **status**: Queued, Sending, Paused, Completed, Cancelled or Failed;
* how many **failed**, if any did.

On that card you can **Pause**, **Resume**, **Cancel** or **Dismiss** the tracking.
Completed cards disappear on their own after a few minutes.

## Broadcast or Kampp Flow?

Both send messages, but they solve different problems:

| Use a **broadcast** when… | Use **Kampp Flow** when… |
| - | - |
| It's a one-off announcement, right now | It's a message that should repeat on its own |
| You decide on the spot who gets it | The trigger is an event (joined a team, went quiet, has a birthday) |
| It goes through the app's chat | It goes through WhatsApp |

<Tip>
  One-off announcements through chat; routine in [Kampp Flow](/en/flow-what-is). Trying to
  automate by hand ends in forgetting — and sending manually what's already routine wastes
  your time every single month.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.