12 Best In-App Messaging Tools in 2026

Search for "in-app messaging tools" and you get three different products under one name. The first is a no-code tour builder that walks someone through your dashboard with tooltips and checklists. The second is a lifecycle tool that sends a modal the same way it sends an email. The third is a notification bell with a list of what happened. They share a name and very few buyers.

Buy the wrong one and the cost shows up fast. A tour builder is made for screens inside the product, not for a schedule of messages to paying customers. A lifecycle tool makes you wait on engineers for a six-step onboarding checklist that a product manager could have built in a tour tool. A feed component gives you a place to show messages, but no way to decide who sees a failed-payment notice on Tuesday and not on Wednesday.

So this page maps the category first, then shortlists 12 tools. For every tool you will see whether the product draws the UI for you or expects your code to draw it, web versus mobile support, the SDKs, and the pricing unit.

Disclosure: I build Sequenzy. It is one of the 12 and gets the same checks as the others. It is not the right pick for product tours, and it does not give you a finished notification bell.

Quick comparison table

Prices are the lowest published entry point on each vendor's pricing page in October 2026. "Not published" means the vendor only quotes. Plans change, so confirm before you buy.

Three products with one name

Product tours and onboarding UI. Appcues, Userpilot, Pendo and Chameleon sit here. You build flows in a visual editor, often a browser extension, and target them by page, element and user property. The product draws the modal, slideout, tooltip, hotspot or checklist on top of your existing UI. The buyer is usually a product, growth or customer success lead. The job is adoption: show a new user where the button is, or announce a feature to the people who would use it.

Lifecycle in-app messages. Braze, Customer.io, OneSignal, Intercom and Sequenzy sit here. These tools send an in-app message the way they send email or push: from a campaign or journey, to a segment, with a trigger, a delay, a stop condition and reporting. The format is usually a modal, a banner, a full screen or a card. Some tools render the UI from their own editor. Others expect your app to draw it from a payload.

Notification feeds and inboxes. Knock, MagicBell and Novu sit here. This is the bell icon, the unread count and the list of notifications your product generated. Your backend triggers a workflow, the message lands in a per-user feed, and the user reads it inside your app. The vendor ships a React component, a set of headless hooks, or both, and you decide where it sits.

The three groups do not compete for the same budget. A feed component in a product that also needs onboarding tours still needs a tour tool. Mapping the category first is the cheapest decision on this page.

How the pricing units differ

Vendors meter different things. Appcues, Userpilot, Pendo, OneSignal and Braze count monthly active users, Chameleon counts tracked users, Customer.io counts profiles including objects, Intercom charges per seat, Knock and MagicBell bill messages or deliveries, and Novu bills workflow runs. Two examples show why this matters. Userpilot's Starter tier stops at 2,000 MAU, and its Growth tier starts at $849 a month, so a 10,000-user app is buying a different plan. MagicBell counts each channel separately, so 100 in-app recipients plus 50 email recipients is 150 deliveries.

The 12 best in-app messaging tools

Product tours and onboarding

1. Appcues

Best for: Product and growth teams that want no-code onboarding flows on web and in native mobile apps from one vendor.

Who draws the UI: Appcues. You build flows in its editor and the SDK renders them. The mobile docs describe multi-step flows made of modals, slideouts and tooltips, plus surveys and embeds that sit inside a screen.

Surfaces: Web, and native mobile through one Appcues Mobile SDK built for iOS and Android. React Native and Flutter wrap the same SDK, and Ionic works through a Capacitor plugin.

Pricing: Not published. The public plans are named Start (up to 3,000 monthly active users), Grow (starting at 3,000 MAU) and Enterprise. A free trial with no credit card begins with a sales call. Pricing is based on MAU, installations and published experiences.

Strengths: The mobile SDK covers the main native and cross-platform stacks, and the docs are specific about deep links, Android edge-to-edge behavior and minimum OS versions.

Where it falls short: The price is quote-only, so you cannot size a budget without a call. The pricing page does not name the features on each tier, so ask for that list in writing.

Verdict: Strong when you need one tool for web tours and native mobile onboarding and you can take a sales call first.

2. Userpilot

Best for: Product teams that want web flows, checklists, banners and NPS with published starter pricing, and a mobile option from the same vendor.

