Customer conversations
Ask for the review after the parcel lands, not when it leaves
Most review requests go out when the label is printed, because that is the event the shop happens to have. The customer is asked to rate something still in transit. Waiting a few days after delivery is a small change to the timing and a large change to what you are asking — but it also moves the message outside WhatsApp's service window, which turns a free-text note into a template, an approval, and a daily sending limit.
- Triggers
- Two
- Runs
- Daily
- Stack
- 4 tools
- Durable execution
- Not required
The flow
Delivery fills a queue with a due date. A separate daily pass decides who is due today, because the waiting is the point of the case.
Marked delivered
Shopify Admin API
Set the due date
n8n · Make
Write the ask queue
Sheets · Airtable
Every morning
n8n 排程
List who is due
n8n · Make
Opted in, not asked before?
n8n IF
Send the approved template
WhatsApp Cloud API
Leave it alone
—
Step by step
- 01
Marked delivered
Shopify Admin APIThe fulfilment event, not the dispatch event. If your system cannot tell those apart, this case is not available to you and the rest of the flow is decoration.
- 02
Set the due date
n8n · MakeAdd the wait — three days, or whatever suits what you sell. Something worn a few times is judged later than something eaten the same evening.
- 03
Write the ask queue
Sheets · AirtableOne row per order: due date, opt-in state, and whether this customer has been asked before. That last column is what stops a repeat buyer being asked every month.
- 04
Every morning
n8n 排程One pass a day. A review request is not urgent, and sending on a schedule keeps the day's volume visible against the limit below.
- 05
List who is due
n8n · MakePull the rows whose due date has arrived. Cap the batch deliberately rather than sending everything the backlog contains.
- 06
Opted in, not asked before?
n8n IFBoth conditions, not either. Opt-in is a platform requirement; not-asked-before is the difference between a request and a nuisance.
- 07
Send the approved template
WhatsApp Cloud APIDays after delivery the service window is shut, so this is a template that was written and approved weeks ago. Name the item — a request that does not say what it is about reads as a broadcast.
What the platform will not allow
This case sits entirely outside the service window, which is the most regulated place to be on WhatsApp. Four rules bound it.
"When the window closes, you can only send pre-approved template messages." A message sent three days after delivery is always outside the window, so free text is never an option here.
WhatsApp Cloud API — Send messages"Templates must have a status of APPROVED before they can be sent in template messages", each is categorised as authentication, marketing or utility, and template quality is rated "based on usage, customer feedback, and engagement" — templates that draw consistent negative feedback can be paused. A review request that annoys people does not merely underperform; it can stop being sendable.
WhatsApp Business Management API — Message templatesMessaging limits are "the maximum number of unique WhatsApp user phone numbers your business can deliver messages to, outside of a customer service window, within a moving 24-hour period", and "newly created business portfolios have a messaging limit of 250". A backlog of a thousand delivered orders cannot be cleared in one morning.
WhatsApp Business Platform — Messaging limits"You may only contact people on WhatsApp if: (a) they have given you their mobile phone number; and (b) you have received opt-in permission from the recipient confirming that they wish to receive subsequent messages or calls from you", and you "must respect all requests" to opt out. Having sold to someone is not opt-in.
WhatsApp Business Messaging Policy
When this is not worth building
Three cases where the upkeep costs more than the missing reviews.
You cannot tell delivered from dispatched. If the only event you hold is the label being printed, the premise of the case is gone and the request arrives while the customer is still waiting for the parcel.
Reviews do not change anything about how you sell. On a channel where nobody reads them and no ranking uses them, you are spending your outside-window sending budget on a number nobody acts on.
Nobody watches the replies. A review request invites an answer, and it lands in the same inbox as everything else. Asking a question and then not reading the response costs more goodwill than never asking.