How to Build Your First Chatbot on the WhatsApp Business API
A working WhatsApp chatbot is not a giant AI project — it's a well-structured flow that greets a customer, answers the questions they actually ask, and hands off to a human when it should. This tutorial walks you through building your first bot on the official WhatsApp Business API with InfiQ, from onboarding your number to going live. You'll set up a greeting, wire up quick-reply buttons, connect a template for anything sent outside the 24-hour service window, test it against your own number, and publish. No code is required for the core flow, and every step below is specific to how the WhatsApp Business API actually behaves — including where messages are free and where they're billed.
What you'll do
Onboard your number with InfiQ, design a greeting and menu with quick-reply buttons, add an approved template for messages sent outside the free 24-hour window, test end-to-end on your own phone, then go live and watch quality rating and delivery.Step 1 — Get your number onboarded and verified
Before you can build anything, you need a live WhatsApp Business API sender. InfiQ handles the Meta onboarding so you're not wrestling with raw Graph API calls: you connect a phone number that isn't already tied to a consumer WhatsApp or WhatsApp Business (the standalone app) account, complete Meta Business verification, and let InfiQ provision the number against your WhatsApp Business Account. Your business retains ownership of that account and its Business-Scoped User IDs (BSUIDs) — the identifiers Meta uses for contacts under the 2026 usernames change — so you're never locked in. Give this step a little lead time: verification and display-name approval are the parts most likely to add a day or two, and nothing downstream works until the number shows as connected.
- Pick a phone number with no existing WhatsApp/WhatsApp Business app account on it
- Complete Meta Business Manager verification (keep your registration documents handy)
- Submit a display name that matches your brand so it clears review the first time
- Confirm the number reads as Connected in InfiQ before moving on
Step 2 — Design the conversation flow, not just replies
Sketch the bot before you build it. The best first chatbots do three things well: welcome the user, present a short menu of the 3–5 things people genuinely message you about (order status, pricing, book a call, talk to a human), and route each choice to a clear answer. In InfiQ's no-code builder you assemble this visually — a greeting node, quick-reply or list buttons for the menu, and a response for each branch. Keep it shallow. A user who taps 'Order status' should reach an answer or a human in one or two steps, not five. Always include an explicit 'Talk to an agent' exit so the bot never traps someone in a loop, and write in the plain, friendly tone your customers use on WhatsApp.
- Start with a greeting that states who you are and what the bot can do
- Offer a menu of the top 3–5 real intents using quick-reply buttons
- Give every branch a clear answer or a fast path to a human
- Add a visible 'Talk to an agent' option in every menu
Step 3 — Add a template for anything sent outside the free window
Here's the rule that trips up most beginners. When a customer messages you first, you get a 24-hour service window during which you can reply with free-form messages at no messaging charge — that window is free, not a billing unit. But if you want to message a customer who hasn't written to you (a re-engagement nudge, an order update after the window closes, an OTP), you must use a pre-approved message template. Templates are categorised as marketing, utility, or authentication, and since Meta moved off per-conversation pricing on 1 July 2025, WhatsApp bills per delivered message according to that category. Choosing the right category matters twice over: it's the difference between approval and rejection, and utility/authentication rates differ from marketing rates. Build one utility template (for example, an order or booking confirmation) as part of this tutorial so your bot can reach out proactively, and submit it early since template review takes time.
- Free-form replies are free only inside the 24-hour service window after a user messages you
- To start a conversation or reply after the window, use an approved template
- Pick the correct category — marketing, utility, or authentication — for both approval and cost
- Remember: billing is per delivered message by category, not per conversation
Step 4 — Test end-to-end before anyone else sees it
Send the bot to yourself first. Message the number from your own phone, walk every menu branch, and confirm each button does what its label promises. Then close the 24-hour window (or wait it out) and trigger your template to verify a proactive message arrives, renders correctly, and shows the right variables filled in. Watch for the small stuff that embarrasses you live: a button that leads nowhere, a variable that prints as {{1}} instead of the customer's name, an emoji that breaks the layout, or a template still stuck in 'Pending' review. Testing against a real handset — not just the builder preview — is the single highest-value habit in this whole process.
- Message the number yourself and click through every branch
- Trigger your template and check variables render with real values
- Confirm delivered and read receipts are flowing back into InfiQ
- Fix dead-end buttons and any 'Pending' templates before launch
Step 5 — Go live and watch the signals that matter
Enabling the bot for customers is one toggle; keeping it healthy is the ongoing work. After launch, monitor two things closely. First, your delivery and read status — a sudden drop usually means a template problem, an opt-in gap, or an unverified number under load. Second, your quality rating: Meta scores your number based on how customers react (blocks and 'not useful' reports drag it down), and a low rating can throttle how many people you can message per day. Only send to people who opted in, keep marketing templates genuinely relevant, and don't blast a brand-new number with high volume on day one — ramp gradually so Meta's systems learn your number is trustworthy. Use InfiQ's India-based support if a template gets rejected or your rating dips; catching it early keeps your bot sending.
- Enable for customers, then watch delivery, read, and failure rates daily
- Track your number's quality rating and act if it slips to medium or low
- Send only to opted-in contacts and keep marketing content relevant
- Warm up a new number gradually instead of a first-day high-volume blast