Channel Selection Strategy
You'll learn: How to decide which notification channel (push, SMS, email, in-app) to use based on urgency, user preferences, and content importance.
The Core Challenge
Not all notifications deserve the same treatment. A "your account was hacked" alert needs different handling than "your friend posted a photo." Choosing the wrong channel wastes resources, annoys users, or fails to deliver critical information on time.
Selection Criteria
1. Urgency Level
- Critical (seconds): SMS + Push notification (e.g., fraud alerts, security events)
- High (minutes): Push notification + in-app (e.g., direct messages)
- Medium (hours): Email + in-app (e.g., weekly summaries)
- Low (days): In-app only (e.g., feature announcements)
2. User Preferences
Respect user-configured settings per notification type. Store preferences in a fast-access store:
user_prefs: {
security: [SMS, PUSH, EMAIL],
social: [PUSH],
marketing: [EMAIL]
}
3. Cost Considerations
- SMS: ~$0.01 per message (most expensive)
- Push: nearly free at scale
- Email: ~$0.0001 per email
- In-app: storage cost only
Use cheaper channels when urgency permits.
4. Delivery Guarantee Requirements
- Must deliver: Multi-channel redundancy (SMS + Push + Email)
- Best effort: Single preferred channel
5. User Context
Consider device status: if a user is currently active in-app, show in-app notification instead of SMS.
The Decision Tree Analogy
Think of it like emergency services: a 911 call (critical) demands immediate sirens and lights, while a parking ticket reminder (low urgency) arrives by mail. Match the channel intensity to the message importance.
Key Takeaway: Channel selection balances urgency, user preferences, cost, and delivery guarantees—choosing the right channel ensures important messages arrive promptly without overwhelming users or budgets.