Grocery Delivery Substitution Chat Playbook
Searches like “grocery substitute LINE Thailand,” “quick commerce out of stock chat,” and “supermarket delivery WhatsApp substitution” need picker-ops sequencing — not freestyle “we swapped it” replies without order-ID tags. Quick-commerce riders, supermarket dark stores, and LINE grocery bots juggle real-time inventory, allergy notes, and COD refunds; substitution disputes spike when picker chat lacks SKU and substitute-approval tags.
Food sibling: food delivery merchant support chat playbook. Refund context: return & refund chat scripts for e-commerce.
Intake
Tags every grocery substitution chat must capture
- Order ID and delivery slot — verified before any substitute promise
- Original SKU and substitute SKU with price delta — linked to thread
- Allergy or dietary flag from order profile — stop-rule before substitute send
- Customer approval status: pending, accepted, rejected — routed tier tag
- Picker channel: in-app, LINE, WhatsApp — unified queue with warehouse tag
SLA
Reply targets grocery delivery teams can defend
- Active substitute rejection: first human reply under 10 minutes in coverage hours
- Allergy-flagged substitute request: under 5 minutes with supervisor tag
- Refund-after-substitute dispute: under 15 minutes with finance escalation tag
- After-hours: honest next-slot auto-reply — no substitute confirmed without picker tag
Scripts
Approved substitution language for LINE and WhatsApp
- Send substitute photo and price delta from approved template — await explicit accept/reject
- Offer refund or reorder from approved matrix — escalate beyond policy to ops lead
- Capture allergy concern with stop-rule — never substitute flagged allergens
- Close loop with updated order total on same tagged thread — audit for COD reconciliation
Stop-Rules
What grocery substitution chat must never confirm
- Never ship substitute without documented customer approval tag
- Never waive delivery fee on allergy incidents without supervisor tag
- Never promise same-slot redelivery without warehouse capacity tag
- Never merge two orders’ allergy profiles on one thread — safety risk
FAQ
FAQs on grocery delivery substitution chat
Should substitutions stay in-app only?
In-app push notifications satisfy many buyers — Thai shoppers still escalate on LINE when substitutes look wrong or allergy notes were ignored. Run both: in-app approval plus tagged overflow queue for disputes and COD refunds.
How does Sookly help?
Sookly maps grocery substitution overflow into a shared Chat Receptionist queue with order tags and allergy stop-rules. Join the waitlist.
Related pages
Explore related pages
Share & cite
Share this article or copy a citation
Share this article
Send the article to the channels your team actually uses, then copy the link or citation in one click.
Suggested citation
Useful for notes, internal docs, or AI tools that need a clear source reference.
Grocery Delivery Substitution Chat Playbook - Shoppers reject substitutes on LINE with no order tag — grocery delivery ops need substitute approval scripts, allergy stop-rules, and picker SLAs before chat promises items the warehouse never picked.
Grocery Delivery Substitution Chat Playbook. Sookly Insights. https://www.sookly.co/en/insights/grocery-delivery-substitution-chat-playbook
Pickers confirm substitutes but LINE disputes still untagged?
Join the waitlist and we will map a grocery delivery substitution chat playbook onto your shared inbox.