Decide what happens after every call
A workflow starts when something happens: a new contact, a call ending, a call missed, a customer replying. Then its steps run on their own. Send a message, wait, ring again, update your CRM, or take a different path by outcome.
On every plan- A call ends
- Wait, then message
- Test run first
Follow-up depends on someone remembering
A good call, then silence
The customer asked for a brochure. Nobody sent it.
A missed call stays missed
Somebody should ring back. On a busy day nobody does.
A new lead waits
A form comes in at night and sits until someone looks at the list.
Building one
Pick a start
Start from a template, or choose a trigger such as Call ends, Call missed, New lead, Lead scored or WhatsApp reply.
Join the steps
Send, wait, branch, call, update. A step joined to several steps runs all of them.
Rehearse
Test workflow is a rehearsal: nothing is sent, nobody is called and no contact is changed.
Switch it on
Only an active workflow runs, from the moment you switch it on. It does not act on what came before.
A workflow on the canvas
One trigger and the steps joined after it. The issues count lists what is missing before it can switch on.
- Your edits are not live until you press Save.
- A run fails when any step did not do its job, and the row says so.
- A disabled step is skipped, and a disabled condition takes its Yes path.
Test workflow is a rehearsal. Nothing is sent and nobody is called.
What you can do
Triggers
Calls, leads, bookings, promises to pay, hand-overs, identity checks, lead scores, QA flags and replies.
Branches and waits
Take a path by outcome. A Wait pauses only the steps after it.
Sends during a call
An agent offers what the trigger names, the caller agrees, and the workflow sends it.
Quiet hours
Messages to customers wait out 9 pm to 9 am, unless you turn that off on the Compliance page.
Run history
See which step failed and why, with waiting time shown apart from running time.
Who it helps
Sales managers
Every warm call followed up the same way, without chasing anyone.
Collections teams
Reminders and retries tied to what was promised.
Operations
A record of what ran, what failed and why.
Which plan has it, and what it costs
| Plan | Starter₹999 a month | Growth₹2,999 a month | Professional₹7,999 a month | Enterprise₹28,000 a month |
|---|---|---|---|---|
| Workflows, up to your plan's count | Included | Included | Included | Included |
| WhatsApp steps | Not included | Included | Included | Included |
| SMS steps | Not included | Included | Included | Included |
| Email steps | Not included | Not included | Included | Included |
| Calendar steps | Not included | Not included | Not included | Included |
| CRM steps | Not included | Included | Included | Included |
What it costs
- A workflow run has no price of its own.
- ₹3.5 to ₹8.5 a minute, by plan. A Call contact step places a real call, billed by the minute like any call, from this rate by voice.
- Messages go out on your own connected account, so your provider bills you for them.
Free trial: Included, with up to 3 workflows.
See every plan and rateWatch out for this
A Call contact step places a real, billed call to a real person, and a send step messages real customers. Deleting a workflow drops every run part-way through a wait, so those follow-ups never go out.
What stays your job
Approved WhatsApp templates and the consent to message someone stay with you. Plain WhatsApp text does not reach a customer who has not written to you in the last 24 hours.
It works with these
Workflows: questions
Does a workflow act on old calls?
What happens if a channel is disconnected?
Can I test without messaging anyone?
What if I move to a smaller plan?
Stop relying on someone remembering.
Start from a template and rehearse it before it goes live.