Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
A BSP inbox is not voice, SES, and a healthcare board
A WhatsApp API inbox is not voice AMD, SES warmup, or a five-stage healthcare board with a non-diagnostic qualifier. Wati-class and Interakt-class tools are strong at WhatsApp. CoPulse is Gupshup WhatsApp plus Plivo, SES, calendars, and wallet-only on one Project. We will not invent their 2026 modules or prices.
- WhatsApp plus the other hops
- Qualifier not a symptom bot
- Wallet vs conversation packs
Buying a BSP and expecting OPD ops
Templates and broadcasts are real. Missing hops are voice AMD, email warmup, Appointment booked vs calendars, and a qualifier that must not diagnose. Library kits that print SMS still need MSG91 connected on CoPulse.
Jobs, then hops
WhatsApp is one hop. Capture, qualify, book, remind, recover still need the rest. There is no compare×WhatsApp nested URL.
- Keep their WhatsApp if you must Dual-run is allowed; CoPulse catalog is Gupshup.
- Add hops Phone, email, web, pipeline.
- Run jobs Qualification, booking, no-show.
- Do not nest URLs No /playbooks/x/whatsapp.
How CoPulse runs it
Product WhatsApp page is Gupshup coexistence, lists, Flows, PRODUCT/CATALOG. Healthcare overlay is the job.
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.
Broadcast without a slot
API tool: 1,000 delivered. CoPulse: same template possible, plus replies hit the qualifier and calendars. Campaign conversion remains reply rate unless booked is tracked.
Stay on a BSP if WhatsApp-only is a written constraint and you will never call or email. Move when no-shows and programs need voice and a board.
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 WhatsApp API / BSP inbox (Wati-class, 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 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 API tools.
Vs-grid (category, not a smear)
CoPulse cells match the product. Typical WhatsApp API / BSP inbox (Wati-class, Interakt-class) cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Typical WhatsApp API / BSP inbox (Wati-class, Interakt-class) |
|---|---|---|
| Omnichannel inbox | One patient inbox: WhatsApp, email, web chat, Instagram, Messenger, and voice on the same contact. | WhatsApp-centric inbox. Email/voice vary — ask them. |
| WhatsApp templates + 24h window | In-session free-text via the conversation agent. Outside 24 hours, approved library templates on Gupshup. | Usually the core: API, templates, broadcasts. 24h rules follow Meta/BSP — verify. CoPulse uses Gupshup. |
| Voice AI | Plivo voice AI with AMD and dialer modes on campaigns. Phone replied is speech-to-text, not attend-intent. | Not typical core. May be a click-to-call. AMD dialer campaigns are CoPulse phone. |
| Pipeline / deals | Default healthcare columns: New enquiry, Appointment booked, Consult done, Treatment plan, Recurring patient. | Labels or tags, not necessarily five healthcare stages. |
| Appointments / calendars | Slot truth lives on Appointments. Autonomous success is sends/reads, not appointment booked. | Varies. Do not assume Appointments-as-slot-truth. |
| Qualifier | Patient Inquiry Qualifier: reason, service, location, times. Non-diagnostic. Emergencies: call emergency services. | Chatbots common; “symptom detection” is a risk. CoPulse refuses diagnosis. |
| Campaigns / drips | Growth campaigns with wallet preview. Conversion is reply rate unless Appointment booked is tracked on the pipeline. | Broadcast sequences. Wallet preview is CoPulse Growth. |
| Conversation agents | Agent Studio, skills, knowledge catalogs (Departments, Doctors, Beds, Services), router, inbox handoff. | Bot builders. Not Agent Studio + catalogs + router by default — verify. |
| Workflows | Agents → Workflows on stage change: agent.run, route.agent, crm.set_custom_properties. Not adaptive nurture. | Chat automations. Stage-enter CRM graphs vary. |
| Autonomous outbound | List/objective sends after plan approve. Success is sends, reads, or contacted — not appointment booked. | Campaigns they name. CoPulse autonomous success is sends/reads. |
| Pricing | Organization wallet only. No seat fees. We do not invent competitor prices. | Conversation packs and seats are common. We do not quote. CoPulse: no seats, wallet markups on /pricing/. |
| HIS / EMR / listing apps | Engagement only. We do not replace hospital information systems, EMR, billing, pharmacy, or listing marketplaces. | Not HIS. Neither are we. |
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 WhatsApp API tool?
If you are WhatsApp-only by policy and already compliant on templates, a BSP inbox can be enough. Move when voice, email, calendars, and a five-stage board are 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 →WhatsApp inbox
Queue-only cousins.
Open →Chatbot
Widget without WhatsApp continuation.
Open →WhatsApp on CoPulse
Gupshup, lists, Flows, PRODUCT/CATALOG.
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