GoalDNA
home
AvailableLast updated May 13, 2026

Communication & announcements

Keep team updates connected to the workspace.

Quick answer

GoalDNA includes in-app conversations, messages, announcements, notifications, posts, and polls with scoped access.

GoalDNA product preview showing inbox context and linked-player guardian update boundaries.
Inbox and guardian updateAvailable

Public-safe product preview based on current GoalDNA workflows.

Product preview context

This public-safe product preview is based on current GoalDNA workflows and uses no private customer, player, guardian, inbox, injury, or member data.

Status
Available
Product areas
InboxAnnouncementsGuardian accessNotifications

Before you start

Name the real owner, the first team, and the role boundaries before inviting more people.

  • Admins
  • Coaches
  • Staff
  • Players
  • Guardians

Step-by-step workflow

Work through the setup in the order a club would actually run it during the week.

  • Choose the right audience
  • Send the update in context
  • Use posts or polls when useful
  • Check notifications
  • Avoid duplicating the same message across tools

What good looks like

These are the available or practical outcomes to verify before moving on.

  • Inbox conversations
  • Send/read messages
  • Notifications
  • News and posts
  • Poll creation and voting

Role visibility checks

Check access boundaries before inviting more staff, players, or guardians.

  • Admins and coaches coordinate updates.
  • Players and guardians see relevant scoped messages.

Common mistakes

Avoid these rollout errors; they create confusion faster than the product can clean it up.

  • Posting every operational detail to every role.
  • Using in-app messages to send private account credentials.
  • Promising SMS or push reminder automation before status changes.

Troubleshooting

Check the concrete schedule, team, roster, and role context before changing permissions.

  • If someone misses a message, check their workspace membership, team assignment, and role scope.
  • If a poll needs analytics beyond basic voting, mark that need as pending rather than promising rich reports.
  • If families ask repeated questions, move kickoff, field, and arrival context into the schedule update.

What not to rely on yet

These limits should stay out of club-critical plans unless feature status changes.

  • SMS/email/push automation is gated.
  • Rich poll analytics are pending.

Beta / partial notes

Use these areas carefully with pilot expectations and transparent communication.

  • SMS, email, and push automation are gated.
  • Rich poll analytics are pending.
  • Advanced announcement automation should not be treated as live.

Example club scenario

A coach sends a match update to the team after lineup prep, while admins use posts or polls for club-level coordination where scoped visibility is appropriate.

FAQ

Does GoalDNA replace every chat app?

It reduces operational chaos around team updates and role-aware messages. Some clubs may still use external tools while automation matures.

Are SMS or push reminders live?

No. SMS, email, and push automation are gated unless feature status later changes.

Related workflows

  • Available

    Roles & permissions

    How GoalDNA separates visibility for different club responsibilities.

    Read Roles & permissions
  • Guide

    Support / contact

    How to request access, ask support questions, or discuss privacy and rollout needs.

    Read Support / contact