Build a No-Code WhatsApp Support Bot in an Afternoon

Most support questions are the same handful asked over and over: "Where's my invoice?", "How do I reset this?", "Can I speak to someone?". You don't need a developer, a chatbot platform subscription, or a machine-learning degree to answer them automatically. With Cliqtel's WhatsApp Flow Builder you can drag together a working support bot in a single afternoon and have it replying to customers 24/7 by the end of the day.

This guide walks you through building a real, useful support bot from scratch: a friendly welcome, a menu that routes billing and technical questions, an after-hours message, and a clean handoff to a human when the bot has done its job. Everything happens visually in your Cliqtel WhatsApp workspace — no code required. The runtime is rule-based and deterministic, so the bot does exactly what you wire up, every single time.

What you'll build

By the end you'll have a support bot that:

• Greets every new message instantly, day or night.
• Offers a three-option menu: Billing, Technical help, and Talk to a person.
• Answers common billing questions with an instant FAQ reply.
• Collects a description of technical issues, then routes them to a human.
• Sends after-hours contacts a "we're closed, we'll reply in the morning" message so nobody is left wondering.

The payoff is real: an instant first response on every conversation, common FAQs deflected automatically, and only the questions that genuinely need a person landing in your team's lap.

Before you start

You'll need a WhatsApp number connected in Cliqtel. If you haven't done that yet, the connect-first onboarding wizard takes a few minutes — see the Flow Builder documentation for the full setup. Once your number is live, open the portal and go to My Numbers → Messaging — WhatsApp → Flows. That's home base for everything below.

Step 1 — Open the Flow Builder and add the trigger

On the Flows tab, create a new flow and give it a clear name like "Support bot". You'll land on a blank canvas with a node palette down the left side.

Every flow begins with a single "Message received" trigger. This fires whenever a customer messages your WhatsApp number. Drag your first node onto the canvas and connect the trigger to it with a labelled connector — that connection is the on-ramp for every conversation.

Step 2 — Greet the customer with a Message node

Drag a Message node onto the canvas and wire the trigger into it. This is your welcome. Keep it warm and short:

"Hi {{name}} 👋 Thanks for messaging Cliqtel support. I can help you right away — what do you need?"

Notice the {{name}} variable. Message nodes support variables so replies feel personal instead of robotic. You'll use these throughout the flow to echo back things the customer tells you.

Step 3 — Add a Menu to route the conversation

Drag a Menu (list) node in after the welcome. A menu can hold up to 10 options; we only need three:

1. Billing — questions about invoices and payments
2. Technical help — something isn't working
3. Talk to a person — straight to a human

Each menu option becomes its own labelled connector you can drag to a different target node. That's how you branch the conversation: one menu, three paths. (If you prefer tappable quick-reply buttons over a list, a Buttons node does the same job for up to 3 options.)

Step 4 — Wire the Billing path to an FAQ reply

Connect the Billing option to a new Message node containing your most-asked billing answer — for example, where to download invoices, when renewals are charged in €, and how to top up a wallet. This is pure deflection: the customer gets a complete answer in seconds and your team never touches it.

Follow the FAQ message with a small Buttons node offering "That helped, thanks" and "I still need help". Wire the second button onward to the handoff you'll build in Step 6 — so the bot resolves the easy cases and escalates the rest.

Step 5 — Collect the issue on the Technical path

Connect the Technical help option to a Collect node. A Collect node saves the customer's next reply into a variable — call it {{issue}}. Prompt them with something like:

"Sure — can you briefly describe what's going wrong?"

Now your agent gets context before they even open the chat. After the Collect node, wire the path into a Handoff node so a real person picks it up with the issue already in hand.

Step 6 — Send both "human" paths to a Handoff

Add a Handoff node. This hands the conversation to a live agent in your team inbox. Wire two things into it:

• The "Talk to a person" menu option, directly — some customers just want a human, and that's fine.
• The end of the Technical help path, after the Collect node, so the agent arrives with the {{issue}} description ready.

A short Message before the handoff sets expectations: "Connecting you to the team now — one moment."

Step 7 — Handle after-hours with a Business hours node

Add a Business hours node right after the welcome, before the menu. It routes the conversation down an open path or a closed path based on your configured hours.

• Open → continue to the menu you built above.
• Closed → a Message node: "Thanks for reaching out! We're closed right now, but we've logged your message and will reply first thing in the morning." then an End node.

Nobody sits in silence after hours, and your team starts the day with a tidy queue instead of a pile of "is anyone there?" messages.

Step 8 — Test in the simulator, then Publish

Before anything goes live, use the built-in Test simulator to run through the flow exactly as a customer would. Try each menu option, type a fake technical issue, and check the after-hours branch. Fix any loose connectors — a menu option with nowhere to go is the most common gotcha.

When it behaves the way you want, hit Save to keep a draft, then Publish to take it live. The moment you publish, your next incoming WhatsApp message runs through the bot.

A quick map of the nodes you used

You didn't touch the other nodes today, but they're waiting when you grow: Condition branches on saved data, Template sends an approved WhatsApp template, Wait pauses before continuing, and API / Webhook calls an external system.

Where to go next

Once your no-code bot is earning its keep, a few natural upgrades are worth exploring:

• Look up real data. The API / Webhook node lets the bot check an order status or account balance mid-conversation — see the Flow Builder docs for the developer API.
• Send richer messages. Add images, product cards, and interactive layouts with WhatsApp rich messages.
• Reach out proactively. Pair your bot with WhatsApp campaigns to send approved templates and follow-ups at scale.

None of that is required to get value today — the core support bot above is genuinely useful on its own.

Start building

An always-on first responder that deflects your FAQs and routes the rest to the right person is a few drag-and-drop nodes away — and you can have it live before the afternoon is out. Open My Numbers → Messaging — WhatsApp → Flows in your Cliqtel portal and follow the step-by-step WhatsApp Flow Builder guide to build yours now.