Case note3 sections · 2 min readBy Dezső Mező · Published October 3, 2026.mdAutomationWhatsAppE-commerceOps
A real client ran sales through a personal WhatsApp: enquiries mixed with chat, screenshots for addresses, and 'did anyone answer this?' as a daily ritual. The fix kept the channel customers already used and replaced only what happened after the message arrived.
01Keep the channel, structure the intake
Customers still write to the same number, but the first reply is a short structured form — product, quantity, delivery address — that lands in a real database row instead of a chat bubble. Nothing about the conversation changes; everything about the record does.
02Status is a message, not a phone call
Each order carries a state — received, confirmed, shipped, done — and every transition fires a templated WhatsApp message back to the customer. The 'where is my package' calls, which were most of the interruptions, mostly stopped.
03A weekly digest replaces the spreadsheet
Once orders are rows, a Monday-morning summary posts the week's numbers into the same chat. Reporting stopped being a task somebody forgot.
What to take away
- Structure the intake, not the channel — customers keep what they know.
- Automate the status ping; most support calls ask the same question.
- Orders as database rows make reporting free.
- Ship the boring version first; integrations can grow later.
More from the lab
Browse all entries
The invoice pipeline that ended the Friday admin block
Self-hosted n8n or Zapier — where the bill actually differs
Enquiry to booked call, without the inbox
MCP servers in production, not in the demo
Want this looked at on your own system?Start a conversation
