Combine real-time conversations, announcements, in-app notifications, native push, email, and SMS with personal preferences and role-aware audiences.
Every notification lands in one in-app feed, and can also arrive by native push, email, or SMS. Items that need a person stay pinned. Items that were only ever information age out on their own. Repeats collapse instead of stacking up.
Important notifications stay visible until the underlying issue is resolved.
A failed payment or an outstanding requirement stays pinned in the feed while it is still open. When the underlying issue is resolved, the item can be dismissed - it does not simply scroll away after a set number of days.
Illustration of the notification feed. Entries are examples, not customer results.
A question between two people, a notice for a group, and the running feed that keeps track of what still needs attention.
Real-time direct and group conversations, with participant management so the right people can be added or removed as a situation changes. Typing indicators and read receipts show whether a message has actually landed with someone.
Staff broadcast to selected groups and audiences, or to the whole organization, and set an expiry so a notice retires itself once it stops being true. Which audiences a sender can select depends on that sender’s permission.
In-app notifications plus native push, email, and SMS, following each person’s per-category preferences. Important items pin until resolved, routine items age out, duplicates collapse, and resolving the issue can dismiss the item.
Notifications can travel in-app, by native push, by email, and by SMS. Preferences are set per category, by each person, rather than as one switch for everything.
The same item can appear in the in-app feed, arrive as a native push notification, be sent as email, or be sent as SMS, according to the preferences that apply to it.
A guardian can keep billing notices on email and SMS while leaving routine class reminders in the app. A coach can do the opposite. The category, not the whole feed, is the unit of choice.
Push, email, and SMS delivery depends on external providers and on each person’s own device and notification settings. Reef controls what it sends and when - it cannot promise that a given message reaches a given device.
Organizations can connect and verify a sending domain they already own, using the SPF and DKIM records Reef supplies, and then send transactional mail from their own address - so an invoice or a form reminder looks like it came from you.
Verifying a domain changes the address families see. It does not decide where a mailbox provider files the message: that is the receiving provider’s decision, not Reef’s.
Browse every capability in the feature index
Duplicates collapse so a repeated notice reads as one entry rather than five. That is noise reduction in the feed, not a claim that every possible duplicate is eliminated everywhere.
Messages, announcements, and notifications come from the same records as the schedule and the ledger, not from a second product beside them.
Announcement audience depends on the sender’s permission.
A coach limited to assigned groups can reach the audiences tied to those groups. Broadcasting to the whole organization is a separate permission, held by the people you decide should hold it - and enforced in the interface and in the database rather than by a screen hiding a button.
Review the security and access approach
Communication also touches classes and scheduling, insights and AI, athlete progress, and documents, forms and safety.
See how Reef can fit your programs, locations, staff, and families.
