**Experience Hub > Mobile Push > Create new**.
2. Enter the name of the push notification (it is only visible on the list of notifications).
3. Select one of the notification types:
- **Simple push**
- **Silent push**
### Select device type
---
In this part of the process, you will declare the operating system of devices which will receive the notifications.
1. On the **Device type** section, click **Define**.
2. Select one of the following tabs:
- **Android** - The push notification will be delivered only to Android devices.
- **iOS** - The push notification will be delivered only to iOS devices.
- **All** - The push notification is will be delivered to devices with any kind of operating system.
Batch delivery - It prevents sending notifications to all recipients at once.
If you plan to send messages to an audience larger than 15,000 profiles, we recommend this option.
For example, if the expected performance of your messaging provider is 1 million messages per hour and the expected audience is 5 million profiles, you can split the communication into 60 batches sent 5 minutes apart: every batch will include ~83000 profiles sending all messages will take 5 hours.
If you send a large number of messages all at once, there is a chance that your application may experience a sudden increase in traffic. To prevent any issues, make sure your application is fully prepared to handle this potentially significant surge in traffic. If a batch takes more than 8 hours to complete for any reason, it is cancelled in Synerise.
Send to all devices - This option lets you send a message to all devices used by a customer. It's unselected by default. If this option remains unselected, the message will be sent to the customer's most recently active device only.
Enable control group - It creates a subgroup of the recipients who won't receive any push notification variant. When to use it? When you send one or several variants of a notification (A/B testing). When a customer is assigned to their control group, the information is available in their Profiles card as an event.
Send without marketing agreement check - To comply with GDPR resolutions, Synerise by default filters out the recipients with marketing agreement off. This option, however, allows to send push notifications to those whose marketing agreement is off (after ticking this option, the number in the estimated reach don't refresh). When to use it? While sending messages that don't contain marketing content, for example, information about delays in shipping.
Include audience changes - Available only for scheduled notifications. It recalculates the number of recipients right before sending the message. By default, the size of the customer segmentation chosen for the push notification is the same as in the moment of sending, even if the number of customers in the chosen segment changed between scheduling the notification and sending. When to use it? When the size of the segments of customers selected as the audience of the notification can change dynamically.
Ignore limits - If you want to make sure that this message is sent to a customer, even it exceeds the global limit of this type of messages for a single customer per day (more information is available here), enable the Ignore limits toggle. You may apply it to system messages such as a transaction confirmation, notifications about order delays, and so on.
.
2. To create or select a ready template, click **Create message**.
- To select a ready template, from the template library select a template. Then you will be directed to the builder in which you can make changes to the template, to use it in the campaign, click **Use in communication**. If you use [Approval Service](/docs/settings/configuration/service-approval), click **Send to approval**.
- To create a new template, in the upper right corner, click **New template**.
1. Select the builder in which you will create a template:
- [See instruction on creating a template in the Visual builder](/docs/campaign/Mobile/creating-mobile-push-templates/mobile-push-visual-builder)
- [See instruction on creating a template in the Code builder](/docs/campaign/Mobile/creating-mobile-push-templates/mobile-push-code-editor)
2. Once the template is ready, click **Use in communication**. If you use [Approval Service](/docs/settings/configuration/service-approval), click **Send to approval**.
### Schedule the notification
---
In this part of the process, you will define when the push notification will be sent.
1. In the **Schedule** section, click **Define**.
1. You can choose between two options:
- To send your notification after clicking the **Send** button on the upper right corner, use the **Display immediately** option.
The notification display is dependent on the [priority](/docs/campaign/Mobile/creating-mobile-push-templates/mobile-push-visual-builder#defining-notification-priority) and/or [content-available option](/docs/campaign/Mobile/creating-mobile-push-templates/mobile-push-visual-builder#enabling-content-available-option) defined in the template, so the display of the notification may not be immediate.
- To plan a message to be sent at a future date, use the **Scheduled** option. Set the start time and the time zone.
Synerise performs best with real-time data. This is why you can't schedule a message for more than 10 days in the future.
To select the best time of sending the message, take a look at the suggestion from the AI engine that calculates the best time (for all recipients). If time optimization is disabled, click [here](/docs/settings/configuration/time-optimizer) to learn more how to enable it and use it.
2. Select the **Silence Hours** setting:
- **Without silence hours** - The communication can be processed and sent out to the recipients at any time during the day.
- **Include silence hours** - With this option, you can set a time of day when the communication can't be sent:
1. In the **From** field, select when the silence hours start.
2. In the **To** field, select when the silence hours end.
The period can't be longer than 12 hours.
When a message can't be sent due to silence hours, a `push.skipped` event is generated.
{
"action": ...
...
"params": {
"clientId": 1111111111,
"season": "autumn",
"campaignName": "Back to school",
"time": 1662392318050,
"title": "Have you prepared for coming back to school?",
"businessProfileId": "xxx"
}
}