# Feature adoption emails: getting users to the feature they need

> How to choose who should hear about a feature, when to tell them, and example feature adoption emails written from what each user already does.

Source: https://behavly.io/guides/feature-adoption-emails · Updated October 10, 2026

A feature adoption email is a message to a user who would benefit from a feature they have not used yet, sent when their own behavior shows they need it and written around the job it does for them. It is not the same as a feature announcement, which tells everyone that something exists. An announcement builds awareness. An adoption email changes what one particular person does next, and that is the part that keeps people in a product: the more of their real work runs through it, the less reason they have to leave.

Most teams ship a feature, send the announcement, watch the open rate, and then wonder why usage barely moves. The gap is that the announcement went to everyone on launch day, while the people who needed the feature needed it on some other day, when they were doing the thing it fixes. This guide is about writing to them on that day. For the general approach of emailing users based on what they do, see [the behavioral email guide](https://behavly.io/guides/behavioral-email).

#### Feature announcement email vs feature adoption email

|  | Feature announcement | Feature adoption email |
| --- | --- | --- |
| **Who gets it** | Everyone, or a broad segment | People whose behavior shows they need the feature and have not used it |
| **When** | Launch day | The moment the need shows up, which is different for each person |
| **What it talks about** | The feature: what it is, what is new | The person’s work: what gets faster or easier for them |
| **How you judge it** | Opens and clicks | First real use, and then a second one |

Keep sending announcements; they tell the whole base what changed. Adoption emails are the follow-up that turns that awareness into use, one person at a time.

#### Which users should get a feature adoption email?

The best candidates are already showing you they need the feature. Look for these signals:

- **They do the job the slow way**: Exporting the same report every week when scheduled reports exist. Creating the same project from scratch when templates exist. Sending reminders by hand when automation exists. This is the strongest signal, because the payoff is time they are already spending.
- **They hit the problem the feature solves**: Rage clicks on a table that needs a filter, repeated visits to one help article, a search that returns nothing. Friction tells you exactly which feature to mention.
- **They use the feature next door**: Someone who sends invoices is a candidate for recurring invoices. Someone who builds dashboards is a candidate for sharing them.
- **They started and stopped**: Opened the setup screen, filled half of it, and left. They already want it; something in the setup got in the way.
- **Their account changed**: Teammates added means permissions start to matter. More data means search and filters start to matter. A new integration connected means the features built on it become relevant.

Just as important is who to leave out:

- **People who already use it.** Check right before sending, not when the list was built.
- **People who have not activated the core product yet.** A secondary feature is a distraction until the main one works for them. Get them there first; see [the SaaS onboarding email sequence](https://behavly.io/guides/saas-onboarding-email-sequence).
- **People whose plan does not include it**, unless the email is honestly an upgrade email and says so.

#### When to send a feature adoption email

Trigger on behavior, not on the calendar. The best moment is right after someone has done the job the slow way, while the cost is still fresh. A note that says “this can happen on its own” lands very differently the day after a tedious manual task than it does on a random Tuesday.

- **After core activation, not during it.** The first week belongs to the main workflow. Feature emails in onboarding compete with the one thing the user has to get right.
- **One feature per email, and space them out.** Coordinate with your other lifecycle emails so a user never gets three different “have you tried” messages in a week.
- **Launch day for everyone, signals for everyone else.** Send the announcement to the whole base, then let adoption emails reach the right people over the following weeks as each one shows the need.

What happens after the first email depends on what the person does:

| What they did | Next step |
| --- | --- |
| Used the feature | A short note a few days later that makes the second use easy. A feature used once is a trial; used twice, it is becoming a habit |
| Clicked but did not finish setup | One follow-up with a shortcut: a template, a prefilled setup, or the single field most people get stuck on |
| Did nothing | Stop. Try a different feature later, or wait for a stronger signal |

#### How to write a feature adoption email

- **Lead with their work, not the feature name.** “Your first-of-the-month invoices can send themselves” beats “Introducing Recurring Invoices”. The feature name can appear once, as a label, after the reader already wants it.
- **Put the payoff in their numbers.** Five invoices, every month, to the same five clients. Concrete figures from their own account do the persuading that adjectives cannot.
- **One step, linked straight to it.** The setup screen, ideally prefilled with their own data. Not the changelog, not a blog post, not the help center.
- **Describe what done looks like in one sentence.** “On the 1st, it goes out with the month in the line item” is enough. Skip the feature tour.
- **Write it like advice from a person.** Plain text from a named sender reads like a colleague’s tip. A designed banner reads like an announcement, which is the email they already ignored.

#### Feature adoption email examples

These use Copperline, a made-up invoicing app for freelancers. Each email ties one feature to something the person already does.

They do the job the slow way

> Subject: Your 1st-of-the-month invoices can send themselves
>
> Hi Leah,
> 
> On the 1st you send the same five invoices to the same five retainer clients. Recurring invoices can do that for you: set each one up once, and Copperline sends it on the 1st with the month in the line item.
> 
> Start with Fernhill Studio, your largest; it takes about a minute.
> 
> Set it up here: [link]
> 
> Omar

They hit the problem the feature solves

> Subject: Chasing the Fernhill invoice
>
> Hi Leah,
> 
> The Fernhill invoice is now 12 days past due. Payment reminders can follow up for you: a short, polite note at 3, 7 and 14 days late, sent from your own address and stopped the moment they pay.
> 
> You can turn it on for overdue invoices only, so clients who pay on time never hear from it.
> 
> Switch on reminders: [link]
> 
> Omar

After the first use: making the second easy

> Subject: Fernhill paid. Four retainers to go
>
> Hi Leah,
> 
> Fernhill’s recurring invoice went out on the 1st without you touching it, and they paid two days later. Your other four retainer clients are still on manual invoices.
> 
> You can copy Fernhill’s setup to all four at once from the Recurring tab.
> 
> Copy it across: [link]
> 
> Omar

Their account changed

> Subject: Giving Nina her own Copperline access
>
> Hi Leah,
> 
> You added Nina to your workspace last week. If she does your books, the Accountant role lets her see every invoice and export your quarterly tax report, without being able to send or edit anything.
> 
> Changing her role is one click on the Team page.
> 
> Set Nina to Accountant: [link]
> 
> Omar

#### Mistakes to avoid

- **Calling the announcement your adoption plan.** A launch email to everyone is awareness. Adoption happens person by person, later.
- **Emailing people who already use the feature.** It tells them you are not paying attention, which is worse than saying nothing.
- **Leading with “Introducing…”.** The feature’s name means nothing to someone who has not felt the problem it solves.
- **Bundling.** “Five features you might have missed” gives the reader five decisions and makes all of them easy to skip.
- **Pushing advanced features before the basics work.** Until the core workflow is a habit, every extra feature is noise.
- **Measuring clicks instead of use.** A click on a feature email is curiosity. The number that matters is how many people used the feature afterward, and how many used it again.
- **No exit when they adopt.** The moment someone uses the feature, every follow-up about it should stop.

#### How to run feature adoption emails in Behavly

Behavly records what each signed-in user does in your product, so you can describe the people doing a job the slow way and have each email written from what that person actually did.

1. Install the tracking snippet from **User Activity → Setup** on your signed-in pages. Page views and clicks are recorded per person with no identify call, which already shows who opened a feature’s screen and who never has.
2. For actions that do not have a page of their own, send events from your product with `behavly.track`, such as `recurring_invoice_created`. These are what an Agent uses for **did an action in your product**, for waits, and for the path’s **Goal**.
3. Create a Behavly-Agent campaign in **Campaigns → New Campaign** and start from the **Feature adoption** example. Or open one of the **Suggested for your users** cards: for a “never did X” pattern Behavly found, it puts that pattern in as who enters and sets X as the goal.
4. Add a **Plain text by Behavly Agent** step. In **Instructions for Behavly Agent**, say what the feature does and who it helps, for example: show someone who sends the same invoices every month how recurring invoices would handle theirs, one link to set it up. Turn on **Skip if they already did it** so people who already use the feature never get the email.
5. Follow it with **Wait until they do something**, waiting for the feature’s action with a limit such as **But no longer than** 5 days, then a **Branch** on **did an action in your product**. Yes leads to the second-use email; no leads to one follow-up with a shortcut, then **Stop the path**.
6. Use **A/B test** on an email step to try two sets of instructions, say a time-saved angle against a worked example. Each person always gets the same version, and Behavly names a winner only once each version has at least 30 sends and the gap is unlikely to be chance.
7. Use **Preview** to read the email Behavly writes for a real person, and turn on **Hold Behavly-written emails for approval** so you approve the emails before they go out.

Each email step shows how many people it reached and how many reached the goal after it, so you judge the path on use rather than clicks. **Frequency** caps emails per person (3 every 7 days by default) but counts only that Agent’s own emails, so leave room for your other sends. Emails go out from your own mailbox, and every Monday, once the Agent has sent 20 emails, **Path review** suggests changes from its own results for you to apply or dismiss.

> Note: Agents are on Starter and above. On the free plan, a one-time campaign to a pattern works well for a launch follow-up: Behavly writes each email from the person’s own activity instead of sending one announcement to everyone.

_The Audience step. Each pattern card shows how many people it resolves to before you send._

## Questions

### What is a feature adoption email?

An email to a user who would benefit from a feature they have not used yet, sent when their behavior shows the need and written around the job the feature does for them. Its goal is first use, then repeated use, rather than awareness.

### What is the difference between a feature announcement email and a feature adoption email?

An announcement goes to everyone on launch day and talks about the feature. An adoption email goes to one person when their behavior shows they need it, and talks about their work.

### When should you send a feature adoption email?

Right after the person does the job the slow way or hits the problem the feature solves, and only once they have activated the core product. One feature per email, spaced out from your other lifecycle emails.

### How do you measure feature adoption from email?

Count how many recipients used the feature afterward, and how many used it a second time, rather than counting clicks. Comparing against similar users who did not get the email tells you how much of that use the email caused.

## Related

- [SaaS onboarding email sequence: what to send, based on what users actually do](https://behavly.io/guides/saas-onboarding-email-sequence)
- [Churn prevention emails: what to send when usage drops](https://behavly.io/guides/churn-prevention-emails)
- [Behavly Agent Campaigns](https://behavly.io/help-center/campaigns/behavly-agents)
- [Running An Agent: Activate, Change, Pause, Stop](https://behavly.io/help-center/campaigns/running-an-agent)