Loading…
Loading…
Notification copy covers in-app alerts, banners, badges, and system messages that inform users of events, changes, or required actions. Good notifications provide the right information at the right time; bad ones train users to ignore all alerts.
stellae.design
Notifications are interruptions. Every notification borrows user attention, and that loan must be repaid with value. Effective notification copy is specific about what happened, why it matters to this user, and what they can do about it.
Before/after examples: • Before: 'New activity on your account' → After: 'Sarah commented on your pull request #142: "Looks good, one small suggestion."' • Before: 'Update available' → After: 'Version 3.2 is ready — includes the dark mode you requested' • Before: 'Action required' → After: 'Your trial expires in 3 days. Add a payment method to keep your projects.'
Notification copy encompasses all the text content delivered through in-app notifications, system alerts, toast messages, badges, and banners that inform users about events, updates, and required actions within the product experience — and its quality directly determines whether users perceive notifications as helpful services or disruptive noise. Unlike push notifications that interrupt users outside the app, in-app notification copy reaches users who are already engaged, which means it competes with the user's active task for attention and must justify the interruption by delivering clear, actionable value in the fewest possible words. Products that write effective notification copy maintain user awareness of important events without fragmenting attention, while products with poorly written notifications create a 'notification blindness' where users learn to ignore all alerts because they cannot quickly distinguish important ones from trivial ones.
GitHub's notification system uses precise, context-rich copy that tells users exactly what happened and why they are being notified — 'alice requested your review on Pull Request #432: Fix authentication timeout' immediately communicates the event, the actor, the action needed, and the specific context, allowing the user to triage without clicking through. Notifications are categorized by reason (direct mention, review request, team mention, watching) with filtering controls that let users tune their notification stream to their role and preferences. This specificity means each notification carries genuine signal value, which keeps users engaged with the notification system rather than learning to ignore it.
Figma displays unobtrusive in-app notifications when collaborators perform relevant actions — 'Jordan left a comment on Header Component' or 'Taylor started editing the same frame' — using concise copy that identifies who did what and where without interrupting the user's design flow with modal dialogs or aggressive alerts. The notifications use the collaborator's name and the specific design element to make each message immediately scannable and relevant, and they auto-dismiss after a brief display to avoid cluttering the workspace. This approach maintains collaborative awareness without creating the constant interruption anxiety that plagues tools where every notification demands immediate attention.
An enterprise project management tool sends in-app notifications with generic copy like 'Something has been updated,' 'A change was made to a project,' and 'New activity in your workspace' — messages that provide no information about what changed, who changed it, or whether the user needs to take action, forcing them to click through each notification to determine its relevance. The system also fires individual notifications for every minor event — each comment, status change, and file upload generates a separate alert — resulting in notification counts in the hundreds that make the notification bell permanently display an unreadable badge number. Users quickly learn to ignore the notification system entirely, which means they also miss the genuinely critical alerts buried in the noise.
• The most common mistake is writing notification copy that describes what happened without explaining why the user should care or what they should do about it — 'Settings updated' tells the user nothing about which settings changed, who changed them, or whether action is needed, making the notification pure noise that trains users to ignore future alerts. Another frequent error is failing to establish a notification hierarchy, so that a critical security alert uses the same visual treatment and copy tone as a minor status update, preventing users from quickly triaging notifications by importance. Teams also neglect notification copy during the design process, treating it as a development implementation detail rather than a UX writing task, which results in developer-written messages like 'Operation completed successfully' or 'Error: null reference exception' reaching end users.
Was this article helpful?