You send one request containing the push and its fallback channels. SMSBAT delivers the push first and waits for the TTL you set. If no delivery confirmation arrives in that time, the next channel is sent — a Telegram bot, a Viber bot, Viber Business Messages or SMS, in the order you configured.
No, and that is deliberate. The app talks to Firebase Cloud Messaging directly and to our REST API for registration and status callbacks. You get the API contract, a Postman collection and an integration guide instead of a dependency that has to be upgraded with every release of your app.
Your app reports the delivered or seen status and the remaining cascade steps are cancelled, so the paid channels are never sent. This callback is what makes the cascade cheaper rather than more expensive.
Yes. Notifications are delivered under your own app, so you use your own Firebase project and your own APNs auth key. The push arrives from your brand, not from ours.
Messages are data-only by design, so the app has to render them — in the foreground and in the background handler. This is the single most common surprise during integration and it is covered step by step in the guide.
Then there is no registered installation for that user and the message goes straight to the first available fallback channel of the cascade.