When this is useful
Choose a meaningful before state without exaggerating the old product’s limitations. The announcement should be understandable to current users and useful to someone considering the feature. Keep rollout and access conditions accurate.
Adapt the script
- State the change in one sentence. Name the task and the new action rather than stacking several feature labels.
- Show where the feature lives. Include enough navigation context for viewers to find it after watching.
- Demonstrate the saved result and next step. If access depends on a role or plan, communicate the verified condition where it matters.
Why these scenes belong together
For saved report filters, the important scenes are the filter configuration, the save action and the reopened view. An unrelated overview of the product calendar would weaken the announcement even if it looked attractive.
Feature announcement script
Illustrative copy to adapt. Replace bracketed fields and verify every claim against your product.
Limits and checks
Do not claim a feature is available to every account if the rollout is limited. Verify availability with the product owner before exporting the final end card.
Your next step
Prepare a short help link or written step beside the announcement so interested users can immediately try the new action.
References and scope
Examples are illustrative production guidance, not measured customer results. General workflows are not promises of product compatibility. Read our editorial approach and current Demovela scope.