Notification & Push Message Copy Framework

## ROLE
You are a notification strategist and UX writer who specializes in crafting messages that users actually want to receive. You understand the psychology of interruption, the fine line between helpful and annoying, and the technical constraints of every notification channel. You have reduced notification opt-out rates by 40%+ for multiple products by writing copy that earns attention instead of demanding it.

## OBJECTIVE
Design a complete notification copy system for [PRODUCT NAME] that drives re-engagement, delivers genuine value, and respects user attention. The product is a [PRODUCT TYPE] and the core user actions to drive are [KEY ACTIONS: daily check-in / content creation / collaboration / purchase / learning progress / social interaction]. The current notification opt-in rate is [CURRENT RATE OR "unknown"] and the target is [TARGET RATE].

## TASK

### Step 1 — Notification Channel Strategy
Define copy guidelines for each channel with its unique constraints:

**Push Notifications (Mobile)**
- Title: Max 50 characters (appears bold on lock screen)
- Body: Max 100 characters (truncated beyond this on most devices)
- Deep link target: Where exactly in the app should this open
- Rich media: When to include images, action buttons, or grouped notifications
- Write 12 push notification templates across these categories:
  1. Activity alerts: "[PERSON] [ACTION] your [ITEM]" — 3 variants
  2. Reminder nudges: "Your [ITEM] is waiting" / "Don't forget to [ACTION]" — 3 variants
  3. Achievement unlocked: "You hit [MILESTONE]!" — 2 variants
  4. Content recommendations: "New [CONTENT TYPE] matching your interests" — 2 variants
  5. Urgency triggers: "[TIME-SENSITIVE EVENT] happening in [TIMEFRAME]" — 2 variants

**In-App Notifications (Bell Icon / Notification Center)**
- Can be longer: Up to 200 characters
- Support rich formatting: Bold names, links, timestamps
- Write templates for:
  - Social actions (likes, comments, follows, mentions, shares)
  - System updates (feature launches, maintenance windows, policy changes)
  - Progress tracking (streaks, goals, usage milestones)
  - Team activity (member joined, document shared, task assigned)
  - Administrative (billing reminders, plan limits approaching, security alerts)

**Email Digest Notifications**
For each email notification type, write subject line (max 50 chars), preview text (max 90 chars), and headline:
- Daily activity summary: Aggregate social and content activity
- Weekly progress report: Stats, achievements, suggestions
- Monthly recap: Big picture stats, trends, comparisons
- Real-time critical alerts: Security, payment failure, account issues
- Feature announcement: New capability available

**SMS Notifications (Where Applicable)**
- Max 160 characters per segment
- Write templates for:
  - Two-factor authentication codes
  - Appointment or event reminders
  - Urgent account security alerts
  - Delivery or status updates for [RELEVANT PRODUCT EVENTS]

### Step 2 — Personalization Token System
Design a token library for dynamic notification copy:

| Token | Example Value | Usage Context |
|-------|--------------|---------------|
| [USER_FIRST_NAME] | Sarah | Greeting, celebration |
| [ACTOR_NAME] | Alex M. | Social activity attribution |
| [ITEM_TITLE] | "Q3 Marketing Plan" | Content reference |
| [COUNT] | 5 | Aggregated activity count |
| [TIME_RELATIVE] | "2 hours ago" | Recency signal |
| [STREAK_COUNT] | 7 days | Motivation |
| [PERCENTAGE] | 85% | Progress indicator |

Write fallback copy for every token when the value is unavailable (e.g., no first name: use "there" or rephrase entirely).

### Step 3 — Frequency & Batching Rules
Define intelligent notification grouping:
- Maximum push notifications per day: [RECOMMENDED: 3-5 for consumer, 1-2 for B2B]
- Batching logic: When more than [N] events occur within [TIME WINDOW], group into a single notification
- Grouped notification copy template: "[ACTOR] and [COUNT] others [ACTION] your [ITEM]"
- Quiet hours: Default [10 PM - 8 AM local time] with user override option
- Escalation ladder: If user ignores [N] notifications in a row, reduce frequency by [PERCENTAGE] automatically
- Re-permission prompt copy for users who have notifications disabled: Write a gentle, benefit-focused request to re-enable

### Step 4 — Opt-Out & Preference Copy
Write copy for notification management that reduces blanket opt-outs:
- Preference center header: Explain the value of staying connected
- Category toggles: Name each notification category in user-benefit language (not technical names)
  - Instead of "Marketing emails" write "Product tips & exclusive offers"
  - Instead of "Activity notifications" write "When someone interacts with your work"
- Frequency options: "Instant / Daily digest / Weekly summary / Off" with description for each
- Unsubscribe confirmation: "You've been unsubscribed from [CATEGORY]. You'll still receive [ESSENTIAL CATEGORY]."
- Win-back message: If user turns off all optional notifications, show a single message explaining what they will miss with a "Reduce instead of remove" option

### Step 5 — Tone Calibration by Context
Write a tone matrix showing how voice shifts by notification urgency:

| Urgency Level | Tone | Example |
|---------------|------|---------|
| Critical (security, payment) | Direct, serious, no personality | "Unusual login detected. Secure your account now." |
| Important (deadlines, mentions) | Clear, slightly warm | "[NAME] mentioned you in [PROJECT]. Take a look." |
| Informational (updates, digests) | Friendly, conversational | "Your weekly roundup is here — 3 wins worth celebrating." |
| Celebratory (achievements, milestones) | Warm, enthusiastic (not over-the-top) | "7-day streak! Consistency is your superpower." |
| Re-engagement (dormant users) | Curious, low-pressure | "Things have been quiet. Here's what's new since you last visited." |