Specialty match reads Departments and Doctors catalogs; it never invents a diagnosis or a treatment from the chat. After qualifier fields exist, offer a named doctor and then a calendar slot. Photos are handoff.
Specialty match is mapping the enquiry to a department and named doctor from knowledge catalogs, then handing to appointment-booking — never producing a clinical plan from the thread.
Dental and ENT chats invite invented treatments. This job only reads catalogs. hc-lead-followup “suggests doctors and slots” is fine as inspiration if “detects symptoms” is deleted.
After qualification, on WhatsApp lists, before calendars.
Conversation agent + knowledge. Router by department for hospitals. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. WhatsApp live catalog is Gupshup. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a personal doctor phone that vanishes when the receptionist leaves.
Patient Inquiry Qualifier (reason, service_need, location, preferred_times). Catalogs: Departments, Doctors, Beds, Services — not a chart. Emergency utterances: call emergency services. Inbox handoff. Knowledge scoped per campus so you do not offer the wrong building.
Agents → Workflows on stage change: agent.run, route.agent, crm.set_custom_properties, crm.update_stage, crm.create_task, templated send.whatsapp/email. Not adaptive nurture.
Clock-based sequences and list blasts with wallet preview. Campaign conversion is reply rate unless you also track Appointment booked on the pipeline.
Keep a dental bot off a health-check reply. Route by stage, channel, or campaign.
One Organization, one Project. Healthcare pipeline labels. Wallet-only. Library kits are sketches — rewrite hops without SMS and without a diagnostic triage agent.
Setup → Channels (WhatsApp/Gupshup, Web, Meta, Email/SES, Phone/Plivo as needed) → Library templates → Agents → Studio (Patient Inquiry Qualifier, catalogs, appointment skill, emergency guardrail, handoff) → Router → Setup → Customers → Pipeline (five default columns) → Appointments/calendars → Agents → Workflows (stage changed: agent.run, route.agent, crm.set_custom_properties) → Growth with Organization wallet preview. Connect SMS (MSG91) under Setup → Channels when you want that hop.
They ask for her. Catalog says Friday. Appointment skill lists 4:00. They send a photo; handoff. Treatment plan column waits for a human consult.
Beds catalog answers class questions in hospitals; it is not occupancy HIS.
Operators assemble this job on the Project. Click-path remains Setup → Channels (WhatsApp/Gupshup, Web, Meta, Email/SES, Phone/Plivo as needed) → Library templates → Agents → Studio (Patient Inquiry Qualifier, catalogs, appointment skill, emergency guardrail, handoff) → Router → Setup → Customers → Pipeline (five default columns) → Appointments/calendars → Agents → Workflows (stage changed: agent.run, route.agent, crm.set_custom_properties) → Growth with Organization wallet preview. Connect SMS (MSG91) under Setup → Channels when you want that hop. Keep the quotable definition in the brief for the team: Specialty match is mapping the enquiry to a department and named doctor from knowledge catalogs, then handing to appointment-booking — never producing a clinical plan from the thread. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, New enquiry, WhatsApp overlay, Dental & specialty, Agent Studio, Growth campaigns, and wallet-only pricing in the same runbook. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Human handoff stays in the omnichannel inbox. Appointments and calendars are the slot truth when this job books time. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them under Agents → Workflows. The agent router keeps the wrong bot off this thread. Knowledge bases hold Departments, Doctors, Beds, and Services catalogs — not a clinical chart. Preview the Organization wallet before a blast. Do not claim HIS or EMR replacement. The Specialty match playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on library kits are estimates, not an SLA. Autonomous success is sends, reads, or contacted — not appointment booked. If this job mentions money, the Organization wallet is the meter. That is the honest operating manual for this URL.
Match hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | Catalog match | Named doctor or department | |
| 2 | Lists | Pick clinician | Choice stored |
| 3 | Calendars | Sibling booking job | Slot |
| 4 | Inbox | Photo / “what’s wrong” | Human |
Catalogs vs diagnosis.
No. Match a doctor. Hand off.
Departments, Doctors, Beds, Services — not a chart.
WhatsApp session or template; SMS when MSG91 is connected.
Scope knowledge per Project or router.
Not until calendars plus the booking playbook.
knowledge-base-doctors-services.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
One URL per omnichannel job.
Directory →Fields first.
Open →Slot after match.
Open →Named-doctor match is the daily job.
ICP →Match happens before booked.
Stage →Lists for department/doctor pick.
Channel overlay →How-to companion. This playbook stays the job URL.
Guide →Agent Studio, skills, knowledge, router, workflows.
Explore agents →Library templates, audiences, wallet preview.
Explore campaigns →Sends and minutes debit the Organization wallet. Creating a CRM row does not.
See pricing →Load Doctors and Services, then book from calendars.
Get started free