Custom announcement.
Publish rich content with an optional call-to-action label. Open a product URL, feedback, chat, or another supported destination from the message.
In-app messaging software
Put the next useful message inside the product moment.
Publish targeted announcements or start a customer chat using page rules, audience conditions, timing, frequency, priority, and measurable calls to action.
09
The answer first
In-app messaging should help a customer act, not decorate a dashboard.
In-app messaging software shows an announcement, prompt, or call to action inside a website or product. The message is useful when it reaches the right audience on the right page, makes the next action clear, stops when its job is done, and leaves enough evidence to judge whether it helped.
Managani Web Messages use the same public script as the Widget. Create a custom announcement or a chat prompt, add rich content, choose an action, and control delivery with deployments, URLs, customer attributes, time on page, exit intent, frequency, priority, and stop rules. Shown, clicked, and dismissed totals make the message inspectable after launch.
Message formats
Announce, guide, or open a conversation.
Chat prompt.
Invite a visitor or signed customer into the team inbox when a page, audience, or product moment suggests that direct help is useful.
Release follow-through.
Pair a changelog entry with a targeted message or highlight so the people affected by a shipped change learn what they can do now.
Delivery workflow
Define eligibility before writing the clever headline.
- 1
Choose one customer outcome.
Decide whether the message should explain a release, recover a stalled workflow, collect feedback, open chat, or move a customer to a specific product action.
- 2
Write the message and action.
Use a direct title, short body, and one clear action. Avoid turning an operational notice into promotional copy or hiding essential information behind a click.
- 3
Target the context.
Select Widget deployments, include or exclude URL rules, and match signed customer properties with all-or-any conditions. Anonymous visitors can receive messages without customer-level targeting.
- 4
Set timing and pressure.
Choose time on page or exit intent, then use one-time, once-per-session, daily, or every-page frequency. Assign priority when several messages may be eligible.
- 5
Stop and measure.
Stop after a click, dismissal, first display, or configured view count. Compare shown, clicked, and dismissed totals with the surrounding product activity before deciding to keep the message.
Design and safety
Match the product without trapping the customer.
A message can inherit the active site theme or use controlled presentation settings.
1
Choose a respectful position.
Select a supported placement and width that leaves the underlying product usable. Preview small screens, drawers, sticky navigation, and important controls.
2
Keep dismissal obvious.
Customers should understand how to close a non-critical message and whether it may appear again. Do not use frequency rules to fight the user’s decision.
3
Coordinate competing messages.
Use priority and stop conditions so onboarding, release, support, and promotional messages do not all claim the same product moment.
Limitations
Not an omnichannel campaign platform.
Web Messages do not replace enterprise email, SMS, mobile push, customer-data platforms, journey orchestration, ad audiences, or transactional communication. They are product-surface messages delivered through configured Managani Widget deployments. Keep legally required notices and critical service communication in appropriate channels.
Connected advantage
The message can respond to product context.
Signed identity, customer metadata, tracking events, feedback, releases, and chat already live in the same product system. That lets a lean team target useful product communication without exporting every segment into another campaign tool.
Release discipline
Treat every active message as part of the interface.
Keep an inventory of published messages with an owner, audience, start condition, stop condition, and removal date. Review that inventory before each release so an old promotion does not compete with a new onboarding step or critical service notice.
Test the final message against real route transitions, signed and anonymous states, reduced screen height, keyboard navigation, and translated product copy where applicable. Confirm that the destination works after the user clicks and that dismissing the message persists at the intended frequency. Use the shown, clicked, and dismissed counts as diagnostics, not vanity metrics: a high click rate may reflect confusion, while a high dismissal rate may mean the message reached the wrong moment. Retire the message when the product itself can make the next action obvious.
FAQ
In-app messaging, answered plainly.
What is in-app messaging?
It is targeted communication shown inside a website or product while someone is using it. Common jobs include onboarding, release education, support prompts, announcements, and calls to action.
Can Managani target anonymous visitors?
Yes. Anonymous visitors can receive messages based on deployment, URL, timing, and general rules. Signed identity is required for customer-property targeting and customer-linked history.
What actions can a message open?
A configured call to action can open chat, feedback, a URL, or no destination. Choose the action that matches the stated outcome instead of adding a button by default.
How is this different from a product highlight?
A Web Message is a freestanding announcement or chat prompt. A highlight points to one interface element. Tours coordinate several ordered steps. Use the least intrusive format that solves the job.