Skip to main content
Choose the channels that match your goals, then start sending or combine them with Journeys to reach users wherever they respond. Each channel has different capabilities and setup requirements.
Email and SMS can be configured without a developer. Email needs access to your domain’s DNS settings, and SMS needs an approved sender. Push notifications, in-app messages, and Live Activities require SDK integration. See the Developer guide or invite a developer to your team.

​
Messaging channels

Email

Marketing and transactional emails with built-in deliverability tools.

Mobile push

Push notifications on iOS, Android, Huawei, and Amazon, even when the app isn’t open.

Web push

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

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

Branded, rich messages with read receipts. Falls back to SMS when the device or carrier doesn’t support RCS.

Live Activities

Real-time updates on the iOS Lock Screen and Dynamic Island. For Android, build a similar experience with Live Updates.

​
Channel comparison

Start SMS and RCS sender registration well before your launch date. You can’t send SMS or RCS to users until carriers approve your sender. See Sender resource applications for timelines by country.

​
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 push notifications

Compose and send your first push notification.

Send emails

Send marketing and transactional emails from the dashboard, Journeys, or the API.

Send SMS

Send SMS, MMS, and RCS messages and choose the right texting program.

Journeys

Automate multi-channel flows based on User behavior.

Push fallback to email or SMS

Deliver critical messages by email or SMS when push notifications fail.

Transactional messages

Send OTPs, billing updates, and reminders through push, email, or SMS with the API.

​
FAQ

​
Which channel should I set up first?

Start with the channel that matches your most immediate goal. Email is usually the fastest to launch without a developer, as long as you can update your domain’s DNS settings. SMS also doesn’t require a developer, but you can’t send until your sender is approved, so start registration early. 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, send a push notification, then follow 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 separate environments, such as development, staging, and production. Each app has its own App ID, Users, and messages, so test sends and test data never reach your production Users. See Apps, Organizations, and accounts for details.