Other tools split tours, help and analytics across different apps. Your CSM stitches them together by hand.
Product Fruits brings onboarding, help widget and analytics into one platform. One source of truth.
You shipped a new feature.
Almost nobody knows.
Your team ships fast. The feature works. Three months later the dashboard tells you nobody used it.
We are launching a lot of features every quarter, but we don't see adoption.
One of our biggest bottlenecks right now is just making sure our users are aware of new features that we're rolling out.
With respect to product adoption: how can we make more customers aware about the features that we're releasing at a very high pace?
Four principles that turn every release into a used feature,
not a changelog line
Stop treating adoption as a hope. Announce inside the product, show people how it works, measure who actually clicked, and go back for the ones who missed it.
Announce new features inside the product
A release note email in an inbox competes with everything else in that inbox. A banner inside the product doesn't.
Newsfeed post, banner or pop-up the moment the feature ships
Trigger on next login or any other event
Segment so only the accounts with access to the feature see it
Don't just announce it, show them how to use it
A banner or newsfeed tells users a new feature exists. New feature tour or a hint in the UI gets them to actually try it.
Pair every announcement with a tour showing how to use it
Add a video card, it sells the feature faster than a paragraph of text
The hint stays visible until the user tries it or dismisses it
Ask why the feature landed, or didn't
A click tells you they saw the announcement. It doesn't tell you why they skipped the feature, or what they thought once they tried it. A short survey does.
Trigger a survey right after someone tries the new feature
Send a different survey to users who saw the announcement and never opened it
Bring what customers actually said into the next roadmap review
Go back for the ones who scrolled past
Most users dismiss the first banner. That's not rejection, that's timing. Catch them later, in context.
Re-trigger the announcement for users who dismissed it
Behavior-based hint: land on the old workflow, see a nudge pointing at the new one
Feature adoption becomes a loop that runs itself, not a one-time email
Why CS leaders pick
Product Fruits for onboarding
Built for CS to author, not engineering to ship
Most onboarding tools assume you have a dev team free to wire up flows. Product Fruits is built so your CS lead or onboarding manager authors directly, no engineering ticket.
Drag and drop your flow in a visual editor, no code
Preview every change on your live app before users see it
Automatically translate to any language
Account onboarding doesn't stop at first login
Onboarding isn't one moment. It's every new teammate, every new workflow your customer adopts. Elvin (our onboarding agent) stays with the user the whole way, so your CSMs don't get pulled back in every time something changes.
- 1Connect your docs
- 2Test the answers
- 3Embed in your app
- 4Watch usage and retention climb
Hear it from our customers
"It gives customers a clear self-service experience through the help center, guided tours, tooltips, and in-app support so they can find answers instantly instead of waiting for our team."
"Before, we had to provide a lot more support on how to use our portal. Now, when a question comes up regularly or when we're releasing new products, we set up a quick tour and the number of questions is reduced significantly."
"We have seen improved user engagement, reduced reliance on support teams and a smoother overall user experience, allowing our team to focus more on account growth rather than reactive support."
"A large portion of first-level support questions is now handled by Elvin (AI agent). Users get immediate, accurate answers without needing to reach out to our team."
G2 leader
"It reduces the need for constant training sessions, demos, and support tickets, saving both time and money for the team."
"The time and effort spent on manually onboarding each client has been significantly reduced."
"We can create and update help content without relying heavily on developers, which saves time and lets us improve the customer experience much faster."
"It helps simplify user onboarding and reduces the need for constant manual support. By guiding users directly within the product, it improves self-service and saves time for both the team and customers."
