Community Push Notifications: What to Send and What to Skip
How community push notifications work, which ones members welcome, how to avoid overload, and why a native app gives coaches a direct line to members.
By the Hopper team

A community push notification is a short message that lands on a member's phone, even when they are not in your app. Done well, it is the nudge that brings someone back to a reply, a live session or a lesson. Done badly, it is the reason they mute you or delete the app. For a coach, the best setup is one where the community, the courses and the checkout live in one branded app, so the nudge always leads somewhere that makes sense. That is what we built Hopper to be, with a native iOS and Android app on both plans.
This guide covers how push works, what to send, how often, and how to ask for permission without losing members before you have even started.
TL;DR
- Push notifications reach a member's phone through Apple's or Google's delivery service, and only after the member says yes.
- Messages tied to a person's own activity (a reply, a mention, a session time change) work best. Broadcast promotions work worst.
- Research on learning apps shows notifications can lift engagement, and also that too many push uninstalls up.
- Sort every possible alert into must-send, should-send, digest and never-send before you switch anything on.
- A native app on both iOS and Android gives you a home-screen presence that a link in an email never will.
Table of Contents
- How push notifications actually reach your members
- Why a native app changes the equation
- What is worth a push: examples that earn their place
- What the research says about helping versus annoying
- A simple four-tier system for deciding what to send
- Frequency, timing and quiet hours
- Asking for permission without losing the member
- Using notifications to support habits, not pressure
- What this means if you are moving off Kajabi, Circle or a tool stack
- Ready to give members one app that feels like home
- Our view: a notification should feel like a friend tapping your shoulder
- FAQ
- Sources
How push notifications actually reach your members
It helps to know the plumbing, because it explains why permission matters so much.
When a member installs an app and agrees to notifications, the app registers the device with Apple's push service on iPhone or Google's Firebase Cloud Messaging on Android. Each install gets its own unique token, and your platform sends messages to that token, which Apple or Google then deliver to the phone. Knock's technical explainer walks through this in detail.
Two things follow for you:
- No consent, no push. iOS has always required an explicit permission prompt. Android only required explicit opt-in from Android 13 onwards, per the same explainer. If a member taps "don't allow," you cannot override it.
- Push is separate from email and the in-app bell. It is the one channel that reaches a member who is not looking at your community at all. That is its power, and the reason it needs a higher bar than email.
The other piece is where the push comes from. A message from your own branded app, sitting on a member's home screen next to their other apps, feels like part of their day. A browser alert from a tool they barely remember signing up for does not.
Why a native app changes the equation
Most coaches we talk to arrive with a stack: a course platform here, a community there, a storefront, a link page. Each tool has its own notification settings, its own email footer, its own login. A member who joined your cohort in one place and buys a workshop in another gets messages from three directions, or from none at all.
When the community, the library and the checkout sit in one hub, one app, one set of notification preferences, the member gets a single, coherent relationship with you. Hopper includes a native iOS and Android app for members on both the Base and Pro plans, so that home-screen presence is not an upgrade you pay extra for.
This matters most for three kinds of coach:
- Cohort and 1:1 coaches, where timing is everything: a session moved, a reply waiting, a deadline tomorrow.
- Membership owners (meditation and yoga teachers, for instance), where the habit of opening the app daily is the product.
- Coaches who outgrew a one-community limit and now run several programmes. One account on Hopper runs unlimited hubs, so each programme can have its own space without a second subscription.
If you want more on keeping people coming back beyond notifications, our guide on community engagement ideas that retain paying members goes deeper.
What is worth a push: examples that earn their place
The clearest pattern across well-run communities is that the best pushes are about something the member cares about right now, not something you want to announce.
Meetup's help documentation is a useful real-world model. According to Meetup's notification guide, changes to an event's time or location go out by push immediately, while email and inbox versions can take up to 15 minutes. Replies to someone's comment also push immediately to that person. New group discussions, on the other hand, notify only group leaders right away. Everything else rolls up later.
Translate that to a coaching community and you get a natural list:
- A reply to a member's post or a mention of their name. Personal, relevant, and it invites a response.
- A live call time change or a replay going up. Time-sensitive and something the member signed up for.
- A direct message from you or a teammate. A 1:1 relationship signal.
- A drip lesson unlocking when the member has opted into progress reminders.
- A payment or membership issue. Rare, but important enough to interrupt.
What does not belong here: general promotions, "we miss you" nudges and a daily blast about everything that happened in the feed. Those are better as email or a weekly digest, where a member can read them on their own time.
What the research says about helping versus annoying
The evidence is encouraging, with a clear warning attached.
A 2025 study of 53 university students, published in Springer's International Journal of Educational Technology in Higher Education, found that regular push notifications from Moodle enhanced engagement and self-regulation and reduced procrastination. The authors also noted that some students found them distracting, and that volume can desensitize people. Some participants asked for more personalization.
A larger earlier study tracked 12,071 users of a mobile English-learning app. Pham, Nguyen, Hwang and Chen (2016) found that message and comment notifications had the highest click rates, and that notifications in general increased sessions, time spent and retention. Test reminders were clicked 17.1% of the time against 9.7% for content-update notices. But over-frequent notifications did the opposite and could raise uninstall rates. Their suggestion for educators was to build social communication inside the learning app, since people responded most to messages and comments.
Those two findings point the same way. People respond to notifications that come from other people and relate to their own activity. They tune out notifications that feel like a campaign calendar. A community, where replies and conversations are the product, is a natural fit for the first kind.
These are studies of students and a learning app, not of coaching businesses, so treat them as a guide to member behavior rather than a promise of a particular result.

