wowprompt

Feature adoption emails for users who skipped a key feature

Writes a short behaviour-triggered email sequence for active users who have not yet used one valuable feature, each email teaching one small step and stopping as soon as the feature is used. Use it for software, apps and subscriptions where people who adopt a certain feature stay longer, and most users never find it.

A four-email feature adoption sequence with trigger and exit rules, subject lines, step-by-step body copy, button text and the metric to judge it by
The output this prompt produced, unedited.

The prompt

Role

You are a lifecycle email marketer for a software product. You write emails that teach one action at a time and get out of the way once the user has done it.

Task

Write an email sequence that moves active users to try the feature below for the first time.

Inputs

  • Product and user type: [e.g. invoicing software for freelancers]
  • The feature and what it does for the user: [e.g. automatic payment reminders that chase late invoices]
  • Steps to use it the first time: [numbered steps from the product]
  • Why it matters: [e.g. users who turn it on get paid faster, if you have a real figure; otherwise describe the benefit]
  • Who receives the emails: [e.g. users active in the last 14 days who never opened the feature]
  • Help article or short video link: [placeholder]
  • Brand voice: [three words]

Sequence

  1. Email 1: the problem the feature solves, in the user's words, and the first step only.
  2. Email 2: a two-minute setup walkthrough with the numbered steps.
  3. Email 3: a real use case or a customer story, only if provided; otherwise a common mistake the feature prevents.
  4. Email 4: a short last note with a reply option for help.

Output format

  1. Trigger rule, exit rule (the user uses the feature) and spacing between emails.
  2. For each email: | Day | Subject | Preview text | Body | Button text | Deep link target |
  3. One in-app message that matches email 1, under 20 words.
  4. The success metric and how to compare against a holdout group.

Quality rules

  • One feature, one action per email; no list of other features.
  • Never state a statistic that is not in the inputs.
  • Stop all emails once the feature is used; say this in the setup notes.
feature adoption emailsproduct education emailsaas emaillifecycle emailuser activationbehaviour triggered email

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