Is it not risky to draw attention to a cancellation?

The customer already knows. The message is the difference between them quietly leaving and telling you what went wrong.

Can complex cases reach a person?

Yes. Any branch can end in a Responses node that routes the conversation into a human inbox with the order attached.

Apps used

Order Cancellation Save

When an order is cancelled, ask why on WhatsApp and offer a swap or a held discount before the customer is gone.

Win-backWhatsApporder_cancelled

Use this flow See how it's wired

Asking why, immediately

Your order #5104 was cancelled. Mind telling us why? It helps us fix it.

Out of stockWrong itemChanged mind

Wrong item

Got it. Same jacket in Medium is in stock — want us to swap it and ship today?

Why run the order cancellation save flow?

Cancellations are usually fixable: out of stock, wrong size, a payment hiccup, delivery taking too long. The flow fires the moment an order is cancelled, asks why, offers a swap or a held discount, and routes the complicated cases to a human inbox. Tagging the reasons over time shows you the upstream problems worth fixing.

A reason, every time

Every cancellation leaves a tag behind, so the pattern behind them stops being guesswork.

The swap beats the refund

Wrong size or wrong variant is a fixable problem, and fixing it keeps the revenue.

Ops get the signal

Reason tags accumulate into the upstream problems worth solving — stock, sizing, delivery lanes.

How it's wired

This is the flow as it appears in the Nonito builder. Every node here is a real node you can drag, configure and change — nothing about this diagram is decorative.

Order Cancellation Save — flow builderLive in Nonito

Triggers

Trigger Event

Event:Order cancelled

Messaging

Template:cancel_reason

Buttons:Out of stock · Wrong item · Changed mind

Logic

Filter

Condition:Reason tag

Wrong item

Recommendations

Product Recommendations

Source:Same collection, different variant

Messaging

Template:swap_offer

Changed mind

Actions

Discount

Type:Held discount, 7 days

Messaging

Template:win_back

In the app, drag nodes to rearrange and click any node to configure it. Trigger nodes start the flow; messaging nodes end a branch.

How does this flow work?

1An order is cancelled, and the flow fires straight away rather than at the end of the week.
2A WhatsApp message asks why, with the common reasons as tappable buttons.
3A Filter node routes on the reason the customer picked.
4Wrong item pulls a recommendation from the same collection and offers a swap.
5Changed mind generates a held discount and sends a win-back message instead.

Who should use this flow?

Brands with a cancellation rate worth attacking, where ops can act on the reasons.

Restaurants & F&B

Chains and cafés on Foodics or Zyda, from one branch to twenty.

See their full stack →

Questions about this flow

Is it not risky to draw attention to a cancellation?: The customer already knows. The message is the difference between them quietly leaving and telling you what went wrong.
Can complex cases reach a person?: Yes. Any branch can end in a Responses node that routes the conversation into a human inbox with the order attached.

Related flows

All flows →

Second chance

Refund Recovery

When a refund is issued, acknowledge it on WhatsApp, offer credit toward the next order, and tag what went wrong.

Trigger EventWhatsAppDiscount

Win-backUse this flow →

Underused

Shipping & Delivery Updates

Send proactive WhatsApp updates at every shipping event, then recommend the next product on the delivered message.

Trigger EventWhatsAppWait for Event

Post-purchaseUse this flow →

Most adopted

Order Confirmation

When an order is created, confirm it on WhatsApp — and filter fake cash-on-delivery orders before they ship.

Trigger EventFilterWhatsApp

Post-purchaseUse this flow →

Customer obsession starts here.

See how Nonito helps you understand your customers and engage with them at the right time.

Schedule a Demo