Send announcements

There are three ways to reach players, and they serve different purposes.

1. Feed announcements

At Admin -> Announcements, create a feed post. These show on the public /announcements page of your event site. Use these for schedule changes, parking updates, and post-game recaps. Pin the most important one to the top.

2. Email broadcasts

At Admin -> Email, compose a broadcast. Pick an audience with the filter builder:

• All registrants for everything-everyone messages
• By sport for sport-specific updates
• Captains only for roster reminders
• Unpaid only to nudge abandoned carts
• By division for bracket-specific messages

The form shows a recipient count before you send. Subject and body only — no fancy templates, because a plain email always delivers.

3. SMS broadcasts

At Admin -> SMS, same filter builder, sent as text messages. Before it will send:

1. Turn on SMS Notifications under Feature Flags on the event's Overview page.
2. Texting must be set up for the platform. Texts go out through the platform's own Twilio account, which a platform admin sets up once on the platform Settings page; organizers have no credentials to add.

Players can opt out of SMS in their profile. The opt-out list is honored automatically.

Best practices

• One email per day max, unless it's a real emergency. Player inboxes fill fast.
• Big button at the top. A Good Times broadcast has a CTA, one sentence of context, and nothing else.
• Preview before sending. The "Send test to me" button fires a copy to your admin email.
• SMS for urgency only: lightning delay, field closed. Don't use SMS for marketing — you'll lose your opt-ins.

When to use the feed vs. email vs. SMS

• Feed: permanent record ("Finals are at 4:30 on Field 2")
• Email: important but not urgent ("Early bird ends Sunday")
• SMS: time-critical ("Lightning delay, hold in cars")