WhatsApp for Subscription Brands: Cut Churn, Save Payments

Subscription brands are the strongest vertical in our own data. The subscription profile on our Industries page reads 96% open rate, 45% click-through, 12–18% click-to-purchase conversion and 82% repurchase within 90 days — the highest repurchase figure of any vertical listed there.

The reason is structural rather than clever copy. A subscription already has a rhythm: every renewal is a scheduled moment where a customer either continues or quietly stops. Email lands in an inbox that is already full, and the decisions you need from a subscriber are small ones — skip this month, swap the flavour, pause until March. Small decisions belong in the channel where people answer in minutes.

Those figures are bands rather than single numbers on purpose; how the Forecast is calculated sets out where they come from. And WhatsApp complements email here rather than replacing it: keep receipts, invoices and long-form content in the inbox, and put the time-sensitive decisions on WhatsApp.

Three flows cover the moments where subscription revenue is actually won or lost. The conversion figures are click-to-purchase rates from Keaz customers in this vertical.

1. Renewal notice with skip, swap or pause — 17.2%. Sent a few days before the next shipment: the plan, the ship date, and three one-tap options. It reads as a service message, not a campaign, and it catches the dissatisfaction that would otherwise turn into a cancellation.
2. Failed-payment notice — 14.8%. A card expired or a bank declined a renewal. The subscriber did not choose to leave and often does not know it happened, so a short message with a link to update the card recovers revenue that no retention offer needs to buy back.
3. Cancel-save — 12.5%. Triggered when someone starts to cancel. One alternative, offered once: a one-month pause, a smaller box, a longer interval. The goal is to keep the relationship, not to win the argument.

All three are retention flows, which is why they convert well above acquisition messaging: the recipient is already a customer with a live plan. For the acquisition side of the same channel, the food and beverage playbook covers the reorder rhythm, and RFM segmentation for Shopify stores is how you decide which subscribers deserve a save offer at all.

Keaz has no native "subscription renewal" or "failed payment" trigger, and it is worth being precise about that before you plan a flow around one. A flow starts from one of five triggers: Contact Purchase and Abandoned Checkout, both Shopify events; Smart Activation, which is Keaz-internal; Chat-in, when the customer writes first; and Webhook, for events that happen outside Keaz.

Subscription renewals, failed payments and cancellations are not Shopify order events — they live in whatever tool owns the billing schedule. So they arrive through the Webhook trigger, which is documented for exactly this case: a payment confirmed, or a payment that failed, sent to Keaz as an HTTP request. Because the payload carries your own fields, the message can name the plan and the amount instead of announcing that there was a problem.

1. Create a flow under Flows and open the Starting point block.
2. Select Webhook as the trigger event.
3. Configure the outgoing webhook in your subscription or billing tool. This step differs per system, because every tool describes its outgoing webhooks differently.
4. Write the message using the fields the payload sends, and add a quick reply or link that resolves the event in one tap.
5. Save, then activate the flow and watch the first live sends before adding delay steps.

Three things have to be in place, all covered in the flows overview: the sending system has to know which contact the event belongs to, the contact has to exist in Keaz and be matchable to the payload, and the contact has to hold a valid opt-in. A webhook proves that an event happened. It does not establish that you may message someone about it.

The instinct is a discount. The better first offer is usually a pause. In Recurly's 2026 State of Subscriptions report, 38% of consumers said they would rather pause than cancel; brands that added a pause option saw pause usage rise sharply, and three in four of those subscribers returned within months.

A pause protects the price you sell at. A discount teaches subscribers that threatening to cancel is worth money, and the margin never fully comes back. Keep the discount as a second offer, if at all, and never in the same message.

Then measure it. Revenue is attributed per flow through a discount code that you create in Keaz and that Keaz creates in your shop, so orders redeeming that code are credited to that flow. Each flow needs its own code — reuse one across the renewal notice and the cancel-save and you can no longer tell which of the two saved the subscriber.

• Treating the webhook as permission. A failed payment is a real event and still not a licence to message. The opt-in has to exist independently, and it has to be documented.
• Counting a skip or a pause as a loss. A skipped month keeps the plan alive. Measured against a cancellation it is the good outcome, so the renewal flow should be judged on retained plans, not on shipments.
• Leading the save with money. Discount-first cancel-save flows convert, then erode price integrity across the whole base.
• Sending the renewal notice on the renewal day. If the charge has already gone through, skip and swap are no longer available and the message creates a support ticket instead of a decision.
• Writing the failed-payment message like a dunning letter. The subscriber is not a debtor; a card expired. Neutral wording and one link to update the card outperform urgency.
• Sharing one discount code across flows. Attribution collapses, and the flow you would have cut looks identical to the one you should scale.

Do I need a subscription app on Shopify for this?

Something has to own the billing schedule and decide when a renewal is due or a payment has failed. Keaz does not replace that system; it reacts to it. As long as your subscription or billing tool can send an HTTP request when an event occurs, the flow can run.

Is there a native failed-payment trigger in Keaz?

No. There are five triggers, and the Webhook trigger is the supported path for subscription and payment events. The message templates for each vertical are in the template library.

Will offering a pause cost me revenue?

It defers revenue rather than losing it, which is the trade you want against a cancellation. The published evidence points the same way: most subscribers who pause come back, and a paused plan can be restarted without a new acquisition cost.

How long should a failed-payment sequence be?

A flow can be a single message or several with delay blocks in between, and there is no fixed limit on steps. For failed payments, start with one message and one reminder; if the card is not updated after two attempts, the problem is usually not the message.

How much of subscription churn can messaging realistically fix?

The involuntary part, mostly. In Recurly's churn benchmarks (network data, July 2026) ecommerce runs a median 4.25% churn, of which 1.38 points are involuntary — roughly a third, and the part that responds to a well-timed message rather than to a product change.