Chatbot BuilderAutomation

Answer the same five questions without being there

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.

No code
drag, drop, publish
24 hours
answered, including holidays
Clean handover
to a human on request

What you need to start

  • A connected WhatsApp number
  • A clear idea of the five questions you answer most often — that is the first bot

The problem

Half of every inbox is “what are your timings”, “do you deliver here”, “what does it cost”.

  • The same handful of questions consume most of the day.
  • Anything arriving after closing waits until morning, by which time they have asked someone else.
  • The genuinely interesting enquiries are buried under the routine ones.

Inside the panel

This is the screen you will work in

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.

app · Dashboard / Chatbot Builder

Chatbot Builder

Publish
Trigger

First message

Text

Hi! How can we help? 👋

Reply Buttons

Prices · Timings · Human

AI Reply

From your price list

Handover

Assign to agent

Test this flow
An illustration of the real panel, drawn from the same design system — not a live demo.

Step by step

How it actually works

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.

  1. 01

    Decide what starts it

    2 minutes

    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.

    • Keyword triggers with exact or contains matching
    • First-message triggers for anyone you have not spoken to before
    • Out-of-hours only, so daytime chats still go straight to a person
    • Ad-referral triggers, so a lead from an ad gets a different opening line
  2. 02

    Draw the flow

    20–30 minutes for a first bot

    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.

    • Message, question, button, list, condition, delay and jump nodes
    • Branches on what someone typed, a tag they carry, or a field you already hold
    • Media nodes for a menu, a price list or a location
    • You write every word it sends — nothing is generated behind your back
  3. 03

    Collect what you need to qualify them

    part of the 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.

    • Answers saved to contact fields, not just to the transcript
    • Validation on phone numbers, emails and dates so you do not store rubbish
    • Tags applied as they qualify — “bulk enquiry”, “out of area”
    • A CRM deal opened at the end, with everything it collected attached
  4. 04

    Point it at your own material

    10 minutes

    Give it your prices, policies and FAQs so its answers come from what is true about your business rather than from something it invented.

    • Answers drawn from the material you supply
    • Anything it cannot answer from that material goes to a human instead of guessing
    • Update the material and the answers change — no rebuilding the flow
  5. 05

    Set the handover rules

    5 minutes

    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.

    • “Talk to a human” stops the bot for that conversation immediately
    • The chat is tagged, assigned and flagged so your team knows it is now theirs
    • Any agent can take over mid-flow from the inbox at any time
    • The full bot transcript stays on the conversation, so nobody asks the customer to repeat themselves
  6. 06

    Test it, publish it, then watch it

    ongoing

    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.

    • Test mode that walks the flow without messaging real customers
    • Per-node completion, so you can see exactly where people leave
    • Version it, pause it, or switch it off entirely without deleting it

The routine questions stop reaching a person, and the ones that need a person arrive already answered halfway.

Setting it up

What you actually click

Six steps, in order, with the screen each one lives on. No developer and no integration project — this is all done in the panel.

Time to set up
about 30 minutes for a first bot
Before you start
A connected number, and the five questions you answer most often
Start free
  1. 1

    Create the bot

    Chatbot → New bot

    Name it for what it does — “after-hours enquiries” beats “Bot 1” the moment you have two of them.

  2. 2

    Set the trigger

    Chatbot → Trigger

    Keyword, first message from an unknown number, outside business hours, or an ad referral. Out-of-hours is the safest first bot.

  3. 3

    Drag out the flow

    Chatbot → Canvas

    Start with a Text block, then Reply Buttons for the three things people ask. Join the blocks by dragging from one handle to the next.

  4. 4

    Collect what qualifies them

    Canvas → Ask & Wait

    Ask for city, budget or requirement and save each answer to a contact field, so it is usable later rather than buried in a transcript.

  5. 5

    Add your own material

    AI → Knowledge

    Paste your prices and policies. The AI Reply block answers from this, and hands to a human for anything it cannot find there.

  6. 6

    Test it, then publish

    Chatbot → Test this flow

    Walk the flow yourself first. Publishing is one switch, and pausing it is the same switch — nothing is deleted.

The short version

What it does about it

01

Build it by dragging

Questions, buttons, conditions and replies. No code, and no developer waiting on a brief.

02

It knows when to stop

Ask for a human and the bot steps aside, marks the chat and tells your team.

03

It qualifies while you sleep

Collect budget, city, requirement — so the morning starts with a warm list, not a cold one.

04

Answers from your own material

Point it at your prices and policies so it answers from what is true, not what it invented.

05

Nothing it sends is a surprise

You write every message. What it says is exactly what you typed.

In detail

Everything it does

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.

Building

  • Drag-and-drop canvas, no code anywhere
  • Message, question, button, list, condition, delay and jump nodes
  • Branching on answers, tags or contact fields
  • Media nodes — image, document, location
  • Multiple flows, each with its own trigger

Triggers

  • Keyword, exact or contains
  • First message from an unknown number
  • Outside business hours only
  • Click-to-WhatsApp ad referral
  • Button press from a previous flow

What it does with the answers

  • Saves them to contact fields
  • Applies tags as it qualifies
  • Opens a CRM deal with the answers attached
  • Triggers an automation for anything else you want to happen

Handover

  • Stops on request, on frustration, or after failed attempts
  • Assigns and tags the chat for your team
  • Agents can take over mid-flow from the inbox
  • Full transcript kept on the conversation

In practice

Three businesses, three ways

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.

A real-estate agent

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.

A service business at night

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

The specifics

Limits and facts

Bots per workspace
Metered per plan
Nodes per flow
No practical limit
Languages
Whatever you write — the bot sends your words
Handover
Instant, to any available agent

What you need first

  • A connected WhatsApp number
  • A clear idea of the five questions you answer most often — that is the first bot

What is metered

  • ChatbotsUnlimited

Pricing

Two ways to get it

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.

On its own

Chatbot Builder

₹399/month

What is metered

  • ChatbotsUnlimited
Add this module

Or as part of a plan

Plans that include it

A bundle is usually cheaper than three modules bought separately — and add-ons only ever add, so nothing you already have is affected.

Questions

Will it sound robotic?

That is up to your copy. You write every message it sends — nothing is generated behind your back.

What if it gets something wrong?

Any agent can take over mid-conversation, and the bot stands down for that chat immediately.

Do I need a developer to build one?

No. It is a drag-and-drop canvas, and a useful first bot usually takes under half an hour.

Can it run only at night?

Yes. Trigger it outside business hours and daytime conversations go straight to a person as normal.

What happens to what it collected?

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.

Try it before you pay anything

Connect a number, import your contacts, and see whether it fits how you work.