Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
You already have stages — add WhatsApp, voice, and wallet sends
This page is for teams that already think in CRM stages but need WhatsApp templates, voice confirmation, and wallet sends in the same product. LeadSquared is widely known in India as a sales CRM and lead-management suite, especially in education and real estate. We will not inventory their WhatsApp or telephony add-ons or invent a price. CoPulse is wallet-only, Gupshup WhatsApp, Plivo voice, Growth drips, Agent Studio, and Bookings on one Project. Compare jobs: qualification, site-visit booking, property launch.
- Stages you already understand
- Messaging + voice in-product
- No seat fees
A mature CRM with a bolted inbox is still two products
Ops already lives in funnels. The gap is operational WhatsApp (24h vs template on Gupshup), Visit Caller, and campaign wallet preview without a per-user line item. Seat-based CRMs in this category typically charge for users — check their current list. CoPulse Unlimited is $0 platform: unlimited projects, agents, channels; usage from the Organization wallet (messaging 1.10×, voice/LLM 1.30×). Autonomous tasks here still do not stop on appointment booked.
Jobs, then hops
Keep thinking in stages. Hops: WhatsApp qualify, voice confirm, email launch digest, Meta as capture. There is no compare×WhatsApp nested URL.
- Map stages Setup → Customers → Pipeline to names your desk already uses.
- Connect hops Gupshup, Plivo, SES — not a side app if you can avoid it.
- Jobs lead-qualification, site-visit-booking, property-launch.
- Wallet Preview before the launch list.
How CoPulse runs it
If you migrate, conversation agents replace the “who texts” gap. Workflows on stage enter replace some CRM automations. Growth replaces a separate broadcast tool. We do not claim a one-click LeadSquared importer.
Growth drips / campaigns
Clock-based. Wallet preview. Not adaptive nurture.
Workflows
Agents → Workflows on pipeline stage change.
Autonomous outbound
Optional lists. Success is sends/reads — not visit booked.
Operator setup
Organization wallet. Project channels. Real Estate labels: Buyers & Tenants, Bookings.
Pipeline names → Channels → Studio → Workflows → Library → Growth wallet preview.
Launch Friday without a second WhatsApp vendor tab
CRM-suite way: export segment, paste into a BSP, hope stages update. CoPulse: matched segment in Growth, approved template, wallet preview, Reply Triage in the same inbox, Visit Caller if they book. Click-path: Growth, Library, inbox, appointments.
Stay on a LeadSquared-class CRM if your reporting, LSAs, and compliance already live there and WhatsApp is a thin channel you accept as a bolt-on. Switch or dual-run when site-visit ops and wallet messaging should be native. Never treat this page as their feature matrix — ask them.
Read this page as a jobs brief, not a lawsuit. The CoPulse column is the product you can click: Setup → Channels, Library templates, Agent Studio, agent router, Agents → Workflows, autonomous list tasks (sends and reads, not appointment booked), Growth campaigns/drips, pipeline stages, appointments/calendars, omnichannel inbox, human handoff, Organization wallet. The Sales CRM / lead-management suites (LeadSquared class) column is category positioning. If that vendor shipped a new WhatsApp or voice module this quarter, believe their docs over our “typical” cell. We still will not invent their price. Operators implementing after a bake-off should run lead qualification, site-visit booking, and property launch on a Project — those URLs are the jobs, not nested channel clones. Adaptive nurture is not shipped. WhatsApp live catalog is Gupshup. Phone “replied” is STT. Campaign conversion is reply rate. Marketplace vs CRM suppression is a known gap — do not mix those audiences casually. Property managers should not copy token stages onto leasing. That is the honest footer for LeadSquared-class CRM.
Vs-grid (category, not a smear)
CoPulse cells match the product. Sales CRM / lead-management suites (LeadSquared class) cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Sales CRM / lead-management suites (LeadSquared class) |
|---|---|---|
| Omnichannel inbox | One buyer inbox: WhatsApp, email, web chat, Instagram, Messenger (including post comments when Meta is connected), and voice on the same contact. | CRM activity plus whatever messaging module they sell today. Confirm whether WhatsApp, email, and voice share one thread. |
| WhatsApp templates + 24h window | In-session free-text via the conversation agent. Outside 24 hours, approved library templates on Gupshup. Operators pick templates; planners do not auto-provision session plus closed-window pairs. | Often an integration or add-on in this category — not something we will checklist. CoPulse: Gupshup templates + 24h. |
| Voice AI | Plivo voice AI. Visit Caller confirms site visits. Phone “replied” means speech-to-text after the script — not purchase intent. Greeting trained in Agent Studio. | Click-to-call or a telephony partner is common in CRMs. CoPulse ships Visit Caller-style voice AI on Plivo. |
| Pipeline / deals | Bookings on a Project pipeline you name under Setup → Customers → Pipeline. Buyers & Tenants, not a generic lead dump. | Strength of the category: funnels, scores, users. CoPulse: Bookings you configure, vertical labels Buyers & Tenants. |
| Drips / campaigns | Growth campaigns and drips with wallet preview. Clock-based. Not adaptive nurture. Campaign conversion is still reply rate, not Interested as a first-class state. | Marketing automation is a typical CRM-suite pillar. CoPulse drips are clock-based, not adaptive, conversion = reply rate. |
| Conversation agents | Agent Studio: skills, knowledge bases, training. RE Qualifier / Visit Scheduler patterns. Agent router by stage or channel. | Task owners and maybe bots. CoPulse: Agent Studio skills and knowledge. |
| Workflows | Agents → Workflows fire on pipeline stage change and can start an agent or set CRM custom properties. | CRM automations. CoPulse: Agents → Workflows including stage change and custom properties. |
| Autonomous outbound | List or objective sends after plan approve. Operator picks an existing library template. Success is sends, reads, or contacted — not site visit booked. WhatsApp, email, phone only. | If they offer AI outbound, read their success definition. Ours is sends/reads/contacted. |
| Appointments / calendars | Appointment skill and public calendars on the contact. Stage should match the hold. Autonomous tasks do not stop when a slot is booked. | Meetings objects vary. CoPulse appointment skill writes the hold on the contact. |
| Wallet vs seats | No monthly seat fees. CoPulse Unlimited: unlimited projects, agents, and channels. Organization wallet: messaging 1.10×; voice AI and LLM 1.30×; campaign cost preview before send. | Typically seats and editions. We do not invent numbers. CoPulse: no seat fees, wallet usage. |
| Knowledge / RAG | Project knowledge bases (brochures, floor plans, EMI sheets you uploaded). Stale files are an operator problem. No generated floor-plan art. | Content libraries maybe. CoPulse: project PDFs on the conversation agent. |
| Human handoff | Omnichannel inbox handoff with full thread. Router can silence the qualifier at negotiation. RM inherits fields and visit history. | Owner change in CRM. CoPulse: inbox thread + router off the qualifier at negotiation. |
Playbooks to run, not a dump
Bake-offs fail when they stay on checkmarks. Run these three jobs on a Project.
Frequently asked questions
Including when to stay where you are.
When should we stay on a LeadSquared-class CRM?
Stay if that suite is already your system of record for reporting and users, and you are willing to keep WhatsApp/voice as modules. Look at CoPulse when messaging, voice confirms, and wallet preview should sit on the same Booking as the stage.
Do you list their prices?
No. Seat and conversation packs change. CoPulse publishes wallet markups on pricing: no monthly seats; messaging 1.10×; voice AI and LLM 1.30×; campaign preview before send.
Is this a complete feature matrix?
No. Named vendors ship add-ons. Our CoPulse column is the repo. Their column is category-typical. Ask them for a current demo.
Will autonomous tasks stop when a visit is booked?
No. Success is sends, reads, or contacted. Use appointment skill, drips, and Visit Caller for the visit job.
WhatsApp provider?
Live catalog is Gupshup. Do not plan an invented Meta Cloud WhatsApp hop. /channels/instagram redirects to Meta (IG/Messenger).
Can we dual-run?
Yes. Keep a CRM of record if reporting lives there. CoPulse is the omnichannel execution Project. CSV import is v1. We do not invent a native sync.
Related
Parent compare hub, sibling bake-offs, product, pricing.
Compare hub
All real-estate bake-off pages.
Directory →HubSpot-class CRM
Generic CRM vs Indian visit ops.
Open →Sell.do-class property CRM
Vertical CRM category.
Open →Pipeline & CRM
Stages plus the hops.
Explore →Real estate hub
ICPs, channels, pipeline, playbooks.
Hub →Wallet-only pricing
No seat fees. Usage from the Organization wallet.
Pricing →Bake off on a live Project, not a slide
Connect WhatsApp and voice, run qualification and a Saturday slot, preview the wallet on a small launch list.
Get started free