Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
A WhatsApp inbox is not a site-visit pipeline
A WhatsApp inbox is not a buyer pipeline with agents, drips, and site-visit stages. Shared-inbox tools are built to assign chats. CoPulse keeps Buyers & Tenants and Bookings on the Project: RE Qualifier in Agent Studio, library templates when the 24-hour window closes (Gupshup), Visit Caller on voice, Growth drips, workflows on stage enter, wallet-only pricing. Judge this page on jobs — qualification, visit booking, launch — not on whether someone can see a green tick.
- Inbox plus Bookings
- Voice confirm hop
- Wallet, not seats
Green ticks without a Saturday hold
Property teams buy a shared WhatsApp inbox because the pain is “messages in personal phones.” Six months later the pain is Saturday no-shows, portal duplicates, and launch lists that ignore the 24-hour window. An inbox product can be excellent at SLA and assignment. It is still not Agent Studio, knowledge PDFs, appointment skill, Plivo Visit Caller, or a Bookings kanban you configure under Setup → Customers → Pipeline. Do not treat this comparison as a claim that inbox tools “cannot do WhatsApp.” They are WhatsApp. CoPulse is WhatsApp plus the rest of the buyer journey on one contact.
Jobs, then hops
If you only needed a queue, a shared inbox category can be enough. Site-visit ops needs web/portal capture → WhatsApp qualify → voice confirm → email for long files. There is no compare×WhatsApp nested URL.
- Capture Portal or web still creates the enquiry. Inbox-only stacks often leave that in Excel.
- Qualify RE Qualifier writes BHK, budget, locality, timeline on the Booking.
- Book Appointment skill. T-24h library template if the session closed.
- Confirm Visit Caller. Phone replied is STT, not “they will show.”
How CoPulse runs it
Conversation agent in the omnichannel inbox. Growth drips for reminders and launches. Workflows on Site visit booked. Autonomous list send is optional for win-back and does not stop when a visit is booked. No Meta Cloud WhatsApp hop — catalog is Gupshup.
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 → Channels (WhatsApp/Gupshup, Phone/Plivo) → Library templates → Agents → Studio + Router + Workflows → Customers pipeline → Growth with wallet preview.
Same 3BHK ping, two outcomes
Inbox-only: Rahul replies from a shared queue, promises Saturday, nothing on a calendar, no T-24h utility template, no voice hop. CoPulse: Setup → Channels already live; qualifier writes fields; Visit Scheduler holds Saturday 11; Friday template; Visit Caller. Click-path is the playbook, not a nested /compare/whatsapp-crm/whatsapp URL.
When to stay on a shared inbox: a tiny desk that only answers inbound WhatsApp and books visits in a paper diary on purpose. When you run launches or Saturday inventory, you need pipeline plus voice. See wallet-only pricing — no seat fee to add an RM to the same thread.
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 Typical shared WhatsApp inbox 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 WhatsApp inbox.
Vs-grid (category, not a smear)
CoPulse cells match the product. Typical shared WhatsApp inbox cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Typical shared WhatsApp inbox |
|---|---|---|
| Omnichannel inbox | One buyer inbox: WhatsApp, email, web chat, Instagram, Messenger (including post comments when Meta is connected), and voice on the same contact. | Category: team WhatsApp inbox and assignment. Other channels, if any, are usually add-ons — confirm on their site. |
| 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. | Core product is WhatsApp chat. Template and 24h behavior depends on their BSP; we do not invent their rules. |
| 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. | Not the usual core. Calling is typically a separate product or a human with a mobile. |
| Pipeline / deals | Bookings on a Project pipeline you name under Setup → Customers → Pipeline. Buyers & Tenants, not a generic lead dump. | Often a thin contact list, not Bookings stages you configure for site visit → token → loan. |
| 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. | Broadcasts are common in this category. Clock-based visit drips tied to a calendar hold are not the default story. |
| Conversation agents | Agent Studio: skills, knowledge bases, training. RE Qualifier / Visit Scheduler patterns. Agent router by stage or channel. | Chatbots or canned replies are common. Agent Studio, skills, and project knowledge bases are CoPulse’s model. |
| Workflows | Agents → Workflows fire on pipeline stage change and can start an agent or set CRM custom properties. | Assignment rules, not necessarily CRM stage-enter agents. |
| 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 campaigns, treat success as whatever they publish. CoPulse autonomous success is sends/reads, not booked visits. |
| 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. | Usually not a first-class calendar 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. | Many inbox tools sell per-seat or per-inbox plans. We do not quote their prices. CoPulse has no seat fees. |
| Knowledge / RAG | Project knowledge bases (brochures, floor plans, EMI sheets you uploaded). Stale files are an operator problem. No generated floor-plan art. | Macros and help articles maybe. Not project floor-plan knowledge on the qualifier. |
| Human handoff | Omnichannel inbox handoff with full thread. Router can silence the qualifier at negotiation. RM inherits fields and visit history. | Assign to a teammate in the queue. Not RM inheritance of visit + EMI context on a Booking. |
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 shared WhatsApp inbox?
If you only need a team queue for inbound WhatsApp, no launches, no voice confirms, and no Bookings kanban, a shared inbox category can be enough. Move when Saturday slots, portal duplicates, or launch templates become the job.
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 →vs Wati-class WhatsApp tooling
Broadcasts vs visit pipeline.
Open →Excel + WhatsApp
The other common starting stack.
Open →Omnichannel inbox
WhatsApp plus the rest of the timeline.
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