The template
Organize a customer feedback response around the issue, the product change, and what happens next.
Use this scene sequence as an editable outline. Replace sample wording with verified details; the sequence is a planning aid, not a fixed duration or a platform specification.
| Beat | On screen | Narration | Review check |
|---|---|---|---|
| 1. The request | Show the relevant workflow, not private support data. | Summarize the feedback neutrally. | Is the wording approved? |
| 2. Status | Show a current product screen or roadmap label. | Say whether the change shipped or is planned. | Is the status current? |
| 3. What changed | Demonstrate the released action. | Describe what a customer can now do. | Does this work for all stated accounts? |
| 4. How to use it | Show the entry point and result. | Name any prerequisite or limitation. | Are plan limits and permissions correct? |
| 5. Follow-up | End with support or feedback guidance. | Invite a specific next action. | Does the CTA reach the right team? |
How to fill it in
- Hook: state the viewer's problem or the outcome they want.
- Context: show only the setup the viewer needs to understand the workflow.
- Main action: focus on one or two meaningful product steps.
- Outcome: show what changed, using only claims you can support.
- Next step: give viewers one specific action to take.
Customize it for your audience
Choose a response format that matches the status of the feedback. For a shipped improvement, demonstrate the changed path and tell affected users where it is available. For a planned item, explain the status without promising a date unless one is approved; for a declined request, provide a concise reason and any practical alternative. Remove support details that could identify the sender, and secure permission before quoting them. Make a separate internal version if staff need decision history. Recheck the issue status and help links before publication so the video does not outlive the product state it describes.
Prepare the final handoff
Pair the published response with the canonical help article or release note that explains the current behavior. Record the feedback status and review date, then assign an owner to revisit the asset if the feature changes. Keep private support correspondence out of the public handoff folder.
Production and approval checklist
Before recording or animation, confirm the viewer, destination, desired next action and product version. Replace every illustrative name, number and screen with approved material, or label it as sample content. Check that each scene advances the story and that voiceover fits the time available on screen. Review the draft once for product accuracy, once for audience comprehension and once for permissions, accessibility and destination requirements. Make the final reviewer and approval date explicit; recheck volatile facts such as pricing, availability, release status, event details and platform rules just before publishing. Keep the script, source assets and approved export together so an update can be made without guessing which version is current.
Who it serves
Customers want a direct answer about a request: whether it was heard, what changed, and how to find it. Describe the issue in approved terms without exposing a private support conversation.
Evidence and review
Have the product owner confirm whether the change shipped, is in preview, is planned or was declined. Show current screens for released behavior and label roadmap information.
Do not promise an unapproved fix or date, or imply that a customer-specific change is generally available.
A worked example
Illustrative scenario, not a customer story: State the feedback in approved terms, show the related product change if it shipped, and explain what the customer can do now. Separate a planned change from a released one.
Make it automatically
DemoVexa can use your product code and project context to draft a brief, script, and scene plan. Review every screen, claim, permission, and recording before publishing.
Frequently asked questions
Can I quote the customer who gave feedback?
Only with permission and an approved quote. Otherwise describe the request generally and remove names, account details, support IDs and clues that could identify the person or organization.
How should a planned feature be shown?
Label it as planned or in preview and avoid presenting it as part of the current product. Recheck status with the product owner just before publication.
Can I use this template for free?
Yes. The outline is page content you can copy without an account. Adapt it to your product, check the destination's current requirements, and verify every claim, date, permission and third-party asset before publication.
Make your next product video with DemoVexa
Download the app to make a video from your code, or start a free trial with 15 renders.