Anyone with a price list
People message “price” and wait.
→The rule replies with the list, tags the chat, opens a deal and tells the sales channel — in under a second.
AutomationsAutomation
One rule can tag a chat, open a CRM deal, assign an agent and alert your team. It runs whether or not anyone is watching.
The boring steps happen every time, in order, with a record of what ran and why.
What you need to start
The problem
“The follow-up everyone agreed to do, that nobody remembers to do.”
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 → Automation.
Message contains “price”
Trigger · incoming WhatsApp message
Contact is not tagged “Customer”
Condition · all of 1 must match
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.
Something that happens in the platform starts the rule: a keyword arriving, a first message, a tag being applied, a deal moving stage, a deal won or lost, a campaign reply, an ad lead.
A trigger fires often; conditions decide whether this particular one qualifies. Match on tags, fields, source, the agent who owns it, or the time of day.
Several actions run in order from one trigger. Reply, tag, assign, open a deal, move a stage, create a task, add to a segment, send an email, notify Slack, call your own webhook.
Every rule carries a frequency limit, and the defaults are deliberately conservative. This is the setting that stops an automation from messaging one person twenty times.
Test the rule against a real recent conversation. It reports exactly what it would have done, and does none of it.
Every firing is logged with the trigger, the conditions that matched and each action’s result. “Why did my customer get this?” has a written answer.
The rules that matter most are the boring ones: tag it, log it, tell someone.
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.
Automations → New automationName it after what it does — “price enquiry → tag, deal, notify” reads better in a list of twenty than “Rule 4”.
Automation → WhenA keyword, a first message, a tag being applied, a deal changing stage, an ad lead arriving, or a delay after any of those.
Automation → IfNarrow it with all-of and any-of groups on tags, fields and message content, so the night rule and the day rule can differ.
Automation → ThenAdd them in the order they should run — reply, tag, open a deal, assign, notify. Each one records its own result.
Automation → FrequencyOnce per conversation, once per contact, or a daily ceiling. This is the setting that stops a rule messaging one person twenty times — do not skip it.
Automation → Dry runTest against a real recent conversation. It reports which conditions matched and what it would have done, and does none of it.
The short version
A keyword, a first message, a tag, a deal moving stage, a deal won.
Reply, tag, assign, open a deal, move a stage, notify Slack — several at once, in order.
Once per conversation, once per person, or a daily ceiling — so a rule can never message someone twenty times.
A dry run checks the rule against a real conversation and tells you what it would do, without doing it.
Every firing is logged with what it did and why, so “why did my customer get this?” has an answer.
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
People message “price” and wait.
→The rule replies with the list, tags the chat, opens a deal and tells the sales channel — in under a second.
Weekend enquiries were being lost.
→Out-of-hours messages get an acknowledgement, a tag and a Monday-morning task on the right person.
Customers reorder every few weeks but need reminding.
→A rule fires 30 days after a deal is won, sends a utility template and opens a fresh deal if they reply.
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.
On its own
₹299/month
What is metered
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.
No. Every rule has a frequency guard, and the defaults are conservative on purpose.
It fails quietly and is recorded. A broken automation never blocks a customer’s message from arriving.
They run in order and each records what it did, so a conflict is visible in the log rather than mysterious. Rules cannot trigger each other in a loop.
Yes — dry run it against a real recent conversation. It tells you what it would have done and does none of it.
Through webhook actions and the developer API, yes. Anything we do not do natively, you can hand to your own endpoint.
Works well with
A no-code flow builder that handles the routine, qualifies the lead, and hands over to a human the moment someone asks for one.
From ₹399/moPipelines, stages, tasks and history — with leads created from WhatsApp conversations instead of typed in again afterwards.
From ₹399/moStop 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/moConnect a number, import your contacts, and see whether it fits how you work.