WhatsApp Chatbot Builder: Automate Customer Support Without Writing Code

A WhatsApp chatbot can handle the repetitive questions your support team answers every day: store hours, order status, pricing, return policy, booking availability. Done well, it resolves a meaningful share of inbound conversations without any human involvement — freeing your team to focus on the complex ones. How large that share gets depends entirely on how repetitive your inbound mix is, so measure it on your own traffic rather than trusting a headline figure.

This guide shows you how to build one with Wasaas's no-code chatbot flow builder.

How Wasaas chatbot flows work

The flow builder is built around keyword triggers. When someone sends a message containing a keyword (or phrase) you define, the chatbot sends back a pre-written reply. Triggers can be:

• Exact match — the message is exactly "price" or "hi"
• Contains — the message includes "delivery" anywhere in the text
• Regex — for advanced pattern matching (e.g. order numbers)

Each trigger has a corresponding reply that can be plain text, an image, a document, or a list of options for the user to choose from.

Step 1 — Plan your conversation flows

Before opening the builder, sketch the questions your customers ask most often. Group them into categories:

• General info (hours, location, contact)
• Orders (status, cancellation, returns)
• Pricing (product costs, plans, discounts)
• Support (how to use your product)

Map out 5–10 of the highest-volume questions. These become your first chatbot flows.

Step 2 — Create your welcome message

The most important trigger is the one that fires when someone first messages you. Common triggers: hi, hello, مرحبا, or a default fallback (fires when no other trigger matches).

Your welcome reply should tell the customer what the bot can help with and list the keywords they can use:

"Hi! 👋 Welcome to Acme Support. Reply with:
1️⃣ PRICE — for pricing
2️⃣ ORDER — to track your order
3️⃣ RETURN — for returns & refunds
Or type your question and a human agent will respond shortly."

If you would rather drive this from code, the WhatsApp chatbot API page covers how inbound messages reach the flow engine, how trigger matching actually works, and what the endpoint returns.

Step 3 — Build individual reply flows

For each keyword, create a new flow in the Chatbot Flows section of the dashboard — or, if you'd rather script this instead of clicking through the UI for every flow, the Chatbot Flow API exposes the same create/edit/delete operations over REST:

1. Set the trigger keyword (e.g. "PRICE" or "order")
2. Write the reply message (text, image, or document)
3. Optionally add a follow-up — a second message sent a few seconds later with more detail or a call-to-action link

Example pricing flow:

Trigger: "PRICE" or "pricing" or "cost"

Reply:

"Here are our current plans 📋
• Starter: $29/mo — 2 sessions, 5,000 messages
• Business: $79/mo — 5 sessions, 20,000 messages
• Enterprise: $149/mo — unlimited sessions & messages

Start your free 7-day trial at wasaas.org/register"

Substitute your own plans, naturally — and if you are quoting Wasaas pricing to your own customers, take the current figures from the pricing page rather than from this example.

Step 4 — Handle fallbacks gracefully

Not every message will match a trigger. Set up a default fallback flow that fires when nothing else matches. Good fallback replies:

• Acknowledge the message: "Thanks for reaching out! 🙏"
• Give options: list the keywords the bot understands
• Set expectations: "A human agent will reply within 2 hours during business hours."
• Offer an alternative: "Or email us at support@example.com"

A graceful fallback prevents frustrated customers who feel ignored when the bot cannot answer.

Step 5 — Review conversation history

The Messages section of the dashboard shows every conversation, including which bot flow fired and what the customer replied. This is invaluable for improving your flows: look for messages that hit the fallback repeatedly — those are candidates for new triggers.

Review your fallback conversations weekly for the first month, then monthly once flows are stable.

Combining bots and humans

A chatbot works best as a first-response layer, not a replacement for human support. Common hybrid patterns:

• Bot handles FAQs instantly, escalates complex issues to a human agent
• Bot collects context (name, order number, issue type) before the human takes over — saves the agent time
• Bot handles everything outside business hours, human team picks up in the morning

Advanced: using the API for dynamic chatbot replies

For more complex workflows — looking up a real order status from your database, personalising replies with the customer's name, or triggering actions in your CRM — the no-code flows will not be enough on their own, because Wasaas does not push inbound events to your server. What you can do instead is have your own WhatsApp service fan the inbound message out: post it to /api/v1/incoming so the keyword flows still run, and to your own endpoint so your code can query your database and reply through the Wasaas send API with dynamic content.

Getting started

The Wasaas chatbot builder is included in all plans. Sign up for a free 7-day trial, connect your WhatsApp number, and you can have your first flow running in under 20 minutes.