AutomationsAutomation

When this happens, do that — across the whole platform

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.

Cross-module
inbox, CRM, campaigns, email
Guardrails
so a rule cannot spam anyone
Full log
of every run and its reason

What you need to start

  • A connected WhatsApp number for inbox triggers
  • The CRM module if you want deal triggers and actions

The problem

The follow-up everyone agreed to do, that nobody remembers to do.

  • The process exists in someone’s head and stops working the week they are away.
  • Steps that take ten seconds each add up to most of an afternoon.
  • Nobody can say afterwards why a particular customer got a particular message.

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 → Automation.

app · Dashboard / Automations

Automations

New automation
WHEN

Message contains “price”

Trigger · incoming WhatsApp message

IF

Contact is not tagged “Customer”

Condition · all of 1 must match

Then
Send template “bulk_rates”
Tag the chat “Hot lead”
Open a deal in Sales pipeline
Assign round-robin to available agent
Notify #sales on Slack
GuardrailOnce per conversationDaily ceiling 200 Dry run
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

    Pick the trigger

    1 minute

    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.

    • Inbox triggers — keyword, first message, chat assigned, chat resolved
    • CRM triggers — deal created, stage changed, deal won, deal lost, task overdue
    • Marketing triggers — campaign replied, ad lead received, email link clicked
    • Time triggers — a delay after any of the above
  2. 02

    Narrow it with conditions

    2 minutes

    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.

    • All-of and any-of groups, so “wholesale enquiry outside hours” is one rule
    • Conditions on contact fields, deal fields, tags and message content
    • Business-hours awareness, so the night rule and the day rule can differ
  3. 03

    Chain the actions

    5 minutes

    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.

    • Reply with a template or a saved quick reply
    • Tag the chat, set a contact field, add to a segment
    • Open a CRM deal, move its stage, assign an owner, create a task with a due date
    • Notify Slack or hit your own webhook, for anything we do not do ourselves
  4. 04

    Put the guardrails on

    the important minute

    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.

    • Once per conversation, once per contact, or a ceiling per day
    • Quiet hours, so nothing auto-sends at 3am
    • Rules never re-trigger themselves — one automation cannot feed another in a loop
  5. 05

    Dry run it before you trust it

    2 minutes

    Test the rule against a real recent conversation. It reports exactly what it would have done, and does none of it.

    • Shows which conditions matched and which did not
    • Lists the actions in the order they would have run
    • Nothing is sent, tagged or created during a dry run
  6. 06

    Publish it, then audit it

    ongoing

    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.

    • Run history per rule, with success and failure per action
    • A failed action is recorded and never blocks the customer’s message from arriving
    • Pause a rule instantly without deleting it or losing its history

The rules that matter most are the boring ones: tag it, log it, tell someone.

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 10 minutes per rule
Before you start
A connected number; the CRM module for deal triggers
Start free
  1. 1

    Create the rule

    Automations → New automation

    Name it after what it does — “price enquiry → tag, deal, notify” reads better in a list of twenty than “Rule 4”.

  2. 2

    Pick the trigger

    Automation → When

    A keyword, a first message, a tag being applied, a deal changing stage, an ad lead arriving, or a delay after any of those.

  3. 3

    Add conditions

    Automation → If

    Narrow it with all-of and any-of groups on tags, fields and message content, so the night rule and the day rule can differ.

  4. 4

    Chain the actions

    Automation → Then

    Add them in the order they should run — reply, tag, open a deal, assign, notify. Each one records its own result.

  5. 5

    Set the guardrail

    Automation → Frequency

    Once 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.

  6. 6

    Dry run, then activate

    Automation → Dry run

    Test against a real recent conversation. It reports which conditions matched and what it would have done, and does none of it.

The short version

What it does about it

01

Triggers from anywhere

A keyword, a first message, a tag, a deal moving stage, a deal won.

02

Actions everywhere

Reply, tag, assign, open a deal, move a stage, notify Slack — several at once, in order.

03

Guardrails built in

Once per conversation, once per person, or a daily ceiling — so a rule can never message someone twenty times.

04

Test before you trust it

A dry run checks the rule against a real conversation and tells you what it would do, without doing it.

05

A record of every run

Every firing is logged with what it did and why, so “why did my customer get this?” has an answer.

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.

Triggers

  • Keyword in an incoming message
  • First message from a new contact
  • Tag applied or removed
  • Deal created, stage changed, won or lost
  • Campaign reply, ad lead, email click
  • A delay after any other trigger

Conditions

  • Contact and deal fields
  • Tags, with all-of and any-of groups
  • Message content matching
  • Inside or outside business hours
  • Assigned agent or pipeline

Actions

  • Send a template or quick reply
  • Tag, untag, set a field, add to a segment
  • Assign or reassign the conversation
  • Open a deal, move a stage, create a task
  • Send an email, notify Slack, call a webhook

Safety

  • Frequency caps per conversation, per contact and per day
  • Quiet hours
  • No self-triggering loops
  • Dry run against a real conversation
  • Full run log with per-action results

In practice

Three businesses, three ways

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.

A team with a Monday problem

Weekend enquiries were being lost.

Out-of-hours messages get an acknowledgement, a tag and a Monday-morning task on the right person.

A shop with repeat orders

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

The specifics

Limits and facts

Rules per workspace
Metered per plan
Runs per month
Metered per plan, counted live
Actions per rule
Several, executed in order
Logging
Every run, with per-action results

What you need first

  • A connected WhatsApp number for inbox triggers
  • The CRM module if you want deal triggers and actions

What is metered

  • Automation rulesUnlimited
  • Automation runs a monthUnlimited

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

Automations

₹299/month

What is metered

  • Automation rulesUnlimited
  • Automation runs a monthUnlimited
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

Can it message people at random?

No. Every rule has a frequency guard, and the defaults are conservative on purpose.

What if a rule breaks?

It fails quietly and is recorded. A broken automation never blocks a customer’s message from arriving.

Can two rules fight each other?

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.

Can I try one safely?

Yes — dry run it against a real recent conversation. It tells you what it would have done and does none of it.

Does it work with my own systems?

Through webhook actions and the developer API, yes. Anything we do not do natively, you can hand to your own endpoint.

Try it before you pay anything

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