Skip to content
Open Screeb

In-app message best practices

Write in-app messages and product tours that help users instead of interrupting them, pick the right format and moment, and improve them from their results.

Concept4 min read, updated Oct 15, 2026

A good in-app message helps a user at the moment they need it. A bad one is one more popup to close. These principles help you build messages and product tours that users read, follow and act on. To learn how messages work, read In-app messages and product tours.

Give each message a single purpose: announce one feature, explain one button, lead to one action.

  • Keep the text short: a title, two or three lines, one clear button.
  • Name the button after what happens (“See the new report”), not “OK” or “Next”.
  • Split a long explanation into the steps of a product tour rather than one crowded window. Use the Stepper block to show the user where they are, and a Checklist block for an onboarding with several tasks.
  • Always leave a way out. Add “Skip” next to the action, so a user who is busy can dismiss the message without hunting for it.
You want to Use
Inform without blocking the page Banner
Explain one element of the interface Popover, attached to that element
Draw the eye to an element, or start a tour from it Beacon
Announce something important, or ask for a decision Modal
Show richer content next to the page: onboarding checklist, video, resources Sidebar
Place content inside the page, in its flow Embedded (websites only)

Keep the Modal for what deserves to interrupt. For everything else, a Banner, a Popover or a Beacon lets the user keep working. Avoid several Popovers on the same screen: show them one after the other in a product tour.

In iOS, Android, Flutter and React Native apps, use a Banner, a Modal or a Sidebar: Popover and Beacon cannot anchor to the elements of a mobile app yet. Keep the text even shorter and the buttons large enough for a finger.

A message shown as the page loads gets closed before it is read. Tie it to what the user does instead.

  • Start the message on an event or a page visit, so it appears when it is relevant. See Choose who sees your message and when.
  • Use step conditions to wait for the right moment: a delay, a scroll, a session duration, or an element present on the page.
  • Do not stack messages on a new user’s first session. Spread them over the first days, or start each one after the action it follows.
  • By default, a user sees a message once. Use Display again only for a message that is worth repeating, and set a workspace capping for messages so users never see too many.

A message lands well when it fits the person who reads it. Build it for a persona, not for everyone.

  • Under Who, target a Segment or user properties: role, plan, account age, how much they use a feature. See Create user segments.
  • When two personas need different things, build one message for each. An admin setting up permissions and a new user opening their first project do not need the same tour.
  • Start with two or three personas whose needs really differ. Every extra segment is one more message to keep up to date when your product changes. If two messages keep needing the same edits, merge them.
  • Personalize the text with variables, such as the user’s first name, see Personalize questions with variables and hidden fields. Write the message in your users’ languages: when your workspace has several languages, the general settings of the editor offer a “Translate content” button. Nothing is translated until you click it.

A message is a success when users do what it was built for, not when it is seen. Check its displays, the step where a tour loses users and the outcome after its launch: Measure the results of your messages explains how to read them. Then fix the step with the biggest drop first.

These are guidelines, not rules enforced by Screeb: the editor lets you build any combination. Your own results are the best guide: keep what works for your users and change what they skip.