sently 0.9.2 → 0.10.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sently",
-  "version": "0.9.2",
+  "version": "0.10.0",
   "description": "Runtime-agnostic messaging library for Node.js, Bun, Deno, and Cloudflare Workers. Channel-first email, SMS, WhatsApp, and push with pluggable provider transports.",
   "type": "module",
   "sideEffects": false,
@@ -207,6 +207,10 @@
       "import": "./dist/transports/msegat.js",
       "types": "./dist/transports/msegat.d.ts"
     },
+    "./transports/unifonic": {
+      "import": "./dist/transports/unifonic.js",
+      "types": "./dist/transports/unifonic.d.ts"
+    },
     "./transports/whatsapp-cloud": {
       "import": "./dist/transports/whatsapp-cloud.js",
       "types": "./dist/transports/whatsapp-cloud.d.ts"
@@ -215,6 +219,14 @@
       "import": "./dist/transports/webpush.js",
       "types": "./dist/transports/webpush.d.ts"
     },
+    "./transports/fcm": {
+      "import": "./dist/transports/fcm.js",
+      "types": "./dist/transports/fcm.d.ts"
+    },
+    "./channel-result": {
+      "import": "./dist/channel-result.js",
+      "types": "./dist/channel-result.d.ts"
+    },
     "./observability": {
       "import": "./dist/observability/console.js",
       "types": "./dist/observability/console.d.ts"
@@ -295,6 +307,18 @@
       "import": "./dist/webhooks/sndr.js",
       "types": "./dist/webhooks/sndr.d.ts"
     },
