Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
Launch replies should become visits — on the same contact
WhatsApp campaign products vs CoPulse where launch replies become qualified visits on the same contact. Interakt is widely known for WhatsApp marketing and commerce-style campaigns. That category is built to send and retarget. CoPulse property-launch and property-campaigns are omnichannel (WhatsApp plus email, Meta as capture), then lead-qualification and site-visit-booking on the Booking. We will not fake their commerce or flow features or their price list.
- Reply is a Booking
- Email is a launch hop
- Voice after the slot
Retargeting is not a site-visit hold
Campaign products optimise send, read, tap. Property desks need a calendar event and a van. GrowthLoop’s demo funnel (Reached → Replied → Qualified → Site visits booked → Bookings) is campaign analytics — still not autonomous stop-on-booked. If Interakt-class tools now include CRM, check them. Our table speaks to the campaign-product category: excellent at WhatsApp sends; visit ops is CoPulse’s job set. No defamation. No invented pricing.
Jobs, then hops
Campaign send (WhatsApp+email) → reply on WhatsApp → qualify → voice confirm. There is no compare×WhatsApp nested URL.
- Segment CRM fields, not only last-tap.
- Wallet preview Then send.
- Triage Conversation agent, not a retarget wait.
- Visit site-visit-booking.
How CoPulse runs it
Growth campaigns + Reply Triage agent + workflows. Autonomous launch follow-up optional, sends/reads. Planner does not auto-build 24h template pairs.
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.
Library launch templates → Growth audience → wallet preview → Studio Reply Triage → pipeline → Phone Visit Caller.
412 WhatsApp teasers, 2,800 email digest, visits on the same graph
Library launch playbook split. Campaign-product way: retarget the taps next week. CoPulse: taps become Qualified Bookings this week if four fields exist. Click-path: Growth, inbox, calendars.
Stay on an Interakt-class campaign product if WhatsApp marketing is the mandate and sales owns visits in another system you like. Move when the reply must be a Booking with voice confirm. Wallet-only on our side.
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 WhatsApp campaign / commerce products (Interakt 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 Interakt-class campaigns.
Vs-grid (category, not a smear)
CoPulse cells match the product. WhatsApp campaign / commerce products (Interakt class) cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | WhatsApp campaign / commerce products (Interakt 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. | Campaign reply inboxes are common. Full email+voice+Meta comments on one contact varies — ask them. |
| 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. | Category core: campaigns, flows, templates. CoPulse: Gupshup library + 24h agent. |
| 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. | Uncommon as Visit Caller. CoPulse: yes, with STT honesty. |
| Pipeline / deals | Bookings on a Project pipeline you name under Setup → Customers → Pipeline. Buyers & Tenants, not a generic lead dump. | Tags and commerce states maybe. Not necessarily 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. | Category strength. CoPulse drips are not adaptive; no smart send-time. |
| Conversation agents | Agent Studio: skills, knowledge bases, training. RE Qualifier / Visit Scheduler patterns. Agent router by stage or channel. | Chatbots in the flow. CoPulse: Agent Studio + router. |
| Workflows | Agents → Workflows fire on pipeline stage change and can start an agent or set CRM custom properties. | Flow builders. CoPulse: CRM stage-enter. |
| 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. | Scheduled campaigns. CoPulse autonomous: approve plan, pick template, count 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. | Usually a button URL. CoPulse: appointment skill. |
| 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. | Conversation or marketing plans — we do not quote Interakt. CoPulse: 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. | Catalog/FAQ in flows. CoPulse: project knowledge PDFs. |
| Human handoff | Omnichannel inbox handoff with full thread. Router can silence the qualifier at negotiation. RM inherits fields and visit history. | Agent assign in the campaign inbox. CoPulse: RM context from the 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 an Interakt-class campaign product?
Stay if WhatsApp campaigns are the whole motion and a separate CRM already books visits well. Choose CoPulse when launch replies must qualify and confirm on the same contact, including voice.
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 →Wati-class WhatsApp
Inbox/broadcast category.
Open →Shared inbox
Queue without campaigns.
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