How to Announce New Features In-App: 10 Examples for B2B SaaS

Product Managers, Product Marketers, and UX Designers often face the challenge of ensuring new features actually get used. Launching a powerful new capability in your B2B SaaS product is only half the battle; the other half is making sure your existing customers discover and adopt it. Relying solely on email announcements or blog posts often falls short, as users might miss them or not connect the dots back to their daily workflow. This is where effective in-app new feature announcement strategies become critical.

As covered in Juno School's insights, in-product communication encompasses anything within the product or offering itself that helps users understand and engage. These methods are vital for driving feature adoption, improving user retention, and ultimately demonstrating the ongoing value of your SaaS solution. Instead of pulling users out of their workflow, you meet them where they are, guiding them directly within the interface.

1. The 'Coming Soon' Banner

To build anticipation before a major release, a "Coming Soon" banner can be highly effective. This approach, similar to banners or pop-ups that say "watch out this space for more," generates curiosity and primes users for an upcoming enhancement. It's a subtle way to hint at future value without disrupting current tasks.

• When to use: For significant features or overhauls that require user preparation or a mental shift.
• How to use: Keep the message concise and benefit-oriented. Link to a landing page with more details or a sign-up for early access.
• Best practice: Schedule its appearance a few weeks before launch to build sustained excitement.

2. The Non-Intrusive Tooltip

Tooltips are excellent for providing contextual information about new or updated elements without interrupting a user's flow. These are the "signs or symbols that you might have noticed with an 'i' or some kind of asterisk" that, when hovered over or clicked, provide more information. They are perfect for subtle feature adoption strategy.

• When to use: For minor UI changes, new fields, or enhancements to existing features that don't require a full walkthrough.
• How to use: Ensure the tooltip text is brief, clear, and directly relevant to the element it's attached to.
• Best practice: Make them discoverable but not demanding. Avoid auto-opening tooltips unless absolutely necessary for critical changes.

3. The Guided Product Tour

For more complex new features or significant workflow changes, a guided product tour can be invaluable. These are "like guided walking tools, which are like virtual tours, where one gets to start a product tour by clicking on a particular place, then they're guided on what to fill, where to go, etc." They actively walk users through the new functionality step-by-step.

• When to use: For introducing entirely new modules, complex workflows, or a complete redesign of a core feature.
• How to use: Keep tours concise and focused on key actions. Allow users to skip or exit at any point.
• Best practice: Trigger tours only upon a user's first interaction with the new feature, or offer it as an opt-in.

4. The 'What's New' Modal/Popup

A "What's New" modal or popup is a direct way to announce a new feature to customers upon their first login after a release. While popups can be intrusive, when used thoughtfully, they ensure critical updates are seen. This is a common form of in product marketing examples for major updates.

• When to use: For major releases, significant feature additions, or critical updates that affect a broad user base.
• How to use: Make it visually appealing, with a clear headline, concise benefits, and a single, strong call to action. Include an easy-to-find 'X' or 'No Thanks' option.
• Best practice: Limit these to truly impactful announcements and avoid overusing them to prevent user fatigue.

5. Embedded How-To Videos

Sometimes, a visual explanation is the most effective. Embedded how-to videos offer "a lot of assistance... in the form of how-to videos, video showcasing how that particular feature works within the product." Placing these directly within the feature's UI makes learning seamless.

• When to use: For features that involve complex steps, visual setup, or demonstrate a new workflow.
• How to use: Keep videos short, focused, and directly demonstrate the feature's usage. Ensure they are easily accessible from within the relevant section.
• Best practice: Provide captions or transcripts for accessibility and ensure videos load quickly.

6. Feature Hotspots / Pulsing Dots

For drawing attention to subtle UI changes or newly added buttons, pulsing dots or hotspots are a gentle prompt. These small, animated indicators subtly point out new interactable elements without blocking the user's view or requiring a click to dismiss.

• When to use: For minor additions, new menu items, or small improvements that might otherwise go unnoticed.
• How to use: Use sparingly and ensure they disappear after the user interacts with the element or after a set number of sessions.
• Best practice: Combine with a brief tooltip that appears on hover for immediate context.

7. In-App Notification Center

A dedicated in-app notification center acts like a personalized inbox for updates, news, and new feature announcements. It's less intrusive than a modal because users choose when to engage with it, making it a powerful tool for how to announce a new feature to customers over time.

• When to use: For ongoing product updates, personalized feature announcements, or to house a history of releases.
• How to use: Prioritize notifications, allowing users to mark as read or dismiss. Categorize updates if the volume is high.
• Best practice: Provide a clear indicator (like a badge) for new notifications to encourage users to check the center.

8. Changelog/Release Notes Page

For technical users or those who want a comprehensive overview of every update, an accessible changelog or release notes page within the app is ideal. This provides a detailed record of all new features, bug fixes, and improvements, serving as a transparent communication channel.

• When to use: For all types of releases, especially for users who prefer detailed documentation.
• How to use: Keep entries clear, concise, and easy to scan. Link directly to relevant features or help articles.
• Best practice: Update regularly and ensure it's easily discoverable from the main navigation or a "What's New" modal.

9. Empty States with Feature Prompts

An often- overlooked opportunity for an in-app new feature announcement is utilizing empty states. When a user lands on a page or section that is currently blank (e.g., no projects created yet, no data imported), this is a prime spot to introduce relevant new features that help fill that void.

• When to use: For features that help users get started, overcome initial hurdles, or populate empty sections of the app.
• How to use: Clearly explain how the new feature solves the empty state problem and provide a direct call to action.
• Best practice: Personalize the message based on user segment or previous actions if possible.

10. Interactive Walkthroughs

Beyond simple guided tours, interactive walkthroughs require users to perform actions to progress. This hands-on approach ensures deeper engagement and understanding of complex new features, transforming passive viewing into active learning.

• When to use: For features with steep learning curves, critical first-time setups, or when you need to ensure users understand a specific workflow.
• How to use: Break down complex processes into small, manageable steps. Provide clear instructions and immediate feedback.
• Best practice: Offer a "skip" option for experienced users and ensure the walkthrough is robust enough to handle user mistakes gracefully.

Choosing the Right Announcement for Your Feature

Selecting the best method to announce a new feature to customers depends on several factors. Consider the complexity of the feature, its impact on user workflow, and your target audience. A simple decision matrix can guide your choices:

• Feature Complexity:
  • Simple (e.g., new button, minor UI tweak): Tooltips, Hotspots, In-App Notification Center, Empty State Prompts.
  • Moderate (e.g., new report, enhanced workflow): 'What's New' Modals, Embedded How-To Videos, Guided Product Tours.
  • Complex (e.g., new module, major redesign): Guided Product Tours, Interactive Walkthroughs, 'Coming Soon' Banners (pre-launch), Changelog.
• Target Audience Impact:
  • All Users: 'What's New' Modals, 'Coming Soon' Banners, In-App Notification Center, Changelog.
  • Specific Segment/Role: Tooltips (contextual), Embedded How-To Videos (within feature), Empty State Prompts (if segment-specific).
• Desired Engagement Level:
  • Passive Discovery: Tooltips, Hotspots, In-App Notification Center, Changelog.
  • Active Learning: Guided Product Tours, Embedded How-To Videos, Interactive Walkthroughs.
  • Immediate Awareness: 'Coming Soon' Banners, 'What's New' Modals.

Mastering these in-app new feature announcement techniques can significantly boost adoption and user satisfaction. For a deeper dive into product launches and generating excitement around your offerings, explore Juno School's comprehensive resources. For instance, understanding how to effectively communicate product changes is a key component of a successful launch, a topic thoroughly covered in Juno's Digital Marketing course.

Additionally, crafting compelling messages for these announcements can be enhanced by learning effective ad copy strategies. You can learn more about how to write ad copy in 30 minutes for various marketing channels, including in-app messaging. For those interested in leveraging AI, there's also a guide on how to write a PRD with ChatGPT, which can help streamline the documentation process for new features.