Who draws the UI: Userpilot. Teams build flows without code, and the SDK renders them on web and in apps.

Surfaces: Web, plus a native mobile SDK for Android, iOS, React Native, Flutter, .NET, Cordova and Capacitor. The mobile page names carousels, slideouts, push, NPS and surveys as native formats. It does not name checklists or banners for mobile, so confirm those before you rely on them.

Pricing: The Starter plan is $299 a month for up to 2,000 MAU. Growth starts at $849 a month. Enterprise is quote-only, and the page lists monthly prices only. Mobile is an add-on to Growth or Enterprise, priced by mobile MAU. A 14-day free trial needs no credit card.

Strengths: Two published prices, one vendor for web and mobile, and a trial with no card.

Where it falls short: The mobile SDK is not in Starter. Confirm each feature by tier before you commit.

Verdict: Good if you want published numbers and web plus mobile in one contract. Budget for Growth if mobile is the reason you are buying.

3. Pendo

Best for: Product organizations that want analytics, session replay and in-app guides in one platform, starting from a free tier.

Who draws the UI: Pendo. Guides are built without code and delivered through the SDK. The mobile SDK covers iOS, Android, React Native, Flutter, SwiftUI, Jetpack Compose, MAUI and Compose Multiplatform, and the vendor says supported capabilities vary by framework. Check the framework page for your stack before you assume a tooltip works the same as on web.

Pricing: The free plan covers up to 500 monthly active users and includes analytics, in-app guides, NPS surveys and unlimited web and mobile app keys. Going over 500 MAU blocks creating new guides, NPS surveys or segments until you upgrade. The paid tiers, Base, Core and Ultimate, are contact-sales only, and session replay, discovery, sentiment and orchestration are add-ons. A 30-day free trial of the full platform is available through sales.

Strengths: It is the only tool in this group with a free tier that covers both web and mobile guides, and analytics sit in the same product.

Where it falls short: Paid pricing is hidden and modular, so the bill grows with add-ons. It is a larger platform than a team that wants one onboarding flow needs.

Verdict: A strong pick when analytics and guides belong in one place and you can start free. Expect the bill to grow as you add modules.

4. Chameleon

Best for: Web SaaS teams that want no-code tours, checklists, tooltips and surveys, and are not planning native mobile apps.

Who draws the UI: Chameleon. Its pricing page lists product tours, embeddables, microsurveys, checklists, tooltips and modals as in-app experiences, built in a browser extension.

Surfaces: Web and mobile web. The help center says Chameleon "does not support native mobile apps but fully supports mobile web applications." Experiences are turned off for browser widths under 720px until you enable mobile display under Governance, then Controls.

Pricing: There is no free plan. The Startup plan starts at $279 for 2,000 monthly tracked users (MTUs) and includes 10 live experiences. Pro starts at $750 a month for 5,000 MTUs with up to 20 live experiences. Growth starts at $1,250 a month for 5,000 MTUs, billed annually, with unlimited live experiences. Enterprise is custom. The pricing page offers a 14-day trial with no card, though a demo modal elsewhere on the page mentions a 30-day trial, so ask which applies.

Strengths: A clean web experience for onboarding and in-app guidance, with the same experience types across tiers.

Where it falls short: No native iOS, Android, React Native or Flutter SDK. Live experience caps on the lower tiers matter once you run a full onboarding program.

Verdict: A good web-only purchase. If React Native or Flutter screens are on the roadmap, pick a tool from the mobile column instead.

Lifecycle in-app messages

5. Braze

Best for: Large consumer and enterprise programs that run cross-channel journeys and want in-app messages and content cards inside the same orchestration as email, push, SMS and WhatsApp.

Who draws the UI: Braze for in-app messages. Braze has four in-app message types, slideup, modal, full and HTML full, and its SDKs display them with Braze-built templates on web, iOS, Android, React Native and Flutter. Content cards are a feed the SDK delivers. You can use the default UI or build your own and log impressions yourself. Braze's docs now point banner-style use cases to Banners, with a migration guide from content cards.

Surfaces: Web, iOS, Android, React Native and Flutter, with content cards also documented for Unity, Cordova, .NET MAUI and tvOS.

