Business Process Automation Checklist: Fix It Before You Build

"We tried automation and it made things worse." We hear some version of this in a lot of first calls. When we ask what was automated, the story is usually the same. A follow-up went out twice to the same customer, one of them at 2 am. A confirmation quoted last month's price. A lead was assigned to a salesperson who had left in March. The tool did exactly what it was told. The process it was told to follow was already broken.

Automation does not think. A person notices that a phone number is missing a digit or that an order looks strange. A workflow pushes it straight through, at any hour, as many times as it is triggered. So the work that decides whether automation helps you happens before anyone opens a tool.

Below is the checklist we would want every owner to fill in before paying for a build. It fits on one page. Under each line is a short note on why it matters, and after that, a worked example of one messy process going through it.

The one-page version to print

Pick one process, not your whole business. Then answer each line with a clear yes. A "sort of" counts as a no.

1. One named person owns this process and will fix it when it breaks.
2. We walked through a real case from last week with the person who does the work.
3. We can name the exact event that starts the process.
4. Every piece of data it needs has one home and one format.
5. Every decision is written as a rule a new employee could follow.
6. The unusual cases are written down, and each one has somewhere to go.
7. We have marked where a human takes over, and how they get alerted.
8. Any message it sends to customers follows WhatsApp and email rules.
9. We wrote down today's numbers so we can compare after launch.
10. Someone will check it every week once it is live.

Block out about an hour with the person who actually does the work, not the manager who describes it. Bring last week's real examples: the WhatsApp chats, the Excel rows, the invoices.

What each line is really asking

1. One named person owns it

"Sales team" is not an owner. "Sana" is. When a process has no single owner, every task the automation creates lands in a shared space and everyone assumes someone else picked it up. The owner is also the person who notices when the automation quietly stops working.

2. A real case, not the SOP

Your SOP document describes how the process should work. A real case from last Tuesday shows how it does work: the extra phone call, the screenshot forwarded to a colleague, the step that only happens "if Ali is free". Walk one case from start to finish and write down every step, who did it and which tool they used.

3. The exact starting event

"When an order is confirmed" sounds clear until you ask what confirmed means. The customer said yes? The payment screenshot arrived? Someone checked the bank app? Pick one event a computer can see, such as a form submitted, a status changed in your sheet, or a payment marked received.

4. One home, one format for data

If customers live in three Excel files on three laptops, the automation will pick the wrong one. Merge them into one list. Store phone numbers in one format with the country code, such as +92 for Pakistan or +971 for the UAE. Decide which fields must be filled before a record can move forward, and delete old test entries.

5. Decisions written as rules

"Repeat customers get free delivery" is a rule. "We use our judgment on delivery" is not. If you cannot write a decision in one plain sentence, the automation cannot follow it either. Some decisions genuinely need a person, and that is fine. Mark them as human steps instead of forcing a rule.

6. Exceptions with a destination

Listen for words like "sometimes", "unless" and "except when" during the walkthrough. Each one is an exception. For each, decide where it goes: a named person, a separate list, a hold status. An automation built only for the normal case drops every unusual case on the floor, and you find out from an angry customer.

7. The human handover

Complaints, negotiations, refunds and anything sensitive should reach a person quickly. Decide the exact trigger for handover and how the person is alerted, whether that is a WhatsApp notification, a task in your CRM or both.

8. Customer messaging rules

Owners often expect to message any customer from a dashboard for free. On the official WhatsApp Business Platform, a first message to someone who has not written to you in the last 24 hours must be an approved template, which Meta charges for per message at a price Meta sets and changes. Replies inside a customer's conversation are free. Plan which of your automated messages fall on which side of that line, and only message people who contacted you or opted in.

9. Today's numbers

How many times does this process run each week? How long does one round take? How often does it go wrong? Write it down now. Without a before number, nobody can say whether the automation helped.

10. A weekly check

Automations break when a form field is renamed or an app changes something. They usually break silently. Ten minutes every Monday reviewing failed runs and stuck records keeps a small fault from running for a month.

A worked example: WhatsApp orders at an online clothing shop

Here is an example of the kind of process we see often. Picture a small women's clothing brand in Faisalabad selling through Instagram and WhatsApp. The owner wanted one thing: "automatic order confirmations on WhatsApp." This is what the process looked like when walked through honestly.

1. A customer sends a screenshot of a dress from Instagram, sometimes with a voice note asking about size.
2. The salesperson replies, confirms stock by asking the owner's brother, and sends the price.
3. The customer pays by JazzCash, Easypaisa or bank transfer and sends a screenshot, or asks for cash on delivery.
4. The salesperson types the order into an Excel sheet. The owner's brother keeps a second sheet for dispatch.
5. He books the courier, using a different courier for some cities, a rule nobody had written down.
6. Someone, eventually, sends the tracking number on WhatsApp.

Now the checklist. Owner: nobody, it was split between two people, so the brother took ownership. Starting event: "confirmed" meant different things to each person, so they chose "payment verified or COD approved". Data: two sheets merged into one, phone numbers fixed to +92 format, and seven required fields agreed: name, phone, city, full address, size, colour and payment method. Rules: the courier choice by city was finally written down, along with who gets cash on delivery. Exceptions: out of stock after payment, incomplete address and unclear payment screenshots each went to the brother with a WhatsApp alert. Handover: exchanges and complaints stayed fully human.

Line 8 changed the plan. The order confirmation goes out while the customer is still chatting, so it is a free reply. The tracking message often goes out two or three days later, outside the 24-hour window, so it needed an approved template. Knowing that before the build saved a week of confusion about why some messages were not sending.

Only then was anything automated. The AI on WhatsApp now asks for any missing fields in Urdu, Roman Urdu or English, writes the order into one sheet, and sends the confirmation. When the courier is booked, the tracking template goes out on its own. Payment checks and exchanges stayed manual on purpose.

One more lesson from our own work that applies here: if customers send voice notes, test the AI with real ones. Speech-to-text once wrote our customers' Urdu in Hindi script, and the AI replied in Hindi until we forced Urdu transcription.

When a "no" means stop, and when it can wait

Not every no is equal. A missing owner, an unclear starting event or messy data means stop: building now will cost more to fix later. A few exceptions without a destination can wait, as long as the handover in line 7 catches them and sends them to a person. A missing before number is not a reason to delay, but take one week to measure while you plan.

Which process to run through it first

Choose something that happens often, follows clear rules and costs money when it is slow. For most small businesses, from a shop in Lahore to a trading company in Dubai, that means lead intake and first replies, follow-ups after a quote, invoice reminders, weekly reports, or onboarding a new client. Leave rare, judgment-heavy work like custom pricing for large projects until later. Our workflow automation page shows how these first flows usually connect.

What we build after the checklist, and what we leave alone

Every business process automation project at AMEVIX DIGITAL starts with this kind of walkthrough before a single workflow is built. We map your top one to three processes, flag the data that needs cleaning, and tell you plainly which steps should stay manual. Then we connect what is worth connecting: WhatsApp automation on the official platform, website forms, your CRM, invoices and reports, all in one client dashboard, tested with real cases before going live.

Start with one process this week and fill in the ten lines yourself. If you get stuck on owners, data or exceptions, that is what our automation audit is for, and we will help you decide what to fix before anything is built.

Further reading

See how this looks in practice across our AI automation, custom CRM and lead generation services, or tell us the outcome you need.