Users see the update they need
An announcement reaches users for whom the feature is available and useful in current work.
Users notice a new feature, try it in their workflow and return to it at work. Your team connects a release to a clear first action.
An announcement reaches users for whom the feature is available and useful in current work.
A tooltip or tour leads to the first action on the working screen.
A detailed entry helps users and your team return to the context of a change.
Introduce automation, guide the first rule, and keep the explanation close.
Introduce automation where users manage requests. Help them see which repeated step it removes.
Guide users through their first automation rule. Help them set it up without another walkthrough from your team.
Explain how automatic assignment works. Give users a reference they can revisit before creating a rule.
Choose a new feature and the action users should complete to begin using it at work.
Briefly explain what changed and who will use it.
Open a tour or tooltip on the screen where users try the feature.
Check the journey and update entry, then show them to the right audience.
An entry keeps the full explanation. Add a pop-up or tour when users need to notice and try a feature in the product.
Choose users by role, attributes, page or events your product sends.
Show a short tooltip beside an element or guide several steps in a tour.
Yes. Once connected, your team changes the message, tour and entry without another app release.
Show us a new feature. In the demo, we will connect the announcement, first action and full explanation.
We’ll email you to arrange a demo.