DX-004 · Proposal · 26/10/2026 · T-004 Message customers when an order changes status
Claude proposes notifying customers through Zalo ZNS, because 9 in 10 customers have already messaged the shop on Zalo, and it is almost three times cheaper than SMS. Task T-004 Message customers when an order changes status has been stuck for 4 days because there is no channel yet.
Three channels customers can read; they differ in how many customers receive it, price and the day sending starts.
Customers read it right in the Zalo they already use with the shop.
Fits when regular customers message the shop on Zalo; today that is 9 in 10 customers.
Change later add SMS alongside, no need to drop Zalo; about half a day.
Needs a verified Zalo OA and an approved message template, 3–5 days. While waiting, send email to customers who have one (question 2).
Every customer receives it, even on old phones.
Fits when many older customers do not use Zalo.
Change later register the sender name again if the carrier changes, 7–10 days.
Cheap and works from tomorrow.
Fits when customers leave an email; today only 18% of orders have one.
| Zalo ZNS | SMS | ||
|---|---|---|---|
| customers reached | 90% | 100% | 18% |
| cost per month | ~390,000 VND | ~1,040,000 VND | < 3,000 VND |
| can send after | 3–5 days | 7–10 days | 1 day |
Customers with an email are notified right away, without waiting 3–5 days.
Fits when waiting for Zalo to approve the template; turn it off once Zalo works.
Change later turn it off with one config line.
Claude sends straight through Zalo using the customer's real number.
Fits when the customer agreed to receive messages when ordering.
Claude does not call Zalo; the customer sees the message only after opening the app.
Fits when the owner wants customer data to stay inside; customers will see the message later.