A simple four-tier system for deciding what to send
Before you switch on any alert, sort every possible trigger into one of four buckets. This is the same logic a good editor uses on a newsroom's breaking-news alerts: the more a channel interrupts, the higher the bar.
Tier 1, must-send (push immediately). Anything affecting access or money: a failed payment, a changed login, a membership ending. Also a live session starting or moving.
Tier 2, should-send (push, because the member asked). Replies to their posts, mentions, direct messages, reminders for events they signed up for.
Tier 3, digest. New posts in spaces they follow, new lessons in the library, general community activity. Bundle these into one daily or weekly summary.
Tier 4, never-send by push. Sales promotions, generic re-engagement nudges and anything you would be embarrassed to send at 11 p.m.

Worked example: a 40-person cohort
Say you run a 12-week career coaching cohort with 40 members, a weekly live call and a discussion space.
- Tier 1: "Tonight's call moved to 7 p.m." goes out as a push the moment you change it.
- Tier 2: "Maya replied to your post" goes out as a push, because Maya's reply is personal.
- Tier 3: Week 4's worksheets, three new posts and two new replies in the general space become one Sunday summary.
- Tier 4: Your upcoming alumni workshop goes by email, with one mention in the community feed.
The result is that a member's phone buzzes only when something has happened to them or to something they signed up for. That is the whole discipline.
Frequency, timing and quiet hours
No universal number is right, but a few habits keep you on the right side of the line.
- Respect the member's clock. The open-source community platform Komunitin documents sending most pushes only between 8 a.m. and 10 p.m. in the member's local time zone, while urgent items still go immediately. Its notification documentation is a good template if you coach across time zones.
- Batch the non-urgent. The same documentation groups non-urgent items like new members into digests instead of sending one push each.
- Let members choose. The same documentation splits notifications into categories, such as account activity and community news, that members toggle independently. Aim for the same idea: a member who wants replies but not news should be able to say so.
- Start conservative. It is far easier to let members opt into more than to win back someone who muted you.
If you coach internationally, time zones are the quiet killer. A 3 p.m. push for you is 3 a.m. for a member in Sydney. When in doubt, send nothing at night unless it is Tier 1.
Asking for permission without losing the member
Because you cannot override a "no," the moment you ask matters more than the wording.
The Knock explainer notes that iOS has always required an explicit prompt, and Android only from version 13. In practice, a member who declines on first launch, before they have seen anything of value, is hard to win back.
A better flow for a coaching community:
- Let the member in first. Let them see the community, meet the group and read a welcome post.
- Ask after a moment of value. Right after they post their first introduction or reply to someone is natural.
- Say what they will get, in one line. "We'll ping you when someone replies to you or when a live call changes." Specific beats vague.
- Do not nag. If they say no, point them to their notification settings later and rely on email for the essentials.
The welcome stage deserves its own plan. Our student onboarding template lays out a five-phase approach, and the permission ask fits neatly into the early steps.
Using notifications to support habits, not pressure
Push works best when it reinforces something members already want to do. If you use points, streaks or badges, a notification that celebrates a milestone feels like recognition rather than a nudge. Our guide to research-backed gamification ideas for course creators shows which mechanics hold up.
Two practical rules:
- Tie every push to a deep link so a tap lands on the exact reply, lesson or session. A push that opens a home screen wastes the member's attention.
- Review your pushes monthly. If a type gets ignored, move it down a tier.
What this means if you are moving off Kajabi, Circle or a tool stack
Migrating is the moment when notifications are most fragile. Members who were used to emails from one tool and a community on another now have to install an app and say yes to alerts. A few things make it smoother:
- Tell members what is changing and why, in your own voice, before the move.
- Send one clear invitation to the new app rather than several.
- Keep email as the safety net for anyone who declines push.
- Move your members and payments together. Hopper offers free migration and onboarding, a done-with-you process that includes client and payment transfer, so you are not rebuilding your member list by hand.
If you have felt the pain of paying more as your member count grows, the pricing structure matters too. Hopper's Base plan is $58 per month, or $580 per year, and Pro is $108 per month, or $1,080 per year. Members, hubs, team and products are unlimited on one plan, and Pro carries 0% fees.
Ready to give members one app that feels like home
If your community, courses and checkout are scattered across tools, your notifications are scattered too. Hopper brings the discussion feed, the library, async coaching (on Pro), a storefront and landing pages into one hub, with a native app for your members on iOS and Android. Our free migration and onboarding is built for coaches who already have paying clients and want to move without starting over.
See the plans on the Hopper pricing section, or join the waitlist to talk through your move.
Our view: a notification should feel like a friend tapping your shoulder
I started building Hopper after watching coaches duct tape together five tools and then wonder why their members drifted away. Every tool had its own notifications, its own emails and its own idea of what mattered.
We think the answer is not more alerts. It is one place where the conversation, the learning and the buying all live, so that when your phone lights up, it is because someone you care about said something to you.
That is why we built the native iOS and Android app into both plans and gave every account unlimited hubs, members and products. Coaches should not be charged more for growing, or penalized for running more than one programme.
The lecture hall is closed. The playground is open. A good notification is simply an invitation to come play.
Cedrik, Founder at Hopper.so
FAQ
Should members allow push notifications from a community?
Yes, if they want to hear about replies, mentions and live session changes quickly. Push is the only channel that reaches them when they are not in the app. They can change their choice later in their phone's notification settings or the app's own preferences, so saying yes is not a permanent commitment.
How often should a coach send push notifications?
There is no fixed number, but research on a learning app of more than 12,000 users found that over-frequent notifications raised uninstall rates. Keep push for things tied to the member's own activity or a time-sensitive event, and move everything else into a daily or weekly digest or an email.
What is the difference between push, email and in-app notifications?
In-app notifications appear inside the community, usually as a bell icon, and only help when the member is already there. Email arrives in the inbox and can be read later. Push appears on the phone's lock screen or banner, even when the app is closed, which is why it should be reserved for what is timely.
Do push notifications work on both iPhone and Android?
Yes. Apple delivers them through its Apple Push Notification Service and Google through Firebase Cloud Messaging, and a native app is registered with whichever matches the member's device. Each device gets its own token, and both systems need the member's permission, Android since version 13.
Sources
- How push notifications work on Apple and Android (Knock)
- What notifications Meetup can send (Meetup Help)
- You have a notification: the role of push notifications in learning (Springer, 2025)
- Effects of Push Notifications on Learner Engagement in a Mobile Learning App (2016)
- Komunitin notification documentation
Recommended
On our list and want off? .