Pricing: Not published. Editions are Braze Go, Select, Pro and Enterprise, priced by monthly active users with a profile allowance, plus a shared pool of Action Credits for messaging. Braze's own example is one credit for an SMS and five for a WhatsApp message. There is no free tier, but there is a free trial.

Strengths: The deepest channel set in this list and a mature SDK family across web and mobile.

Where it falls short: Quote-only pricing and a credit model make costs hard to forecast. It takes engineering and a team to run. For a small SaaS that wants one welcome modal, it is more platform than the job needs.

Verdict: The enterprise default when in-app is one channel among many and you have the team to run it. Compare it with Braze alternatives before you commit to the credit model.

6. Customer.io

Best for: Product and lifecycle teams that want modal and inline in-app messages next to email and push, on one event-based stack.

Who draws the UI: Customer.io. You design messages in its editor and the SDK renders them. Inline messages need a place in your layout, such as an InlineInAppMessageView on Android or the InlineInAppMessage composable in Jetpack Compose. On web you add a JavaScript snippet, and for inline messages an empty element with an id.

Formats: Modal (top, center or bottom, over an overlay), inline (part of the page), and overlay, which works on websites only. Customer.io's docs do not list a full-screen type. Banner-style messages are built as a top or bottom modal or as inline. Multi-step messages can change display from one step to the next.

Surfaces: Web through a snippet, plus iOS, Android, React Native, Expo and Flutter SDKs.

Pricing: Essentials starts at $100 a month, billed monthly, for 5,000 profiles, with extra profiles at $0.009 each as overages. It includes 2 object types, 2 workspaces and 1M emails a month. Premium starts at $1,000 a month, billed yearly, with custom profile volume. Enterprise is sales-led. Push and in-app are unlimited on all plans, and extra email costs $0.12 per 1,000 on every plan. Startups that have raised under $10M can get a year free through the startup program. There is no free plan.

Strengths: Unlimited push and in-app on all listed plans, a clear entry price and an event model that works well with email.

Where it falls short: No free plan, Premium is billed yearly only, and the formats are modal and inline rather than a full product-tour builder. Profiles include objects, so the count can rise faster than your users.

Verdict: A good fit when you already run Customer.io for email and want in-app next to it. Compare it with Customer.io alternatives if you are weighing a change.

7. OneSignal

Best for: Mobile apps that want push and in-app messages on a free start, with a drag-and-drop editor.

Who draws the UI: OneSignal. You design messages in a drag-and-drop block editor or an HTML editor, and the SDK shows them. There are four layouts: top, which slides down; center, which expands from the middle; bottom, which slides up; and full, which fills the screen for onboarding, multi-step offers and carousels. Carousels use the full layout and support up to 10 cards.

Surfaces: Mobile only. OneSignal's FAQ says in-app messages are available only for mobile apps with the OneSignal mobile SDK installed. The mobile SDK reference covers Android, iOS, Unity, React Native, Flutter and Cordova or Ionic. Its four triggers are on app open, session duration, time since the last message, and custom triggers set with the SDK.

Pricing: The Free plan is $0 and covers mobile push up to 1,000 monthly active users, with in-app messages unlimited under the same cap. Growth starts at $19 a month plus usage, at $0.012 per MAU for mobile push, and includes unlimited in-app messages with mobile push. Professional and Enterprise are custom, on annual contracts.

Strengths: A free start that includes in-app, carousels, four layouts and four triggers.

Where it falls short: It is mobile only, so it does nothing for your website. Messages are fetched at the start of a session, so a user has to be in the segment before the session begins.

Verdict: Good for a mobile-first product where push is the main job and in-app is second. Compare it with OneSignal alternatives once your MAU grows past the free cap.

8. Intercom

Best for: Support teams that already run Intercom's inbox and want in-app chats and posts next to it.

Who draws the UI: Intercom. Its Messenger and in-app formats are built in Intercom and rendered by its web and native SDKs. On iOS and Android, the native SDKs support chats, posts in small and large formats, push notifications and mobile carousels.

Surfaces: The web Messenger, plus native iOS and Android SDKs. Banners show only in the web Messenger. Native apps do not render them, and Intercom's workaround is a Contacts Banners API that is still labeled as a preview.

