Channels

Eleven channels behind one subscriber model. Each is configured per app; you connect your own provider accounts and pay providers directly at cost — WingBlaze never marks up carrier or provider fees.

Channel	Device token	Setup
Mobile push (FCM)	FCM registration token	Upload the Firebase service-account JSON (Setup step or POST /apps/:id/credentials/fcm)
Mobile push (APNs)	APNs device token	Upload the .p8 key + key/team id + bundle topic
Web push	Push subscription	Automatic — VAPID keys are generated with the app
Email	Email address	Verified SES sender (PATCH /apps/:id/settings → emailFrom)
SMS	E.164 phone number	Your own Twilio account (POST /apps/:id/credentials/twilio) — carrier fees bill to you directly, never marked up
WhatsApp	E.164 phone number	Your WABA credentials (POST /apps/:id/credentials/whatsapp)
Telegram	Chat id via your bot	Bot token (POST /apps/:id/credentials/telegram) — works in campaigns, transactional sends and journeys
RCS	E.164 phone number	RBM agent service account + agent id (POST /apps/:id/credentials/rcs)
LINE	LINE userId via your Official Account	Channel access token (POST /apps/:id/credentials/line)
Zalo	Zalo user id via your Official Account	OA access token (POST /apps/:id/credentials/zalo)
Viber	Viber user id via your bot	Bot auth token + sender name (POST /apps/:id/credentials/viber)

Southeast-Asia channel map

Pick the rail your market actually uses: WhatsApp for Indonesia, Malaysia and Singapore; LINE for Thailand; Zalo for Vietnam; Viber alongside Messenger for the Philippines; Telegram as the low-cost overlay everywhere. All ride your own provider accounts at cost. Zalo note: OA access tokens expire (~25h) — automate the refresh against the credentials endpoint.

RCS specifics

Messages send as text with an Open suggested action when the message has a deepLink; messages with an imageUrl upgrade to a standalone rich card. Handsets that aren't RCS-capable prune automatically (like dead push tokens) — target SMS as the fallback. Your RBM agent must be approved by Google and carriers before live sends.

Delivery behavior (all channels)

• Exactly-once: a per-run send ledger plus worker dedupe means retried jobs never double-send.
• Dead tokens disable the device and surface as bounced events.
• Frequency caps & quiet hours (per app, subscriber-local) suppress campaign sends — never transactional ones.
• Webhooks: HMAC-signed delivery events to your endpoint, plus the integrations catalog.