Skip to main content
OneSignal supports multiple messaging channels, each with different capabilities and setup requirements. Choose the channels that match your goals, or combine several to build a multi-channel experience with Journeys.
Email and SMS can be configured without a developer. Push notifications, in-app messages, and Live Activities require SDK integration — see the Developer guide or invite a developer to your team.

​
Messaging channels

Mobile push

Alert-style notifications on iOS, Android, Huawei, and Amazon — even when the app isn’t open.

Web push

Browser-based notifications that reach Users even when your site isn’t open.

Email

Marketing and transactional emails with built-in deliverability tools.

In-app messages

Rich, interactive messages displayed while Users are active in your app.

SMS

Direct text messages for urgent or time-sensitive communication.

RCS

Rich messaging with branded content and read receipts on Android.

Live Activities

Real-time updates on the iOS lock screen. Similar capabilities available for Android.

​
Channel comparison

​
Next steps

After setting up a channel, continue with the rest of your OneSignal implementation.

Quickstart guide

Full implementation walkthrough: Users, segments, sending messages, and analytics.

Developer guide

SDK reference, API docs, User identity, and testing for engineering teams.

Send messages

Compose and send your first message after setting up a channel.

Journeys

Automate multi-channel flows based on User behavior.

​
FAQ

​
Which channel should I set up first?

Start with the channel that matches your most immediate goal. Email and SMS are the fastest to configure and don’t require a developer. If you already have a mobile app, push notifications provide the highest visibility for re-engagement.

​
Can I use multiple channels in the same OneSignal app?

Yes. A single OneSignal app supports all channels. Adding multiple channels lets you use Journeys to automate multi-channel flows — for example, sending a push notification, then following up with an email if the User doesn’t engage.

​
Do I need separate apps for testing and production?

Yes, this is strongly recommended. Use separate OneSignal apps for development, staging, and production to avoid sending test messages to real Users. See Apps, Organizations, and accounts for details.