Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
A sales CRM add-on is not a wallet-metered omnichannel Project
A sales CRM with add-on WhatsApp is not wallet-metered Gupshup plus Plivo plus calendars on one Project inbox — check their docs for this quarter’s modules; we will not invent their price. LeadSquared-class tools are strong at users, stages, and reporting. CoPulse is strong at the care job hops and wallet-only usage. Dual-run: they can remain reporting CRM of record.
- Clickable CoPulse column
- Category, not a smear
- No invented price
Seats, connectors, and a missing confirm hop
Healthcare desks inherit a sales CRM. WhatsApp is a connector. Voice is another SKU. Calendars may be a meeting object that is not Appointment booked as we define it. We describe the category. If they shipped a native BSP this quarter, believe them. CSV import is how names often enter CoPulse. Native sync is not invented here.
Jobs, then hops
Reporting can stay in the CRM. Execution jobs run on CoPulse. There is no compare×WhatsApp nested URL.
- Keep reporting if needed Dual-run.
- Execute hops here Qualify, book, remind, recover.
- Align stages Five healthcare labels, not sales Qualified/Demo unless you rename on purpose.
- Preview wallet No seat tax to add a nurse to the thread.
How CoPulse runs it
Pipeline product + inbox + agents. Autonomous still sends/reads.
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 appointment booked.
Operator setup
Organization wallet. Project channels. Healthcare pipeline labels. Not HIS/EMR.
Setup → Channels (WhatsApp/Gupshup, Phone/Plivo, Email/SES, Web, Meta as needed) → Library templates → Agents → Studio (qualifier, catalogs, appointment skill, emergency guardrail) → Router → Workflows → Customers pipeline (five columns) → Appointments/calendars → Growth with Organization wallet preview.
Lead captured in the CRM, slot lost in WhatsApp
CRM has the lead. Connector sends a template. No AMD confirm, no no-show playbook on the same timeline. CoPulse: enquiry-capture through no-show-recovery on one contact. Conversion: their dashboards vs our reply rate and Appointment booked.
Stay on LeadSquared-class CRM if company reporting must live there and connectors already cover every hop you will ever run. Add CoPulse when WhatsApp+voice+calendars+wallet are the desk.
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, five healthcare pipeline stages, appointments/calendars, omnichannel inbox, human handoff, Organization wallet. The Typical sales CRM with WhatsApp add-on (LeadSquared-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 patient qualification, appointment booking, and no-show recovery 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. CoPulse is not HIS/EMR. The qualifier does not diagnose. That is the honest footer for LeadSquared-class CRM.
Vs-grid (category, not a smear)
CoPulse cells match the product. Typical sales CRM with WhatsApp add-on (LeadSquared-class) cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Typical sales CRM with WhatsApp add-on (LeadSquared-class) |
|---|---|---|
| Omnichannel inbox | One patient inbox: WhatsApp, email, web chat, Instagram, Messenger, and voice on the same contact. | Activity on the lead. True omnichannel patient inbox varies — verify. |
| WhatsApp templates + 24h window | In-session free-text via the conversation agent. Outside 24 hours, approved library templates on Gupshup. | Often a connector or partner. 24h/Gupshup specifics vary. We do not invent them. |
| Voice AI | Plivo voice AI with AMD and dialer modes on campaigns. Phone replied is speech-to-text, not attend-intent. | Click-to-call or a telephony add-on. AMD campaign modes: ask them. |
| Pipeline / deals | Default healthcare columns: New enquiry, Appointment booked, Consult done, Treatment plan, Recurring patient. | Usually a strength: stages, users, reports. Labels may be sales, not healthcare defaults. |
| Appointments / calendars | Slot truth lives on Appointments. Autonomous success is sends/reads, not appointment booked. | Meetings objects vary. Slot truth vs stage: ask them. |
| Qualifier | Patient Inquiry Qualifier: reason, service, location, times. Non-diagnostic. Emergencies: call emergency services. | Forms and lead fields. Not necessarily a non-diagnostic conversation qualifier. |
| Campaigns / drips | Growth campaigns with wallet preview. Conversion is reply rate unless Appointment booked is tracked on the pipeline. | Marketing automation SKUs. Adaptive claims vary. CoPulse drips are not adaptive nurture. |
| Conversation agents | Agent Studio, skills, knowledge catalogs (Departments, Doctors, Beds, Services), router, inbox handoff. | Bots as add-ons. Agent Studio is CoPulse. |
| Workflows | Agents → Workflows on stage change: agent.run, route.agent, crm.set_custom_properties. Not adaptive nurture. | CRM automation. Different graph than Agents → Workflows. |
| Autonomous outbound | List/objective sends after plan approve. Success is sends, reads, or contacted — not appointment booked. | Sequences they name. CoPulse autonomous = sends/reads/contacted. |
| Pricing | Organization wallet only. No seat fees. We do not invent competitor prices. | Seats and packs. We will not invent a number. CoPulse: no seats; see /pricing/. |
| HIS / EMR / listing apps | Engagement only. We do not replace hospital information systems, EMR, billing, pharmacy, or listing marketplaces. | Not HIS. Integrations maybe. CoPulse is not HIS either. |
Playbooks to run, not a dump
Bake-offs fail when they stay on checkmarks. Run these three jobs on a Project.
Patient qualification
Four fields. Non-diagnostic. Emergencies to emergency services.
Open playbook →Appointment booking
Calendars first; Appointment booked follows. Not an autonomous trophy.
Open playbook →No-show recovery
Stay off Consult done. Offer a later slot on the same contact.
Open playbook →Frequently asked questions
Including when to stay where you are.
When should we stay on a LeadSquared-class CRM?
If it is the company system of record and already runs WhatsApp, voice, and calendars to your satisfaction, stay. Bake off CoPulse when execution hops and wallet-only messaging are the gap — dual-run reporting if needed.
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 an appointment is booked?
No. Success is sends, reads, or contacted. Use the appointment skill, drips, and voice confirms for the slot job. Appointment booked is a column plus a calendar fact.
WhatsApp provider?
Live catalog is Gupshup. Connect it under Setup → Channels. Product: WhatsApp.
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 healthcare bake-off pages.
Directory →WhatsApp API tools
BSP-first instead of CRM-first.
Open →Clinic software
HIS-lite / listing vs sales CRM vs engagement.
Open →Pipeline & CRM
Healthcare stages, Appointments, activity.
Explore →Healthcare 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 calendar slot, recover a no-show on the same contact, preview the wallet.
Get started free