messengerChat apps, SMS and push, with a reliability layer

One message model for SMS and RCS, WhatsApp, Messenger and Instagram, Telegram and Viber, Slack, Discord, Teams and Google Chat, and push, and on top of it what the other libraries leave to you: a persistent queue, an audit of every state, one model of delivery receipts, idempotency and fallback between channels. Zero dependencies.

Get Started

Why messenger?

Compared with alternatives

💬

Twelve channels, one message

SMS and RCS, WhatsApp, Messenger and Instagram, Telegram and Viber, Slack, Discord, Teams and Google Chat, and push, through the HTTP APIs of their providers without their SDKs — including the Ukrainian SMS and Viber providers no other library has.

The channels

🧾

A reliability layer

A persistent queue and outbox, an audit of every state of a message, and one model of delivery receipts from webhooks that are verified before they are read.

The comparison

🔁

Fallback that knows what happened

WhatsApp, then SMS if it was not delivered in time; never a second one-time code after a send of unknown outcome. Idempotency keys, errors classified as permanent or temporary.

The design

🪶

Zero dependencies

Built on node:* modules and fetch, for Node.js 22+, Bun and Deno. A queue or a database driver is passed in by your application. CommonJS with ESM named imports and hand-written typings.

API

Work in progress

The library is being designed: the features above are what it is built to do, not what the published package does yet. See Why @alexify/messenger? for the plan.