The audience behind every message, in one place
Contacts is its own module, not a tab buried in the messaging tool — because the audience is what every other module reads from. Import a CSV, group people four different ways, and broadcast to any of them without leaving the screen.
What you actually get
Four ways to group people, because they are four different jobs
Most WhatsApp tools give you tags and call it a CRM. A tag cannot express “the 300 people I am inviting to this launch” and a fixed list cannot express “whoever stops repeating.” Both matter, so both exist — alongside your own custom fields and the team that works them.
Each with their own login, so who replied to whom stays on the record.
Search by name or number, filter by tag, select in bulk. Import a CSV straight from another platform — it finds the phone, name and tag columns by header rather than demanding a fixed order. Export any view. Block and opt-out are handled explicitly, and neither can ever be messaged by a campaign.
Applied by you, by a flow, or by the AI. The ones automation writes — cod-confirmed, ndr, needs-human — are marked read-only, because renaming a tag a flow depends on would break it silently and the failure would look like the flow simply stopped working.
You put people in it and it stays put. Send to a list next month and it reaches exactly the people in it today. Right for a one-off — a launch invite, a wholesale price drop, an event.
“COD buyers who never repeated.” Re-answered every time it is read, so whoever qualifies tomorrow is in it tomorrow with nothing to refresh. Right for anything ongoing — winbacks, VIP treatment, a flow's audience.
Appointment date, credit days, GST number, policy expiry. Whatever your business actually tracks. Usable inside a template as {{contact.key}} and as a rule in a segment, so a field you invent on Monday can drive a campaign on Tuesday.
Each person logs in with their own credentials and answers from the same number. Owner, Admin and Member roles decide who can spend money and who can only work the inbox. Open chats per agent are visible on one screen, so you can move work before a customer waits a day.
What each plan includes
Contacts are not charged per head — the number below is a fair-use ceiling, not a meter. What scales with the plan is how many ways you can slice them and how many people can work the inbox.
Starter ₹1,999/mo | Growth ₹3,499/mo | Unlimited ₹18,999/mo | |
|---|---|---|---|
| Team seats | 1 | 3 | 25 |
| Contacts | 25,000 | 1,00,000 | 20,00,000 |
| Tags | 10 | 100 | null |
| Segments | 2 | 10 | null |
| Lists | 10 | 25 | null |
| Custom attributes | 5 | 20 | null |
| Messages / second | 40 | 80 | 1000 |
What stops a campaign going to the wrong people
The expensive mistake in this software is not a missing feature. It is one message reaching an audience nobody intended.
Never everybody. A campaign with no audience selected sends to zero people, which is the only safe direction for that mistake to fail.
The exact number, before the campaign exists — not after you press send.
Segments re-count at send time. If one grew more than 10% since you confirmed it, nothing goes out and it asks you to look again.
It never falls back to a wider audience. Deleting a segment cannot silently turn a targeted campaign into a blast.
From every list, every segment, every campaign. There is no path that ignores them.
An agent sees threads assigned to them plus the unassigned queue — enforced on the page, the API and the URL, not just hidden from the list.
How this differs from a sales CRM, and from a WhatsApp blaster
| Sales CRM | WhatsApp blaster | OpsTower | |
|---|---|---|---|
| Built around | Deals and pipeline | A contact upload | Conversations and orders |
| Knows the order behind a chat | Only if you sync it | No | Yes — from your Shopify store |
| Dynamic segments | Yes | Rarely | Yes, re-counted at send |
| Per-agent logins | Yes | Usually one shared | Yes, with roles |
| Agent sees only their chats | Yes | No | Yes, enforced server-side |
| Who owns the WhatsApp number | n/a | Often the vendor | You — your own Meta WABA |
| Message cost | n/a | Marked up per message | Meta bills you directly, no markup |
It is a conversation and contact CRM. There is no deal pipeline, no stages and no revenue forecasting — if you need those, keep your sales CRM and run this beside it.
See the whole Pulse module →Works with what you already run
Your own Meta WhatsApp Business Account, your Shopify store, and your payment gateway for the order data behind every message.
Pulse is included from ₹1,999/month
One subscription, every module in your tier. WhatsApp message fees are billed to you by Meta directly and are never marked up.
Billed monthly. Switch or cancel any time.
Free trial
Everything, for 14 days
Seeing it work on your own orders before you pay anything.
- Stores
- 1
- Seats
- 1
- Contacts
- Unlimited
- Every module unlocked
- Pulse · Radar · Pilot · Boomerang · Raves
- Echo switched on, free
- Extra seats, free
- Full flow builder + AI
- All 13 ready-made flows
- Your own WhatsApp number
- No card required
Starter
Stop the two biggest leaks
Brands doing 300–1,500 orders a month, mostly COD.
- Stores
- 1
- Seats
- 1
- Contacts
- 25,000
- Your own Meta WhatsApp account
- No markup on Meta’s rates
- Campaigns with audience preview
- Template manager + Meta submission
- 7 templates written for you
- 20-template catalogue
- Shared team inbox
- 24-hour window countdown
- 40 messages / second
- Click-to-WhatsApp ad leads
Growth
Fulfilment on rails
Brands doing 1,500–4,000 orders a month.
- Stores
- 1
- Seats
- 3
- Contacts
- 1,00,000
- Pilot — auto-fulfilment rules
- Dry-run safety on every rule
- Campaign scheduler
- Campaign click tracking
Pro
The whole post-purchase stack
Brands doing 4,000–12,000 orders a month that want one dashboard.
- Stores
- 1
- Seats
- 10
- Contacts
- 5,00,000
- Boomerang — returns portal
- Runs on your own domain
- Raves — photo reviews
- Cross-module automations
Unlimited
Everything, including your own apps
Brands doing 12,000+ orders a month that want the apps and the API.
- Stores
- 1
- Seats
- 25
- Contacts
- 20,00,000
- Pocket — your own iOS + Android apps
- We publish it, then transfer it to you
- Pocket monthly included — the one-time build is quoted separately
- Full REST API
- Webhooks
This is a conversation and contact CRM. It has no sales pipeline, deal stages or revenue forecasting — keep your sales CRM and run this alongside it. Contact volume is a fair-use ceiling per plan; tags, segments, lists and custom attributes are capped by tier.