Users understand what changed
An explanation names the change, its value and the next action.
Users see a change, find the new location or feature and start using it at work. Your team gives customers one exact release explanation.
An explanation names the change, its value and the next action.
A short announcement on the changed screen leads to the feature or full entry.
One published entry explains the update in your product and on the public page.
Keep one release explanation and guide users into scheduled reports.
Explain scheduled reports in a release note. Give users one place to understand the change and revisit the details.
Announce scheduled reports on the Reports screen. Help users notice the change and find where to try it.
Guide users through their first report schedule. Help them put the update to work in their weekly routine.
Start with a full entry, then prepare a short announcement for the screen where users see the change.
Explain the change and the user’s next step.
Publish the entry in the product, on a public page or in both places.
Show a pop-up to the right audience and lead to the entry or feature.
A pop-up draws attention to a change in the product. A changelog keeps details users can revisit.
No. It makes an entry available in the selected channel. Use a pop-up for an in-product message.
Yes. Set display rules by role, attributes, page and events.
Once connected, your team updates entries, messages and tours, then publishes a new version.
Show us a product update. In the demo, we will connect the full entry, announcement and user action.
We’ll email you to arrange a demo.