+    "./webhooks/twilio-sms": {
+      "import": "./dist/webhooks/twilio-sms.js",
+      "types": "./dist/webhooks/twilio-sms.d.ts"
+    },
+    "./webhooks/whatsapp-cloud": {
+      "import": "./dist/webhooks/whatsapp-cloud.js",
+      "types": "./dist/webhooks/whatsapp-cloud.d.ts"
+    },
+    "./webhooks/unifonic": {
+      "import": "./dist/webhooks/unifonic.js",
+      "types": "./dist/webhooks/unifonic.d.ts"
+    },
     "./errors": {
       "import": "./dist/errors.js",
       "types": "./dist/errors.d.ts"

package/site/content/docs/channels/hooks.mdx

@@ -50,21 +50,22 @@ await mailer.send({
 | Channel | Callbacks | Context |
 | --- | --- | --- |
 | Email | `onSend`, `onSuccess`, `onError`, `onRetry`, `onFallback` | `messageId`, recipients, subject, provider. |
-| SMS | `onSend`, `onSuccess`, `onError` | `messageId`, recipient number, provider. |
-| WhatsApp | `onSend`, `onSuccess`, `onError` | `messageId`, recipient number, provider. |
-| Push | `onSend`, `onSuccess`, `onError` | `messageId`, redacted endpoint, provider. |
+| SMS | `onSend`, `onSuccess`, `onError`, `onRetry`, `onFallback` | `messageId`, recipient number, provider. |
+| WhatsApp | `onSend`, `onSuccess`, `onError`, `onRetry`, `onFallback` | `messageId`, recipient number, provider. |
+| Push | `onSend`, `onSuccess`, `onError`, `onRetry`, `onFallback` | `messageId`, redacted endpoint / FCM token fingerprint, provider. |
 
 `onSuccess` receives the delivery result and optional duration in milliseconds. `onError` receives the error and optional duration.
 
 ## Retry and fallback
 
-Email `onRetry` runs only with `RetryTransport`. Email `onFallback` runs only with a fallback transport; both are configured as decorators around an email transport.
+`onRetry` runs only with `RetryTransport`. `onFallback` runs only with a fallback (or weighted fallback) transport.
+Wire either decorator around the channel transport you pass to `createMailer`, `createSmsSender`, `createWhatsAppSender`, or `createPushSender`.
 
 ## Troubleshooting
 
 <Accordions>
   <Accordion title="Why does onRetry not run?">
-    `onRetry` is wired only when the mailer's transport is `RetryTransport`.
+    `onRetry` is wired only when the sender's transport is `RetryTransport`.
   </Accordion>
   <Accordion title="Why does my hook error not stop the send?">
     Hook failures are intentionally swallowed so observability code cannot break message delivery.

package/site/content/docs/channels/index.mdx

@@ -18,7 +18,7 @@ Each sender accepts a provider transport, so delivery providers can change witho
 | Email | `createMailer` or `createSMTPMailer` | Sender, recipient, subject, and body. |
 | SMS | `createSmsSender` | Recipient number and body. |
 | WhatsApp | `createWhatsAppSender` | Template or text message. |
-| Push | `createPushSender` | Browser subscription, title, and body. |
+| Push | `createPushSender` | Web Push subscription or FCM token, plus title and body. |
 
   </Step>
   <Step title="Wire in a transport">
@@ -52,7 +52,7 @@ await sms.send({
 | `createSMTPMailer` | Yes | Email configured with SMTP host, port, and authentication. |
 | `createSmsSender` | No | SMS with an `SmsTransport`. |
 | `createWhatsAppSender` | No | WhatsApp with a `WhatsAppTransport`. |
-| `createPushSender` | No | Web Push with a `PushTransport`. |
+| `createPushSender` | No | Web Push or FCM with a `PushTransport`. |
 
 ## Troubleshooting
 

package/site/content/docs/channels/push.mdx

@@ -1,14 +1,16 @@
 ---
 title: Push
-description: Send encrypted Web Push notifications through a push transport.
+description: Send Web Push or FCM notifications through a push transport.
 icon: Bell
 source: "src/push.ts"
 ---
 
-Use Web Push for browser notifications after a browser has granted permission and returned a subscription.
-The sender passes the subscription and notification payload to a push transport.
+Use push for browser Web Push subscriptions or FCM device tokens.
+The sender passes the target and notification payload to a push transport.
 
-<Callout title="The one rule">Treat subscription endpoints as secrets: they are long-lived delivery tokens.</Callout>
+<Callout title="The one rule">Treat subscription endpoints and device tokens as secrets — they are long-lived delivery credentials.</Callout>
+
+## Quick start
 
 <Steps>
   <Step title="Create a Push sender">
@@ -27,10 +29,11 @@ const push = createPushSender({
 ```
 
   </Step>
-  <Step title="Send to a stored browser subscription">
+  <Step title="Send to a browser subscription or FCM token">
 
 ```ts
-const result = await push.send({
+// Web Push
+await push.send({
   subscription: {
     endpoint: "https://fcm.googleapis.com/fcm/send/example",
     keys: { p256dh: "browser-public-key", auth: "browser-auth-secret" },
@@ -39,7 +42,12 @@ const result = await push.send({
   body: "Your weekly report is ready to view.",
 });
 
-console.log(result.status);
+// FCM (with FcmTransport)
+await push.send({
+  token: deviceRegistrationToken,
+  title: "Report ready",
+  body: "Your weekly report is ready to view.",
+});
 ```
 
   </Step>
@@ -53,15 +61,16 @@ console.log(result.status);
 | `plugins` | `PushPlugin[]` | Optional transforms run before delivery. |
 | `hooks` | `PushHooks` | Optional callbacks for delivery activity. |
 
-## Push and VAPID options
+## Options shapes
 
-| Option | Type | Meaning |
+`PushOptions` is a union:
+
+| Shape | Required target | Transport |
 | --- | --- | --- |
-| `subscription` | `PushSubscription` | Required browser endpoint plus `p256dh` and `auth` keys. |
-| `title`, `body` | `string` | Required notification content. |
-| `data`, `icon` | `Record<string, unknown>`, `string` | Optional application payload and icon URL. |
-| `ttl` | `number` | Optional delivery lifetime in seconds. |
-| `subject` | `string` | Required Web Push contact URI for the VAPID transport. |
+| Web Push | `subscription` | `WebPushTransport` |
+| FCM | `token` | `FcmTransport` |
+
+Shared fields: `title`, `body`, optional `data`, `icon`, `ttl`, `messageId`.
 
 ## Troubleshooting
 
@@ -70,23 +79,20 @@ console.log(result.status);
     Web Push validates subscription endpoint hosts before sending. Add only exact private relay hostnames with `allowedEndpointHosts` when needed.
   </Accordion>
   <Accordion title="Why is the endpoint redacted in hooks?">
-    The endpoint path can contain a long-lived delivery token, so hook context keeps only a redacted form.
-  </Accordion>
-  <Accordion title="What does verify do?">
-    `push.verify()` delegates to the transport when available; the Web Push transport checks its VAPID credential shape.
+    Endpoint paths and FCM tokens are long-lived credentials, so hook context keeps only a redacted fingerprint.
   </Accordion>
 </Accordions>
 
 ## Learn more
 
 - [Push options](../reference/push-options)
-- [Transport contracts](../reference/transport-contracts)
-- [Web Push interoperability](../guides/webpush-interop)
+- [Web Push](../transports/webpush)
+- [FCM](../transports/fcm)
 - [Hooks](./hooks)
 
 ## Next
 
 <Cards>
   <Card title="Web Push transport" href="/docs/transports/webpush" />
-  <Card title="All transports" href="/docs/transports" />
+  <Card title="FCM transport" href="/docs/transports/fcm" />
 </Cards>

package/site/content/docs/channels/sms.mdx

@@ -77,12 +77,15 @@ Twilio also accepts a default `from` or `messagingServiceSid` when you construct
 ## Learn more
 
 - [SMS options](../reference/sms-options)
-- [Transport contracts](../reference/transport-contracts)
+- [Unifonic](../transports/unifonic)
+- [Decorators](../decorators) — retry / fallback across SMS providers
+- [Channel send result](../reference/channel-result)
 - [Hooks](./hooks)
 
 ## Next
 
 <Cards>
+  <Card title="Unifonic" href="/docs/transports/unifonic" />
   <Card title="SMS transports" href="/docs/transports" />
   <Card title="Provider OTP extras" href="/docs/guides/vendor-extras-otp" />
 </Cards>

package/site/content/docs/decorators/fallback.mdx

@@ -1,34 +1,61 @@
 ---
 title: Fallback
-description: Fail over across ordered email transports.
+description: Fail over through an ordered list of channel transports.
 icon: GitBranch
 source: "src/transports/fallback.ts"
 ---
 
-Fail over across ordered email transports.
+Fail over through an ordered list of transports when the current one errors.
+Works with email, SMS, WhatsApp, and push.
 
-<Callout title="The one rule">Permanent client errors do not fall through by default.</Callout>
+<Callout title="The one rule">Wrap each entry in `RetryTransport` when you want in-provider retries before failover.</Callout>
 
-## Configuration
+## Quick start
 
-Pass a non-empty transport array; options include `shouldFallback`, `onFallback`, and `cooldownMs`.
-
-<Steps><Step title="Wrap an email transport">
+<Steps>
+  <Step title="Build a chain">
 
 ```ts
 import { FallbackTransport } from "sently/transports/fallback";
-
-const transport = new FallbackTransport([primary, secondary], { cooldownMs: 300_000 });
+import { TaqnyatSmsTransport } from "sently/transports/taqnyat-sms";
+import { UnifonicTransport } from "sently/transports/unifonic";
+
+const transport = new FallbackTransport(
+  [
+    new TaqnyatSmsTransport({ bearerToken: process.env.TAQNYAT_TOKEN!, sender: "MyBrand" }),
+    new UnifonicTransport({ appSid: process.env.UNIFONIC_APPSID!, senderId: "MyBrand" }),
+  ],
+  { cooldownMs: 300_000 },
+);
 ```
 
-</Step><Step title="Create the mailer">
+  </Step>
+  <Step title="Use the matching sender">
 
 ```ts
-const mailer = await createMailer({ transport });
+import { createSmsSender } from "sently/sms";
+
+const sms = createSmsSender({ transport });
 ```
 
-</Step></Steps>
+  </Step>
+</Steps>
+
+## Result fields
+
+Successful sends include `provider` and `providerIndex` for the transport that handled the message.
+
+## Troubleshooting
+
+<Accordions>
+  <Accordion title="Why did it not fail over on 400?">
+    Permanent client errors (400 / 401 / 403) do not fail over by default — they usually fail on every provider.
+  </Accordion>
+</Accordions>
 
-<Accordions><Accordion title="Does this replace the inner provider?">No. It delegates sends to the wrapped transport.</Accordion></Accordions>
+## Next
 
-<Cards><Card title="Email channel" href="/docs/channels/email" /></Cards>
+<Cards>
+  <Card title="Weighted fallback" href="/docs/decorators/weighted-fallback" />
+  <Card title="Retry" href="/docs/decorators/retry" />
+</Cards>

package/site/content/docs/decorators/index.mdx

@@ -1,25 +1,27 @@
 ---
 title: Decorators
-description: Wrap an email transport with retry, fallback, preview, or idempotency.
+description: Wrap any channel transport with retry, fallback, preview, or idempotency.
 icon: Layers
 source: "src/transports/retry.ts"
 ---
 
-Decorators wrap another email transport. The mailer still calls `send` the same way — only the transport path changes.
+Decorators wrap another transport. The channel sender still calls `send` the same way — only the transport path changes.
+Retry, fallback, and weighted fallback work for email, SMS, WhatsApp, and push.
+Preview and idempotency remain email-oriented.
 
-<Callout title="The one rule">Pass the outermost decorator to `createMailer`. Inner transports stay providers (or other decorators).</Callout>
+<Callout title="The one rule">Pass the outermost decorator to the matching channel sender (`createMailer`, `createSmsSender`, …).</Callout>
 
 ## Available decorators
 
-| Decorator | Import |
-| --- | --- |
-| [Preview](./preview) | `sently/transports/preview` |
-| [Retry](./retry) | `sently/transports/retry` |
-| [Fallback](./fallback) | `sently/transports/fallback` |
-| [Weighted fallback](./weighted-fallback) | `sently/transports/weighted-fallback` |
-| [Idempotency](./idempotency) | `sently/idempotency` |
+| Decorator | Import | Channels |
+| --- | --- | --- |
+| [Preview](./preview) | `sently/transports/preview` | Email |
+| [Retry](./retry) | `sently/transports/retry` | Email, SMS, WhatsApp, Push |
+| [Fallback](./fallback) | `sently/transports/fallback` | Email, SMS, WhatsApp, Push |
+| [Weighted fallback](./weighted-fallback) | `sently/transports/weighted-fallback` | Email, SMS, WhatsApp, Push |
+| [Idempotency](./idempotency) | `sently/idempotency` | Email |
 
-## Typical stack
+## Typical stack (email)
 
 ```ts
 import { createMailer } from "sently/mailer";
@@ -35,10 +37,25 @@ const transport = new FallbackTransport([
 const mailer = await createMailer({ transport });
 ```
 
+## Typical stack (SMS)
+
+```ts
+import { createSmsSender } from "sently/sms";
+import { FallbackTransport } from "sently/transports/fallback";
+import { TaqnyatSmsTransport } from "sently/transports/taqnyat-sms";
+import { UnifonicTransport } from "sently/transports/unifonic";
+
+const sms = createSmsSender({
+  transport: new FallbackTransport([
+    new TaqnyatSmsTransport({ bearerToken: process.env.TAQNYAT_TOKEN!, sender: "MyBrand" }),
+    new UnifonicTransport({ appSid: process.env.UNIFONIC_APPSID!, senderId: "MyBrand" }),
+  ]),
+});
+```
+
 ## Learn more
 
 - [Transports](../transports)
-- [Email channel](../channels/email)
 - [Hooks](../channels/hooks)
 
 ## Next

package/site/content/docs/decorators/retry.mdx

@@ -1,11 +1,12 @@
 ---
 title: Retry
-description: Retry failed email sends with configurable backoff.
+description: Retry failed sends with configurable backoff on any channel transport.
 icon: RotateCw
 source: "src/transports/retry.ts"
 ---
 
-Retry failed email sends with configurable backoff.
+Retry failed sends with configurable backoff.
+Works with email, SMS, WhatsApp, and push transports.
 
 <Callout title="The one rule">Authentication errors are not retried.</Callout>
 
@@ -13,22 +14,44 @@ Retry failed email sends with configurable backoff.
 
 `maxAttempts`, `backoff`, `baseDelay`, `retryOn`, and `onRetry` are optional.
 
-<Steps><Step title="Wrap an email transport">
+## Quick start
+
+<Steps>
+  <Step title="Wrap a transport">
 
 ```ts
 import { RetryTransport } from "sently/transports/retry";
+import { TaqnyatSmsTransport } from "sently/transports/taqnyat-sms";
 
-const transport = new RetryTransport(new ResendTransport({ apiKey: "..." }), { maxAttempts: 3 });
+const transport = new RetryTransport(
+  new TaqnyatSmsTransport({ bearerToken: "...", sender: "MyBrand" }),
+  { maxAttempts: 3 },
+);
 ```
 
-</Step><Step title="Create the mailer">
+  </Step>
+  <Step title="Pass it to the channel sender">
 
 ```ts
-const mailer = await createMailer({ transport });
+import { createSmsSender } from "sently/sms";
+
+const sms = createSmsSender({ transport });
 ```
 
-</Step></Steps>
+  </Step>
+</Steps>
+
+## Troubleshooting
+
+<Accordions>
+  <Accordion title="Does this replace the inner provider?">
+    No. It delegates sends to the wrapped transport.
+  </Accordion>
+</Accordions>
 
-<Accordions><Accordion title="Does this replace the inner provider?">No. It delegates sends to the wrapped transport.</Accordion></Accordions>
+## Next
 
-<Cards><Card title="Email channel" href="/docs/channels/email" /></Cards>
+<Cards>
+  <Card title="Fallback" href="/docs/decorators/fallback" />
+  <Card title="Hooks" href="/docs/channels/hooks" />
+</Cards>

package/site/content/docs/decorators/weighted-fallback.mdx

@@ -6,6 +6,7 @@ source: "src/transports/weighted-fallback.ts"
 ---
 
 Choose a weighted primary transport and fail over on errors.
+Works with email, SMS, WhatsApp, and push.
 
 <Callout title="The one rule">At least one entry with positive total weight is required.</Callout>
 
@@ -13,22 +14,42 @@ Choose a weighted primary transport and fail over on errors.
 
 Each entry has `transport` and positive `weight`; it accepts fallback options and optional `random`.
 
-<Steps><Step title="Wrap an email transport">
+## Quick start
+
+<Steps>
+  <Step title="Build weighted entries">
 
 ```ts
 import { WeightedFallbackTransport } from "sently/transports/weighted-fallback";
 
-const transport = new WeightedFallbackTransport([{ transport: primary, weight: 80 }, { transport: secondary, weight: 20 }]);
+const transport = new WeightedFallbackTransport([
+  { transport: primary, weight: 80 },
+  { transport: secondary, weight: 20 },
+]);
 ```
 
-</Step><Step title="Create the mailer">
+  </Step>
+  <Step title="Pass it to the channel sender">
 
 ```ts
 const mailer = await createMailer({ transport });
+// or createSmsSender / createWhatsAppSender / createPushSender
 ```
 
-</Step></Steps>
+  </Step>
+</Steps>
+
+## Troubleshooting
+
+<Accordions>
+  <Accordion title="Does this replace the inner provider?">
+    No. It delegates sends to the wrapped transports.
+  </Accordion>
+</Accordions>
 
-<Accordions><Accordion title="Does this replace the inner provider?">No. It delegates sends to the wrapped transport.</Accordion></Accordions>
+## Next
 
-<Cards><Card title="Email channel" href="/docs/channels/email" /></Cards>
+<Cards>
+  <Card title="Fallback" href="/docs/decorators/fallback" />
+  <Card title="Decorators" href="/docs/decorators" />
+</Cards>

package/site/content/docs/get-started/entrypoints.mdx

@@ -54,26 +54,27 @@ const mailer = await createSMTPMailer({
 
 | Import | Exports | Use |
 | ------ | ------- | --- |
-| `sently` | Shared factories, types, OAuth2, errors, Fallback / WeightedFallback / Cloudflare Email | General email entrypoint. |
+| `sently` | Shared factories, types, OAuth2, errors, `toChannelSendResult`, Fallback / WeightedFallback / Cloudflare Email | General email + shared helpers. |
 | `sently/mailer` | `createMailer` | Email with an explicit transport (smallest HTTP path). |
 | `sently/smtp` | `createSMTPMailer` | SMTP relay configuration. |
 | `sently/sms` | `createSmsSender` | SMS sender. |
 | `sently/whatsapp` | `createWhatsAppSender` | WhatsApp sender. |
-| `sently/push` | `createPushSender` | Web Push sender. |
+| `sently/push` | `createPushSender` | Push sender (Web Push or FCM). |
+| `sently/channel-result` | `toChannelSendResult` | Shared `{ messageId, provider, accepted }` mapping. |
 
 ## Supporting entrypoints
 
 | Import | Use |
 | ------ | --- |
-| `sently/transports/*` | One provider or email decorator transport. |
-| `sently/webhooks/<provider>` | One webhook parser (smallest graph). |
+| `sently/transports/*` | One provider or decorator transport (retry / fallback work across channels). |
+| `sently/webhooks/<provider>` | One webhook parser (email, SMS, or WhatsApp). |
 | `sently/webhooks` | Convenience barrel of all webhook helpers. |
 | `sently/errors` | Stable sently error classes and codes. |
 | `sently/plugins/template` | Template plugin and simple engine. |
 | `sently/auth/oauth2` | SMTP OAuth2 client. |
 | `sently/pool` | SMTP connection pool. |
 | `sently/dkim` | DKIM signing entrypoint. |
-| `sently/idempotency` | Idempotency transport and memory store. |
+| `sently/idempotency` | Idempotency transport and memory store (email). |
 
 ## Troubleshooting
 

package/site/content/docs/get-started/installation.mdx

@@ -5,7 +5,7 @@ icon: Package
 source: "package.json"
 ---
 
-sently is an ESM package for applications that send email, SMS, WhatsApp, or browser push.
+sently is an ESM package for applications that send email, SMS, WhatsApp, or push (Web Push / FCM).
 Install it in the application that owns your delivery credentials and provider transport configuration.
 
 <Callout title="The one rule">Import the narrowest sently entrypoint that contains the sender or transport you use.</Callout>
@@ -52,7 +52,8 @@ const mailer = await createMailer({
 | Email over SMTP | `sently/smtp` |
 | SMS | `sently/sms` |
 | WhatsApp | `sently/whatsapp` |
-| Web Push | `sently/push` |
+| Push (Web Push or FCM) | `sently/push` |
+| Shared send-result mapping | `sently/channel-result` |
 
 ## Troubleshooting
 

package/site/content/docs/get-started/introduction.mdx

@@ -5,7 +5,7 @@ icon: Compass
 source: "README.md"
 ---
 
-sently sends email, SMS, WhatsApp, and browser push without making provider SDK calls your application API.
+sently sends email, SMS, WhatsApp, and push (Web Push or FCM) without making provider SDK calls your application API.
 Choose the channel sender first, then attach the provider transport that performs delivery.
 
 <Callout title="The one rule">Use `createMailer`, `createSmsSender`, `createWhatsAppSender`, or `createPushSender` in app code; swap transports when provider configuration changes.</Callout>

package/site/content/docs/guides/webhooks.mdx

@@ -1,12 +1,13 @@
 ---
 title: Webhooks
-description: Parse provider delivery events into a shared EmailEvent shape, with optional signature checks.
+description: Parse provider delivery events into EmailEvent or DeliveryEvent shapes, with optional signature checks.
 icon: Webhook
 source: "src/webhooks.ts"
 ---
 
-Use webhooks when a provider posts delivery updates (delivered, bounced, and similar).
-sently turns each provider payload into `EmailEvent[]` so your app can share one handler.
+Use webhooks when a provider posts delivery updates (delivered, bounced, failed, and similar).
+Email parsers return `EmailEvent[]`. SMS and WhatsApp parsers return `DeliveryEvent[]`.
+Map email events with `toDeliveryEvent` when you want one ingest pipeline.
 
 <Callout title="The one rule">
   Verify the signature against the unmodified raw request body before you trust or act on the event.
@@ -53,7 +54,7 @@ const events = parse(JSON.parse(rawBody));
 
 ```ts
 for (const event of events) {
-  if (event.type === "bounced") {
+  if (event.type === "bounced" || event.type === "failed") {
     // suppress or alert using event.messageId / event.recipient
   }
 }
@@ -65,19 +66,32 @@ for (const event of events) {
 
 ## Provider entrypoints
 
-| Import | Parse export | Verify export |
-| ------ | ------------ | ------------- |
-| `sently/webhooks/brevo` | `parse` | — |
-| `sently/webhooks/mailgun` | `parse` | `verifySignature`, `verifyPayload` |
-| `sently/webhooks/postmark` | `parse` | — |
-| `sently/webhooks/resend` | `parse` | `verifySignature` |
-| `sently/webhooks/sendgrid` | `parse` | — |
-| `sently/webhooks/ses` | `parse` | — |
-| `sently/webhooks/sndr` | `parse` | `verifySignature` |
-
-The convenience barrel `sently/webhooks` re-exports named helpers such as `parseSndrWebhook` and `verifySndrSignature`.
+| Import | Channel | Parse export | Verify export |
+| ------ | ------- | ------------ | ------------- |
+| `sently/webhooks/brevo` | Email | `parse` → `EmailEvent[]` | — |
+| `sently/webhooks/mailgun` | Email | `parse` | `verifySignature`, `verifyPayload` |
+| `sently/webhooks/postmark` | Email | `parse` | — |
+| `sently/webhooks/resend` | Email | `parse` | `verifySignature` |
+| `sently/webhooks/sendgrid` | Email | `parse` | — |
+| `sently/webhooks/ses` | Email | `parse` | — |
+| `sently/webhooks/sndr` | Email | `parse` | `verifySignature` |
+| `sently/webhooks/twilio-sms` | SMS | `parse` → `DeliveryEvent[]` | `verifySignature` (`X-Twilio-Signature`) |
+| `sently/webhooks/unifonic` | SMS | `parse` → `DeliveryEvent[]` | — |
+| `sently/webhooks/whatsapp-cloud` | WhatsApp | `parse` → `DeliveryEvent[]` | `verifySignature` (`X-Hub-Signature-256`) |
+
+The convenience barrel `sently/webhooks` re-exports named helpers such as `parseSndrWebhook`, `parseTwilioSmsWebhook`, and `toDeliveryEvent`.
 Bundlers tree-shake unused names; Node/Deno without a bundler evaluate every re-export.
 
+## SMS status callbacks
+
+Twilio posts form fields (`MessageSid`, `MessageStatus`, `To`). Pass a parsed object or `URLSearchParams`:
+
+```ts
+import { parse } from "sently/webhooks/twilio-sms";
+
+const events = parse(await request.formData().then((fd) => Object.fromEntries(fd)));
+```
+
 ## SNDR signatures
 
 SNDR signs with `X-Sndr-Signature: t=<unix>,v1=<hex>`.
@@ -99,7 +113,9 @@ Most frameworks parse JSON before your handler runs. Read the raw body first (`r
 
 <Accordion title="Which providers are supported?">
 
-Brevo, Mailgun, Postmark, Resend, SendGrid, SES, and SNDR. Import each from its `sently/webhooks/<provider>` subpath.
+Email: Brevo, Mailgun, Postmark, Resend, SendGrid, SES, SNDR.
+SMS / WhatsApp: Twilio SMS, Unifonic, WhatsApp Cloud.
+Import each from its `sently/webhooks/<provider>` subpath.
 
 </Accordion>
 
@@ -107,14 +123,13 @@ Brevo, Mailgun, Postmark, Resend, SendGrid, SES, and SNDR. Import each from its
 
 ## Learn more
 
-- [Webhook events](/docs/reference/webhook-events) — `EmailEvent` fields and type unions
-- [SNDR transport](/docs/transports/sndr) — send path that produces those message ids
+- [Webhook events](/docs/reference/webhook-events) — `EmailEvent` / `DeliveryEvent` fields
 - [Exports](/docs/reference/exports) — package entrypoints
 
 ## Next
 
 <Cards>
-  <Card title="Webhook events" description="Normalized EmailEvent fields." href="/docs/reference/webhook-events" />
-  <Card title="SNDR" description="Send email through SNDR." href="/docs/transports/sndr" />
+  <Card title="Webhook events" description="Normalized event fields." href="/docs/reference/webhook-events" />
+  <Card title="Channel send result" description="Shared accepted mapping." href="/docs/reference/channel-result" />
   <Card title="Exports" description="Public package entrypoints." href="/docs/reference/exports" />
 </Cards>