Thank You
A short thank-you for the orders your COD confirmation never covers — paid online, at the counter, or from a draft.
Three kinds of order, ticked individually. Nothing is ticked when you switch it on — a thank-you is a courtesy, so Wapify never starts sending one on its own.
Wapify's order-update automations are built around cash on delivery, which leaves a gap: the orders that were simply paid for. Thank You fills it — a card payment, a sale at the counter, a draft order you built by hand. One short message, once, with a button back to the order.
What fires it
Not a moment — a kind of order. You tick which kinds are worth a thank-you, and an order matching one of them is thanked as soon as it arrives.
The three are mutually exclusive by construction: an order is a POS sale, or a completed draft, or an ordinary online order. Tick all three and no customer can be thanked twice.
Switching the automation on isn't enough. With nothing ticked it sends nothing, and the card says so with a warning rather than letting you believe it's running.
Why cash-on-delivery orders aren't on the list
They're deliberately absent, and absent through every door.
A COD order already gets the COD Confirmation the moment it's placed, and a customer who taps Confirm is already answered with "Thank you for confirming your order!". A third message in the same minute isn't gratitude, it's noise.
That includes COD orders you later mark as paid. Marking a COD order paid — after the courier hands over the cash — fires Shopify's order paid event exactly like a card sale would, so Online paid orders checks the payment method rather than trusting the word "paid". Anything that looks like cash on delivery is skipped, including free-text gateway names a merchant typed themselves: Cash on Delivery (COD), Pay on delivery, الدفع عند الاستلام.
The check here is deliberately wider than the one COD Confirmation uses to decide what to confirm. The two mistakes aren't equal: missing a COD order sends a customer a second message minutes after their confirmation, while skipping a thank-you costs nothing anyone notices.
Draft orders belong to one automation at a time
Draft orders are the one kind two automations both want. COD Confirmation has a Send for draft orders switch, and Thank You has its Draft orders tick — and a draft order should get one message, not two.
So the two settings release each other. Tick draft orders here and COD Confirmation quietly stops sending for them; turn COD Confirmation's switch on and this tick clears. Whichever you changed last is the one that holds them, and Wapify tells you in a toast when the other let go.
Which one you want depends on whether your drafts are already agreed. A draft you built with the customer over chat needs a thank-you; a draft where you still need a yes before shipping needs the confirmation.
What the customer gets
- One short message, once per order. No follow-up, no reminder — this is the shortest template in the set on purpose.
- An Order Details button that opens their Shopify order status page, so they can track it themselves.
- Nothing else. The copy promises no next step, because for these orders there isn't one.
The message uses the customer's first name, your store name and the order number. When Shopify sends no name — common for a walk-in POS sale — it opens with a neutral greeting rather than a blank.
Settings
- The master toggle — on or off, and everything below it dims when it's off.
- Which orders — the three tickboxes above. Multi-select, nothing ticked by default.
- Message language — from the global language picker, shared with every other automation.
There's no delay control. A thank-you has one right moment, and it's now.
Orders that can't be messaged
A POS walk-in frequently has no customer record at all, and an order with no usable phone number can't be messaged. Those aren't errors — they're a normal outcome for this automation — but they're still written to Logs with the reason, so you can see why a sale got no message.
Quiet hours
Thank You observes quiet hours in full. A message that would land between 02:00 and 11:00 store time waits until morning — a thank-you is the definition of something that can. Only COD Confirmation and messages you send by hand are exempt.
Sending one by hand
There's no Orders-page bulk action for this one. Two routes exist instead:
- From a chat — the Inbox composer's template picker lists it under Follow up, filled from the customer's most recent order. It sends even while the automation is switched off, because picking it is a deliberate per-conversation act.
- From Logs — resend a message that failed.