Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
Property CRM vs agents, campaigns, and wallet sends
Sell.do-style property CRM vs CoPulse as omnichannel agents plus campaigns, compared on jobs not a fake checkmark list. Sell.do is widely known as a real-estate CRM used by Indian developers and channel teams. We will not claim their WhatsApp, calling, or site-visit modules, and we will not invent pricing. CoPulse is the Project layer: inbox, Agent Studio, Gupshup templates, Visit Caller, Growth launches, wallet-only. Developers ICP and channel-partner-leads are the jobs to read next.
- Jobs, not checkmarks
- CP status on templates
- Wallet, not seats
A property-aware CRM can still leave WhatsApp and voice in a side app
Developer desks need inventory fields, CP attribution, and site-visit language. A vertical CRM category is built for that vocabulary. The gap we talk about is operational: 24h vs template, voice confirm, launch wallet preview, RM handoff on the same thread. If Sell.do-class products already do some of that, treat our table’s “other” column as category-typical, not a takedown. Dual-running is allowed: CRM of record vs CoPulse as the omnichannel execution layer — we do not invent a native sync.
Jobs, then hops
CP or portal in → WhatsApp qualify → voice visit → email launch/construction. Stages you name. There is no compare×WhatsApp nested URL.
- Keep property nouns Buyers & Tenants, Bookings, custom properties for partner_id.
- Connect hops Channels on the Project.
- Run jobs qualification, site-visit-booking, property-launch, channel-partner-leads.
- Preview wallet Before a launch list.
How CoPulse runs it
Conversation agents and workflows on stage enter. Growth for teasers. Autonomous only for lists, sends/reads. Gupshup not Meta Cloud WhatsApp.
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.
Setup → Customers pipeline + properties → Channels → Studio → Workflows → Library → Growth.
CP three buyers before noon, status without Friday Excel
Vertical CRM way: three leads, channel manager still XLS. CoPulse: three Bookings, partner tag, visit booked template to the CP, qualifier on the buyer. Click-path: inbox, kanban, workflow log. Playbooks, not a /sell-do/whatsapp child page.
Stay on a Sell.do-class CRM if inventory, CP reports, and developer workflows already fit and channels are good enough. Add CoPulse when the buyer’s WhatsApp and the visit van need the same timeline. No seat fees on our side — pricing. Their editions: 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 Indian property CRM suites (Sell.do 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 Sell.do-class property CRM.
Vs-grid (category, not a smear)
CoPulse cells match the product. Indian property CRM suites (Sell.do class) cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Indian property CRM suites (Sell.do 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 inbox or notes. Whether WhatsApp is native varies — check them. CoPulse: omnichannel by default. |
| 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. | May be integrated. We will not mark yes/no. CoPulse: session vs Gupshup library templates. |
| 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. | Calling features appear in property CRMs; depth varies. CoPulse: voice AI Visit Caller, STT ≠ intent. |
| Pipeline / deals | Bookings on a Project pipeline you name under Setup → Customers → Pipeline. Buyers & Tenants, not a generic lead dump. | Category strength: property pipelines. CoPulse: configurable Bookings including loan and construction if you add them. |
| 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. | Reminders and campaigns may exist. CoPulse: Growth, clock-based, wallet preview, not adaptive. |
| Conversation agents | Agent Studio: skills, knowledge bases, training. RE Qualifier / Visit Scheduler patterns. Agent router by stage or channel. | Users and maybe bots. CoPulse: Agent Studio. |
| Workflows | Agents → Workflows fire on pipeline stage change and can start an agent or set CRM custom properties. | CRM automation. CoPulse: stage-enter agents and 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. | Unknown / vendor-specific. Ours: list send, sends/reads. |
| 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. | Site-visit objects are typical in this category. Confirm calendar depth with them. CoPulse: appointment skill 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. | Usually packaged CRM editions. We do not invent figures. CoPulse: wallet-only, no seats. |
| Knowledge / RAG | Project knowledge bases (brochures, floor plans, EMI sheets you uploaded). Stale files are an operator problem. No generated floor-plan art. | Project data in CRM fields. CoPulse: PDFs in knowledge for in-chat retrieve. |
| Human handoff | Omnichannel inbox handoff with full thread. Router can silence the qualifier at negotiation. RM inherits fields and visit history. | Owner assignment. CoPulse: inbox + router 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 Sell.do-class property CRM?
Stay if that CRM already matches how developers and CPs report, and you are happy with its channels. Consider CoPulse when omnichannel execution, voice confirms, and wallet launches should not live in a side tool.
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 →LeadSquared-class CRM
Horizontal CRM suite.
Open →Portal CRM
Source system, not the after-layer.
Open →Campaigns & drips
Launches with wallet preview.
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