When this is useful
Choose a first task that matches the account’s starting state. A video for an empty workspace should not assume imported data or administrator permissions. Keep setup prerequisites visible so users can recognise when they need another step first.
Adapt the script
- Welcome the user and name the first outcome. Avoid listing every navigation item as though each needs immediate attention.
- Show the first path with sample information. Explain the input the user needs to provide and where the result will appear.
- Tell the user how to continue or get help. Keep that guidance close to the task they just watched.
Why these scenes belong together
A reporting product might begin with selecting a sample dataset and opening the first view. Connecting a live account can be explained separately if it introduces permissions and decisions the welcome video cannot cover clearly.
Welcome and first-task script
Illustrative copy to adapt. Replace bracketed fields and verify every claim against your product.
Limits and checks
A welcome video cannot replace an accessible, understandable onboarding interface. If the product requires an important choice, the user should be able to understand it outside the video too.
Your next step
Watch from a new account’s perspective and note every prerequisite the script assumes. Add the missing context or choose a simpler first task.
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.