Pricing: Essential is $29 per seat a month, Advanced is $85 and Expert is $132, all shown billed annually. Fin AI Agent starts at $0.99 per outcome. In-app chats, banners and tooltips are on every plan. Posts, checklists, product tours, surveys and the Series campaign builder sit behind Proactive Support Plus, an add-on at $99 a month that includes 500 messages. There is no free plan, but there is a 14-day trial with no card.

Strengths: The best fit if support conversations are the job, with in-app chat next to the inbox your team already uses.

Where it falls short: Seat pricing grows with the team, in-app tours and posts require an add-on, and banners do not render natively on mobile. It is not built as a lifecycle campaign tool for non-support teams.

Verdict: Good when your support team owns the conversation. Less useful as a first onboarding tool. Compare it with Intercom alternatives if you only need the in-app piece.

9. Sequenzy

Best for: SaaS, app and online-store teams that already run email sequences and want in-app messages, content cards, push and SMS as steps in the same builder.

Who draws the UI: Your app. Sequenzy sends in-app messages in modal, banner (top or bottom) and full-screen formats, plus content cards that stay in the app's feed until dismissed or expired, with pinning. Your app renders them with its own components and reports displayed, clicked, dismissed and read events, which feed the step stats in the sequence.

Surfaces: iOS through Swift Package Manager, Android through the sequenzy-android package, React Native as plain TypeScript that runs in Expo Go, and Flutter. The React Native SDK takes its push token from expo-notifications or React Native Firebase, and the Flutter SDK takes it from firebase_messaging. Web apps fetch the in-app feed from the browser or from a backend and draw it with their own code.

Orchestration: In-app messages are a "Show In-App" step inside the same sequence as your email steps. You can branch on tags, lists, segments, events, clicked links and fields, wait for an event with a timeout path, stop on a later event, run A/B test steps that pick a winner, and set delays, plus a local-time sending window for email steps.

Pricing: Billing is by emails sent, with unlimited contacts. The Free plan includes 2,500 emails a month. Paid plans start at $19 a month for 15,000 emails and go up to $349 a month for 1.2 million. Push and in-app are unlimited on every plan, including Free, and do not use email credits. The SMS add-on starts at $16 a month for 1,000 credits and sends to US and Canada numbers only.

Strengths: One builder for email, push, in-app and SMS. In-app is unlimited, the branching and A/B testing match the email side, and contacts are not billed.

Where it falls short: It is not a product tour builder, and it does not provide product tours or walkthroughs. It does not give you a finished notification bell, so your team builds the feed screen. There is no WhatsApp, and the ecosystem is smaller than Braze or Iterable.

Verdict: Pick Sequenzy when in-app is one step in an email-led lifecycle and your engineers will draw one or two screens. Pick something else for product tours or a turnkey bell icon. Read the mobile SDK docs and the in-app message docs before you scope the build.

Notification feeds and inboxes

10. Knock

Best for: Product teams that want an in-app notification center on several surfaces, with the workflows running on their backend.

Who draws the UI: Knock ships pre-built components for React on the web, plus feed views for React Native, iOS and Android. You can override how a notification cell renders, or go headless and build the UI on the feed API and real-time service.

Surfaces: React for web, React Native, Swift for iOS and macOS, Kotlin for Android, and Flutter. Each SDK fetches feed items, sets seen, read and archived status, and connects to Knock's real-time service.

Feed behavior: Feeds return newest first, with no way to change the order. Knock does not let you pin messages, so a pinned list needs several feeds and filtering. Knock creates one in-app channel by default.

Pricing: The Developer plan is $0 a month, with 10K messages, 500 guide active users and 500 AI agent credits, and no hard cap on notifications. Starter is $250 a month, with 50K messages and then $0.005 per message. Enterprise is quoted. Workflows and triggers are unlimited on all plans, and Knock bills messages sent, not workflows triggered. The pricing page mentions no trial, only a "get started for free" button.

Strengths: The widest set of native surfaces in this group, with unlimited workflows and billing tied to what you send.

Where it falls short: No pinning, and the Starter price is steep for a small app. It is a notification center, not a tour builder, so onboarding flows need a separate tool.

Verdict: Good when a notification center on web and mobile is the job and your backend owns the logic. Compare it with Knock alternatives if the Starter price is the sticking point.

11. MagicBell

