WhatsApp chatbot · Visual builder

A WhatsApp chatbot you build by dragging,
and a human who takes over when it matters.

Most enquiries are the same eight questions. A bot should answer those in seconds, at 11pm, in the customer’s own words — and step aside the moment the conversation is worth a person. In TicAte you draw that on a canvas: blocks, arrows, and a live test beside it.

What is a WhatsApp chatbot?

A WhatsApp chatbot is an automated reply flow that runs on your WhatsApp Business number, answering common questions, showing menus and collecting details without an agent typing. In TicAte you build one on a visual canvas — a trigger, then blocks that send text, buttons, lists or media, ask a question and save the answer, call your own API, ask an AI agent, or hand the conversation to a person. It runs on Meta’s official WhatsApp Business API, so it obeys the same 24-hour window and template rules as everything else.

See it on your own enquiries

The blocks you get

Nine blocks, and no code anywhere

Each block does one thing. Wire them together and you have anything from a two-line auto-reply to a qualification flow that writes back to the CRM.

Keyword and catch-all triggers

Start on any first message, or only when the text matches your keywords. Fuzzy matching forgives “helo” and “enquery”, and the bot can be told to stay quiet on conversations a person already owns.

Buttons, lists and media

Reply buttons for a three-way choice, an interactive list for a longer menu, and image, document, audio or video blocks — the native WhatsApp controls, not a wall of “reply 1 for sales”.

Questions that stick to the record

Ask for a name, a city, a budget or a date, and the answer is written onto the contact as a real field — so the next agent, automation or broadcast segment can use it.

An AI step, where you want one

Drop an AI agent block into the flow for the open-ended part of the conversation, with a turn limit, then continue down the scripted path. Structure where you want structure, language where you need it.

Call your own systems

An HTTP block with GET or POST, your headers, and variables filled into the body — check stock, fetch an order status, create a ticket, then keep going with what came back.

Handover that actually happens

A handoff block assigns the conversation to the right team and stops the bot dead. Everything the bot collected is already on the record when the agent opens it.

Building one

From blank canvas to live bot

Pick what it should handle

Take the questions your team answers fifty times a week — hours, prices, location, order status, appointment booking — and decide which the bot owns end to end.

Draw the flow

Drag blocks onto the canvas and connect them. Buttons branch, questions store their answers, and any path can end in a handoff to a person.

Test it on your own number

Message the bot yourself and watch it walk the graph. Change a block, send again — no deploy step, no waiting.

Turn it on, and watch the sessions

Switch the bot live and every run is logged: what fired, which path it took, where it handed over. Tune it from what customers actually typed.

Bot: after-hours enquiries

TriggerAny message, 7pm–9am, unassigned only

Live

MenuSales · Support · Store timings

3 buttons

QuestionWhich city are you in?

→ contact

AI agentAnswers from your price list

Max 4 turns

HandoffAssign to Sales, stop the bot

On ask

Good to know

WhatsApp chatbot questions

Do I need to write code?

No. The builder is a canvas of blocks you connect, and everything configurable — keywords, button labels, the question text, which team a handoff goes to — is a form field. The HTTP block is the only place you would paste anything technical, and only if you want the bot to talk to your own system.

Can a customer always reach a person?

Yes, and it is one block. Any path can end in a handoff, the bot stops the moment it hands over, and you can tell it never to speak on a conversation an agent already owns. An AI step also has a turn limit, after which it gives up and fetches a human.

Will a chatbot get my number banned?

Not on the official API, used normally. TicAte runs on Meta's WhatsApp Cloud API and respects the 24-hour window and template rules — the bot replies inside an open conversation. Numbers get banned for unsolicited bulk messaging and unofficial automation tools, not for answering the people who messaged you.

Does it work in Indian languages?

The scripted blocks say whatever you type in them, in any language and any script. The AI step replies in the language the customer wrote in, including Tamil, Hindi and Malayalam alongside English.

What happens outside the 24-hour window?

A bot can only reply freely inside the 24-hour customer service window. Outside it, Meta requires an approved template — so re-engagement is a template broadcast or an automation, and TicAte writes and submits those templates for you.

How is this different from the automations?

The automation engine is trigger-condition-action: it fires once and does something. The chatbot builder holds a conversation across several messages, remembering where the customer is in the flow. Most workspaces use both.

Keep reading

Next to the chatbot

AI chatbot for WhatsApp

Your own model, your own price list and policies, and a handover the moment it is unsure.

WhatsApp Flows

When a menu is not enough: a real form, inside the chat, without sending anyone to a website.

WhatsApp Business API

How the official API works, what it costs, and how to get a number live in days.

A WhatsApp chatbot you build by dragging,and a human who takes over when it matters.