--- title: "How to Build a WhatsApp Chatbot Without Code: Step-by-Step" description: "How to build a WhatsApp chatbot without code: pick goals, design flows with buttons and lists, add Arabic, hand over to agents, test, follow Meta rules and track metrics." canonical: "https://omnichannels.ai/blog/whatsapp-chatbot-no-code-guide/" language: "en" updated: "2026-11-02" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" category: "whatsapp" primaryQuery: "how to build a whatsapp chatbot" keywords: ["how to build a whatsapp chatbot", "whatsapp chatbot no code", "create whatsapp bot without coding", "whatsapp chatbot flow design", "arabic whatsapp chatbot", "whatsapp chatbot best practices", "whatsapp bot human handover"] published: "2026-11-02" author: "OmniChannels.ai Editorial Team" reviewer: "BroadNet Messaging Solutions Team" readingMinutes: 11 answer: "To build a WhatsApp chatbot without code, get a WhatsApp Business API number through a provider, list the five to ten questions customers ask most, design a flow with buttons and lists for each, add Arabic and English versions, set a handover to a human agent, test with real phones, then launch and track containment, handover and satisfaction. Meta allows automation but expects clear escalation paths." takeaways: ["A chatbot runs on the WhatsApp Business API, not the free WhatsApp Business app, so the first step is an API number from a provider.", "Start with the five to ten requests that make up most of your conversations; a narrow bot that works beats a broad bot that guesses.", "Reply buttons allow up to three choices and list messages up to ten rows, so design menus around those limits.", "WhatsApp's business policy allows automation when responding inside the 24-hour customer service window but expects prompt, clear and direct escalation paths such as transfer to a human agent.", "Meta's terms restrict AI providers whose AI is the primary functionality offered on the platform; a business using AI inside its own customer service is a different case, but read the current terms."] faq: - q: "Can I build a WhatsApp chatbot without coding?" a: "Yes, for common cases. Menu and keyword flows with buttons, lists and fixed answers can be configured without writing code, and simple lookups can call your systems through an API connection that a developer sets up once. You still need a WhatsApp Business API number and approved templates for messages your business starts." - q: "Do I need the WhatsApp Business API to build a chatbot?" a: "Yes, for a full chatbot. The WhatsApp Business app has simple automation such as greeting and away messages, but flows with buttons, lookups, handover to many agents and integrations run on the WhatsApp Business API through a provider. The API number is a different setup from a phone number used in the app, so plan the move." - q: "How long does it take to build a WhatsApp chatbot?" a: "It depends on scope, approvals and who decides the content. The slow parts are usually not the bot itself but Meta business verification, template approval and agreeing the answers internally. Start with a small flow, launch it to a limited audience and expand. We do not promise approval times, because Meta decides them." - q: "Are chatbots allowed on WhatsApp?" a: "Yes. WhatsApp's business policy allows automation when responding inside the 24-hour window and expects prompt, clear and direct escalation paths such as transfer to a human agent. Meta's terms also restrict AI providers whose AI is the primary offering on the platform. Using a bot inside your own customer service is a different case; check the current terms." - q: "What is the difference between a rule-based chatbot and an AI agent?" a: "A rule-based or flow chatbot follows paths you wrote in advance: menus, keywords and fixed answers, so every response is predictable. An AI agent understands free text, answers from a knowledge base and can take actions through connected tools. Many businesses start with a flow bot and add an AI agent for open-ended questions, always with human handover." - q: "How do I make a WhatsApp chatbot work in Arabic and English?" a: "Write native Arabic copy rather than translating word for word, ask the customer to choose a language in the first message, and keep one flow with two language versions. Meta supports Arabic template languages such as ar, ar_EG and ar_AE. Preview every message on a real phone, because right-to-left text and variables can display unexpectedly." sources: - title: "WhatsApp Business Messaging Policy" url: "https://whatsappbusiness.com/policy/" - title: "Meta Terms for WhatsApp Business Platform (section 4.7, AI Providers)" url: "https://www.facebook.com/legal/Meta-Terms-for-WhatsApp-Business-Platform" - title: "Send messages and the customer service window, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages" - title: "Interactive reply buttons messages, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/interactive-reply-buttons-messages" - title: "Interactive list messages, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/interactive-list-messages" - title: "Supported languages for message templates, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/supported-languages" --- # How to Build a WhatsApp Chatbot Without Code: Step-by-Step Canonical: https://omnichannels.ai/blog/whatsapp-chatbot-no-code-guide/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies This guide is for business owners, marketing managers and support leads who want a working WhatsApp chatbot without writing code. It walks through eight steps from goals to launch, with design limits from Meta, Arabic and English guidance, handover rules and the metrics to track. ## What is a WhatsApp chatbot? A WhatsApp chatbot is an automated assistant that receives customer messages on a WhatsApp Business API number and replies with answers, menus or actions, handing over to a person when needed. The customer sees a normal WhatsApp chat. There are two kinds: - **Flow (rule-based) chatbot:** follows paths you design: welcome menu, buttons, lists, keywords, fixed answers and lookups. Predictable and easy to review. - **AI agent:** understands free text, answers from a knowledge base and can use tools. More flexible, and needs stronger guardrails. See [WhatsApp AI agents for customer service](/blog/whatsapp-ai-agent-customer-service/). Most teams should start with a flow bot for the top requests and add an AI agent once the basics work. ## What do you need before you build? You need a WhatsApp Business API number, a verified business with a display name, and a few approved templates for messages your business starts. Customer-started chats do not need templates. 1. **A WhatsApp Business API number** from a provider. The free WhatsApp Business app is a different product; see [API vs Business app](/blog/whatsapp-business-api-vs-business-app/) and [how to set up the API](/blog/how-to-set-up-whatsapp-business-api/). 2. **Business verification and display name.** Use the [readiness checklist](/tools/whatsapp-api-readiness-checklist/) to prepare documents. 3. **A shared inbox** where agents take over. See the [Omni Inbox](/platform/unified-inbox/). 4. **Content owners.** Someone has to approve answers on prices policy, refunds and opening hours. ## How do you build a WhatsApp chatbot without code? 8 steps Follow these steps in order. Each one reduces the risk of the next. ### Step 1: Set one clear goal Pick one job for version one: answer FAQs, qualify leads, book appointments, give order status or collect feedback. Write one measurable target, such as "answer the five most common questions without an agent". ### Step 2: Find the top intents Export or read 100 recent conversations and tag each by topic. The five to ten topics at the top become your intents. Add "talk to a person" as an intent from day one. ### Step 3: Write the flow on paper Draw each path: trigger, bot message, customer choices, outcome. Keep every path under four steps. A customer should reach an answer or a person quickly. ### Step 4: Choose the right message format Use the format that fits the choice, within Meta's limits: | Format | Limit | Use for | |---|---|---| | Reply buttons | Up to 3 buttons per message | Yes/no, confirm/reschedule, language choice | | List message | Up to 10 rows in a menu | Main menu, branches, time slots | | CTA URL button | One link button | Tracking page, payment page, forms | | Free text prompt | Open reply | Order number, date, name | | WhatsApp Flow | Form-like screens | Longer data capture; see [WhatsApp Flows](/blog/whatsapp-flows-guide/) | More detail on each format is in [interactive messages: buttons and lists](/blog/whatsapp-interactive-messages-buttons-lists/). If you have more than ten options, group them into two levels. ### Step 5: Write copy in Arabic and English Write each message natively in both languages and ask for the language in the first reply. Rules that avoid common problems: - One idea per message; WhatsApp is read on small screens. - Arabic is right to left; preview variables, numbers and mixed Latin text on a real phone. - Meta lists Arabic template languages ar, ar_EG and ar_AE; check its list when choosing the template language for Saudi or other markets. - Keep the tone consistent with your brand, and read [Arabic customer messaging best practices](/blog/arabic-customer-messaging-best-practices/). ### Step 6: Design the handover Every path needs a way to reach a person. WhatsApp's business policy expects prompt, clear and direct escalation paths where automation is used, such as in-chat transfer to a human agent. Define triggers: - The customer asks for a person, or types words such as "agent". - The bot fails to understand twice in a row. - The topic is sensitive: a complaint, payment dispute, medical issue. - A high-value customer or lead is identified. When the bot hands over, pass the conversation history, tell the customer what happens next and, outside business hours, when a reply will come. Our guide to [chatbot to human handoff](/blog/whatsapp-chatbot-human-handoff/) has the design details. ### Step 7: Test with real phones Test before any customer sees it. A checklist: 1. Every button and list row leads where it should. 2. Typos, voice notes, images and emoji get a polite fallback, not silence. 3. "Agent" works from every screen. 4. Arabic and English versions both display correctly. 5. The bot behaves correctly after the 24-hour window closes: free-form messages are allowed only inside the window; after it closes you can only send approved templates. 6. Lookups return correct data and fail gracefully when your system is down. 7. Test numbers and data are not left in production. Test access should go to your own verified numbers first, then a small group of staff, then a limited audience. ### Step 8: Launch small, measure and expand Announce the bot on your website, QR codes and ads. Review transcripts weekly for the first month, fix the top three failures and add intents one at a time. ## What does Meta allow? Policy for chatbots and AI Meta allows automation on the WhatsApp Business Platform but sets conditions: opt-in for contacting people, escalation paths and respect for opt-outs. - **Opt-in:** WhatsApp's policy lets you contact people only if they gave you their phone number or username and agreed to hear from you. A customer who messages you first can be answered in the 24-hour window. - **Automation:** the policy says you may use automation when responding during the 24-hour window, and expects prompt, clear and direct escalation paths, such as in-chat transfer to a human agent. - **Opt-out:** you must respect requests to block, discontinue or opt out. - **AI providers:** Meta's Terms for the WhatsApp Business Platform contain a section on AI Providers (section 4.7) that restricts developers of AI technologies from using the platform where the AI is the primary functionality offered, and prohibits using platform data to train AI models when a business retains an AI provider. A business running a bot inside its own customer service is a different situation from distributing a general-purpose assistant, but check the current terms with your legal team, because they are updated. Rules change, so always confirm on Meta's pages linked in the sources. ## Flow chatbot or AI agent: which one should you build? Choose a flow bot when questions are predictable and answers must be exact, and an AI agent when customers phrase things freely or the bot must act in your systems. | | Flow chatbot | AI agent | |---|---|---| | Input | Buttons, lists, keywords | Free text in English or Arabic | | Answers | Written in advance | Grounded in a knowledge base | | Predictability | High | Needs guardrails and review | | Good for | Opening hours, order status, bookings, lead capture | Open-ended questions, multi-step requests | | Risk | Dead ends if a path is missing | Wrong or invented answers if not grounded | | Handover | Triggered by rules | Triggered by rules and confidence | You can combine them: a flow handles the menu and an AI agent handles free text, both with a route to a person. ## Worked example: a Doha dental clinic "Doha Smile Clinic", a synthetic clinic, chooses one goal: reduce phone calls about appointments. Its 100-conversation review shows five intents: book, reschedule, opening hours, location and prices-by-treatment. | Step | Bot message | Customer choice | Outcome | |---|---|---|---| | 1 | Language: Arabic or English? | Two buttons | Sets language | | 2 | Main menu (list): book, reschedule, hours, location, talk to a person | One row | Routes the flow | | 3 | Reschedule: asks for the booking reference | Free text | API lookup of the appointment | | 4 | Offers three available slots | Three buttons | Confirms, sends a confirmation | | 5 | If no match after two tries | None | Hands over to a receptionist with history | On treatment prices the bot does not guess: it answers with the clinic's published information or hands over. After launch, the team reviews transcripts for a month and adds a "bring documents" reminder as an approved template. ## Which metrics should you track? Track resolution without an agent, handover, fallback and satisfaction, and compare them week by week. | Metric | Formula | What it tells you | |---|---|---| | Containment rate | Conversations resolved by the bot with a success signal ÷ conversations started with the bot | How much the bot really handles | | Handover rate | Conversations passed to an agent ÷ bot conversations | Whether the bot is too narrow or too cautious | | Fallback rate | "I did not understand" replies ÷ bot messages | Gaps in intents or menus | | Drop-off per step | Customers who stop at each step ÷ customers reaching it | Confusing screens | | CSAT after bot | Satisfied ÷ responses | Quality as customers see it | | First response time | See [first response time](/blog/first-response-time-customer-service/) | Speed for the conversations that do reach a person | Count a conversation as contained only with a success signal, such as a tap on "this answered my question", a completed booking, or no contact on the same topic within a few days. Survey design is in [CSAT, NPS and CES](/blog/csat-nps-ces-customer-satisfaction-metrics/). ## What mistakes should you avoid? - **Trying to answer everything on day one.** Start with the top intents. - **No visible way to reach a person.** Policy and customers both expect one. - **Menus with too many options.** Group into two levels. - **Silent failures.** Always send a fallback message. - **Machine-translated Arabic.** Have a native speaker review. - **Ignoring the 24-hour window.** After it closes, a bot can only send approved templates. - **Promotions inside service flows.** Marketing content has its own template category and opt-in rules. - **Never reading transcripts.** They are the cheapest source of improvements. ## How OmniChannels.ai helps OmniChannels.ai, powered by BroadNet Technologies, provides [chatbots](/platform/chatbots/) with menu, keyword, button and list flows, API lookups and handover to the Omni Inbox, in English and Arabic. For free-text questions, [AI agents](/platform/ai-agents/) powered by BroadNet AI add knowledge-base answers, tool use and human handover. BroadNet is an official Meta Business Solution Provider, and our team handles WhatsApp onboarding and registrations with you. Book a demo and bring your top ten customer questions.