Notifications members do not hate

Every notification spends a little of a member's attention. Spend it on something they care about, such as a reply to their question or a reminder that the live session starts soon, and they are grateful. Spend it on something they do not care about, such as a new post in a forum category they have never visited, and they grow irritated. Do that often enough and they switch notifications off entirely, including the ones they would have wanted.

That is the real risk of over-notifying. It is not only annoying; it trains members to ignore you. A thoughtful approach to notifications keeps the channel valuable, so that when something important happens, members actually see it.

Decide what deserves a notification

Start by sorting every notification your site sends, or could send, into tiers:

1. Must send: account security, payment problems, receipts and changes to their membership. Members need these regardless of preferences.
2. Should send: things that involve the member directly, such as replies to their posts, mentions of their name, messages from other members and reminders for events they registered for.
3. Could send, usually in a digest: new content in topics they follow, activity in groups they belong to, upcoming events they might like.
4. Do not send as a notification: general promotions, “we miss you” nudges every few days, and activity in areas the member has never shown interest in.

The second tier is where notifications shine. The more personally relevant the trigger, the more welcome the alert.

Match the channel to the urgency

Membership sites can notify people in several ways, and each has a different cost to the member:

• On-site alerts, such as a bell icon with a count, are the gentlest. Members see them only when they visit.
• Email suits things that can wait a few hours and may need a record, such as replies or event details.
• Push notifications on a phone or browser interrupt immediately, so reserve them for time-sensitive things the member asked for.
• Text messages are the most intrusive and should be kept for urgent, expected messages such as a session starting shortly or a security code. Text messages alongside email covers consent and timing for these.

A useful rule: the more a channel interrupts, the higher the bar for using it.

Batch, delay and respect the clock

Ten separate emails about ten replies in the same thread is ten interruptions. Group related activity together:

• Combine several replies to one discussion into a single notification.
• Offer a daily or weekly digest for lower-priority activity, and make it the default for new members.
• Avoid sending non-urgent notifications at night in the member's own time zone.
• Time event reminders sensibly: one the day before and one shortly before the start is usually plenty.

Also make on-site counts meaningful. A red badge showing a large number that never goes down stops meaning anything. Clear the count once the member has seen the items, and do not count low-value activity.

Write notifications that stand on their own

A good notification tells members who did what, and where, without needing to click. Then the click takes them straight to it. Compare these examples from a hypothetical membership for amateur radio operators run by Winona:

Before: “You have a new notification.”

After: “Hamid replied to your question about antenna tuning in the Beginners forum: ‘Try shortening each side by about an inch and check again…’”

Before: “Reminder: event tomorrow.”

After: “Tomorrow at 7pm your time: Field Day planning session. Join link and agenda inside. Can't make it? The recording will be in the library within two days.”

The better versions name the person, the topic and the place, and include enough of the content that members can decide whether to act. Link directly to the reply or event, never to a general page where they have to search. The same care in wording discussed in microcopy: the small words that guide members applies to every notification you write.

Give members control, in context

Preferences pages matter, but members rarely visit them until they are already annoyed. Offer control where the annoyance happens:

• A “Mute this thread” option on busy discussions
• “Follow” and “Unfollow” on topics, groups and people
• A link in every notification email to change how often they receive that type
• A clear choice between instant, daily digest, weekly digest and off for each category

Set conservative defaults, and let members opt into more. A new member who finds the volume too high will switch everything off; one who finds it too low can easily turn more on. For email in particular, preference centers: let members choose what they get explains how to organize those choices.

A simple notification plan

Here is how Winona's club set its defaults:

• Replies to your posts and mentions: on-site and email, instant, grouped by thread
• Direct messages: on-site and email, instant
• Events you registered for: email the day before and a push reminder shortly before, if enabled
• New posts in followed topics: weekly digest
• Everything else: on-site only

Your first steps

1. List every notification your site sends, with its trigger and channel.
2. Sort them into must, should, could and do-not-send tiers.
3. Move could-send items into a digest and remove do-not-send items.
4. Rewrite vague notifications so they say who, what and where.
5. Add mute and follow options where activity happens.
6. Set conservative defaults for new members, and review opt-out rates each quarter.