skills/knock-notification-best-practices/rules/notification-copy-best-practices.md

---
title: Notification copy best practices
description: Core principles and guidelines for writing effective notifications across all channels and notification types
tags:
  - notifications
  - copywriting
  - messaging
  - best-practices
  - cross-channel
  - user-engagement
  - transactional
  - lifecycle
  - promotional
category: knock-notification-best-practices
last_updated: 2026-01-23
---

# Notification copy best practices

## Core principles

### Be specific and actionable
Users scan notifications in seconds. Lead with essential information and make the required action clear.

**Bad example:**
```
You have a new update in your account
[View update]
```

**Good example:**
```
Sarah Chen commented on your design proposal
[Click here to reply]
[Click here to view project]
```

### Include maximum context
Notifications pull users away from other tasks. Make the interruption worthwhile by providing enough context to help them decide whether to act immediately.

**Bad example:**
```
Your deployment's status changed
```

**Good example:**
```
Deployment #142 status changed from 'pending' to 'failed'
```

### Use active voice
Active voice creates more engaging notifications by putting the actor first and reducing word count. It feels more personal and makes notifications easier to scan and act upon.

**Bad example:**
```
Your report has been viewed by 12 people
```

**Good example:**
```
12 people viewed your report
```

### Use consistent terminology
Match the language in your notifications to your product's UI. If your app calls them "projects," don't suddenly switch to "workspaces" in notifications.

### Format for each channel
Every channel displays notifications differently, from character limits to link formatting. Understand how your messages will appear across each channel before sending.

## Writing guidelines by notification type

### Transactional notifications
Confirm user actions or system events where messaging clarity and accuracy matter most.

**Guidelines:**
- Confirm exactly what happened
- Include relevant identifiers (order numbers, amounts)
- Provide next steps when applicable
- Maintain neutral, professional tone

**Examples:**
```
📦 Your order #4521 has shipped via FedEx. Track package: [link]

✅ Password successfully updated. You'll need to sign in again on other devices.

💾 Export complete: customer_data_2024_q4.csv (45.2 MB) ready for download
```

### System notifications
Communicate technical events or service status where technical accuracy meets user-friendly language.

**Guidelines:**
- Translate technical events into user impact
- Provide clear timelines when possible
- Offer actionable next steps
- Link to detailed information

**Examples:**
```
⏰ Scheduled maintenance tonight 2-4 AM EST. API responses may be slower than normal.

⏳ Your API key expires in 7 days. Generate a new key to prevent service interruption.

🪫 Storage usage at 85% (42.5 GB of 50 GB). Upgrade for uninterrupted service.
```

### Lifecycle messaging
Encourage users to return to your product by balancing value with frequency to avoid notification fatigue.

**Guidelines:**
- Provide clear value proposition
- Use social proof when relevant
- Create urgency appropriately (not artificially)
- Respect user preferences

**Examples:**
```
💬 3 teammates commented on your design.
[See what they're saying]

📋 Your weekly summary: 487 new visitors, 12% increase from last week

✅ Lisa Chen completed the task you assigned: 'Update API documentation'
```

### Promotional messaging
Communicate offers, updates, and new features to drive engagement and adoption.

**Guidelines:**
- Lead with the benefit, not the feature
- Make offers specific and time-bound
- Include clear CTAs that match the message
- Segment based on user behavior and preferences

**Examples:**
```
🤑 Save 30% on annual plans — 3 days left to upgrade

🆕 New: AI-powered insights now analyze your team's productivity patterns

🪫 You've used 80% of your API calls.
[Upgrade to Pro for unlimited access]
```

## Testing checklist

Before shipping any notification:

1. **Read aloud**: Does it sound natural?
2. **Remove context**: Does it make sense without prior knowledge?
3. **Check truncation**: Does the key message survive character limits?
4. **Test personalization**: Do variables render correctly with real data?
5. **Verify links**: Do all CTAs lead to the right place?

## Implementation guidelines

When implementing notifications:
- Define clear categories (transactional, engagement, system)
- Create templates for common notification types
- Set up user preference controls
- Test across all target channels
- Monitor engagement metrics
- Implement batching for high-frequency events
- Plan for internationalization
- Document copy guidelines for your team