The Feature Request Video That Turns Waiting Into Loyalty
Feature request updates are one of the most underutilized retention tools in SaaS. A customer who submitted a request six months ago and never heard back is a churn risk. A customer who receives a personal video explaining what happened to their request — whether it shipped, was declined, or is on the roadmap — becomes a advocate. This script closes the loop on feature requests in a way that builds trust rather than eroding it.
When to use this script
Use this script when a feature a customer previously requested has shipped, been added to the roadmap, or been definitively declined. Closing the loop regardless of the outcome is what differentiates companies that earn loyalty from those that just collect feature requests.
What does the Feature Request Status Update script look like?
Hey {{contact_name}}, {{sender_name}} here — a while back you asked about {{feature_request}}, and I wanted to personally follow up because I have an update for you.
{{feature_status_message}} — {{feature_detail}}. The reason {{feature_decision_context}}. I specifically remembered your request because {{personal_connection_to_request}}, and I wanted to make sure you heard about it from me rather than just seeing a changelog notification.
If you want to {{next_step_offer}}, just reply to this email or grab a time below. And if there are other things on your wishlist for {{product_name}}, {{contact_name}}, I would genuinely love to hear them — your input has been useful for us.
How can I make the Feature Request Status Update script work better?
Close the Loop Regardless of the Outcome
The most impactful thing about this touchpoint is that you respond at all. Customers who submitted feature requests and never heard back are among your highest churn risk segments. A video saying 'we decided not to build this and here is why' earns more respect than silence — and far more than a generic 'we value your feedback' auto-reply.
Reference the Original Request Specifically
Showing that you remembered a specific request — especially months later — signals that customer input genuinely influences your company. Even if you have the request logged in a system, framing it as 'I specifically remembered your request' makes the follow-up feel personal rather than automated.
Be Honest When a Request Was Declined
Vague non-answers about declined features erode trust over time. If a feature will not be built, explain the honest reason: it is outside the core use case, it conflicts with another design decision, or the demand was not sufficient to justify the investment. Customers respect transparency far more than corporate hedging.
What are the variations of the Feature Request Status Update script?
The Feature Shipped Version
When the feature the customer requested has been built and is now available.
The Feature On Roadmap Version
When the feature has been formally added to the product roadmap with a target quarter.
The Feature Declined Version
When the feature request has been evaluated and definitively will not be built.
What performance can I expect from this script?
Frequently asked questions
How do I track which customers have open feature requests to follow up with?
Maintain a feature request log in your CRM or customer success platform that captures the requesting customer, the request, and the date. Tag requests with a status field (open, in development, shipped, declined) and trigger a follow-up task whenever the status changes. Customers who never hear back are a hidden churn risk.
What if I have hundreds of open feature requests and cannot send individual videos?
Prioritize by customer value — focus personalized video follow-ups on your top accounts and high-usage customers. For the long tail, a personalized-feeling video generated by AI at scale, where each one references the customer's specific request and the status, lets you close every loop without recording each one individually.
How should I handle a feature request that has been in 'under consideration' for over a year?
Be honest about the timeline ambiguity: 'This is still on our list but I want to be transparent — it has not moved to active development and I cannot give you a timeline. If this is a blocker for you, I want to know so we can discuss workarounds.' Silence is worse than uncertainty.
Should product managers or CSMs send these videos?
Both have value, but CSMs are typically the right sender because they own the customer relationship. If the feature is highly technical, a brief cameo from the product manager in the video — or a quote attributed to them — adds credibility. The relationship owner should deliver the message.
What is the right cadence for proactively sharing product updates with customers?
Feature request updates should be sent on the day of the status change, not batched into a monthly newsletter. Timeliness is what makes the update feel personal rather than programmatic. Proactively sharing a changelog once a month is a complement to, not a replacement for, individual feature request follow-ups.
More templates
Close Every Feature Request Loop With a Personal Video
Outvid generates a unique AI video for every customer — referencing their specific request and its status — so no feature request ever goes unanswered again.