Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
Voice AI for confirms — RMs still own the price
Voice AI covers confirmation and no-show hops; humans still own negotiation, with the thread in one inbox. A calling team is the right category when every lead must hear a human first. CoPulse is the right category when WhatsApp already qualified BHK and budget, and you need Visit Caller plus T-24h templates without hiring a night shift for “are you coming tomorrow.” We do not claim to replace a full BPO. We do claim Plivo voice, Agent Studio greetings, and STT “replied” is not intent.
- Visit Caller hop
- RM for token
- Same inbox as WhatsApp
Burning agent-hours on “are you coming at 11”
Calling teams are good at stubborn phones and regulated scripts. They are expensive on T-24h confirms and no-show callbacks that a trained voice agent can attempt. They are also disconnected from WhatsApp history unless someone pastes it. CoPulse: omnichannel inbox, appointment on the contact, Visit Caller, then rm-handoff when they ask for a discount. Autonomous outbound can place list calls after approve — success is still contacted/sends, not “visit booked.”
Jobs, then hops
WhatsApp qualify first (usual). Voice confirm. Humans on token. Email for files. There is no compare×WhatsApp nested URL.
- Qualify on chat Do not spend a minute of BPO time asking BHK if WhatsApp already has it.
- Hold the slot Calendar + pickup note.
- Voice confirm Visit Caller. Train the greeting.
- Escalate No-show recovery or RM inbox — not a second CRM.
How CoPulse runs it
Voice AI is a hop inside site-visit-booking and no-show-recovery. Conversation agent stays on WhatsApp. Workflows enqueue the call on stage enter. Drips cover the template if they do not pick up. SMS is not live as a confirm channel.
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 Phone (Plivo) + WhatsApp → Studio Visit Caller greeting → Workflows on Site visit booked → Library T-24h → wallet for minutes.
40 Saturday holds, two callers vs Visit Caller plus two RMs
Calling-team way: 40 connects for confirms, then the same people try to negotiate. CoPulse: 40 Visit Caller attempts, inbox shows who spoke, RMs only take pricing threads. Click-path: Agents → Studio, appointments, inbox. Phone replied ≠ they will arrive — ops still watches the gate.
Stay with a calling team when your ICP will not use WhatsApp, or when every conversation is a regulated pitch you will not put on an LLM. Hybrid is common: BPO for raw portal, CoPulse for confirmed visits. Minutes debit the Organization wallet; there is no seat fee for the RM who takes handoff. See pricing.
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 Calling team / BPO desk 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 Calling team.
Vs-grid (category, not a smear)
CoPulse cells match the product. Calling team / BPO desk cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Calling team / BPO desk |
|---|---|---|
| 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 a dialer disposition, not WhatsApp + email + voice on one contact. |
| 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. | Often absent or a personal phone beside the headset. |
| 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. | Human agents. Quality varies. Not Agent Studio voice AI. |
| Pipeline / deals | Bookings on a Project pipeline you name under Setup → Customers → Pipeline. Buyers & Tenants, not a generic lead dump. | Dispositions in the dialer. May not be Bookings stages. |
| 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. | Callback lists. Not Growth template drips. |
| Conversation agents | Agent Studio: skills, knowledge bases, training. RE Qualifier / Visit Scheduler patterns. Agent router by stage or channel. | People. Scripts on paper or the dialer. |
| Workflows | Agents → Workflows fire on pipeline stage change and can start an agent or set CRM custom properties. | Campaign cadences in the dialer, not CRM stage-enter on CoPulse. |
| 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. | Predictive dialers exist in that category. CoPulse autonomous voice still counts contacted/sends, 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. | If the CRM is separate, the dialer may not own the calendar. |
| 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. | BPO is typically per-agent-hour or per-connect. We do not quote vendors. CoPulse: wallet for AI minutes, 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. | Script packs. Not project knowledge retrieved in chat. |
| Human handoff | Omnichannel inbox handoff with full thread. Router can silence the qualifier at negotiation. RM inherits fields and visit history. | Warm transfer if they are well run. Still may miss WhatsApp history. |
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 keep the calling team as-is?
Keep humans on first-touch if buyers will not chat, or if legal/compliance forbids AI voice. Add CoPulse when confirms and no-shows are eating agent-hours that should be RM time.
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 →FAQ chatbot vs agents
The other “AI” dead end.
Open →WhatsApp inbox
Chat-only cousin.
Open →AI agents
Voice greeting, skills, handoff.
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