Skip to content
WhatsApp

A familiar channel, inside the whole journey.

Templates managed end to end, buttons that decide the next step, and a guard against the one cost surprise every WhatsApp sender eventually meets.

THE CHANNEL

What it's for.

Service and post-purchase conversations, confirmations and reminders that need a reply, and rich content with buttons, on the app most of your customers already keep open.

01 · Compose

Compose with the rules applied.

Build the full template, header, body, footer, buttons and media, in its own tab with a live preview, with the platform's rules applied before submission so you don't build something that will be rejected.

02 · Lifecycle

The whole template lifecycle, in one place.

Create, clone, keep versions, upload media, submit for approval, watch approval status, read the quality rating, and sync two ways so what you see matches what the platform holds, including the template's current category. Approval itself still sits with the platform; what you get is one place to run it from.

03 · Cost protection

Cost protection.

WhatsApp templates are priced by category, and a template can be re-categorised after it was approved. Most platforms pass that straight through, so a utility template quietly reclassified as marketing keeps sending at the higher rate until an invoice arrives. Here, every sync checks the category. If it changed, WhatsApp is withdrawn from that template immediately and logged. Sending stops before the spend accrues. The template keeps working on its other channels, and you decide whether to restore it.

04 · Buttons

Buttons that branch.

A journey can wait for a button tap and give each button its own path, each with its own deadline. That deadline can be measured from when the message was read rather than sent, so a customer who opens it two days later gets their full window. A no-tap path handles everyone else.

WhatsApp Flows.

A journey step can open a native WhatsApp flow, so a customer completes a richer interaction without leaving the chat.

05 · Events

What comes back.

Delivery, read receipts and button taps, all as events on the same data path as everything else.

Also on the way out.

Click-to-chat links minted by xNotify's own link service, with an optional pre-filled message, credited to the message that carried them. Per-channel consent with history, so a customer opted in to WhatsApp and out of SMS is treated as exactly that.

What it replaces

A WhatsApp provider that submits templates and stops there, leaving category changes, replies and journeys to you.

The pilot

WhatsApp inside one journey, in eight weeks.

Book a Demo