Broadcasts

The Broadcasts plugin sends a one-off announcement — by email or text message — to your whole team, your facilitators, or every customer with a booking in a date range.

It's built for the weather day: a storm rolls in, you have to cancel or reschedule a full slate of bookings, and every affected customer needs to hear from you at once. It works just as well for staff announcements — a schedule change, a closure, an all-hands note.

This is a feature plugin — email broadcasts work the moment you enable it, with nothing to configure. Text broadcasts additionally use the Twilio connection from Company settings (the same one as the SMS Inbox).

Setup

1. Open Plugins → Browse Plugins and click Install on Broadcasts.
2. Click Enable on the setup page. A Broadcasts page appears in your Plugins menu.
3. Grant the Broadcasts (send) permission to the roles allowed to send — see Permissions below.

Sending a broadcast

Open Plugins → Broadcasts and compose:

1. Channel — email, or text message (if Twilio is connected).
2. Audience — one of three:
   • Team — every staff member with access to the current location.
   • Facilitators — the facilitators at the current location.
   • Customers with bookings — pick a date range (defaults to today), and optionally narrow by activity or booking status. Cancelled bookings are included by default, since you'll often notify customers right after bulk-cancelling their day.
3. Review the recipients — the list updates live as you adjust the audience. Every recipient is checked by default; untick anyone who shouldn't get the message. A skipped panel shows who can't be reached and why (no email on file, invalid phone number, and so on) — nobody is silently dropped.
4. Write the message — subject and body for email, just a body for texts. Email goes out as a clean, plain announcement under your location's name — no buttons or marketing framing.
5. Send. You'll get a confirmation with the recipient count before anything goes out.

History

The History tab lists every broadcast with its outcome counts. Open one to see the full message and a per-recipient breakdown — sent, failed (with the reason), pending (still being delivered), or skipped (never attempted, with the reason). While a broadcast is still delivering, the detail view updates automatically.

Deduplication and hygiene

• A customer with several bookings in the range gets one message, not one per booking.
• A facilitator who is also a staff member gets one message.
• Rows with a missing or invalid email/phone are skipped with a reason instead of failing the send.
• Each message is sent individually — recipients never see each other's addresses.

Limits

• 500 recipients per broadcast. For a bigger audience, narrow the date range or filter by activity and send in batches.
• The customer audience is capped at 2,000 matching bookings per query — a very wide date range will ask you to narrow it.

Permissions

• Composing, sending, and viewing recipient details require the Broadcasts (send) permission (administrators have it automatically). Recipient lists include customer contact details, which is why viewing them is gated too.
• Staff without the permission can still see the history list — subjects and counts, but no recipient details.

Good to know

• Announcements, not campaigns: there's no scheduling, no templates, and no marketing automation — for automated, event-driven messages use Workflows.
• Text broadcasts are delivered through your Twilio connection and count toward your Twilio usage and billing.
• Broadcasts are per-location: the audience is always resolved at the location you're working in.