Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
A WhatsApp inbox is not a patient pipeline
A WhatsApp inbox is not a patient pipeline with agents, drips, calendars, and Appointment booked as a stage. Shared-inbox tools assign chats. CoPulse keeps the five healthcare columns, Appointments as slot truth, a non-diagnostic qualifier, Gupshup templates after 24 hours, optional Plivo confirms, and wallet-only pricing. Judge on jobs — qualification, booking, no-show — not green ticks.
- Inbox plus pipeline
- Calendars vs column
- Wallet, not seats
Green ticks without a calendar hold
Clinics buy a shared WhatsApp inbox because the pain is personal phones. Months later the pain is no-shows, duplicate ads, and reminder lists that ignore the 24-hour window. An inbox can be excellent at SLA. It is still not Agent Studio, catalogs, appointment skill, AMD voice, or a kanban under Setup → Customers → Pipeline. This is not a claim that inbox tools “cannot do WhatsApp.” They are WhatsApp. CoPulse is WhatsApp plus the rest of the care job on one contact. SMS is MSG91 on CoPulse when connected — same honesty as WhatsApp (Gupshup).
Jobs, then hops
If you only needed a queue, a shared inbox can be enough. OPD ops needs web/QR/Meta capture → WhatsApp qualify → calendars → voice confirm → email prep. There is no compare×WhatsApp nested URL.
- Capture Widget, QR, ads still create New enquiry. Inbox-only stacks often leave that in Excel.
- Qualify Four fields. Not a diagnosis. Emergencies to emergency services.
- Book Appointments/calendars, then Appointment booked.
- Recover No-show stays off Consult done.
How CoPulse runs it
Conversation agent in the omnichannel inbox. Growth for reminders. Workflows on Appointment booked. Autonomous lists optional for recall — success is sends/reads, not booked.
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.
Same fever ping, two outcomes
Inbox-only: assigned to a receptionist, promised Thursday, nothing on a calendar, no T-24h template, no voice. CoPulse: qualifier writes fields; calendars hold 10:30; Friday template; AMD confirm. Click-path is the playbook, not /compare/whatsapp-inbox/whatsapp.
Stay on a shared inbox if you only answer inbound WhatsApp and book in a paper diary on purpose. When reminders, no-shows, or programs matter, you need pipeline plus calendars. See wallet-only 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, five healthcare pipeline stages, appointments/calendars, omnichannel inbox, human handoff, Organization wallet. The Typical shared WhatsApp inbox 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 WhatsApp inbox.
Vs-grid (category, not a smear)
CoPulse cells match the product. Typical shared WhatsApp inbox cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Typical shared WhatsApp inbox |
|---|---|---|
| Omnichannel inbox | One patient inbox: WhatsApp, email, web chat, Instagram, Messenger, and voice on the same contact. | Category: team WhatsApp inbox and assignment. Other channels are usually add-ons — confirm on their site. |
| WhatsApp templates + 24h window | In-session free-text via the conversation agent. Outside 24 hours, approved library templates on Gupshup. | Core product is WhatsApp chat. Template and 24h rules depend on their BSP; 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. | Not the usual core. Calling is typically a human with a mobile. |
| Pipeline / deals | Default healthcare columns: New enquiry, Appointment booked, Consult done, Treatment plan, Recurring patient. | Often a thin contact list, not five healthcare stages you configure. |
| Appointments / calendars | Slot truth lives on Appointments. Autonomous success is sends/reads, not appointment booked. | Usually not first-class Appointments on the contact. |
| Qualifier | Patient Inquiry Qualifier: reason, service, location, times. Non-diagnostic. Emergencies: call emergency services. | Macros or a bot FAQ. Not a named non-diagnostic Patient Inquiry Qualifier. |
| Campaigns / drips | Growth campaigns with wallet preview. Conversion is reply rate unless Appointment booked is tracked on the pipeline. | Broadcasts are common. Clock-based reminder drips tied to a calendar hold are not the default story. |
| Conversation agents | Agent Studio, skills, knowledge catalogs (Departments, Doctors, Beds, Services), router, inbox handoff. | Chatbots or canned replies. Agent Studio + catalogs is CoPulse’s model. |
| Workflows | Agents → Workflows on stage change: agent.run, route.agent, crm.set_custom_properties. Not adaptive nurture. | Assignment rules, not necessarily CRM stage-enter graphs. |
| Autonomous outbound | List/objective sends after plan approve. Success is sends, reads, or contacted — not appointment booked. | If they offer campaigns, treat success as whatever they publish. CoPulse autonomous success is sends/reads, not booked. |
| Pricing | Organization wallet only. No seat fees. We do not invent competitor prices. | Many inbox tools sell per-seat or per-inbox plans. We do not quote their prices. CoPulse has no seat fees. |
| HIS / EMR / listing apps | Engagement only. We do not replace hospital information systems, EMR, billing, pharmacy, or listing marketplaces. | Not HIS. Neither is CoPulse. Inbox tools also do not replace EMR — do not buy either as a hospital information system. |
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 shared WhatsApp inbox?
If you only need a team queue for inbound WhatsApp, no programs, no voice confirms, and no pipeline, a shared inbox can be enough. Move when slots, no-shows, or templates become the job.
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 →Excel + WhatsApp
When the list is a spreadsheet.
Open →WhatsApp API tools
BSP/inbox products with APIs.
Open →Omnichannel inbox
WhatsApp beside voice and email on one contact.
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