Request a Demo
RU
RU

Push

We develop highly reliable mobile Push notification software. Notifications are sent directly via Android, iOS and Huawei services, 100% free for the customer.

Guaranteed delivery rate >90%.

Push notifications are sent to:

  • Android apps (version 4.4 and above) – via FCM (Firebase Cloud Messaging),
  • iOS apps (version 10 and above) – via APNS (Apple Push Notification service),
  • Android apps on HUAWEI devices via HUAWEI Push Kit.
Push is part of the Notification Server, so notifications that are not delivered as Push can be forwarded via any other channel, for example, Viber or SMS. This saves messaging costs significantly.

Saving messaging costs

Many companies that have their own mobile apps can send Push notifications but cannot save SMS messaging costs. The most common reasons are:

  • No centralized communication system, resulting in the inability to switch all messages to omnichannel delivery scenarios using Push messaging.
  • Low delivery rates, which significantly reduces savings. Maintaining a delivery rate requires a high degree of expertise in this area and ongoing work to account for the peculiarities of working with various devices and mobile OS innovations.
The Notification Server makes it easier for companies to cut their communication expenses by focusing on their core business.

The Notification Server delivers over 90% of Push notifications. We can guarantee an SLA on delivery rate.

Easy integration with mobile app

SDK
Our SDK (a set of libraries for easily embedding Push into a mobile application) already contains everything you need to properly handle Push notifications; we've applied the best practices improving service quality and delivery rates. The SDK also implements the user interface of the app section for viewing notification history. The SDK greatly eases the task of a mobile app developer, wiping out the need to learn about Push features.
API
The mobile app and the Notification Server communicate via Push API: registering apps, updating client data, transmitting delivery statuses, receiving additional content, etc. The Push API is used by the SDK to communicate with the server.

Enhanced security

All components are installed on the customer's premises. Messages and subscriber data do not pass through third-party servers.

Mobile app requests to the server are signed using a private key. The signature is verified on the server. This approach makes it impossible for an intruder to send requests on behalf of the user.

Push sending is done through secure protocols from Google and Apple.

There is an option whereby Push only notifies the app of a message, while the message itself is retrieved directly from the server. In this case, text messages do not pass through Google and Apple clouds.

Support for multiple devices from one customer

To fully utilize Push in omnichannel message delivery scenarios, a phone number is used as the customer identifier. In this case, the customer may have multiple devices. Push can be sent both to all the customer's devices at once or to a specific device.

rWhen push notification is enabled in new devices or the token changes in already enabled devices, the subscription data is updated on the server. This is easily done through our SDK.
  • Targeting
    Storage of arbitrary subscriber attributes on the server is supported. This data can be used to set up targeted sending through your personal dashboard.
  • Content delivery
    Messages can be sent to mobile apps either directly in the Push notification itself, or additionally requested by the app from the server after receiving the Push. Messages requested from the server have no size limitations and can contain data in any format, for example, HTML.
  • Delivery statuses
    The Notification Server provides not only Push delivery statuses to the device, but also notification read statuses.

    Delivery statuses are sent to the Notification Server even if the Android or iOS app was not running on the mobile device when Push was sent.

Compatible across various devices

Push delivery to different devices and with different OS versions has its own peculiarities. This is mostly the case with Android devices from Chinese manufacturers. Without taking into account such features, Push delivery rate is markedly reduced and you end up saving just a little on SMS messaging costs.

We are constantly working on adapting the Notification Server and SDK to the characteristics of devices and operating system versions. This would ensure very high delivery rates and boost the level of service.

Enrichment of transactional push notifications

Messages about payments made with bank cardscan contain the logos of the payment beneficiaries and their names in Cyrillic. In the absence of a logo, the message contains the logo of the payment category (products, gas stations, etc.).

This makes Push more attractive and informative for recipients.

WINGS provides a ready-made database of trade organizations' logos and is ready to provide a level of logo coverage for transactions in accordance with an SLA.

Notification history

Push SDK allows you to quickly build a notification history section in the customer's mobile app, which will be accessible even without Internet access. Having such notification history adds value to the Push channel for users. It also reduces the number of users who would disable Push notifications after a period of time.

With a ready-made library, you can deploy your Push notification significantly faster, thereby saving resources and time.

Deep linking

Push notifications can contain information telling the mobile app which section or page to open when the user clicks Push.

Interactive notifications

Push notifications can contain interactive buttons performing certain actions. Having such elements motivates users towards performing their desired actions and it increases response rate.