Notifications & Messaging Features

An inventory of every message, channel rules, sensible defaults and a preference centre, then the routines and builds that keep in-app, email and push notifications useful rather than noisy.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Notifications & Messaging Features, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

202

Starter tasks

🧩 Product Management

Notifications & Messaging Features

Designing in-app, email and push notifications that are useful rather than noisy, with sensible defaults and user controls.

  1. Inventory of every notification the product sends
  2. Notification volume and engagement baseline
  3. Notification categories and the rules attached to each
  4. Approval gate for adding a new notification
  5. Channel rules for push, email, in-app and SMS
  6. Default notification settings for new accounts
  7. Notification preference centre design
  8. Unsubscribe and opt-out path audit
  9. Notification pipeline architecture map
  10. Weekly notification health review
  11. Opt-out reasons and complaint review
  12. Email deliverability monitoring
  13. Push token hygiene and delivery failure handling
  14. Quarterly notification copy review
  15. Over-notified users report
  16. Notification incident runbook and kill switch
  17. Template library and version control
  18. Quarterly notification pruning
  19. Support tickets about missing and unwanted messages
  20. Push platform fundamentals for iOS and Android
  21. Email authentication and deliverability fundamentals
  22. Writing notification copy that earns the tap
  23. Send times, time zones and quiet hours research
  24. Notification fatigue and attention reading
  25. Accessible notifications on screen and in email
  26. Messaging consent and privacy rules primer
  27. Choosing a notification delivery provider
  28. Frequency caps and quiet hours
  29. Digests and batching for activity notifications
  30. In-app notification centre
  31. Deep links that land on the right screen
  32. Cross-channel deduplication and suppression
  33. Security and transactional message reliability
  34. SMS channel decision
  35. Lock screen previews and sensitive content
  36. Preference centre launch and settings migration
  37. Bulk sender requirements readiness check
  38. Peak season sending plan
  39. New sending domain warm-up
  40. Notification provider migration cutover
  41. Notifications for B2B products with admins and members
  42. Early-stage startup notification starter set
  43. Engineer joining the notification platform team
  44. Taking over a noisy legacy notification system
  45. Collaboration product mentions, assignments and replies
  46. Relevance ranking for candidate notifications
  47. Long-term notification holdout
  48. Time-sensitive and critical alert design
  49. Event-driven notification rules engine
  50. Notification audit trail and data retention

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Inventory of every notification the product sends

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most products send far more messages than anyone on the team can list: welcome emails written at launch, a push someone added for a growth test, receipts from the billing system, digests nobody remembers turning on.

First tasks

  • Export the list of active email templates from the delivery provider
  • Search the codebase for every call to the push, email and SMS send functions
  • Ask support, billing and marketing which tools send messages to users on their behalf
  • Ask the agent to merge the lists into one table with trigger, channel and owner columns
  • Re-run the inventory and reconcile it with the previous version @recurring(yearly)

Notification volume and engagement baseline

Without a baseline, every argument about whether users get too many messages is an opinion. Measuring sends per active user per week by channel, alongside open or tap rate, unsubscribes, push opt-outs and spam complaints, shows where the volume really sits and gives later changes something to be compared against.

First tasks

  • Pull last month's send counts by channel from the provider dashboards
  • Divide sends by weekly active users to get messages per user per channel
  • Record the 30-day unsubscribe, complaint and push opt-out rates
  • Refresh the baseline figures in the metrics log @recurring(monthly:4)

Notification categories and the rules attached to each

A password reset, a comment reply, a weekly summary and a promotion for a new plan should not live under the same rules, yet many products treat them identically. Sorting every message into a small set of categories, such as security and account, transactional, activity, product updates and marketing, decides which ones users can switch off, which respect quiet hours and which need marketing consent.

First tasks

  • Draft five to seven category names with one example message each
  • Tag every row in the notification inventory with a category
  • Write the opt-out, quiet-hours and consent rule for each category
  • Review the mixed-purpose messages with your privacy adviser

Make it yours.

Install Notifications & Messaging Features, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.