01
Context decides the message
Match the prompt to the page or visitor state instead of broadcasting one generic announcement.
Reach the visitor before they think to open chat.
In-app messages inside the support surface
Create a focused announcement, prompt, or survey and show it inside the same Widget already connected to your Agent.
Start with 100 creditsOne-time $1 activation · 100 credits included · No automatic subscription
How it works
Create one useful prompt for one clear moment.
The message, audience, timing, and result stay together so teams can review the experience before publishing.
- 1
01 · Compose
Write the smallest message that helps
Use a headline, concise context, and one action that makes sense on the current page.
Message
DraftPage
Pricing
Headline
Need help choosing?
Action
Ask a question
- 2
02 · Target
Choose who should see it and where
Aim the Nudge at the relevant page or visitor state instead of interrupting everyone.
Audience
TargetedLocation
/pricing
Visitor
First session
Delay
After page view
- 3
03 · Learn
Review the response and refine
Use impressions, engagement, and dismissals to decide whether the message earns its place.
Performance
LiveImpressions
Tracked
Engagement
Tracked
Dismissals
Tracked
The right prompt arrives in context. The visitor keeps control.
What changes
Help that appears in the moment it becomes useful.
A good in-app message removes uncertainty without turning the product into a wall of popups.
02
The Widget stays the interaction surface
Visitors can continue into the Agent or Shared Inbox without loading a separate tool.
03
The response remains measurable
Impression, engagement, and dismissal states show whether the Nudge helped or interrupted.
Designed for the edge cases
Protect attention while making the message useful.
Targeting and restraint matter as much as the copy.
Focused announcements
Share a concise update, invitation, or prompt inside the existing Widget surface.
You stop dealing with: adding another site-wide banner for a message that matters on one page.
Page and visitor targeting
Choose the context in which a Nudge should appear and keep unrelated visitors undisturbed.
You stop dealing with: showing every message to every customer.
Support continuation
Let the visitor move from the prompt into the Agent or teammate Conversation without changing surfaces.
You stop dealing with: sending interested visitors into a disconnected form or tool.
Outcome states
Track impressions, engagement, and dismissals to judge whether the prompt should stay live.
You stop dealing with: keeping a popup because no one knows whether it works.
Attention has a cost
Make every interruption explain itself.
The targeting and outcome stay visible so teams can keep only the messages that help.
Context
The message matches the page
Visitors see a prompt related to what they are doing now.
Control
Dismissal stays easy
The visitor can close the Nudge and continue without friction.
Outcome
Engagement is measurable
Keep, refine, or remove the message using visible response states.
Choose the interruption model
A targeted Nudge inside support, not another popup stack.
Compare how the message relates to the visitor and the next support step.
Page targeting
CommunicateConfigured
Generic popupVendor dependent
Site bannerManual rules
Continue to support
CommunicateSame Widget
Generic popupSeparate form
Site bannerNot native
Dismissible
CommunicateCustomer controlled
Generic popupUsually
Site bannerDepends on design
Outcome states
CommunicateImpressions and response
Generic popupCampaign metrics
Site bannerCustom analytics
Questions before you start
Questions about In-App Messages.
How Nudges appear and what teams can learn.
Put the right prompt in the right moment.
Choose one page where visitors regularly hesitate, write one helpful message, and review the response.
Start with 100 creditsOne-time $1 activation · Grounded answers · Human takeover · Cancel anytime