The Patient Inquiry Qualifier asks reason, service, location, and times — it does not diagnose, and emergencies are sent to emergency services. Library hc-lead-followup names a Patient Triage that “detects symptoms & speciality”; CoPulse marketing and this job refuse that. Specialty match reads catalogs after these fields exist.
Patient qualification is writing the four qualifier fields on the contact, matching published catalogs when useful, and handing off anything clinical — never inventing a diagnosis from chat or photos.
Kits and demos love a doctor-bot. Operators then paste protocols into knowledge. This job is intake. service_need is what they asked for (GP, dental consult, health-check package), not what the model inferred. Lists and Flows on WhatsApp can capture the four fields without a 20-message chat. Photos of rashes are inbox handoff, not an exam.
Usually after capture, on WhatsApp or the widget, before a calendar offer.
Conversation agent is the runtime. Do not autonomous-qualify a cold list as if it were inbound. 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. Refuse diagnosis. Handoff on “what’s wrong with me.”
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.
Walk-in QR creates the row. Qualifier stores fever as reason and GP as service_need. Agent offers to match a GP from Doctors — it does not prescribe. If they ask for antibiotics, inbox. hc-lead-followup’s “Triaged 88%” is an estimate, not a clinical SLA.
Independent practitioners are the handoff queue. Hospitals router by department after fields exist.
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: Patient qualification is writing the four qualifier fields on the contact, matching published catalogs when useful, and handing off anything clinical — never inventing a diagnosis from chat or photos. 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, Clinics, 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 Patient qualification 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.
Qualify hops. Slot offer is the next job. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | WhatsApp / web | Four fields | Fields stored |
| 2 | WhatsApp lists/Flows | Structured capture | Same contact |
| 3 | Inbox | Clinical / emergency | Human |
| 4 | Calendars | Not yet unless they insist | Booking playbook |
Non-diagnostic qualifier vs kit “triage.”
No. Hand off. Book a consult from catalog.
No. It is the service they asked for against your Services catalog.
Coming soon. Not live.
No. Fields only. Booking is a sibling playbook plus calendars.
Inspiration only. Do not configure “detects symptoms.”
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
One URL per omnichannel job.
Directory →Create the row first.
Open →Doctors catalog after fields.
Open →Where this qualifier runs all day.
ICP →Intake column.
Stage →Session for qualify and lists/Flows.
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 →Four fields, emergency redirect, catalogs — then book.
Get started free