Conversation agent
Agent Studio, skills, knowledge, router, inbox handoff.
A widget that cannot continue on WhatsApp is not the desk
A website bot that cannot continue on WhatsApp, voice, and email is not an omnichannel desk, and it must still refuse diagnosis. CoPulse web chat and optional web voice live on the site widget; WhatsApp continues the same contact after they share a number. Web Push is a separate Setup channel. Emergencies go to emergency services.
- Continue on WhatsApp
- Refuse diagnosis
- Push is not this overlay
A footer bot that diagnoses a rash
Hospital sites install a widget trained on symptoms. That is the failure mode. CoPulse qualifier stores reason and service_need, matches catalogs, hands off photos. If the widget cannot continue on WhatsApp, T-24h reminders never happen. SMS is not the live fallback.
Jobs, then hops
Web is capture. WhatsApp is session. Voice confirms. Email is prep. There is no compare×WhatsApp nested URL.
- Widget Chat / optional web voice.
- Qualify Four fields. No diagnosis.
- Number share Same contact on Gupshup.
- Book and remind Calendars, templates, optional AMD.
How CoPulse runs it
Web channel + same Studio agent as WhatsApp. Phone overlay is Plivo, not the widget.
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.
Pediatrics page to Thursday 6:30
FAQ bot answers hours and dies. CoPulse offers two slots, continues on WhatsApp, reminds. Push was never this job.
Stay on a chatbot if the site only needs an hours FAQ and you will never message off-site. Move when slots and reminders matter. Must still refuse diagnosis either way.
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 website chatbot / FAQ widget 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 Chatbot widget.
Vs-grid (category, not a smear)
CoPulse cells match the product. Typical website chatbot / FAQ widget cells describe how that category is usually sold. Check the vendor for current modules. We never invent their pricing.
| Capability | CoPulse | Typical website chatbot / FAQ widget |
|---|---|---|
| Omnichannel inbox | One patient inbox: WhatsApp, email, web chat, Instagram, Messenger, and voice on the same contact. | Widget transcripts, often siloed from WhatsApp. |
| WhatsApp templates + 24h window | In-session free-text via the conversation agent. Outside 24 hours, approved library templates on Gupshup. | Usually a click-out link, not the same contact session. |
| Voice AI | Plivo voice AI with AMD and dialer modes on campaigns. Phone replied is speech-to-text, not attend-intent. | Rare. Web voice on CoPulse is click-to-talk on the same widget, not a BPO. |
| Pipeline / deals | Default healthcare columns: New enquiry, Appointment booked, Consult done, Treatment plan, Recurring patient. | Leads emailed to a mailbox. Not five stages. |
| Appointments / calendars | Slot truth lives on Appointments. Autonomous success is sends/reads, not appointment booked. | A booking iframe maybe — verify. Not necessarily Appointment booked as we define it. |
| Qualifier | Patient Inquiry Qualifier: reason, service, location, times. Non-diagnostic. Emergencies: call emergency services. | FAQ NLP. High diagnosis risk if trained on symptoms. |
| Campaigns / drips | Growth campaigns with wallet preview. Conversion is reply rate unless Appointment booked is tracked on the pipeline. | Usually none after the tab closes. |
| Conversation agents | Agent Studio, skills, knowledge catalogs (Departments, Doctors, Beds, Services), router, inbox handoff. | The widget is the agent. No router by department unless they added it. |
| Workflows | Agents → Workflows on stage change: agent.run, route.agent, crm.set_custom_properties. Not adaptive nurture. | Bot flows, not CRM stage-enter. |
| Autonomous outbound | List/objective sends after plan approve. Success is sends, reads, or contacted — not appointment booked. | Unlikely. CoPulse autonomous is list outbound, not the widget. |
| Pricing | Organization wallet only. No seat fees. We do not invent competitor prices. | Widget MAU or seats. We do not quote. CoPulse: wallet for agent turns; voice minutes follow phone. |
| HIS / EMR / listing apps | Engagement only. We do not replace hospital information systems, EMR, billing, pharmacy, or listing marketplaces. | Not HIS. A booking iframe is still not EMR. |
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 website chatbot?
If you only need on-site FAQs (hours, location) and will never continue on WhatsApp or voice, a widget can be enough — still block diagnosis. Move when the job is a booked slot on one contact.
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
Where the thread should continue.
Open →Clinic software
Listing widgets vs engagement widget.
Open →Web on CoPulse
Widget, web voice, not Web Push.
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