Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
Spreadsheets cannot book Saturday or brief an RM
Broadcast lists in a spreadsheet cannot qualify, book visits, or hand off an RM with context. The stack is familiar: CSV from 99acres, mail merge vibes, personal WhatsApp, a calling sheet. CoPulse is the Project after the lead arrives — omnichannel inbox, Bookings stages, Agent Studio, library templates, Visit Caller, Growth wallet preview. This is not a slight on Excel; it is a job comparison for Indian property desks that have outgrown the file.
- One Booking per buyer
- No personal-phone SLA
- Wallet preview before blasts
The file is never the same file
Channel partners send Excel. Portals send Excel. The intern copies into WhatsApp Business. Two RMs call the same number. Launch day, someone pastes 8,000 cells into a broadcast tool with no wallet preview and no 24-hour plan. Duplicate-leads and portal-lead-followup exist because this stack fails in public. CoPulse still imports CSV v1 — we do not pretend portals vanish. After import, qualification and visits are product jobs, not another tab.
Jobs, then hops
Excel is a source, not a hop. Real hops: WhatsApp qualify, voice confirm, email for NRI packs. There is no compare×WhatsApp nested URL.
- Land the row Import or inbox. Search phone before a twin Booking.
- Qualify Four fields on the deal, not a comment column.
- Slot Calendar, not a highlighted cell.
- Handoff RM gets the thread, not a forwarded screenshot.
How CoPulse runs it
Conversation agent after import. Workflows on New enquiry. Drips for T-24h. Autonomous win-back only on a CRM list you approve — sends/reads, not token paid. Do not keep a parallel SMS column in the sheet as if CoPulse sent it.
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.
Customers import → Setup → Channels → Studio qualifier → pipeline → Library → Growth wallet preview → inbox.
Friday 8 p.m. Housing dump
Excel way: intern splits the file in WhatsApp groups. CoPulse: import, workflow starts qualifier templates (window closed → library). Four buyers book Sunday. Visit Caller Friday. Click-path: Customers, Agents → Workflows, appointments.
Stay on Excel if you have ten names a week and one broker who is the CRM. The moment you have CP lists and Saturday vans, the sheet is the incident. Pricing is usage on the Organization wallet, not a seat for the intern.
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 Spreadsheet + personal WhatsApp 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 Excel + WhatsApp.
Vs-grid (category, not a smear)
CoPulse cells match the product. Spreadsheet + personal WhatsApp cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Spreadsheet + personal WhatsApp |
|---|---|---|
| Omnichannel inbox | One buyer inbox: WhatsApp, email, web chat, Instagram, Messenger (including post comments when Meta is connected), and voice on the same contact. | Personal or device WhatsApp. History leaves when the broker does. |
| 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. | Broadcasts from a phone or a BSP paste. 24h window is easy to miss from a sheet. |
| 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 sheet. Humans dial. No Visit Caller greeting in Agent Studio. |
| Pipeline / deals | Bookings on a Project pipeline you name under Setup → Customers → Pipeline. Buyers & Tenants, not a generic lead dump. | Columns you invented. No stage-enter workflow. |
| 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. | Reminder columns and hope. Not Growth drips on a calendar hold. |
| Conversation agents | Agent Studio: skills, knowledge bases, training. RE Qualifier / Visit Scheduler patterns. Agent router by stage or channel. | None. People type. |
| Workflows | Agents → Workflows fire on pipeline stage change and can start an agent or set CRM custom properties. | Macros maybe. Not Agents → Workflows on 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. | Mail-merge energy. CoPulse autonomous still needs an approved template and counts 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. | A date cell. Not an 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. | Excel is “free” until the van and the duplicate RM time. CoPulse: no seats, wallet for sends. |
| Knowledge / RAG | Project knowledge bases (brochures, floor plans, EMI sheets you uploaded). Stale files are an operator problem. No generated floor-plan art. | A Drive folder of PDFs. Not retrieved in chat from a knowledge base. |
| Human handoff | Omnichannel inbox handoff with full thread. Router can silence the qualifier at negotiation. RM inherits fields and visit history. | Forwarded chat export. Context dies. |
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 Excel plus WhatsApp?
A solo agent with a handful of buyers and no launches can live in a sheet. Stay there until duplicates, CP status, or Saturday no-shows cost more than connecting channels on a Project.
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 →WhatsApp inbox vs pipeline
Next step after the sheet.
Open →Portal CRM only
When the portal is the other silo.
Open →Pipeline & CRM
Bookings instead of rows.
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