Back to the blog
AutomationPublished 4 min read

From WhatsApp Chats to a System: Tidying Up Scattered Orders

WhatsApp is a fine place to talk with customers, but not a place to keep order data. Here's how to move that data into a system, one step at a time.

A person writing in a notebook while holding a phone
Photo by Wanderlust in Frame on Unsplash

Many businesses in Indonesia run on WhatsApp. Orders arrive in chat, addresses come in separate messages, payment proofs are photos, and everything is copied again into Excel or a notebook. While orders are few, this works. Once things get busy, things start slipping through. This article covers how to tidy it up in stages, without forcing customers to leave WhatsApp.

Signs your orders are getting scattered

  • Digging through chats for data. You scroll back through old conversations to find an address, a variant, or a quantity.
  • Matching transfer proofs by hand. Payment screenshots are checked one by one against the bank statement, and some never get confirmed.
  • Leads never hear from you again. People who asked for a price and went quiet are never contacted, because no list reminds you.
  • Different versions of the truth. The admin and the owner each keep their own Excel file, and the numbers don't match.
  • Reports take half a day. To know this week's order count, someone has to rebuild it from the chats.

The problem isn't WhatsApp. The problem is that order data ends up stored inside conversations, and a conversation is a poor place to keep data.

The principle: WhatsApp for talking, a system for data

Your customers are comfortable on WhatsApp, and forcing them onto another app can cost you orders. What moves is the data: who ordered what, how many, where it ships, whether it's paid, and what happens next. The conversation stays on WhatsApp, while the official record lives in one place you can search and summarise.

Five gradual steps

1. A structured form or catalogue

Replace "what would you like to order?" with a simple form or catalogue that always asks for the same details: name, WhatsApp number, product, quantity, and city. On submit, the form can open WhatsApp with a prefilled message, so the customer still feels they're just chatting. The difference is that the data arrives complete. Add a simple spam filter too, such as a trap field only bots fill in.

2. One place for all the data

Every form entry lands in one list, not in each admin's own chats. At first, Google Sheets is enough. As volume grows, a simple CRM helps: each order or lead has a status, an owner, and notes, so it's clear what hasn't been handled yet.

3. QRIS payments with automatic confirmation

With a payment gateway, customers pay by QRIS, e-wallet, or virtual account, and the gateway sends a notification to your system. The system checks that the notification is genuine and marks the order as paid without anyone checking by hand. Fees and terms differ between gateways and can change, so compare before you choose.

4. Automatic reminders and follow-ups

Once the data is tidy, reminders can run on their own: nudging leads who haven't replied, or alerting the admin when a task falls due. The rules: only message people who have given consent, never send the same message twice, and retry sends that fail.

5. Reports available any time

Because all the data sits in one place, you can see straight away how many orders are at each stage and how many are paid, then download it as a spreadsheet file if needed.

A real example: enrolment at Numekara

Numekara is the education business we run ourselves, and it's where we built and used this flow first. Its consultation form uses a bot trap field, a minimum fill time, and a safeguard so double submits don't create duplicate records. Each submission becomes a new lead right away, the sender gets a confirmation email, and the admin gets an alert.

Those leads go into a CRM with 10 pipeline stages, from new enquiry and contacted through to enrolled or lost. Each lead has an owner, an activity log, and follow-up tasks. From the same page, the admin can raise an invoice and record a payment, and the data can be exported to CSV.

Online payments use Midtrans for QRIS, GoPay, and virtual accounts. Payment notifications are signature-checked and recorded once, then access unlocks immediately and the lead moves to enrolled automatically. Manual transfers use a unique amount code so they're easy to match.

Follow-ups run through a scheduled job every three hours that checks contact consent, logs every send so nothing is duplicated, and retries failures. One honest note: at Numekara, WhatsApp is only a click-to-chat button. Automated follow-ups go out by email, and admin alerts go through Telegram and email.

When the simple route is enough

If you get a handful of orders a day and one person handles them, a form that opens WhatsApp plus a Google Sheet is probably enough. A CRM, a payment gateway, and scheduled automation start to pay off when there's more than one admin, daily orders grow, or leads start slipping away because nobody followed up. Building a big system before you need it only adds maintenance costs.

Customers can still chat on WhatsApp. The difference is that your business data no longer lives inside the chat.