AI chatbots on WhatsApp save time when each one handles a few well-defined workflows: order status, bookings, lead qualification, common questions and a clean handoff to a person. Built on the WhatsApp Business Platform with approved templates and live data, these flows answer routine messages instantly and leave staff free for conversations that need judgement.
The WhatsApp Business Platform, accessed through Meta’s Cloud API or a business solution provider such as Twilio, 360dialog, Infobip or a CRM with built-in WhatsApp, lets companies connect bots and inboxes to WhatsApp. Business-initiated messages need pre-approved templates; customer messages open a 24-hour window for free-form replies. Pricing and policy details are set by Meta and change, so confirm current rules before building.
What should be in place before building workflows?
- A verified business and an approved display name.
- A provider or direct Cloud API setup connected to your inbox or CRM.
- Clear opt-in sources and an automatic opt-out command.
- API access to the systems the bot needs: orders, bookings, CRM.
- A shared inbox where human agents take over conversations.
- Approved templates for any message the business sends first.
Workflow 1: order status
Order questions are often the largest share of e-commerce messages and the easiest to automate.
- Customer asks about an order; the bot asks for the order number or recognises the phone number linked to recent orders.
- The bot queries the store or order system through an API.
- It replies with status, carrier and tracking link in a short message.
- If the order is delayed beyond the promised date, the bot apologises, gives the new estimate and offers a person.
- If the order cannot be found, it asks once more, then hands off with the details collected.
The AI model’s role is understanding varied wording, such as “where’s my stuff” or a voice-note transcript, and writing a natural reply. The facts come from the order system, never from the model.
Workflow 2: bookings and appointments
Clinics, salons, restaurants and service businesses can let customers book in the chat. The bot checks availability through the booking system’s API, offers a few slots as reply buttons, confirms the choice and sends a confirmation. A reminder template goes out before the appointment, with options to confirm or reschedule.
Keep rescheduling and cancellations in the flow. A booking bot that cannot cancel pushes the hard part onto staff anyway.
Workflow 3: lead qualification
For B2B and high-value services, click-to-WhatsApp ads on Facebook and Instagram start conversations with interested people. The bot asks two to four qualifying questions, such as company size, need and timing, using buttons where possible. It writes the answers into the CRM and routes qualified leads to a salesperson, with the conversation attached.
Do not interrogate. Every extra question loses some people. Ask only what sales needs to decide the next step.
Workflow 4: frequently asked questions
Opening hours, delivery areas, return policies, payment options and product availability are good FAQ topics. Ground the bot in an approved knowledge base, such as your FAQ page and policy documents, and instruct it to answer only from those sources. When the question falls outside, it says so and offers a person.
Review unanswered questions weekly. They show gaps in both the bot and the website.
Workflow 5: human handoff
Handoff is a workflow, not an afterthought.
- Triggers: the customer asks for a person, the bot fails twice, or the topic is restricted, such as complaints, refunds or health questions.
- The bot tells the customer a person will reply and gives a realistic time, especially outside working hours.
- The conversation, customer details and any order number move to the agent’s inbox.
- The agent replies within the 24-hour window, or uses a template if the window has closed.
- After resolution, the conversation is tagged so the team can see which topics need handoff most.
How do templates fit into the workflows?
Templates cover messages the business starts: order confirmations, shipping updates, appointment reminders and approved marketing. Meta classifies templates into categories such as utility, authentication and marketing, and pricing differs by category and country. Write utility templates for genuine service updates and keep marketing templates for opted-in customers.
Keep templates short, include variables only where needed, such as the customer’s name or order number, and add buttons for the next likely action. A shipping update with a “Track order” button and a “Talk to us” option resolves most follow-up questions before they are typed. Submit templates early, since wording rules are strict and approval may need revisions.
How do you measure the time saved?
Track the share of conversations resolved without a person, average first response time, handoff rate by topic, customer satisfaction after the chat, and opt-outs or blocks. Compare staff hours spent on WhatsApp before and after. For lead flows, measure qualified leads and the speed at which sales reaches them.
Which mistakes slow everything down?
Building one large bot that tries to handle every topic. Letting the model answer from memory instead of live data. Skipping template approval until launch week. Hiding the human option. And measuring only message volume, which can rise for bad reasons.
How Alien Road applies AI chatbots on WhatsApp
In a typical engagement, discovery samples recent WhatsApp and support conversations and tags them by topic, so we know which workflows will save the most time. Most clients start with two: order status or bookings, plus FAQ with handoff.
Setup connects the WhatsApp Business Platform through the client’s provider or CRM, links order or booking systems by API, writes and submits templates, and builds the handoff rules into the agents’ inbox. We test failure cases before launch.
Measurement reports resolution rate, response time, handoff topics, satisfaction and opt-outs monthly, with examples of conversations the bot handled badly and how they were fixed.
Where to start this week
Count last month’s WhatsApp messages by topic. Take the single largest routine topic, often order status, and map its workflow on paper: what the customer asks, what data the bot needs, what it replies and when it hands off. Check that your order system has an API the bot can call. That map is your first build ticket.
Keep reading: AI Marketing Agency · AI Marketing