wowprompt

Push and in-app notification strategy with frequency caps

Plans every push, in-app and email notification a product sends, with the trigger, the value to the user, the channel and a frequency cap, so people keep notifications switched on. Use it before adding a new alert, or when opt-out rates and uninstalls are climbing.

A notification inventory table with triggers, channels, caps and priority, quiet-hour rules, opt-in timing, and sample copy for the three most important messages
The output this prompt produced, unedited.

The prompt

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

  1. Sort every notification into transactional (the user asked for it), useful alert (the user benefits now) or promotional.
  2. Pick one channel each: push, in-app message, email or SMS. Transactional may use more than one.
  3. Set a cap per user: promotional pushes per week, total pushes per day.
  4. Quiet hours and time-zone rules; nothing promotional at night.
  5. When to ask for push permission: after the first moment of value, never on first launch.
  6. User controls: which categories the settings screen lets people switch off.

Output format

  1. | Notification | Type | Trigger | Channel | Cap | Priority | Keep, change or drop |
  2. Quiet hours and cap rules in five bullets.
  3. Permission ask timing in two sentences.
  4. Sample copy for the top three messages, each under 60 characters in the title and 110 in the body.
  5. 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].
push notification strategyin app notificationsnotification frequencyuser retentionproduct messagingnotification design

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity