All AI Patterns
AI Pattern

Proactive Suggestions

Surface timely AI recommendations or next-step actions before the user asks.

Discovery & Onboarding

Core Concept

Proactive Suggestions are AI-generated recommendations, prompts, or next-step actions that appear before the user explicitly asks for them. The idea is simple: instead of waiting for a prompt, the system notices context, timing, history, or intent signals and offers something useful at the right moment. Your document describes this well as “invisible AI moments” that surprise users with exactly what they need, when they need it.

This pattern is different from Suggested Prompts:

  • Suggested Prompts help users start.
  • Proactive Suggestions help users continue, decide faster, or avoid extra work.

Public HAX guidance supports this direction through contextual relevance and remembering recent interactions: the system should use current task, location, time, or recent state to tailor what it shows, as long as it does so in a privacy-aware way.

Problem it Solves

This pattern solves the “I shouldn’t have to ask for everything” problem.

In many AI products, users know they need help, but:

  • they do not know the best next step,
  • they do not want to search or dig through menus,
  • or the timing matters more than the request itself.

Your doc highlights this from a user perspective: proactive suggestions reduce digging, increase shortcut adoption, and create “it gets me” moments that make the product feel smart instead of passive.

It also solves a product problem: without proactive help, useful AI features stay hidden, underused, or only accessible to advanced users. Contextual-assistance pattern libraries make the same point: timely, relevant proactive help can improve usability without forcing users to interrupt their own workflow to ask for it.

When to Use

Use Proactive Suggestions when:

  • the system has reliable context about what the user is doing,
  • there is a clear “next best action,”
  • recommendations can save time or reduce effort,
  • the task is repeated often enough that prediction becomes useful,
  • the product benefits from nudging rather than waiting for explicit prompts.

This works especially well in:

  • writing and editing tools,
  • search and discovery experiences,
  • work productivity tools,
  • copilots in docs, email, spreadsheets, and support systems,
  • recommendation-heavy flows where timing matters.

When NOT to Use

Do not use this pattern aggressively when:

  • the system does not have enough context to be accurate,
  • wrong suggestions could cause harm, confusion, or mistrust,
  • the user is doing a focused, sensitive, or high-stakes task,
  • privacy expectations make silent inference feel creepy,
  • the suggestions would interrupt more than help.

Your document indirectly warns about this through related pitfalls: over-contextualizing the wrong data, annoying interruptions, and mode confusion. Those are exactly the risks of a badly implemented proactive system.

User Value

Functional benefits

  • saves time by surfacing the next useful action,
  • reduces searching, digging, and menu hunting,
  • speeds up repeated workflows,
  • increases feature discovery without extra tutorials,
  • helps users act before friction builds up.

Psychological benefits

  • creates a feeling that the product understands the user,
  • builds delight through timely relevance,
  • increases trust when suggestions are consistently helpful,
  • reduces decision fatigue,
  • makes the product feel more supportive and intelligent.

Your document is especially strong here: it directly connects proactive suggestions to trust, loyalty, and retention because the product feels like it “gets you.”

UX Principles Applied

This pattern most strongly maps to:

  • User Value First — suggestions must save effort or improve outcomes.
  • Task and Context Fit — the suggestion must be relevant to the current situation.
  • Clarity of Capability and Limits — users should understand why they are seeing the suggestion.
  • Trust Calibration — helpful suggestions increase trust; wrong ones destroy it.
  • Privacy, Consent, and Permission Awareness — proactive help must not feel invasive.
  • Adaptation with Predictability — the system can adapt, but not in a confusing or erratic way.

Design Guidelines — Do & Don’t

Do

  • Trigger suggestions from real context, not random enthusiasm.
  • Make suggestions timely, specific, and actionable.
  • Explain why the suggestion appeared when needed.
  • Keep the suggestion lightweight and easy to dismiss.
  • Use it for moments where the user clearly benefits from a shortcut.
  • Learn from feedback and acceptance rates over time.

Don’t

  • Don’t interrupt users constantly.
  • Don’t suggest actions based on weak or misleading context.
  • Don’t make users feel surveilled or manipulated.
  • Don’t over-personalize without explanation.
  • Don’t keep pushing irrelevant nudges once the user ignores them.

A good rule:

Proactive should feel helpful, not pushy.

Real Examples (Components Used)

1. Gmail Smart Compose / typing-time assistance

As users type, the system predicts likely next text and offers it inline. This is a proactive suggestion because the system intervenes before the user explicitly asks for help, based on the live context of the sentence. Contextual-assistance references frequently use Smart Compose as a model example.

Components used

  • Ghost text suggestion
  • Accept shortcut
  • Inline suggestion state

2. Copilot-style context-aware next actions

In a side-panel assistant, the AI can suggest actions like summarizing the current file, drafting a reply, or pulling out action items based on what document or workspace is open. Your doc strongly points toward this kind of context-aware shortcut as the future of suggestions.

Components used

  • Side-panel suggestion card
  • Quick action buttons
  • Reason/source text
  • Dismiss control

3. Search / recommendation surfaces

Systems can proactively suggest relevant content or actions based on current context, prior activity, or user signals. Microsoft’s own proactive recommendation systems describe delivering personalized, context-relevant recommendations in real time with a feedback loop for improvement.

Components used

  • Recommendation card
  • Context label
  • Click-to-apply action
  • Feedback controls

Business Impact

This pattern can have strong business value because it increases:

  • retention,
  • repeated usage,
  • shortcut adoption,
  • feature discovery,
  • and perceived intelligence of the product.

Your document explicitly ties proactive suggestions to long-term retention, reduced digging, and memorable delight moments that users talk about.

It can also reduce operational friction by helping users complete tasks faster. But there is a cost side too: if suggestions are wrong, over-frequent, or creepy, they can hurt trust and increase churn. That is why contextual relevance and careful adaptation matter.

KPIs

Useful KPIs for this pattern include:

  • proactive suggestion acceptance rate
  • dismiss rate
  • conversion rate from suggestion to task completion
  • time saved per task
  • repeat usage after suggestion acceptance
  • retention of users exposed to proactive help
  • relevance score or user-rated helpfulness
  • error/false-positive rate for suggestions
  • opt-out or disable rate for proactive features

These metrics help you judge not just engagement, but whether suggestions are actually valuable and trusted. Feedback loops are especially important here.

Engineering Notes

This pattern is more complex than Suggested Prompts because it depends on:

  • context collection,
  • signal interpretation,
  • ranking logic,
  • timing rules,
  • permission handling,
  • and feedback loops.

The system needs to know when to suggest, what to suggest, and how aggressively to intervene. Microsoft HAX guidance on contextual relevance and remembering recent interactions is directly relevant here: proactive behavior depends on good short-term memory and context-sensitive logic, but must remain privacy-aware and predictable.

Teams usually need:

  • event/context pipelines,
  • recommendation or ranking models,
  • experimentation support,
  • suppression rules,
  • analytics,
  • and user controls for personalization or dismissal.

Future Outlook

This pattern will likely grow from simple nudges into adaptive orchestration:

  • next-best-action recommendations,
  • role-aware suggestions,
  • team-level suggestions,
  • cross-app proactive assistance,
  • and agent-like proactive help that surfaces the right option before the user asks.

But the future challenge is not just making suggestions smarter — it is making them feel:

  • relevant,
  • understandable,
  • controllable,
  • and non-invasive.

That is what will separate useful proactive AI from annoying AI.

Stay ahead in AI design

Get the latest patterns, principles, and tools — straight to your inbox. No spam, ever.