Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
Portal CRM follows the portal — not the buyer’s next hop
Portal CRMs follow that portal's lead; CoPulse continues the same buyer on WhatsApp, voice, email, and web. MagicBricks- or 99acres-style desks are the source of many enquiries. They are not the omnichannel inbox after the buyer messages a project WhatsApp or comments on Instagram. Portal-lead-followup is the job: import or paste, then 48-hour qualify and Visit Caller on one Booking. We do not tell you to switch the portal off.
- Portal stays the source
- CoPulse is the after-layer
- Dedupe across portals
Speed-to-lead dies in the portal’s email SLA
Portals optimise for their marketplace. Your buyer is already on WhatsApp. If the only CRM is the portal’s, Instagram comments, web widget visitors, and CP WhatsApp never join the graph. Duplicate-leads exists because the same number hits three portals. CoPulse CSV import is v1. There is no invented “we replaced 99acres CRM” claim. There is an omnichannel continuation claim.
Jobs, then hops
Portal dump → WhatsApp (Gupshup) → voice → email if NRI. Web widget is another source, same Booking after merge. There is no compare×WhatsApp nested URL.
- Export / import Honest: operators still land the row.
- Dedupe Search phone. Merge. Keep one RM.
- Qualify now Not tomorrow’s portal email.
- Visit path site-visit-booking playbook.
How CoPulse runs it
Inbox + pipeline after import. Workflows on New enquiry. Campaigns for launches to your list, not the portal’s. Autonomous should not dual-send CRM and marketplace allocations — that suppression gap is documented; keep audiences clean.
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.
Import → Customers search → Channels WhatsApp/Phone → Studio → pipeline → Library → wallet.
Housing at 9:40 p.m., visit Sunday
Portal CRM: email at 11 a.m. CoPulse: template or session qualifier tonight, Sunday 10, Visit Caller. Click-path: import, inbox, appointments. Brokers ICP lives here.
Stay on portal CRM alone if 100% of enquiries never leave that portal and you accept email SLAs. The moment you run a project WhatsApp or a booth QR, you need a Project inbox. Usage on the Organization wallet, no seats.
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 Portal-native CRM (listing portals) 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 Portal CRM.
Vs-grid (category, not a smear)
CoPulse cells match the product. Portal-native CRM (listing portals) cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Portal-native CRM (listing portals) |
|---|---|---|
| Omnichannel inbox | One buyer inbox: WhatsApp, email, web chat, Instagram, Messenger (including post comments when Meta is connected), and voice on the same contact. | Portal messages and their UI. Not Meta comments + web chat + voice on one timeline. |
| 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 exist as a partner feature — check the portal. CoPulse WhatsApp is Gupshup on your Project. |
| 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. | Unlikely as Visit Caller with Agent Studio greetings. |
| Pipeline / deals | Bookings on a Project pipeline you name under Setup → Customers → Pipeline. Buyers & Tenants, not a generic lead dump. | Portal lead statuses. Not your loan and construction columns. |
| 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. | Portal notifications. Not Growth wallet-previewed launches to your matched list. |
| Conversation agents | Agent Studio: skills, knowledge bases, training. RE Qualifier / Visit Scheduler patterns. Agent router by stage or channel. | Portal chat widgets maybe. Not your knowledge-trained qualifier. |
| Workflows | Agents → Workflows fire on pipeline stage change and can start an agent or set CRM custom properties. | Portal automations, if any. Not stage-enter on your Bookings. |
| 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. | Not CoPulse list tasks. Do not mix unrevealed marketplace rows with CRM blindly. |
| 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. | Portal meeting tools vary. CoPulse stores the appointment 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. | Portal packages and lead packs — we do not quote them. CoPulse: no seat fees, wallet for your sends. |
| Knowledge / RAG | Project knowledge bases (brochures, floor plans, EMI sheets you uploaded). Stale files are an operator problem. No generated floor-plan art. | Listing copy on the portal. Not Tower B PDF in Agent Studio. |
| Human handoff | Omnichannel inbox handoff with full thread. Router can silence the qualifier at negotiation. RM inherits fields and visit history. | Portal assignment. RM still lacks WhatsApp + visit context unless you export. |
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 portal CRM only?
If every lead is exclusive to one portal and you never run owned WhatsApp, web, or CP intake, their CRM may be enough. Add CoPulse when the buyer continues off-portal.
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 →Excel + WhatsApp
The export destination.
Open →LeadSquared-class CRM
When you already think in stages.
Open →Omnichannel inbox
After the portal ping.
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