Choose on inbox, calendars, non-diagnostic agents, and wallet — not a widget or HIS
Choose on omnichannel inbox, calendars, non-diagnostic agents, and wallet-only pricing — not a chatbot widget and not an HIS. These pages are bake-offs for clinic and hospital desks: shared WhatsApp inboxes, Excel plus chat, calling teams, clinic-management and listing apps, WhatsApp API tools, LeadSquared-class CRMs, and website chatbots. CoPulse cells match the product you can click. Other cells describe the category. We never invent their pricing. There are no playbook×channel nested URLs.
- 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 vs-grid whose CoPulse column is clickable product (inbox, 24-hour WhatsApp templates on Gupshup, Plivo voice with AMD, five healthcare stages, calendars, non-diagnostic qualifier, Growth drips, Agent Studio, workflows, autonomous sends/reads, wallet-only, not HIS). Then ignore the grid and run three playbooks on a Project: patient qualification, appointment booking, no-show recovery. If those jobs work, the bake-off is over. If you only needed a queue, a listing page, or an HIS, the FAQ on that leaf says when to stay. CoPulse is engagement: conversation, calendar nudge, and pipeline — not hospital information system, EMR, billing, or pharmacy.
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 unless Appointment booked is tracked on the pipeline. Phone replied is speech-to-text, not attendance. Email warmup is daily caps, not engagement-ordered. CSV import is v1. Adaptive nurture is not shipped. WhatsApp is Gupshup. The Patient Inquiry Qualifier does not diagnose; emergencies go to emergency services. Knowledge holds Departments, Doctors, Beds, and Services — not a clinical chart. Library kits that still print SMS or “detects symptoms” are sketches. Operators still pick library templates. That honesty is why the CoPulse column is long — it is not a row of green ticks. Wallet-only pricing: no seats; messaging and voice markups are on pricing. Dual-run is allowed: keep HIS or a reporting CRM if that is the chart of record.
- Pick the category page WhatsApp inbox, Excel+WA, call center, clinic software / listing apps, WhatsApp API tools, LeadSquared-class CRM, or chatbot widget.
- Read “when to stay” Every FAQ includes a stay path. Dual-run with HIS is expected.
- Run the three jobs Non-diagnostic qualification, calendar slot, no-show recovery on the same contact.
- 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 patient pipeline |
| Excel + WhatsApp | Typical Excel plus personal WhatsApp | A sheet cannot qualify, book, and recover on one timeline |
| Call center | Typical clinic / hospital calling team | Calls without the WhatsApp thread are a second silo |
| Clinic software | Typical listing / clinic-management / HIS-lite app | Engagement beside HIS — we do not replace the chart |
| WhatsApp API tools | Typical WhatsApp API / BSP inbox (Wati-class, Interakt-class) | A BSP inbox is not voice, SES, and a healthcare board |
| LeadSquared-class CRM | Typical sales CRM with WhatsApp add-on (LeadSquared-class) | A sales CRM add-on is not a wallet-metered omnichannel Project |
| Chatbot widget | Typical website chatbot / FAQ widget | A widget that cannot continue on WhatsApp is not the desk |
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 patient inbox: WhatsApp, email, web chat, Instagram, Messenger, and voice on the same contact. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms 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. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Voice AI | Plivo voice AI with AMD and dialer modes on campaigns. Phone replied is speech-to-text, not attend-intent. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Pipeline / deals | Default healthcare columns: New enquiry, Appointment booked, Consult done, Treatment plan, Recurring patient. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Appointments / calendars | Slot truth lives on Appointments. Autonomous success is sends/reads, not appointment booked. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Qualifier | Patient Inquiry Qualifier: reason, service, location, times. Non-diagnostic. Emergencies: call emergency services. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Campaigns / drips | Growth campaigns with wallet preview. Conversion is reply rate unless Appointment booked is tracked on the pipeline. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Conversation agents | Agent Studio, skills, knowledge catalogs (Departments, Doctors, Beds, Services), router, inbox handoff. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Workflows | Agents → Workflows on stage change: agent.run, route.agent, crm.set_custom_properties. Not adaptive nurture. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Autonomous outbound | List/objective sends after plan approve. Success is sends, reads, or contacted — not appointment booked. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| Pricing | Organization wallet only. No seat fees. We do not invent competitor prices. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
| HIS / EMR / listing apps | Engagement only. We do not replace hospital information systems, EMR, billing, pharmacy, or listing marketplaces. | Usually strong on chat and broadcasts; voice AMD, five-stage healthcare board, and wallet-only messaging are not the default pitch — verify the vendor. We do not invent their price. | Usually strong on stages, users, and reporting; clinic WhatsApp 24h plus Plivo confirms may be connectors — verify the vendor. Seats are typical; we do not quote prices. |
A worked bake-off week (not a smear)
Monday: connect Gupshup WhatsApp and the web widget on a Project; load Departments/Doctors/Services — not a chart. Tuesday: run patient qualification on ten real enquiries; emergencies redirect to emergency services; photos of rashes go to inbox, not a diagnosis. Wednesday: appointment-booking writes Appointments/calendars, then the Appointment booked column via a human or workflow — not because an autonomous task reported reads. Thursday: reminder templates plus optional voice with AMD; phone replied is STT. Friday: two no-shows stay off Consult done and get a later slot. If a shared inbox, Excel sheet, BPO, listing app, BSP, seat CRM, or website widget cannot complete that week without a side spreadsheet, that is the bake-off. If it can, stay. Dual-run with clinic software is normal: they keep listing/HIS; CoPulse keeps the conversation. We will not invent their seat price or claim they lack a module they shipped this quarter. There is no /compare/whatsapp-inbox/whatsapp nested URL.
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/healthcare/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 calendar slot, and a no-show recover
Connect Gupshup and Plivo, run the three playbooks, watch the Organization wallet — then decide. Keep HIS if you have one.
Get started free