Conversation agent
Agent Studio: Patient Inquiry Qualifier, catalogs, appointment skill, emergency guardrail, inbox handoff when confidence drops or the visitor asks for a human.
Booked slots and confirmed consults, not a chatbot pretending to be a doctor
Clinics and hospitals turn WhatsApp enquiries into booked slots, confirmed consults, and follow-up plans, with a non-diagnostic qualifier that never pretends to be a doctor. CoPulse is engagement: Patient Inquiry Qualifier, Departments/Doctors/Beds/Services catalogs, appointments and calendars, omnichannel inbox with human handoff, and wallet-only pricing.
- Non-diagnostic qualifier
- Catalogs and calendars
- Inbox handoff
Why front-desk WhatsApp is not a care desk
Personal doctor phones, Excel recall lists, and missed confirmations leak slots. A generic chatbot that guesses symptoms is worse. CoPulse keeps the qualifier honest: reason, service_need, location, preferred_times — then a human or the appointment skill books time. Emergencies are redirected to emergency services.
Omnichannel journey
Capture from web, ads, and walk-in QR; qualify on WhatsApp; confirm on voice; send prep and report-ready notes on email — one patient timeline in the inbox.
- Capture Website widget, Meta ad leads, and walk-in QR create a New enquiry on the Project. Web Push is a separate Setup channel; web voice is not.
- Qualify on WhatsApp The conversation agent collects reason, service_need, location, and preferred_times against catalogs. Outside 24 hours, send an approved Gupshup template.
- Confirm on phone Voice AI confirms tomorrow’s slot and recovers no-shows with AMD and dialer modes. Replied is speech-to-text, not that they will attend.
- Email for prep and reports Prep instructions, packages, and report-ready pings go on email. They do not replace WhatsApp qualification.
How it runs in CoPulse
Conversation agents for intake, Growth campaigns for programs, workflows on stage change, optional autonomous lists for overdue check-ups. Success on autonomous is sends and reads — not appointment booked.
Campaigns and drips
Library templates on WhatsApp (Gupshup) plus email. Preview Organization wallet cost. Do not treat SMS as live.
Workflows
Agents → Workflows: on Appointment booked, queue the reminder template. On Consult done, start a prep or feedback drip. Not the same runtime as an autonomous task.
Autonomous agents
List or objective outbound after you approve a plan. Measure sends, reads, or contacted. A human or workflow marks Appointment booked when the calendar is true.
Operator setup
One Organization, a Project per hospital, clinic cluster, or program. Pick Healthcare at signup so pipeline labels match the five default columns.
Setup → Channels (WhatsApp via Gupshup, email, phone, web, Meta if you run ads) → Library templates → Agents → Studio (qualifier + catalogs + appointment skill + emergency guardrail) → Agents → Router → Setup → Customers → Pipeline → Appointments/calendars → Growth campaigns with Organization wallet preview.
From enquiry to recurring patient
Monday: a Meta lead and a website chat both land as New enquiry. The qualifier asks service and preferred times against Doctors and Services. Tuesday: the appointment skill offers a calendar slot; the desk confirms in the inbox if the visitor asks for a named doctor not in catalog. Wednesday: T-24h WhatsApp reminder; a quiet thread gets a voice confirm. After consult, a workflow can move Consult done and start a treatment-plan drip. None of this replaces LIS, EMR, or pharmacy. None of it claims the bot diagnosed anything.
Operators should keep catalogs current. A stale doctor list is how you offer a slot with someone on leave. Router by department if cardiology and dental should not share an agent. Wallet-only means the Organization tops up once.
Patient Inquiry Qualifier fields are reason, service_need, location, and preferred_times. The agent does not invent a clinical finding. Knowledge bases hold Departments, Doctors, Beds, and Services catalogs — not a clinical chart. Appointments and calendars are the slot truth; the Appointment booked column is not inferred from a campaign send. The omnichannel inbox keeps WhatsApp, voice, email, and web on one contact so a nurse or desk can take human handoff with the thread. Pricing is wallet-only — no seat fees. Autonomous tasks, when used, count sends, reads, or contacted until a human or workflow moves the pipeline. If a visitor describes an emergency, the agent must tell them to call emergency services immediately; CoPulse is not an emergency line and not an HIS or EMR. Use ICP pages for hospitals, clinics, diagnostics, dental and specialty OPDs, independent practitioners, and health-check programs. Channel overlays, pipeline stages, playbooks, and compare pages sit under the same industry tree. Do not fork a playbook into a WhatsApp-only child URL. For the healthcare hub, keep one Organization and a Project per facility or program cluster. Preview wallet cost before any blast. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on stage change only when you attach them under Agents → Workflows. The agent router keeps a specialty bot off a billing thread. Funnel percentages on library kits are estimates, not an SLA.
Channel sequence for an OPD enquiry
Every hop writes the same contact. There is no separate WhatsApp-only job URL.
| Hop | Channel | What happens | Owner |
|---|---|---|---|
| 1 | Web / Meta / QR | Enquiry created | Capture |
| 2 | Qualifier + catalog match | Conversation agent | |
| 3 | Phone | Confirm or no-show recover | Voice agent |
| 4 | Prep / report-ready | Campaign | |
| 5 | Inbox | Human handoff | Desk / nurse |
Who this is for
Six care-team ICPs. Each page is omnichannel — not a WhatsApp-only clone.
Hospitals
Department routing from a shared inbox; catalogs, not the chart.
Open ICP →Clinics
Walk-ins and missed calls qualified on the Project inbox.
Open ICP →Diagnostics
Sample slots and report-ready pings — not an LIS replacement.
Open ICP →Dental & specialty
Named doctor and slot from catalog; no diagnosis from chat.
Open ICP →Independent practitioners
Qualifier plus calendars on wallet-only pricing.
Open ICP →Health programs
Overdue lists: campaigns or autonomous sends and reads.
Open ICP →Frequently asked questions
What CoPulse is for care desks — and what it is not.
Does the agent diagnose or recommend treatment?
No. The Patient Inquiry Qualifier collects reason, service_need, location, and preferred_times. Knowledge bases hold Departments, Doctors, Beds, and Services. Clinical questions go to human handoff.
What if the visitor has an emergency?
Tell them to call emergency services immediately. CoPulse is not an emergency line.
Is SMS live for reminders?
Connect SMS under Setup → Channels (MSG91). WhatsApp templates (Gupshup), voice, and email remain available hops.
Will an autonomous campaign stop when the appointment is booked?
No. Autonomous success today is sends, reads, or contacted. Slot truth lives on Appointments/calendars and the Appointment booked column.
Does this replace our HIS or EMR?
No. CoPulse is engagement: inbox, agents, campaigns, pipeline, calendars. Billing, pharmacy, and clinical charts stay in your existing systems.
How is WhatsApp connected?
Live WhatsApp in the catalog is Gupshup under Setup → Channels. Library templates are required outside the 24-hour window.
How do we pay?
Wallet-only — no seat fees. Preview blasts on the Organization wallet. Pricing.
Related
Jobs, how-tos, compare, and product surfaces this vertical uses.
Healthcare guides
How-tos: qualifier, 24-hour window, calendars versus pipeline.
Open →Playbooks
One URL per omnichannel job.
Open →AI agents
Studio, skills, knowledge, router, workflows, autonomous.
Open →Inbox
Omnichannel thread and human handoff.
Open →Pipeline
Five healthcare columns on the Project.
Open →Wallet-only pricing
Organization wallet, not per-user seats.
Open →Stand up the patient qualifier
Connect WhatsApp via Gupshup, load catalogs, and offer the first calendar slot from chat.
Get started free