Best for: Web products that want a notification inbox and push from one vendor, priced by deliveries.

Who draws the UI: MagicBell on web. The @magicbell/react package ships an Inbox and a FloatingInbox that need a user JWT, which your server generates. In React Native, MagicBell's own example builds the inbox from plain components. The headless package, @magicbell/react-headless, is deprecated and ships no UI.

Surfaces: React on web, and push delivered through APNs and FCM. MagicBell's mobile example is React Native built with Expo. Native iOS and Android apps build their own inbox UI on its APIs.

Pricing: Builder is $0 a month for 1,000 deliveries, one project, unlimited users and all integrations. Startup is $249 a month for 50,000 deliveries, with overage at $0.0025 per delivery, five projects and $99 per additional project. Enterprise is custom. Deliveries count per channel. No trial is mentioned on the pricing page.

Strengths: A free tier with unlimited users, a web inbox component and push from the same vendor.

Where it falls short: Per-channel delivery counting makes multi-channel sends cost more than you expect. The React Native inbox is a build-it-yourself job.

Verdict: Good when a web inbox and push are the job and you are comfortable with the per-delivery bill. Compare it with MagicBell alternatives if the per-channel meter is a problem.

12. Novu

Best for: Developer teams that want a notification workflow engine, a drop-in web inbox and the option to self-host.

Who draws the UI: Novu on web. The @novu/react package includes a drop-in Inbox component with a bell icon, feed and preferences, and @novu/nextjs covers Next.js. It also has headless hooks such as useNotifications for custom UI. On React Native, @novu/react-native gives you hooks only, with no prebuilt Inbox.

Surfaces: React and Next.js on web, and React Native through hooks. Novu has no native Swift or Kotlin client SDK and no Flutter SDK. For those, call the Inbox REST API and build the screen yourself, and send push through FCM and APNs from Novu's backend.

Pricing: Free is $0 a month for 10,000 workflow runs, up to 20 workflows, two environments, three team members and every channel, including in-app. Pro starts at $30 a month for 30,000 runs, with overage at $1.20 per 1K. Team starts at $250 a month for 250,000 runs. Enterprise is custom and includes self-hosting, SSO and a HIPAA BAA. No trial is mentioned on paid plans.

Strengths: A free tier that includes in-app, a web Inbox component that works out of the box, and self-hosting on Enterprise.

Where it falls short: No native mobile SDK, and React Native is hooks only. The free tier is capped at 20 workflows and three team members.

Verdict: Good for web and React Native teams that want an inbox component and can build mobile screens. Compare it with Novu alternatives if you need native iOS or Android.

How to choose

Start with the job, then the surface, then the meter.

• You want to teach people how the product works. Start in the tours group. Pick Userpilot if you want published starter pricing, Pendo if you want a free start with analytics, or Appcues if you need native mobile onboarding and can take a sales call. Pick Chameleon only if the product is web.
• You want to send campaigns with an in-app step. Start in the lifecycle group. Pick Braze at enterprise scale with a team to run it, Customer.io if email already runs there, OneSignal for a mobile-only app on a free start, and Sequenzy when in-app is one step in your email sequences.
• Your support team owns the conversation. Intercom is built for that, and it is the wrong purchase for a lifecycle team.
• You want a notification center. Start in the feeds group. Pick Knock for multi-surface feeds, MagicBell for a web inbox priced by delivery, and Novu for a developer-led workflow engine with a web component.
• Your product is web only. Drop OneSignal from the shortlist, since its in-app messages are mobile only. Chameleon, Userpilot, Pendo, Appcues and Customer.io cover the web surface well.
• Your product is native mobile. Confirm the SDK for your framework before anything else. Chameleon has no native SDK at all, so skip it, and Novu's native iOS and Android path is a REST API you build yourself.

Run the same test on every vendor. Load your real user count into the pricing page, write down the features that matter most, and ask for each one in writing. If the vendor cannot say which SDK covers your framework, the mobile part of the price is not real yet.

Related resources

• Best push notification services
• Best customer engagement platforms
• Best email and push notification platforms
• Best iOS Live Activities tools
• Best push notification services for React Native
• Best push notification services for Flutter
• Best lifecycle marketing email tools
• In-app messages in Sequenzy
• Mobile SDKs in Sequenzy