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


Channel comparison

ChannelDeveloper required?Setup timeBest for
EmailNo15–60 minMarketing campaigns, transactional messages, newsletters
SMSNo15–60 minTime-sensitive alerts, OTPs, appointment reminders
Web pushYes15–45 minRe-engaging website visitors, announcements
Mobile pushYes30–60 minApp re-engagement, real-time alerts, promotions
In-app messagesYes (SDK)30–45 minOnboarding, feature announcements, surveys
RCSNoVariesRich branded messaging on Android with read receipts
Live ActivitiesYes (SDK)45–60 minLive scores, delivery tracking, event countdowns

Next steps

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

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.