AdoptAdoption nudge

Adoption Nudge Email

Write a nudge to a stalled user that names a specific unused feature tied to their goal, not a guilt-trip.

The nudge that works never mentions that usage dropped. It leads with the goal the user actually has, points to the one feature that moves it, and asks for a single tiny step. Guilt-based re-engagement just teaches people to ignore you.

The template

Copy it, swap the {{marked}} variables for your account, and run it.

prompt.txt

A user has gone quiet or is under-using the product. Write one short nudge
email that gets them to take a single specific action tied to a goal they
actually have. This is a helpful nudge, not a "we miss you" guilt email.

User: {{user}}
Their goal / why they signed up: {{their_goal}}
What they're NOT using that would help: {{unused_feature}}
What I know about why they stalled: {{stall_reason}}
The one action I want: {{desired_action}}

Rules:
- Lead with their goal, not our engagement metrics. They do not care that usage is down.
- Point to ONE specific unused feature and tie it to their goal. No feature buffet.
- No guilt, no "we noticed you haven't logged in." That makes people defensive.
- Make the action tiny. One click, one reply, one 10-minute thing.

Variables

{{user}}: User (role)e.g. a support team lead at a mid-size SaaS
{{their_goal}}: Their goale.g. cut first-response time on support tickets
{{unused_feature}}: Unused feature that would helpe.g. saved-reply templates, which they've never set up
{{stall_reason}}: Why they likely stallede.g. onboarded during a busy quarter, never got past the basics
{{desired_action}}: The one action you wante.g. set up their first 3 saved-reply templates

Worked example

A CSM notices a user who signed up to cut ticket response times has never touched the saved-replies feature that would do exactly that. They onboarded during a crunch and never came back. She wants to nudge them toward one concrete setup step without making them feel nagged.

filled-prompt.txt

User: a support team lead at a mid-size SaaS
Their goal: cut first-response time on support tickets
What they're NOT using that would help: saved-reply templates, which they've never set up
What I know about why they stalled: onboarded during a busy quarter, never got past the basics
The one action I want: set up their first 3 saved-reply templates

Good output vs bad output

GOODLeads with the user's goal (response time), names one specific unused feature, makes the action a 10-minute setup, and never mentions that usage was low.

Subject: A 10-minute setup that cuts your response time

Hi Sam,

You came to us to get first-response times down. There's one setup step that
moves that number more than anything else, and most teams skip it in their
first busy month: saved-reply templates.

Set up three for your most common ticket types and your team stops rewriting
the same answer ten times a day. It takes about ten minutes. Here's the
two-step guide, and if you'd rather, reply and I'll build the first three with
you on a quick call.

Sam

BADLooks fine at a glance. Here is why it fails.

Subject: We miss you! 👋

Hi Sam,

We noticed you haven't logged in much lately and wanted to check in! Our
platform has so much to offer and we'd hate for you to miss out. Have you
explored saved replies, automations, reporting, integrations, and our new
dashboard? There's so much you can do!

Log back in today to rediscover everything. We're here if you need anything.
Don't be a stranger!

Wrong register"We miss you" and "we noticed you haven't logged in" make it about our metrics and put the user on the defensive, which is exactly what kills a nudge.
No next stepLists five features ("saved replies, automations, reporting, integrations, dashboard") so the one action that would help drowns in a buffet. The user does nothing.
Generic filler"So much to offer", "rediscover everything", "don't be a stranger" is engagement-email boilerplate that gets filtered on sight.
Missing contextNever connects to the user's actual goal (response time), so there is no reason for a busy lead to care.

Guardrails

When NOT to use this

Do not nudge a user who is quiet because they are unhappy or mid-escalation. A cheerful feature tip on top of a real problem reads as tone-deaf.
Skip if you cannot name a specific feature tied to a specific goal. A generic nudge is worse than silence.

Responsible use

Do not auto-blast these on a usage-drop trigger without a human checking the account context. Automation that ignores why someone stalled is spam.
Reference only what the user actually told you their goal was. Do not infer intent from behavior and present it as fact.

Model + settings

Model: Claude Sonnet, this is quick, high-volume drafting.
Temperature: 0.6 (a bit higher, you want warmth and a human voice, not a template)
Settings: The "one specific unused feature tied to their goal" constraint is what separates a nudge from spam. Keep it in every run.
Generate a few subject-line variants and pick the one that leads with the outcome, not the product.

Back to all prompts