WhatsAppAutomationforBusinessinBangladesh:APracticalGuide

What you can automate on WhatsApp

Most of the value comes from four jobs. None of them need a complicated AI system to start. They need a clear set of rules and a connection to the place where your data already lives, such as a Google Sheet, your online store or your courier account.

• Enquiries: instant replies to common questions like price, size, delivery charge inside and outside Dhaka, and opening hours, with a hand-over to a person when the question is unusual.
• Order and parcel status: when an order is confirmed, packed or handed to the courier, the customer gets a message with the tracking details, so they stop asking 'vai, parcel kothay?'.
• Appointment reminders: clinics, salons, tutors and service businesses can send a reminder the day before and let the customer confirm or reschedule with one reply.
• Lead routing to sales: new enquiries are tagged by product or area and assigned to the right salesperson, and anything left unanswered for too long triggers an alert.

WhatsApp Business app vs the WhatsApp Business Platform

The WhatsApp Business app is the free app you install on a phone. It gives you a business profile, a product catalogue, labels, quick replies, a greeting message and an away message. For a shop with one person on the phone, these basics already save time, and you should set them up before paying for anything.

The app has limits. It is built for a person typing, not for software. It does not connect properly to your store, sheet or CRM, and it has no supported way for another system to send messages on your behalf. Tools that fake this through WhatsApp Web break often and can get the number restricted.

The WhatsApp Business Platform, often called the WhatsApp API, is Meta's official route for software to send and receive messages. You use it through Meta's Cloud API directly or through a Meta-approved Business Solution Provider (BSP). It requires a verified Meta business account and an approved display name.

Two rules shape everything you build on the platform. First, when a customer messages you, you can reply freely for a limited customer service window. Second, any message you start, or send after that window has closed, must use a template that Meta has approved in advance, and the customer should have opted in to receive it. Order updates and reminders are templates, so plan their wording early.

A simple example flow for an online shop

Here is a flow for a typical Facebook or website shop in Dhaka that takes cash on delivery and bKash. It is small enough for one project.

• A customer places an order on the website or the team adds it to a Google Sheet from a Messenger chat.
• The automation sends an approved confirmation template on WhatsApp with the order summary and a 'Confirm' and 'Cancel' button.
• If the customer taps Confirm, the order row is marked confirmed. If there is no reply after a set time, the order goes to a person to call.
• When the parcel is booked with the courier, the customer gets a second template with the tracking number.
• Any free-text reply from the customer lands in a shared inbox where the team can answer it, with the order details shown next to the chat.

What it costs to get started

There are three separate costs, and it helps to keep them apart. The first is Meta's own charge for certain messages on the platform, which depends on the message category and the customer's country. Meta changes these rates from time to time, so check the current pricing on Meta's site rather than trusting an old blog post.

The second is the provider or inbox tool, if you use one. Some BSPs and shared-inbox tools charge a monthly fee, others charge per message on top of Meta. The third is the build itself: designing the flow, writing the templates, connecting your sheet or store and testing it.

A single workflow like the order flow above fits a one-time project, and ongoing changes and monitoring fit a monthly plan. See moonlab.space/pricing for current plans. You get a fixed price after the free audit.

Common mistakes

Most disappointing WhatsApp projects fail for the same avoidable reasons.

• Using unofficial tools or bulk senders that automate WhatsApp Web. They are cheap until the number gets banned, and that number is often the one printed on every product.
• Messaging people who never opted in. It annoys customers, leads to blocks and reports, and can hurt your number's quality rating with Meta.
• Building a chatbot with ten menu levels. Customers want an answer or a person, not a phone tree in chat form.
• No hand-over to a human. Every flow needs a clear point where a real person takes over, and the team must see those chats quickly.
• Templates written as an afterthought. Rejected templates delay launch, so write them in plain language with clear variables before the build starts.
• Nobody owns it after launch. Prices change, products change and the bot keeps quoting last month's delivery charge.

When it is not worth it

If you get a handful of WhatsApp messages a day and one person answers them comfortably, the free Business app with quick replies and labels is probably enough. A paid build will not pay back.

It is also not worth automating a process that is not settled yet. If your delivery charges, return policy or booking rules change every week, fix the process first. Automation copies whatever you give it, including the confusion.

If most conversations are negotiations or sensitive cases, keep people in charge and automate only the reminders and status updates.

Get a free WhatsApp automation audit

To find out which job would save you the most time, book a free 30-minute audit at moonlab.space/contact. We look at how your messages actually come in, tell you what is worth automating and what is not, and you keep the list either way.

Related services: customer support automation at moonlab.space/services/customer-support, sales and lead follow-up at moonlab.space/services/sales-and-leads, and order and parcel updates for online shops at moonlab.space/services/e-commerce.