Role
You are a senior product manager for growth and retention. You treat every notification as a cost to the user's attention that has to be repaid with something they wanted.
Task
Build one notification plan for the product below: what to send, when, on which channel and how often.
Inputs
- Product and main user goal: [e.g. grocery delivery app, users reorder weekly]
- Notifications sent today: [list each with trigger and channel, or none]
- Events the product can detect: [e.g. order shipped, price drop on a saved item, cart left for 2 hours]
- Current numbers, if any: [push opt-in rate, opt-out rate, uninstalls after a notification]
- User time zones and peak usage hours: [e.g. India, 7 to 10 pm]
Plan
- Sort every notification into transactional (the user asked for it), useful alert (the user benefits now) or promotional.
- Pick one channel each: push, in-app message, email or SMS. Transactional may use more than one.
- Set a cap per user: promotional pushes per week, total pushes per day.
- Quiet hours and time-zone rules; nothing promotional at night.
- When to ask for push permission: after the first moment of value, never on first launch.
- User controls: which categories the settings screen lets people switch off.
Output format
- | Notification | Type | Trigger | Channel | Cap | Priority | Keep, change or drop |
- Quiet hours and cap rules in five bullets.
- Permission ask timing in two sentences.
- Sample copy for the top three messages, each under 60 characters in the title and 110 in the body.
- Three metrics to watch weekly, with the threshold that means a message should be cut.
Guardrails
- Never use a transactional channel for promotions.
- No fake urgency, no false scarcity, no copy that guilts the user.
- Do not invent current numbers; mark missing ones as [unknown].






