A restaurant
Timings, menu and delivery area asked forty times a day.
→A three-node flow answers all of them, with a “talk to us” button for anything else.
Chatbot BuilderAutomation
A no-code flow builder that handles the routine, qualifies the lead, and hands over to a human the moment someone asks for one.
The routine is answered instantly, at any hour, and a person only sees the conversations that need one.
What you need to start
The problem
“Half of every inbox is “what are your timings”, “do you deliver here”, “what does it cost”.”
Inside the panel
Not a stock illustration — the real layout, the real filters, the real labels from the module itself. You will find it at Dashboard → Services → Chatbot.
Blocks
First message
Hi! How can we help? 👋
Prices · Timings · Human
From your price list
Assign to agent
Step by step
From the first day to steady state, in 6 steps. Every one of these is something the panel genuinely does — nothing here is on a roadmap.
A bot can trigger on a first message from an unknown number, a keyword, a button press, a click-to-WhatsApp ad, or only outside business hours.
Drag nodes onto a canvas and join them. Ask a question, offer buttons, branch on the answer, send an image or a document, wait, or jump to another flow.
Ask for city, budget, product or appointment slot and save each answer onto the contact. The morning starts with a warm list rather than a cold one.
Give it your prices, policies and FAQs so its answers come from what is true about your business rather than from something it invented.
Decide exactly when the bot steps aside: on request, on frustration, after a set number of failed attempts, or at a specific point in the flow.
Run the flow against yourself before it goes live. Once published, look at where people drop out — that node is almost always badly worded rather than badly built.
The routine questions stop reaching a person, and the ones that need a person arrive already answered halfway.
Setting it up
Six steps, in order, with the screen each one lives on. No developer and no integration project — this is all done in the panel.
Chatbot → New botName it for what it does — “after-hours enquiries” beats “Bot 1” the moment you have two of them.
Chatbot → TriggerKeyword, first message from an unknown number, outside business hours, or an ad referral. Out-of-hours is the safest first bot.
Chatbot → CanvasStart with a Text block, then Reply Buttons for the three things people ask. Join the blocks by dragging from one handle to the next.
Canvas → Ask & WaitAsk for city, budget or requirement and save each answer to a contact field, so it is usable later rather than buried in a transcript.
AI → KnowledgePaste your prices and policies. The AI Reply block answers from this, and hands to a human for anything it cannot find there.
Chatbot → Test this flowWalk the flow yourself first. Publishing is one switch, and pausing it is the same switch — nothing is deleted.
The short version
Questions, buttons, conditions and replies. No code, and no developer waiting on a brief.
Ask for a human and the bot steps aside, marks the chat and tells your team.
Collect budget, city, requirement — so the morning starts with a warm list, not a cold one.
Point it at your prices and policies so it answers from what is true, not what it invented.
You write every message. What it says is exactly what you typed.
In detail
The whole list, grouped. If something you need is not here, ask — we would rather tell you it does not exist than let you find out in week two.
In practice
Timings, menu and delivery area asked forty times a day.
→A three-node flow answers all of them, with a “talk to us” button for anything else.
Enquiries need budget and locality before they are worth a call.
→The bot asks both, tags the lead, and only qualified ones reach a person.
Half the enquiries arrive after 8pm.
→An out-of-hours flow collects the details and books a callback slot for the morning.
Before you commit
Limits and facts
What you need first
What is metered
Pricing
Take this module on its own, or as part of a plan that includes it. Either way the price is the software only — WhatsApp conversations are billed to you by Meta at their rates.
Or as part of a plan
A bundle is usually cheaper than three modules bought separately — and add-ons only ever add, so nothing you already have is affected.
That is up to your copy. You write every message it sends — nothing is generated behind your back.
Any agent can take over mid-conversation, and the bot stands down for that chat immediately.
No. It is a drag-and-drop canvas, and a useful first bot usually takes under half an hour.
Yes. Trigger it outside business hours and daytime conversations go straight to a person as normal.
It is saved to the contact and, if you want, opened as a CRM deal — so the answers are usable rather than buried in a transcript.
Works well with
Stop passing a phone around. Every conversation in one place, assigned to a person, with private notes, tags and a clock on how long someone has been waiting.
From ₹299/moOne rule can tag a chat, open a CRM deal, assign an agent and alert your team. It runs whether or not anyone is watching.
From ₹299/moPipelines, stages, tasks and history — with leads created from WhatsApp conversations instead of typed in again afterwards.
From ₹399/moConnect a number, import your contacts, and see whether it fits how you work.