Drive feature adoption after launch

Before you start

This use case works best when you've already set up some foundational elements in Quotient:

• Knowledge Store populated: Add your product overview and brand voice so the Campaign Agent can describe the feature in language that matches how you talk to customers.
• Feature details ready: Have the feature name, key benefits, where to find it in the product, and any screenshots or short demos. The clearer the "what" and "why," the better the adoption content.
• Audience in mind: Know who you're trying to activate — all users, a specific segment, or users who've shown related behavior. This shapes tone and channel.

How to do it in Quotient

1. Start a conversation with the Campaign Agent

Open a new chat and describe the adoption campaign. Include the feature, who you're targeting, and which channels you want. For example:

"We just launched a new reporting export feature. I want to drive adoption among existing customers. Create an email sequence: one announcement email with a clear CTA to try it, plus a follow-up for non-openers. Also draft short in-app tooltip and banner copy we can use in the product, and a brief how-to section we can drop into our help center."

2. The agent creates the campaign and deliverables

The Campaign Agent creates a campaign with tasks for each deliverable — announcement email, follow-up email, in-app copy variants, and any how-to or help content. It focuses on reducing friction (where to click, what they get) and a single clear next step.

3. Provide the details

Share specifics so the copy stays accurate:

• "The feature lives under Settings > Export — mention that in the CTA"
• "Lead with time saved: users can export in one click instead of building reports manually"
• "We're targeting users who've viewed the Reports page in the last 30 days"
• "Tone should be helpful, not salesy — they already have the feature"

4. Review and ship

Review the emails and in-app copy, then schedule or hand off to your email and product teams. For ongoing adoption, you can run a follow-up campaign or use an Agent Job to remind you to check activation metrics and iterate.

What you'll get

A typical feature adoption campaign includes:

• Announcement email — short, benefit-led email with one clear CTA to try the feature
• Follow-up email — for non-openers or non-activators, with a different angle or reminder
• In-app copy — tooltip, banner, or empty-state copy that highlights the feature where users will see it
• How-to or help content — a brief guide or FAQ section that reduces "how do I…?" friction

Tips for better results

• One CTA per email. Don't ask users to "learn more, try it, and share feedback." Ask them to do one thing — usually "try it" with a direct link.
• Lead with the outcome. "Export any report in one click" beats "We've added a new export feature." Frame everything in terms of what the user gains.
• Segment when you can. Adoption messaging for power users can be different from messaging for casual users. Tell the agent who you're targeting.
• Time it after launch. Let the initial launch buzz settle, then hit users who haven't adopted yet with a focused adoption campaign.
• Measure and iterate. Share open and click rates (or activation data) with the agent and ask for a refreshed follow-up sequence if the first wave underperforms.