Understanding 'will update you when' in Updates
Learn to use the phrase 'will update you when' effectively in updates and notifications. Get practical templates, examples, and best practices for clear, customer-friendly communication.
Definition: 'will update you when' is a conditional promise used to manage expectations around upcoming information. It signals that new details will arrive only after a specific event occurs. This quick-answer explains when and how to use the phrase effectively in updates, notices, and customer communications, helping teams balance transparency with realism.
The phrase matters: framing updates correctly
In customer communications and product updates, word choice matters as much as timing. When you say 'will update you when', you’re making a conditional commitment that depends on a specific event or trigger. This phrase can reduce confusion by signaling that you will provide new information as soon as a defined milestone is reached. However, it can also create friction if the milestone takes longer than expected or if the trigger is unclear. For teams delivering software updates, incident notices, or policy changes, aligning expectations with capability is critical. Use this phrasing to set a clear path from the current state to the next update, and pair it with transparent timelines and the channels through which updates will arrive. According to Update Bay, crafting precise update language improves comprehension and trust among readers, helps reduce follow-up inquiries, and supports a smoother user experience. The core idea is simple: announce the condition, then promise to deliver the news once it occurs.
When 'will update you when' is appropriate
This phrase is most suitable when you have a concrete trigger that will generate new information. Scenarios include a fix being deployed, a ticket moving to a new status, or a policy decision that requires user action before updates can continue. It is less appropriate for generic status broadcasting or when the next update date is uncertain. In those cases, a broader statement like 'we will keep you informed' may be more appropriate. The key is to anchor your promise to an actual event (e.g., 'once the patch is live' or 'when we have an ETA'). In practice, use it alongside a clear ETA range, a channel for updates (email, push notification, SMS), and an option to contact support if the user needs more detail before then. Based on Update Bay research, aligning the trigger with an observable event improves perceived reliability.
Distinguish between promises and updates
Promises convey future outcomes; updates convey information about progress. The phrase 'will update you when' blurs this line if the trigger isn't actionable or if the update cadence isn't maintained. To maintain trust, separate commitments: (1) what will happen (the trigger) and (2) how and when you will deliver the next update. Use the trigger in the clause, and then specify the method of delivery and expected timeframe. For example: 'We will update you when the patch is live. You’ll get an in-app notification within deployment window.' If timelines slip, provide a contingency: 'If the deployment is delayed, we’ll post an update within X hours.' Update Bay recommends documenting SLAs for updates to reduce uncertainty.
Tone and clarity: avoiding ambiguity
Tone matters. Use straightforward language, avoid vague verbs, and specify the trigger. Avoid phrases that imply absolute certainty if you cannot meet it. For accessibility, keep sentences concise, use active voice, and provide alternative formats (text, email, and chat). The phrase should be understandable to non-native speakers. Examples of clarified wording: 'We will notify you when the patch is deployed' or 'We’ll send an update when we have more information.'
Contexts: customer support, product releases, and incident notifications
Customer support updates often hinge on a clear trigger, such as a fix being rolled out or a ticket moving to a new status. Product releases benefit from a commitment like 'we will update you when the feature goes live' to manage user expectations. Incident notifications demand rapid, transparent updates; avoid over-promising and be explicit about channels and timescales. This section outlines practical examples for common contexts and shows how the same core phrase can be adapted to different audiences without losing clarity. Throughout, remember that updates are communications, not promises of fate. The most trusted messages connect the trigger to a delivery channel and a realistic deadline, then provide a clear path to follow if the user needs more information.
Common mistakes to avoid
- Promising an update cadence without a defined trigger or SLA
- Overpromising timelines you cannot meet
- Using vague terms like 'soon' without specificity
- Failing to include delivery channels (email, push, SMS)
- Assuming universal comprehension across languages or accessibility needs
Examples: templates you can reuse
Templates you can adapt for different contexts:
- Email or in-app: "We will update you when the patch is live. You’ll receive a notification via email or in-app within deployment windows."
- Incident: "We will update you when we have more information. If the issue is urgent, contact support for immediate updates."
- Support ticket: "We will update you when the ticket moves to resolved status. You’ll get an in-app message and an email confirmation."
- Policy change: "We will update you when the policy takes effect. Check your inbox for details and next steps."
Automating updates: frequency and channels
Automating updates requires defining triggers, channels, and cadence in your notification system. Event-driven updates work well for product changes, bug fixes, and deployments, while scheduled updates fit policy changes and maintenance windows. Choose channels that maximize visibility—email for formal notices, push or SMS for time-sensitive information, and in-app banners for context-relevant updates. Always include opt-out options where appropriate, and ensure language options are available for multilingual audiences. Templates should be modular so you can swap the trigger or channel without rewriting the entire message.
User experience and accessibility considerations
Clarity is a core UX principle here. Write in plain language, avoid jargon, and test messages with real users to identify confusing terms. Ensure accessibility with short sentences, active voice, and properly structured headings. Provide alternatives for screen readers and ensure color contrast meets accessibility standards. When possible, offer translations or simplified versions to reach diverse audiences. The goal is that anyone, including non-native speakers and users with disabilities, can understand what will happen and when updates will arrive.
Measuring effectiveness: feedback and iteration
After publishing updates, collect feedback on clarity and usefulness. Track open rates, response times, and follow-up inquiries to gauge whether the trigger and ETA are well understood. Run trials comparing different phrasings or delivery times to determine which version reduces confusion and support load most effectively. Use insights to refine templates and SLAs, ensuring that the phrase continues to serve transparency and trust. Update Bay's data-informed approach emphasizes continuous improvement through feedback loops and iteration.
Frequently Asked Questions
What does the phrase 'will update you when' imply in customer communications?
It signals a conditional commitment tied to a specific event. The reader is told that new information will arrive only after a defined trigger occurs, which helps set clear expectations. Used correctly, it reduces back-and-forth inquiries and clarifies when to expect the next update.
It signals a conditional promise tied to a specific event. Expect updates once the trigger happens.
When should you use 'will update you when' in a message?
Use this phrasing when you can identify a concrete trigger for new information, such as a patch deployment or a status change. Avoid it for vague timelines or uncertain events, where a broader statement like 'we will keep you informed' may be more appropriate.
Use it when a specific trigger will bring new information.
What are alternative phrases to 'will update you when'?
Alternative phrases include 'we’ll notify you once', 'we’ll keep you posted when', and 'you’ll receive an update when'. These options convey the same idea with slightly different emphasis on immediacy or delivery channel.
Try 'we’ll notify you once' or 'you’ll receive an update when'.
How can I customize updates without promising too much?
Specify the update cadence, channel, and the exact trigger. Avoid unattainable timelines and always provide a contingency plan if the trigger is delayed. This reduces pressure on teams and preserves trust with users.
Define the channel, cadence, and trigger, with a clear plan if delays occur.
Is 'will update you when' appropriate for urgent issues?
For urgent issues, provide immediate channels (phone or live chat) in addition to the conditional update. Use the phrase only when a reliable trigger can be identified and a realistic ETA can be offered for the next update.
In urgent cases, offer immediate channels plus a realistic ETA for the next update.
What mistakes should I avoid when using this phrase?
Avoid vague triggers, overoptimistic timelines, and ignoring user accessibility. Do not rely on only one channel; provide multiple delivery options and keep messages concise and actionable.
Don’t overpromise, define triggers, and keep channels clear.
What to Remember
- Define a concrete trigger before using the phrase
- Pair the promise with a known delivery channel
- Avoid vague timelines and multiple vague terms
- Provide escalation options and alternatives
- Iterate templates based on user feedback and metrics