Choose on inbox, templates, voice, pipeline, and wallet — not a widget
Choose on omnichannel inbox, templates, voice, pipeline, and wallet-only pricing, not a chatbot widget. These pages are bake-offs for Indian property desks: shared WhatsApp inboxes, Excel plus chat, calling teams, portal CRMs, FAQ bots, and CRM or WhatsApp-tool categories (LeadSquared-class, Sell.do-class, Wati-class, Interakt-class, HubSpot-class). CoPulse cells match the product. Named-vendor cells describe the category. We never invent their pricing or defame a module they may have shipped. There are no /guides clones of these keywords.
- Jobs, not checkmarks
- No invented competitor prices
- When to stay on X
How to use this directory
Open the leaf that matches the stack you already have. Each leaf has a 12-row vs-grid: omnichannel inbox, WhatsApp templates and the 24-hour window, voice AI, pipeline, drips, conversation agents, workflows, autonomous outbound, appointments, wallet vs seats, knowledge, handoff. Then ignore the grid and run three playbooks on a Project: lead qualification, site-visit booking, property launch. If those jobs work, the bake-off is over. If you only needed a queue, the FAQ on that leaf says when to stay.
What CoPulse will always admit
Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate. Phone replied is speech-to-text. Email warmup is not engagement-ordered. CSV import is v1. Adaptive nurture is specified, not shipped. SMS is MSG91 under Setup → Channels. WhatsApp is Gupshup, not an invented Meta Cloud path. Marketplace leads and CRM lists are not auto-suppressed against each other. Operators still pick library templates. That honesty is why the CoPulse column is long — it is not a row of green ticks.
- Pick the category page Inbox, Excel, BPO, portal, chatbot, or a named-class CRM/WhatsApp tool.
- Read “when to stay” Every FAQ includes a stay path. Dual-run is allowed.
- Run the three jobs Qualification, Saturday slot, launch teaser with wallet preview.
- Check the wallet No seat fees. Organization wallet. Preview before send. See /pricing/.
Directory
One canonical compare URL per stack. No guide duplicates of these keywords.
Map of bake-offs
Use this table to pick a leaf. The leaf vs-grid is the 12-row capability comparison.
| Page | Category we describe | Unique angle |
|---|---|---|
| WhatsApp inbox | Typical shared WhatsApp inbox | A WhatsApp inbox is not a site-visit pipeline |
| Excel + WhatsApp | Spreadsheet + personal WhatsApp | Spreadsheets cannot book Saturday or brief an RM |
| Calling team | Calling team / BPO desk | Voice AI for confirms — RMs still own the price |
| Portal CRM | Portal-native CRM (listing portals) | Portal CRM follows the portal — not the buyer’s next hop |
| FAQ chatbots | Website FAQ chatbot widget | Price FAQs are not qualification, slots, or CRM writes |
| LeadSquared-class CRM | Sales CRM / lead-management suites (LeadSquared class) | You already have stages — add WhatsApp, voice, and wallet sends |
| Sell.do-class property CRM | Indian property CRM suites (Sell.do class) | Property CRM vs agents, campaigns, and wallet sends |
| Wati-class WhatsApp tooling | WhatsApp Business API inboxes / broadcasts (Wati class) | WhatsApp tooling vs voice, pipeline, and RM handoff |
| Interakt-class campaigns | WhatsApp campaign / commerce products (Interakt class) | Launch replies should become visits — on the same contact |
| HubSpot-class CRM | General CRM / marketing hubs (HubSpot class) | Generic CRM vs Indian WhatsApp and Saturday slots |
CoPulse vs two common categories
Index-level snapshot. Leaves go deeper without inventing vendor checkmarks.
| Capability | CoPulse | Typical WhatsApp inbox / BSP tool | Typical seat CRM / hub |
|---|---|---|---|
| Omnichannel inbox | One buyer inbox: WhatsApp, email, web chat, Instagram, Messenger (including post comments when Meta is connected), and voice on the same contact. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| 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. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| 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. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Pipeline / deals | Bookings on a Project pipeline you name under Setup → Customers → Pipeline. Buyers & Tenants, not a generic lead dump. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| 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. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Conversation agents | Agent Studio: skills, knowledge bases, training. RE Qualifier / Visit Scheduler patterns. Agent router by stage or channel. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Workflows | Agents → Workflows fire on pipeline stage change and can start an agent or set CRM custom properties. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| 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. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| 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 strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| 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 strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Knowledge / RAG | Project knowledge bases (brochures, floor plans, EMI sheets you uploaded). Stale files are an operator problem. No generated floor-plan art. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Human handoff | Omnichannel inbox handoff with full thread. Router can silence the qualifier at negotiation. RM inherits fields and visit history. | Usually strong on chat and broadcasts; voice, Bookings, and wallet-only messaging are not the default pitch — verify the vendor. | Usually strong on stages, users, and reporting; Indian WhatsApp 24h plus Visit Caller may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
Frequently asked questions
Directory questions before a named-vendor leaf.
When should we stay on our current stack?
Each leaf FAQ answers “when to stay on X.” Short version: stay if that category already is the job (queue-only, portal-only, company-standard hub) and you accept the missing hops.
Why not one page vs every product?
We will not fake checkmarks. Named pages describe a class. Ask the vendor for a demo of modules we marked as “varies.”
Where is the WhatsApp-only playbook?
There is none. Jobs are omnichannel. Channel overlays live under /industries/realestate/channels/.
Seat fees?
CoPulse has none. Unlimited projects, agents, channels on the platform. Usage from the Organization wallet. Details on pricing.
Guides with the same keywords?
No. Compare URLs are canonical for these bake-offs. Guides teach how (24h window, agents vs workflows).
SMS in the matrix?
Coming soon. Do not plan it as live in a bake-off script.
Related
Hub, jobs, product, pricing.
Bake off on qualification, a Saturday slot, and a launch preview
Connect Gupshup and Plivo, run the three playbooks, watch the Organization wallet — then decide.
Get started free