返回提示词目录第 1413 页

编写移动应用推送通知文案

围绕应用触发场景设计推送计划与多版本短文案,并安排发送频率、时段规则和效果衡量方式。

完整提示词

<context>
You write push notifications for a mobile app. Push is the most interruptive channel a company has: one irrelevant notification can make a user switch off notifications or uninstall, and notification permission is hard to win back. Experts treat push as a scarce budget. They lead with the specific useful fact (title plus first line must make sense on a lock screen, where text is cut short), personalise with real data, deep-link to the exact screen, respect quiet hours in the user's time zone, cap volume per day and week, and give each type of notification its own settings category so users can switch off marketing without losing order updates. Asking for permission at a moment where the value is obvious works better than asking on first launch.
</context>

<task>
Write push notifications for this app.

<app>
{{app}}
</app>

<moments>
{{moments}}
</moments>
{{#limits}}Current limits and data: {{limits}}{{/limits}}

1. **Notification plan:** for each moment, the trigger, the delay, the deep-link destination, the settings category it belongs to, and whether it is transactional or marketing.
2. **Copy:** for each moment, two variants with a title (aim for under about 40 characters) and body (aim for under about 100 characters so the key fact survives truncation), personalisation fields as `{field}` with a fallback, and an optional rich-media note.
3. Write the permission pre-prompt screen copy shown before the system dialog, placed at a moment of clear value.
4. **Frequency and timing rules:** daily and weekly caps, quiet hours in local time, priority order when several fire, cool-down after a user ignores several in a row, and when push should yield to email or in-app instead.
5. **Measurement:** open rate per type, downstream action, opt-out and uninstall rate after sends, and a holdout for marketing notifications.
</task>

<constraints>
- Character limits vary by device and operating system; state them as approximate and recommend testing on real devices.
- No clickbait, fake urgency, false personal messages ("Anna sent you something" when no one did) or guilt.
- Transactional notifications carry no promotions.
- Note that marketing push may require separate consent in some places and that the user should check; do not state legal rules as fact.
</constraints>

<output_format>
## Notification plan
A table: Moment | Trigger and delay | Deep link | Category | Type.

## Copy
Per moment: two variants with title, body and character counts; then the permission pre-prompt.

## Frequency and timing rules
Bullets.

## Measurement
Bullets.
</output_format>

可替换内容

  • {{app}}
  • {{moments}}
  • {{#limits}}
  • {{limits}}
  • {{/limits}}

分类与标签

商业营销、应用推送、通知文案、用户触达、营销测量

前往 AI 图片创作